EMA Webinar Transcript:

The Journey to Responsible Cloud Adoption: Building a

Flexible Infrastructure for Tomorrow’s Cloud

Applications

Webinar Date:

7/29/10

Featured Speakers:

Julie Craig

Shaun Connolly, VP of Product Management, SpringSource

Abstract:

Cloud computing is here, and there is no longer any question that cloud offers real

benefits to the enterprise. But what is the actual path to the cloud for enterprise

applications?

Join EMA Research Director Julie Craig and SpringSource VP of Product Management

Shaun Connolly for a discussion on how enterprises can harness the economics of

modern applications and infrastructures without compromising flexibility, control, and

choice. Additionally, you will learn how your organization can adopt a planned approach

to evolve to cloud computing and reap the benefits of each step in the journey. You will

also find out how to:

Build applications for the cloud

Deploy applications on a platform that is ideally suited to virtualization

Virtualize custom applications with their associated data

Manage data in cloud or virtualized environments

Manage performance across physical, virtual, and cloud infrastructure

Introduction:

Raleigh Gould

Welcome and thank you for joining us today for The Journey to Responsible Cloud

Adoption: Building a Flexible infrastructure for Tomorrow’s Cloud Applications. My

name is Raleigh Gould and I will be your moderator for today’s event. Our featured

Page 1 of 16

speakers are Julie Craig, Research Director at Enterprise Management Associates and

Shaun Connolly, VP of Product Management at SpringSource.

Julie Craig has over 20 years of experience in software development and enterprise

systems management. Julie has a Masters degree in Computer Information Systems with

emphasis areas in object oriented technologies and enterprise architecture. At EMA,

Julie’s focus is on configuration management and application performance.

Shaun Connolly has more than 20 years of experience in the software industry with a

track record of building early stage and mid-sized software companies into successful

market leaders. At SpringSource Shaun is responsible for overall product strategy,

definition and promotion of SpringSource products.

Before I hand this over to Julie I do want today’s audience to know that we will be

concluding today’s event with a Q & A session, while Shaun and Julie will defer

answering your questions until the conclusion of today’s event, we do encourage you to

log your questions at anytime using the Q & A functionality located in the right-hand

corner of your screen. If you are in full-slide view simply look for the floating toolbar

with the question mark icon and you can log your questions that way. Also, you will be

receiving an on-demand version of today’s event as well as a PDF of the speaker’s

presentations, I will be sending that out via email early next week, so be on the lookout

for an email from Enterprise Management Associates.

Now I am going to go ahead and turn things over to our first featured speaker, Julie

Craig.

Julie Craig

Thank you very much Raleigh, I’m looking forward to today’s presentation, I think it’s

really going to be quite an interesting one. Today’s discussion is about harnessing the

power of the cloud. I see cloud computing as the most significant game changer since the

internet, I know that that is quite a major claim but it’s the truth. Cloud computing,

however, is also a disruptive technology and the verdict is still out as to where it will fit

in the overall constellation of business application delivery. To assist companies in

making sense of cloud’s value proposition EMA launched research we call The

Responsible Cloud late last year. For the next 20 minutes I am going to be talking about

some of our findings as they apply to companies as they go about the process of

developing a cloud strategy.

So cloud, of course, is the latest megatrend and it is definitely not going to go away.

Reaping its benefits requires going beyond technology discussions and thinking about

cloud in context to potential business outcomes. In a way, cloud computing overturns

everything you thought you knew about delivering business applications. One of its

biggest potential benefits is that it offers a way for companies to focus more attention on

the core business and less on the mechanics of delivering technology services.

So from this perspective, one of the biggest benefits is an indirect one. When EMA

conducted this research we worked across multiple practice areas, the reason why we did

so is because the implications of cloud adoption aren’t limited to technology silos such as

security or network or even to IT departments. Like applications, cloud is a cross silo,

cross department, cross business concern and for this reason we see cloud planning as

spanning both IT and business executives. This was also the case with quite a number of

recent developments in terms of the IT world, one of which was service oriented

Page 2 of 16

architecture, which was really the last game changer and I’ll be talking more about that

later in the presentation.

Now any disruptive technology has the potential to create operational chaos and the goal

of responsible cloud adoption is to make sure, as much as possible, that this doesn’t

happen, confusion is okay but chaos is not good. There are many different definitions of

cloud computing virtually as many as there are experts. EMA uses the United States

National Institute for Standards and Technology definition, which is shown on this slide.

Note that cloud computing systems share 5 key attributes. They offer convenient access

to a shared pool of resources, they are easy to provision and require minimal management

effort on the part of the consumer and finally, they can be utilized without significant

interaction with a provider.

There are also a variety of cloud deployment models. Use of private clouds is limited to

a single organization, community clouds, which you’ve probably haven’t heard as much

about, are similar except that they are shared by several related organizations. The public

cloud is what many of us think about when we hear the term cloud. It consists of

infrastructure, platform and applications that are available to virtually anybody with a

credit card. A hybrid cloud is a combination of multiple models. As you can see here

more companies are leaving their options open and opting for hybrid cloud then for

public or private alone. Hybrid cloud enables the service delivery flexibility that virtually

every company is seeking and provides flexible options to host applications on premise

or in the data center as needed. This enables unique capabilities such as bursting, private

clouds can be sized capacity wide for normal application loads but when resource

requirements exceed the capacity the private cloud can burst into the public cloud.

Typically the way this works is by automatically spinning up virtual servers in the cloud

on-demand.

Hybrid cloud can be a good way to go but it requires investments in tool sets that support

the technology and its value proposition. Obviously, for example, bursting requires tools

that can sense constrained resources and add capacity based on preset policies.

The three basic service models that we hear the most about, in terms of cloud, are

software as a service platform as a service and infrastructure as a service. SaaS is the

most all-inclusive with the vendor delivering a full-blown application, the consumers

only responsibilities are to provide network connectivity at appropriate levels and to

monitor performance and availability for SLAs.

Platform as a service is the next most inclusive with the vendor delivering a hosted

environment and pools specific to a particular task. One of the most common use cases

we are seeing today is hosted development and many providers also deliver hosting for

applications that have been developed on their platform.

Infrastructure as a service is the least inclusive and essentially offers their medal in the

cloud. In this model the vendor delivers infrastructure only and the customer is

responsible for provisioning of the entire application, things like operating systems, data

servers and load balancing. This is where virtualization shines since this is typically

accomplished most easily with virtual images.

So, as you can see here SaaS is the most widely utilized, most companies are still

wrapping their heads around how best to use platform and infrastructure as services, so

Page 3 of 16

the services are up there but it’s a little bit more confusing to figure out how you are

actually going to implement them.

So the information in this next section is from the survey portion of The Responsible

Cloud study, which was actually conducted in late Q4 and we actually published The

Responsible Cloud paper in January of this year. So these are some of the drivers that are

sending companies to the cloud, the top ones include operational and capital cost

reduction, improved service quality and better flexibility. Now, remember that these are

drivers and not outcomes, so what you see are expectations. In reality there really isn’t

an easy button and that is part of what we are going to be talking about today. What you

get out of any technology implementation depends solely on what you put into it and

certainly that is the case with cloud computing.

This slide shows the reasons why companies believe that cloud will be strategic for them.

Flexibility is the number one expected strategic benefit with cost savings and

infrastructure rationalization coming in second and third. It’s interesting to note here that

only 15% of those surveyed are speaking from actual experience, however it’s also

significant that even though cloud is still early in the maturity curve companies are

already seeing fundamental improvements in the way they work from cloud utilization.

Like any technology or any disruptive architecture that happens to IT there is significant

upside but there are also pitfalls and as with any technology drawbacks can rapidly

overtake benefits. Note the political issues, basically people related concerns, are the

biggest roadblock and I’ll be talking more about that later. Integration issues are the

number two concern and rightly so. Very few applications run in stand-alone mode,

many cloud adopters are finding that they are eventually cast with linking multiple SaaS

applications, for example, on premise with SaaS and virtually any permeation of cloud

services you can think of. Integration has always been a challenge, even before we were

facing cloud, but cloud is actually making it even more so. Lack of flexibility is also an

issue, particularly with SaaS services where companies are moving from highly

customized products that are delivered on premise. Many companies have invested

millions of dollars, for example, in customizing enterprise resource planning solutions

from Oracle or SAP. When such a company tries to move to a hosted ERP system it

affects the entire company, they find that plain vanilla hosted services aren’t tailored to

their business as their customized systems were. Surprisingly, security is near the bottom

of this list even though security is almost always mentioned as a top inhibitor of cloud

adoption.

In this next section I am going to be discussing some ways that companies can actually

add some of our responsible cloud guidelines to their own cloud planning. This is a

diagram that you have seen before but it’s actually a good way to illustrate some of the

things that go into rolling out some of these complex technology systems. One thing to

keep in mind is that this isn’t the first time our industry has encountered disruption and it

won’t be the last. In fact, disruption has become the new normal. The most successful

companies that I deal with are those that have raised flexibility to an art form and have

been able to hone their ability to quickly grasp ways to make disruption work for them.

The art lies in developing ways that people and processes can more rapidly adapt to

advancements on the technology side. In a way this involves a new type of lifecycle in

Page 4 of 16

which the people and process sides of the equation are approached with the same rigor as

the technology side.

So one way to illustrate this idea is to think about the ways that different companies

reacted to SOA, which I introduced as the last significant disruptor, in my opinion. We

still hear stories that SOA doesn’t work but on the other hand we hear even more stories

that SOA does work, so who’s right? Well, I think that both are right, making a success

out of SOA required many of the same types of skills that are needed to roll out

successful cloud services. The quotes on this slide are from IT executives from multiple

industries that I interviewed through the months and years of my SOA coverage. All of

these executives have lived successful SOA initiatives and by successful I mean

implementations that delivered differentiating value to the business and it’s certainly not

hard to find examples out there.

On an earlier slide I mentioned political issues as the number one inhibitor of cloud

adoption. The first executive quoted here understood that this was the case with SOA as

well, he started his company’s journey to SOA by educating sea level executives about

the potential benefits to the business. Before he could do this he had to develop a clear

understanding of SOA on his own and this actually turned out to be a very good

investment of his time. He was able to fulfill a key new role in this era of disruptive

technology which is, as a technology consultant to the business. In the end these

conversations worked because he had buy-in for significant transformation in the way his

company does business. Interestingly enough, he also ended up getting a good promotion

out of his efforts.

The next quote stresses the importance of governance, the process of controlling all

aspects of service delivery, from access and security to planning and budgeting. His

company had experienced firsthand the problems encountered when governance is

approached as an after that. They were very successful in deploying SOA from a

technology standpoint, soon after they released their first SOA services to production,

however, they were confronted with a system that had deteriorated into chaos.

Unauthorized users were connecting to the services creating security and compliance

exposures. These unauthorized connections also over-utilized the system, resulting in

performance problems for sanctioned users. Departments that had funded and developed

the services were not happy about the fact that others were demanding access and the

company had no policy for sharing development costs across departments.

Now, in the cloud equivalent there are also similar issues. For example, different

departments adopting different standards for customer relationship management or billing

software vendors, nobody is tracking who is using what and eventually these departments

are going to come to somebody to integrate the services or fit it into an overall enterprise

strategy.

The final quote is from a banking executive whose charter was to develop a consistent

user experience across geographies. Services had to meet specific performance SLAs

regardless of whether the customer was sitting in New York or Cape Town. He found

Page 5 of 16

that without repeatable and enforceable processes across geographies that there was no

way to standardize service delivery worldwide.

Now I know that I’ve talked a lot about SOA here but the value proposition of SOA was

high enough that it became a differentiator and in effect is creating an atmosphere where

the haves have a significant agility benefit over the have-nots, so those that have been

successful have a definite advantage over those who have not been successful. I believe

that this will likely be the case with cloud as well. There are a lot of options out there

and a lot of ways that you can use cloud technology but achieving the advantages of

cloud requires that the companies have a strategy for harnessing cloud and other

disruptive technologies, which is the governance lifecycle that I actually mentioned on an

earlier slide.

So, where do you start and what would such a strategy look like? Well, planning and

research are essential in starting the journey. I know that technology is the fun part but

without planning and research you are setting yourself up for long-term issues. You need

a clear understanding of the new technology, in this case cloud, and the value proposition

for your specific industry and company. Once you’ve developed such an understanding

step up to the role of technical advisor to the business, do the research, apply your own

unique industry and business knowledge and develop a high level road map to

communicate that vision to stakeholders.

When the plan passes others in your firm expect that these discussions will uncover some

potential glitches that you might not have anticipated. Once the vision is clarified

develop a governance plan to guide internal departments in requesting and funding cloud

services. When they request services they should actually go through a similar

prioritization process as with any other project. One thing that can help make cloud more

agile and make the company become more flexible in using cloud is to include a fast

track process for cloud on ramping along with your cloud strategy.

Best practice frameworks can certainly help and there is a lot of discussion going on at

the moment about extending ITIL IT service management capabilities, such as change

and configuration management to cloud services as well. I’ve also been hearing that

investments in a service catalog, for example, can significantly streamline

implementation of the self-service and provisioning aspects of cloud.

So, to summarize, cloud is in all of our futures and it has the potential to deliver major

business benefits but it also carries risk. It’s a game changer that requires planning and

governance and without them the potential benefits will be offset by chaos created by

lack of control. One final idea to keep in mind is that in the end every company

perceives IT as being responsible for the applications delivered to the end user. This is

true regardless of whether the service is hosted internally or delivered via infrastructure

platform or software as a service. Users will still call the helpdesk when they have an

application problem and IT has to be ready to help them solve it. Skilled personnel,

repeatable processes and high quality tools support IT in this charter.

Page 6 of 16

In my presentation I’ve talked a lot about the personnel and the repeatable processes.

Shaun Connolly, the next speaker, is going to talk more about the tools aspect of cloud

adoption.

Shaun Connolly

Thank you Julie and thank you to everyone for attending today’s webinar. As Julie

outlined there is this push towards cloud computing and there are definitely some things

that can be learned from past experiences as you begin that responsible journey, if you

will.

Where I would like to take the conversation is to dovetail it a little bit from VMware’s

strategic lines, if you will, take some of the context that Julie has introduced and begin to

drill down and share how we, at VMware, as we are engaging many of our customers as

they consume our virtualization and application of cloud technologies and how we have

been working with them to map out this journey of sorts, that we see, as they begin to

rollout and leverage technology towards the promise of cloud.

So pictorially and again, setting the overarching strategic lens, if you will, how we see

things at VMware is there is this goal for IT as well as IT vendors in the landscape to

produce IT as a service. That notion or that push needs to factor in a variety of different

factors. On the left we have existing applications and existing data center technology and

how does that come forward on this journey? You are creating new applications in order

to differentiate your business and how should you be architecting those applications for

today’s requirements but also doing it in a way that maps the path forward. And then

there is just the plethora of new devices and access methods from a user computing

standpoint. On the right you also have external factors in place, as Julie brought up, the

SaaS applications as well as class computing capacity on-demand and public cloud

infrastructure.

I think the real challenge is, how do you stitch all of this together into a compliant,

manageable and secure whole and what is the path forward? And that’s really the

problem demand at VMware that we are focusing on, we are really looking to address

this problem domain of providing IT as a service holistically. From that virtualized

infrastructure class one that powers public, private and hybrid cloud scenarios, I like to

refer to it as the high speed rail, where your applications that you are going to set on it

and really begin to deliver at a higher pace. On top of that are what are the requirements

of an application platform for running those workloads but also serving some of the

future needs that cloud computing is introducing. And then finally, user center

computing and VMware definitely plays very strongly there with our virtual desktop

technologies and etcetera, so bringing all of this together as a holistic IT as a service

solution.

Page 7 of 16

From the journey, if you will, it all starts to build forward from the data center with

virtualization as that first step and many of our customers have started that journey by

leveraging virtualization and getting some of the achievements of server consolidation.

But in the promise of IT as a service and both compute and application platform and

applications and software as a service, that journey continues into broader notions that

enable you to get more out of that infrastructure rather than just consolidating a set of

servers. So, taking that existing data center, taking a subset of your data center to start to

enhance it with new attributes, leveraging virtualization as that means to an end and

beginning to introduce this notion virtual data centers. And virtual data centers

holistically are about dolling out dynamic resources, not only compute resource and

memory resource but also storage resource and networking resource and truly creating a

virtualized data center that’s further abstracted away from the underlying physical

hardware that powers it.

Virtualization is the key enabler for that and if you sort of play this forward into private

and hybrid cloud scenarios, as you embrace a virtual data center notion, if you will,

within your own 4 walls, within your own private cloud and have that management and

security constructs then you begin to open yourself up to be able to take advantage of

those virtualized data center resources being provided external to your organization. In

the broader VMware strategy, what that does is it enables you to run compute today in

your data center then to leverage and eat those systems, if you will, of partners whose job

it is to host and setup and run this on behalf so you can get different ways of provisioning

and paying for that virtual data center resource.

So when we look at this equation, that is sort of the foundation, if you will, for public,

private and hybrid cloud initiatives that we are doing at VMware. Again, get that high

speed rail of infrastructure in place with the management and security and the ability to

really run workloads and manage workloads in a self-service manner, whether it’s inside

your data center or externally. So opening up a wide range of choice as to how you can

path into this infrastructure cloud, if you will.

Bringing the conversation up another level to applications that are actually being created

and deployed on that high speed rail, as I referred to it earlier, is you want to have an

equal amount of choice at that application platform layer. That is another critical

problem of our overall strategy is opening up choices of where you can actually build and

run your new application. I represent the SpringSource division at VMware and my

focus is on this cloud application platform area and really, where the strategy is, there are

really two halves of the strategy, one of which is providing a programming model that

provides a high level of productivity for developers creating new applications but also

provides a level of choice in portability, so that way they can leverage existing skills and

creating applications have a wider range of choice into where they actually deploy those

applications.

So for those of you who are familiar with spring-in-a-spring framework, it’s basically a

framework that layers on a level of productivity on top of the Java platform and today

Page 8 of 16

over half of the Java developers out there are familiar with Spring and have Spring

development skills and are deploying applications across a wide range of Java platforms

today, whether that’s Tomcat or WebSphere or WebLogic or what have you. The vision

here is taking that to the next level, particularly with cloud based platforms, and not only

enabling them to run on our own SpringSource platform as well as those other Java

platforms but opening another level of choice as it relates to a public cloud type platform.

For some of you who have followed some of the news over the past months, since

SpringSource has been acquired by VMware, we announced two very strategic

partnerships, one with Salesforce.com, who is one of the premier software and service

vendors out there, as well as Google. Our partnerships there are really around ensuring

that that programming model continues to expand and cover a lot of these cloud

computing requirements but does so in a way that ensures that applications are as

portable as they can possibly be between those environments to enable a choice of

deployments for our customers. So in the case of the VMforce platform, for example,

that is a joint effort between us and Salesforce where the goal there is to provide an

enterprise Java platform that enables people who are leveraging the Salesforce platform

to create Java based applications that can tap into that force.com data store and all the

power of the Salesforce platform but create applications in a way that they are very

familiar with, again the Spring-Java way. And the same with Google, creating

applications that can target Google and their app engine as their platform.

If we move ahead a little bit the genesis, or foundation, of our approach here is to

leverage very pervasive and popular technologies that encourage a lightweight, agile

approach to creating those applications, so Spring is one of those technologies, Tomcat is

at the core of our runtime environment and enables us to really get a high degree of scale

and provisioning and speed, if you will, and productivity, and I will get into some of that.

But the point here is as we see building out an application platform we want to make sure

it’s founded on many of the most popular technologies so that skills that are already

existing can be brought forward and brought there for customers as they create

applications. Moreover, if we look at the application platform space, if you will, there

are issues with traditional application platforms and part of the issue is the fact that the

programming model and innovation around creating innovative new applications is a bit

too tightly coupled with the overall platform itself. Many of these platforms have been

designed with physical architectures in mind and not necessarily virtualized and highly

mobile and agile infrastructure in mind.

So those are some of the issues that we typically see and the result is, in particular, our

customers telling us that they are dealing with a high level of complexity and productivity

impact on that. One of the charts I have here is really a comparison that one of our

customer’s, who is in the financial services industry, when they really do an assessment

of the traditional platforms versus some of this lighter weight approach that can provide a

path towards cloud, there are some real savings from a productivity impact that can be

had by embracing some of these new, more agile, more lean type of approaches - so

things that may have taken hours or days or weeks can be really driven down to seconds

Page 9 of 16

or minutes, or in the case of leveraging a virtualized data center, self provisioning and on-

demand. And that’s really the end goal, to get things out of a physical rack and stack and

an arduous complex process of picking up infrastructure and moving it through the

lifecycle but creating very self-serviced notions in the wake of setting some of these new

architectures, if you will.

So that’s really, from the application platform and productivity impact, when we’ve

talked with customers from an application architecture standpoint there is the

infrastructure challenge of moving applications and dealing with firewall settings and

security issues as applications march through the lifecycle, the applications themselves

and ensuring the infrastructure, isn’t overly complex and enables you to create

applications more quickly and in a more productive and portable manner, but also when

I’ve talked with customers with architectures around data, which when you really think

about it at the end of the day, is the lifeblood of applications - really having technology

and architectures in place that enable you to deal with the data problem as how many

customers, when I’ve talked with them, have phrased it. This sort of leads us into how

we kind of see this journey, of sorts, if you will, on how all of these elements come

together into really more of an evolutionary approach that factors in this virtualized

infrastructure. A lightweight application infrastructure that’s more tuned to elastic scale

and more dynamic provisioning types of notions but also addressing data as a first class

citizen and not mixing it in and mixing concerns, if you will, in your application

infrastructure but actually treating that data layer as its own separate notion so it can do

the things such as global distribution and partitioning of data, so data can go where it

needs to go, in a timely fashion and in a secure and controlled manner.

When we look at this evolutionary approach, if you will, to the ultimate nirvana of having

a cloud platform and a platform as a service notion, there are a variety of steps that you

can take in order to prepare yourself as you progress along that journey. From both the

VMware side and SpringSource portfolio, we bring certain technologies to bear along

this journey. It of course starts with virtualization and, from our standpoint, from an

application framework that enables the coupled innovation of how do you create

applications from where you deploy them but also a platform that enables you to move a

lot of your existing applications so they can move into this virtualized data center notion

and gain some of those benefits. But as you re-architect them and take on some of the

further elastic scale and lightweight nature of the platform and embracing a run-time

that’s tuned to that as well as the data management notions, which I will cover in a little

bit, will ultimately move you along this journey towards cloud.

The first step in that, I had mentioned as the Spring programming model, so for those of

you who are not overly familiar with it I will just briefly touch on it, but it’s essentially a

framework for creating a Java based application and a wide range of them, so you can

create very rich web applications, but also handle some of these integration scenarios and

vast computing scenarios that Julie had mentioned, as software-as-a-service becomes

more prevalent. If you are running your application, for instance, our VMforce public

platform, and want to integrate some of that data into your data center and your backend

Page 10 of 16

systems, they don’t have a consistent way in programming model that developers can

create as solutions is key into that but also having a model that can evolve and factor in

external cloud platform services as first class notions into the platform as well as

targeting other devices as well as even factoring in social media type services that are out

there, like Twitter or what have you, but bringing them in in a cohesive manner on how

you build applications is really what that Spring model is about.

Then ultimately those applications are deployed on a run-time and our run-time in our

portfolio is called tc Server, it’s based on an apache Tomcat which is the most widely

used Java application server out there. We layer additional administrative and

operational and performance management capabilities around that lightweight run-time

so that you are able to get the benefits of taking and being able to provision infrastructure

from days or weeks down to hours or minutes but you also get the operational controls.

In Julie’s section she basically said that you don’t want a Wild West, you want something

that has operational controls and want to avoid chaos and that’s really where our tc

Server is aimed at, is providing the application operators and the people responsible for

actually running those production apps, be it tools, administrative provisioning,

configuration and diagnostic tools to help make their job easier.

Furthermore, taking a pragmatic approach is not all a now I’m deployed on a cloud

platform and it’s cloud in a box one day, it is this journey, so as you being to figure out

what workloads are appropriate for these internal private clouds we have performance

management technology in our portfolio for that very reason. So that way you can have

deep visibility into the performance of your existing application, ensure that you have

proper baselines set, so that way as you start on your journey to virtualize take, that

advantage of these additional capabilities you can have a consistent across the application

infrastructure and the applications you deployed so you can mitigate the risk, if you will,

of any performance issues. Or if you do see performance issues you have the tools in

place that help you drill down into the very specifics of that and that’s really the role that

our Hyperic technology plays in the scheme of things.

There is message based requirements on passing around that in hybrid cloud scenarios,

for those of you who heard about our RabbitMQ acquisition earlier this year, that’s one of

the reasons why we added that into the mix. And then we recently acquired a company

called GemStone Systems, their gem-fired data fabric really gets to that scalability of

data, being able to get the data that’s locked in back-end systems that might cause huge

latency issues when you start talking about a very dynamic application environment,

unlock the potential of that data, put it in a living and breathing operational data store, if

you will, that’s able to move around wi

IT & DATA MANAGEMENT RESEARCH,
INDUSTRY ANALYSIS & CONSULTING

View Document in the Library & Download

Back To Library

IT & DATA MANAGEMENT RESEARCH,INDUSTRY ANALYSIS & CONSULTING

View Document in the Library & Download

Back To Library

IT & DATA MANAGEMENT RESEARCH,
INDUSTRY ANALYSIS & CONSULTING