Software Developer Technology News

Most people now agree that the cloud has become a core element of any enterprise’s technology strategy. Indeed, in the past few years we have seen the conversation around cloud adoption move from “if” to “when” and “how.” It is, in short, a fact of life. 

What if you were able to achieve both efficiency and innovation in all the business domains and applications across your entire portfolio? What if you could take advantage of the cloud and all of its resources and features to get a “the whole is greater than the sum of its parts” effect? With a good roadmap to lead the way, you can. This chapter covers what it means to move your enterprise to the cloud. We’ll provide examples and learning experiences from Microsoft’s own journey, as well as from those of our customers

There is always a first cloud application. In every IT organization, some brave soul will either move an existing application to the cloud or create a new one there. In so doing, this person will gain an understanding— beyond all the hype—of what developing, testing, deploying, and maintaining a cloud application is all about.

Sooner or later, it becomes obvious that running a large number of the IT portfolio—perhaps even the majority of it—in the cloud makes sense from a variety of perspectives. In most cases, running in the cloud provides substantial cost savings; reduces or eliminates the need for an enterprise to maintain its own datacenters; reduces or eliminates the need to manage hardware and software updates; and enables the sort of innovation we discussed in Chapter 1. The cloud is very compelling; yet the migration phase typically involves many more applications and many more people, and potentially impacts more of IT’s customers than any other—by far

When Microsoft IT began its cloud migration journey in 2009, it followed a similar process. First, it cataloged its operating system instances and application workloads. This assessment included both quantitative data that was mostly retrievable by tools as well as qualitative data that was partially retrievable by tools and also required examination by both the operations team and the business liaison team. This latter category of metadata included relationships, dependencies, and integration points.

Every major change in the way you conduct business entails some amount of risk; few aspects of the cloud have generated more discussion and controversy than those regarding its security and risk. In this time of breaches, nation-state hacking, and growing and profound concern with individual privacy on the Internet, cybersecurity has become a board-level concern, and rightly so.

Most Watch

Last Comments