So You’ve Transitioned To The Cloud – Now What?

I’m willing to bet that when Chinese philosopher Lao-Tzu coined his famous phrase around 500 B.C., “The journey of a thousand miles begins with a single step,” he wasn’t thinking about the time it takes to migrate legacy data center operations to the public cloud. But it couldn’t be more applicable.

For many IT departments, shifting operations to the public cloud can be a long, daunting, and frustrating process. However, it doesn’t have to be. Understanding where the public cloud migration journey begins and where it will ultimately end allows IT professionals to ensure that the first step — and all subsequent steps — are taken in the right direction. And well before the cloud journey actually begins, it’s critical that all stakeholders involved understand the value of moving some or all their IT operations to the public cloud. No one wants to walk a thousand miles in the wrong direction.

While the enormous potential of the public cloud has been well documented, realizing that potential in terms of both quantitative ROI and measurable qualitative benefits requires that a plan be developed and implemented to achieve specific desired results. The reality for most companies embarking on this path is that they can’t do it alone. They require a partner that has experience; they need a “Cloud Sherpa” — a partner who can ensure that their journey into uncharted IT territory will be safe and successful. By moving some or all of your applications to a third-party expert’s management and care, IT departments can better focus on their specific objectives, which can result in significant organizational bottom line results.

The main benefits of transitioning to the cloud are agility, increased scalability, reduced total cost of ownership (TCO), and improved security. To reach your ideal results, below are five main steps for companies implementing the public cloud, and thoughts as to how a third-party provider’s management and care could aid the process.

Begin with the end in mind.

It’s key to keep the long game in mind when planning the move to the public cloud. It starts with identifying challenges to be solved and opportunities to be pursued. Make sure all stakeholders are kept in the loop and involve them in the process. CEOs are typically more open to new applications that increase sales and improve customer satisfaction. CFOs, however, often put more emphasis on cost containment and profit-building, and CIOs usually want service-level improvements. By keeping these individuals in the loop, you increase your chances of success because you will have executive leadership buy-in.

Take stock.

Once you have pinpointed the company’s IT goals, it’s important to conduct a high-level inventory or a refresh of the current list of all the apps being used across your enterprise. The appropriate teams and departments conducting this inventory may uncover utilities, databases, and websites you may have missed. Include information about the purpose of the application, who uses it, and the sensitivity and importance of the data to the business. In order to chart your path to the cloud, you need to know the current state of all apps being utilized.

Map demand.

Mapping demand is crucial in strategizing your move to the public cloud. Ask managers to project growth for existing apps over the next three years, and include new apps the company will take online. By identifying and anticipating future traffic levels and spikes, the team can plan accordingly and be ready for increased growth.

Determine the best cloud candidates.

Review your inventory of applications and data and find the best candidates for cloud migration and implementation. You can pick and choose which apps to move to the cloud and which can stay running on-premise. Apps that experience spikey demand or involve parallel processing (e.g., batch) are naturally a better fit for the public cloud. This is also true for apps requiring DR or needing broad geographic placement.

Decide how far you’ll go.

The beauty of the cloud is that you don’t have to go 100% in all at once. Usually, legacy apps should be left where they are, as they typically can’t benefit from cloud scalability. On the other hand, if you have a pending capital expenditure (CAPEX) investment to refresh infrastructure providing legacy apps, it may make sense to move them to the cloud. Scenarios such as this explain the growing popularity of the hybrid cloud amongst enterprises. Low-risk operations such as project management, file sharing, and any other non-revenue generating applications are all low-hanging fruit that can be moved into the public cloud. With cloud, you can start small and grow at the pace that suits your business.

Any IT trek into new territory is bound to encounter unforeseen issues and challenges. With all the factors to consider when migrating to the cloud, it’s beneficial to have seasoned experts that have successfully managed the transition before. The process is much more streamlined with a guide walking you through it, step by step. Once you’ve narrowed down the list of possible managed public cloud partners, the journey begins.

Powered by WPeMatico

Vertical vs. Horizontal Sourcing In The Cloud Era

When Thomas Friedman wrote his bestselling book The World is Flat in 2005, he was not just talking about level playing fields in terms of commerce. He also touched upon two key trends which were helping the world market to flatten, namely outsourcing and offshoring.

Outsourcing meant segregating manufacturing and services into “components” that could be performed in the most cost effective and efficient manner. This, coupled with offshoring of these components, gave rise to phrases such as “outsource manufacturing to China” and “outsource services to India.” These outsourcing strategies allowed corporations to rearrange their supply chain and orchestrate a greater value by the enterprises, which resulted in enhanced market expansion and profitability.

Componentization of Services Built on Horizontal Layers 

In this instance, componentization of services was built on horizontal layers. Enterprises were using technology “services components,” typically layered on top of one another.

Various models were created to unbundle these service components into distinct services that could then be outsourced to one or many third parties. One of the most successful initiatives in the last decade has been modular sourcing, where each service component was delivered by an entity that has built the expertise and efficiency for that component. Outsourcing companies became good at “remote infrastructure management” or “application management” or as full scale service providers. This model worked well, as long as the service component worked within these layers.

Advent of Cloud Computing & Data Brings Need for Vertical Sourcing

The advent of cloud computing has blurred the lines between these layers. The cloud has not only collapsed the first layer of the distributed data center, but has added a third and critical dimension to the service component — namely application and data leading to greater insights.

This unique phenomenon makes it possible to process data along with applications to generate real time insights so businesses can take decisions faster. In the “cloud” world, these service components will need to be organized differently.

Use Case: Financial Services

As an example, a credit card issuer can launch new products every two to three months (at best) because the insight generated has an inherent delay in the feedback because the sourcing is bundled across multiple entities.

For example, if users stop calling to dispute transactions, it might mean that there are fewer fraudulent transactions. However, it could also mean that the users move on and simply abandon the credit card if they are not able to seamlessly dispute a transaction on the card. The card issuer needs this insight quickly. They must have the ability to respond in a timely manner to a dispute — for a particular age group, on a mobile device, in a particular geography — and offer a different method of resolving the dispute.

Competing products from “born in the cloud companies” are able to respond quickly because their data and applications reside together on cloud.

For companies to respond quickly in today’s cloud world, their services components must change from horizontal to vertical: process, application, data, API, and cloud together for a related function. As an example, the credit card issuer should consider outsourcing the entire service component together.

Some companies have already employed this vertical model of outsourcing in the older world and have reaped tremendous benefits as it ensured sustenance and change worked hand in hand. With the advent of the cloud and its ability to handle large volumes of data and generate insights, it is extremely important that outsourcing is handled as a vertical function.

Table 1. Horizontal Sourcing
Layers Service Components Speed of change
Distributed Data Centers Physical data center management
Remote infrastructure management
12-18 months
Application Management
(custom built and packaged software)
First line of support (incident management)
Second line of support (problem management and long term fixes)
0-3 months
Application Development Routine changes, related business as usual activities, compliance
Changes to support the business for new products and services
3-12 months
Large Development Programs Build net new systems and applications 3-24 months
Table 2. Vertical Sourcing
Layers Service Components Speed of change
Cloud Physical data center management Remote infrastructure management 0-4 weeks
Application Management
(custom built and packaged software)
First line of support (incident management) Second line of support (problem management and long term fixes) 0-4 weeks
Application Development Routine changes, related business as usual activities, compliance Changes to support the business for new products and services 0-12 weeks
Large Development Programs Build net new systems and applications 0-12 months*

* Due to change of technology and processes, it’s uncommon to see programs over a year.

Powered by WPeMatico

Why FPGAs, Hyperconvergence, And DevOps Matter To Your Network

The race to innovate in cloud networking has increased to a sprint. Most recently, Microsoft announced the latest coming out of Project Catapult — the decades-old field programmable gate arrays (FPGAs) that last burst onto the scene in a meaningful way with Bing. FPGAs are being brought to the forefront again as a way to increase the speed and efficiency of Azure while decreasing its cost. The effects of these cloud networking innovations will be felt in myriad ways, so it’s important to explore how these technologies — using Microsoft FPGAs as an example — will start to take shape in network environments.

Decoding the Acronyms

With all of the different custom server technologies at its disposal, it’s important to explore why Microsoft is going in the direction of FPGA vs. central processing unit (CPU), graphics processing unit (GPU), or application-specific integrated circuit (ASIC).

The CPU is a general purpose processor with a broad published instruction set, and while not a speed demon, it can do everything from IP address resolution to analog decoding and graphics. That is why these are ubiquitous in nearly every device type, from phones to computers to embedded devices. On the other hand, a GPU has hundreds, or even thousands, of cores, each performing only a handful of tasks, but doing so very quickly, thanks to custom silicon, programming, and parallelism (think Bitcoin and NSA data centers). Finally, ASIC — the network equivalent of a GPU — is a custom chip that knows how to route network traffic without all of the reporting fuss. It moves packets efficiently and quickly, but slows considerably for non-routine tasks. Each of these chips requires an element of custom-building with tradeoffs in speed and efficiency.

What Microsoft did with Bing, and how Bing was able to catch up to Google, was it started looking for ways to achieve neural net processing and machine learning, knowing that Bing would need to have the kind of performance dedicated chip processors deliver, while also allowing them to adapt over time. So Microsoft turned to a slightly old-school technology: FPGAs. They started putting them on their servers instead of having specialized compute nodes. Microsoft distributed the programmable chips in each one of their servers to localize task-specific compute power that was much more efficient for certain workloads than the servers themselves.

Perhaps Bing’s legacy won’t be that it became a respectable challenger to Google search, but that it launched the architecture behind Azure Project Catapult, the distributed FPGA network. With its FPGA-based network, instead of building custom chips, Microsoft built a distributed network of reprogrammable chips designed for machine learning and other capabilities, including softwared-defined networking (SDN) and routing as part of a beneficial standard infrastructure that is unique to Azure.

It’s important to note that alongside recent announcements about FPGAs, Azure also lowered its pricing, further accelerating the price and efficiency war between cloud goliaths Azure and Amazon Web Services (AWS), and in the process, making the networking in the cloud race a bit more interesting.

But while this is all a very high-level examination of the industry, the question remains: how will this actually affect IT professionals?

Reality for IT Professionals: Hyperconvergence and DevOps in a Hybrid IT World

Hyperconvergence is where we are likely to see this all come into play for the IT professional. For example, Azure Stack is a Microsoft version of enterprise hyperconvergence and essentially allows one to deploy Azure in a data center. It’s blurring the lines between enterprise and cloud technologies and making Azure increasingly attractive for the enterprise. With Azure Stack everything works like it does in the cloud, but on-premises. Microsoft is essentially pushing highly converged capabilities into a rack of homogenous systems side-by-side, supporting a common management and monitoring toolset and transitioning administrators, finally, from Infrastructure-as-a-Service (IaaS) to Platform-as-a-Service (PaaS).

With Azure in the data center, more IT professionals will be moving on-premises workloads to Azure Stack. This is because it will allow them to programmatically manage enterprise infrastructure, and ultimately hit a button and move elements of the infrastructure to Azure. Talk about hybrid IT.

This introduces another approach to hybrid IT and an expansion of the DevOps function in two ways: via cloud networking technologies being applied to enterprise environments (and on-premises businesses seeking to hire Azure developers, for example), and the natural adoption of DevOps as a necessary function for anyone managing apps by APIs and not GUIs.

Best Practices

With the explosion of cloud networking innovations leading to hyperconvergence and an increased blending of traditional and cloud technologies in the enterprise, IT professionals need to be armed with best practices to keep pace with the changing landscape. They should consider the following:

  • Expand understanding of monitoring. Effective network monitoring today means looking at elements from components of the application stack (databases, servers, storage, routers, and switches) to internal network firewalls, internet path, and Software-as-a-Service (SaaS) provider internal network monitoring. Although it’s necessary to be able to get information about the components of application delivery for detailed troubleshooting, from a monitoring perspective, it’s more important than ever to do user experience monitoring across all elements of the delivery chain, including the internet and service provider networks.
  • Learn the intricacies of virtual private cloud (VPC) networking. This involves security policy management, policy group assignment, and security policy auditing. In short, IT professionals can no longer get by with just knowing how to secure internal networks; they must understand how to replicate this process in their VPC.
  • Focus on understanding how bulk traffic travels. When running backups in on-premises environments, the only concern is if offline analytics processing runs at the same time as backups, and if these should be separated to avoid overloading storage. But in cloud environments, this is much more complex and involves understanding where backups are going and where processes are happening. IT professionals should keep an eye on the evolving nature of network trafficking — LAN, WAN, and VPC networks.
  • Hit the books. All of these technologies will require a burst of education to get caught up. And IT professionals shouldn’t wait! These innovations are coming fast and furious and it’s important to keep skillsets fresh to adopt the DevOps mentality.
  • Re-evaluate services regularly. Technology is evolving so quickly, and the services being offered by cloud providers are much differentiated. Vendors are constantly adding capabilities and catching up with one another, like with FPGAs and AWS and Azure block chain services. Having an understanding of these ever-evolving service offerings is important because business will look to IT professionals to be experts in these services just as they would with enterprise technologies.

It can be very difficult to keep up with all of the changes to cloud networking and how these will begin to affect IT professionals in hybrid environments. But understanding the practical viewpoint of these technologies’ predicted effects on IT will enable IT professionals to think about this in a level-headed manner and approach the future of the business with confidence.

Powered by WPeMatico

Securing Hybrid IT

Part of the problem with securing hybrid IT is that many people are confused about what that even means. Furthermore, even those who understand what it means are unsure of how security policies should account for hybrid IT.

Why? Well, it’s complicated, literally.

At its core, hybrid IT is complex — IT infrastructure and applications running on-premises (in your own or a hosted data center) combined with anything in the cloud. It’s a mix of services completely owned and managed by an internal team plus services completely owned and managed by a third-party vendor.

In the most recent SolarWinds IT Trends Report (2016), 92% of IT professionals said adopting cloud technologies is important to their organizations’ long-term business success. While that may point to an all-cloud future, the reality is that you will be leveraging cloud as just part of your overall IT strategy, but not moving all your infrastructure to the cloud for some time, if ever. In fact, according to the report, 60% also said it’s unlikely that all of their organizations’ infrastructure will ever be migrated to the cloud.

This means you need to understand and develop security policies that account for a world with a mixed ownership model.

One of the key pieces to this mixed ownership model is Software-as-a-Service (SaaS). SaaS is a way of delivering software. It simply means that the consumer of the software doesn’t have to worry about the underlying details of the application or infrastructure, they just consume the business service, such as email or CRM. Similarly, in the enterprise, IT usually delivers applications as a service, often with monthly or quarterly bill back to the department or business unit consuming the service. And the past 10 years have seen the mass market adoption of public SaaS, which means we in IT now have even less to worry about in regards to getting applications to users. Of course, there are some challenges that come along with this.

When there’s a problem with the infrastructure or applications required to deliver a service that we don’t own or manage, we’re stuck opening a ticket and waiting to hear back like everyone else. Sure, there are a few things we can check — we can ensure our internal infrastructure is operating or that our next ISP isn’t experiencing any problems, but that’s about it.

This is the core challenge of hybrid IT — responsibility without control.

And of course, this isn’t just a problem for ensuring availability. The classic security model of confidentiality, availability, and integrity all look different in a hybrid IT world. By definition, hybrid IT takes data that was in your data center and spreads it out across the internet. How do you ensure confidentiality if your data is entered into a vendor’s application and that data is then shipped across the world to data centers with different local regulations on data security? Application-level encryption in transit, typically TLS, can help, but just because the data was transported securely doesn’t mean it will be stored securely.

The same thing applies to the integrity of your data. How do you ensure that the data stored out of your control doesn’t get modified? Even in complete on-premises deployments, I rarely see IT departments have a program in place to ensure and audit the integrity of the data they store. To be fair, it’s much easier to find news about data breaches from on-premises deployments than from public cloud or SaaS vendors. The point isn’t to argue that private is more secure than public or hybrid, but that as a supplier or consumer of these services, you need to understand how the confidentiality and integrity of your data is being managed.

Another security issue related to hybrid IT has to do with where certain components of an application are deployed in the cloud. For example, a database or message queue service. This is how many IT departments start when they want to migrate their existing applications to the cloud, particularly web services. Of course, net new applications also follow this path as well.

Whenever you do this, you need to ensure that you not only follow your internal security processes, but that those processes are updated to take into account the unique deployment nature of cloud-based services and how that changes your design. For example, it’s easy to spin up a Database-as-a-Service (DBaaS) instance and simply start using it. But just as you wouldn’t put your database server directly on the public internet, you need to ensure your network policies are in place such that only the required servers can access that service.

This is where I see a lot of people get tripped up. If you are using DBaaS, understand that it’s just one component. Remember, you still have to solve the connectivity and security problems just as you did when you deployed a database in your own data center. Complicating matters is that when it comes to anything “as-a-service,” there is often the expectation of very fast deployment, often at the expense of security. Although this speed vs. security issue has always been a problem, it’s exacerbated by the very nature of the cloud — easy deployment and sitting outside the existing security perimeter.

Whether you’re just getting started down the cloud path or are fully involved in a hybrid IT environment, your security policies and controls should clearly reflect the reality of a distributed, mixed ownership IT world. Wherever you’re at, it’s never too early or too late to ensure your hybrid IT plans position you to deliver secure and reliable services; just be sure to take the necessary time to fully understand how it changes your infrastructure, your team, and your approach to security.

This article appeared in the the 2016 September/October issue of Mission Critical Magazine.

Powered by WPeMatico

5 Ways Data Centers Must Adapt To Support IoT

Recently, the Internet of Things (IoT) has been a hot topic, and it’s easy to see why. Did you know that there are more smart devices and electronic gadgets on earth than people? According to the IDC, the digital universe will reach 44 trillion gigabytes of data from a variety of “things,” such as medical implants, wearable technology, and even vending machines, by 2020. Today, according to CloudTweaks, more than 2.5 billion gigabytes of data is generated every day.

If that doesn’t make you take notice, Cisco says that IoT will reach an economic value of $14.4 trillion by 2022. To take advantage of this growth, many companies will jump on the IoT bandwagon by creating software-defined IoT widgets and the supporting management applications, and make them available around the globe. The result of this IoT explosion causes a strain on data center capacity and accessibility for many com­panies, requiring data center service providers to be able to support increasing data demands.

To understand how the IoT paradigm will affect technologies, we first must have an appreciation for what IoT is. The fundamental concept behind IoT is a network of physical devices (or things) that are embedded with technology to give them the ability to sense or measure their envi­ronment — and then have the capability to store and or programmatically send data through network connectivity. Data from these devices can be sent, stored, or programmatic actions taken. Applications of IoT include smart homes, wearable technology, parking meters, equipment sensors, or refrigerators, to name a few. IoT taps into data that allows us to make smarter decisions, quicker.

IoT brings with it a significantly higher demand for storing and processing data, and requires smarter systems and data center infrastructure tai­lored to handle the increase. At the current rate of IoT growth, now is the time to plan for a scalable data future.

With the influx of data expected to happen in the coming years, IT and tech decision makers need to keep their data operations top of mind, and data centers need to prepare themselves for increased scale, density, and security. When talks of IoT take place, it won’t be just one aspect of the infrastructure that will need to be augmented to support IoT. It will impact the whole technology stack, including the networks, facilities, cabinets, technology platforms, and system administration. Companies and data centers are already starting to see the effects of IoT and must ensure they are capable of handling future data requirements.

According to Dr. Deepak Kumar, CTO at Adaptiva, “In the coming decade, the IoT will cause the bandwidth gap to balloon out of control. Enterprises will see enormous amounts of traffic coming from a massive number of sources. In addition to greater bandwidth, enterprises must plan for bandwidth optimization and enforce stricter traffic management policies. IT departments will need to ensure they have mechanisms that priori­tize internet and intranet access to business-critical applications and devices first.”

In order to prepare for the influx of data, data centers must enhance their current capabilities as it pertains to infrastructure, scalability, services, storage, and security. IoT producers will be looking for data center-as-a-service providers that understand and are making plans to support IoT.


Data centers will have to be flexible to meet the growing and changing needs of IoT devices and demands with limited to no impact on the cus­tomer. Not only will we see an increase in products but we can also expect to see devices change, be updated, or even replaced similar to the way Apple comes out with newer models each year.

The impact on data center scalability is one reason why an outsourced model is a smart decision. It is nearly impossible to adequately plan for what the next several years hold without risk of under-building or over-building data centers — both of which can have huge costs and downside associated with them.


IoT transformation isn’t just for new consumer devices. Data centers themselves are also embracing IoT to gain insights into their own infrastruc­ture and operations. The following enhancements are helping to make data centers the most sophisticated and secure places for businesses to host their data.

  • Real-time asset management with RFID – Radio frequency identification tags (RFID) can be added to equipment or devices inside of a data center. RFID tags use an electromagnetic field to uniquely identify devices. These tags allow data centers to act more efficiently since they require less manpower. Without RFID, employees would have to manually check each piece of equipment to maintain inventories. With RFID the manual checks are automated.

  • Environmental sensors – Data centers are now being equipped with many sensors that are placed in the data center to monitor a wide variety of environmental factors. The data is captured and sent to a system that can then use the data to change the climate of the data center, which is important if the weather or compute demands fluctuate in a data center.

  • Infrastructure sensors – Infrared scanning is used to see what the visible eye cannot see. While current technologies require a human to scan and assess the circuitry, it wouldn’t be a stretch to envision data centers having smart infrared IoT scanners that can monitor cables and electrical circuits for anomalies in real time and either suggest corrective action or instantly resolve issues.

  • Biometric scanners – Biometric scanners allow data centers to ensure that only people who have clearance are able to enter. These devices also make it easy to automatically track every person who enters and exits the data center.

  • Network enhancements – IoT is heavily dependent on having reliable networks in place to support the data produced by IoT devices. Many companies are looking for direct connect solutions between data centers and also channeling their cloud traffic through dedicated secure services.


With the recent onslaught of data and the need for flexibility around scale and changing requirements, an increasing number of companies are look­ing to Data Center-as-a-Service (DCaaS) to meet their needs.

For those who are evaluating their options here are a couple of points to consider:

  • DCaaS is a good solution for companies who aren’t exactly sure what option is right for their business, or what data center size will be best five years from now.

  • DCaaS gives companies the ability to focus on their core business competency, saving cash for building their business.

  • Running a data center requires an investment not only in the facility, but also in the people, the process, and the equipment. By working with a data center colocation provider, you can add scale as needed and only pay for what you need at that moment.

Given today’s evolving technological advancements and data demands, it makes sense for more companies to start embracing the notion of DCaaS and protect against rapidly changing requirements related to scale, security, and infrastructure.


Assuming the predicted 44-zetabyte increase is correct, and if we agree that the current storage demand is about a tenth of that amount, it’s safe to say that there will need to be major storage advancements to support IoT. An influx of users simply means an influx of data that needs to be stored. As millions of IoT devices collect and transmit data every day, all of their information will need to pass through a data center at some point. Data center owners must ask themselves if their current infrastructure will be able to handle all of the data they will generate each day. With the prolif­eration of IoT devices, data centers will have to dramatically increase their storage options and capacity to meet demands.


Years ago, businesses would turn to data centers and typically their only expectation was a cold facility with network and power. But now, as IoT evolves and a growing number of IoT devices will enter the network, the focus is quickly shifting to increased security. The reason? The more end­points that exist within a network, the greater the likelihood of the network’s security being compromised, and each IoT device is an endpoint.

In addition, data center security has been heavily emphasized as legislation surrounding personal information and credit card information contin­ues to develop, especially on the global stage. Businesses with a U.S.-based website may also have customers in Europe or South America, so their data centers should provide a level of compliance and security that safeguards their assets and data in every country.

Look for an increase in data centers obtaining the ISO 27001 certification, which ensures greater protection of data. This certification tests the overall effectiveness of a data center’s information security management system (ISMS). The ISMS is a framework of policies and procedures that include all legal, physical, and technical controls involved in an organization’s information risk management processes. It’s a systematic approach to managing private and sensitive information so it remains secure.


It’s easy to see why IoT brings both excitement and trepidation to those who take the time to think about its ramifications. This growing trend will affect organizations at all levels as they try to figure out the best way to benefit and adapt. For data centers, it’s important that they are flexible in order to prepare for the future and ensure their infrastructure is ready for the oncoming blitz of devices and data. n 

This article appeared in the 2016 September/October issue of Mission Critical Magazine.

Powered by WPeMatico

Why Cloud Architecture Matters

Choosing an enterprise cloud platform is a lot like choosing between living in an apartment building or a single-family house. Apartment living can offer conveniences and cost-savings on a month-by-month basis. Your rent pays the landlord to handle all ongoing maintenance and renovation projects — everything from fixing a leaky faucet to installing a new central A/C system. But there are restrictions that prevent you from making customizations. And a fire that breaks out in a single apartment may threaten the safety of the entire building. You have more control and autonomy with a house. You have very similar choices to consider when evaluating cloud computing services.

The first public cloud computing services that went live in the late 1990s were built on a legacy construct called a multi-tenant architecture. Their database systems were originally designed for making airline reservations, tracking customer service requests, and running financial systems. These database systems feature centralized compute, storage, and networking that served all customers. As their numbers of users grew, the multi-tenant architecture made it easy for the services to accommodate the rapid user growth.

All customers are forced to share the same software and infrastructure. That presents three major drawbacks:

  1. Data co-mingling: Your data is in the same database as everyone else, so you rely on software for separation and isolation. This has major implications for government, healthcare, and financial regulations. Further, a security breach to the cloud provider could expose your data along with everyone else co-mingled on the same multi-tenant environment.
  2. Excessive maintenance leads to excessive downtime: Multi-tenant architectures rely on large and complex databases that require hardware and software maintenance on a regular basis, resulting in availability issues for customers. Departmental applications in use by a single group, such as the sales or marketing teams, can tolerate weekly downtime after normal business hours or on the weekend. But that’s becoming unacceptable for users who need enterprise applications to be operational as close to 24/7/365 as possible.
  3. One customer’s issue is everyone’s issue: Any action that affects the multi-tenant database affects all shared customers. When software or hardware issues are found on a multi-tenant database, it may cause an outage for all customers, and an upgrade of the multi-tenant database upgrades all customers. Your availability and upgrades are tied to all other customers that share your multi-tenancy. Entire organizations do not want to tolerate this shared approach on applications that are critical to their success. They need software and hardware issues isolated and resolved quickly, and upgrades that meet their own schedules.

With its inherent data isolation and multiple availability issues, multi-tenancy is a legacy cloud computing architecture that cannot stand the test of time.

The multi-instance cloud architecture is not built on large centralized database software and infrastructure. Instead, it allocates a unique database to each customer. This prevents data co-mingling, simplifies maintenance, and makes delivering upgrades and resolving issues much easier because it can be done on a one-on-one basis. It also provides safeguards against hardware failures and other unexpected outages that a multi-tenant system cannot.

The provider is able to replicate application logic and database for each customer instance between two paired and geographically diverse data centers in each of our eight regions around the world. This can be done in near real-time with each side of the paired data centers fully operational and active. Automation technology can quickly move customer instances between these replicated data center pairs.

It’s important to emphasize that multi-instance is not the same single-tenant, where the cloud provider actually deploys separate hardware and software stacks for each customer. There is some sharing of infrastructure pieces, such as network architecture, load balancers, and common network components. But these are segmented into distinct zones so that the failure of one or more devices does not affect more than a few customers. This enables the creation of redundancy at every layer. For example, at the internet borders, a vendor might have multiple border routers that connect to several tier- one providers on many different private circuits, direct connections, and on different pieces of fiber.

This leads to another important difference between multi-tenant and multi-instance architectures: the approach to disaster recovery. Permanent data loss is a risk inherent to all multi-tenant architectures, and that means external disaster recovery sites are no longer viable options.

True, these are sites that a vendor can fail to if the active side fails. But they are only tested a few times a year and only used if an extreme situation arises. If (when) that happens, they risk failing under load. When that happens, data is lost forever.

That risk virtually disappears in a multi-instance environment. Again, there is not one master file system that services all customers. You can scale out pieces of hardware — stack them on top of each other like LEGO blocks. Each block services no more than a few customers, so one hardware crash cannot affect all the blocks. And because replication is automatic, the secondary side is immediately accessible.

When you partner with a cloud provider that bases its platform on a multi-instance architecture, you’re moving into your own house. Your data is isolated, a fully replicated environment provides extremely high availability, and upgrades on the schedule you set, not the provider. Cloud architecture matters because you’re in control, and better protected when disaster strikes.

Powered by WPeMatico

Transitioning To An Agile IT Organization

If you have even a passing interest in software development, you’re likely familiar with the premise of agile methods and processes: keep the code simple, test often, and deliver functional components as soon as they’re ready. It’s more efficient to tackle projects using small changes, rapid iterations, and continuous validation, and to allow both solutions and requirements to evolve through collaboration between self-organizing, cross-functional teams. All in all, agile development carves a path to software creation with faster reaction times, fewer problems, and better resilience.

The agile model has been closely associated with startups that are able to eschew the traditional approach of “setting up walls” between groups and departments in favor of smaller, more focused teams. In a faster-paced and higher-risk environment, younger companies must reassess priorities more frequently than larger, more established ones; they must recalibrate in order to improve their odds of survival. It is for this reason that startups have also successfully managed to extend agile methods throughout the entire service lifecycle — e.g., DevOps — and streamline the process from development all the way through to operations.

Many enterprises have been able to carve out agile practices for the build portion of IT, or even adopt DevOps on a small scale. However, most larger companies have struggled to replicate agility through the entire lifecycle for continuous build, continuous deployment, and continuous delivery. Scaling agility across a bimodal IT organization presents some serious challenges, with significant implications for communication, culture, resources, and distributed teams — but without doing so, enterprises risk being outrun by smaller, nimbler companies.

If large enterprises were able to start from scratch, they would surely build their IT systems in an entirely different way — that’s how much the market has changed. Unfortunately, starting over isn’t an option when you have a business operating at a global, billion-dollar scale. There needs to be a solution that allows these big companies to adapt and transform into agile organizations.

So what’s the solution for these more mature businesses? Ideally, to create space within their infrastructure for software to be continuously built, tested, released, deployed, and delivered. The traditional structure of IT has been mired by ITIL dogma, siloed teams, poor communication, and ineffective collaboration. Enterprises can tackle these problems by constructing modern toolchains that shake things up and introduce the cultural changes needed to bring a DevOps mindset in house.

I like to think of the classic enterprise technology environments as forests. There are certainly upsides to preserving a forest in its entirety. Its bountiful resources — e.g., sophisticated tools and talented workers — offer seemingly endless possibilities for development. Just as the complex canopy of the forest helps shield and protect the life within, the infrastructure maintained by the operations team can help protect the company from instability.

But the very structure that protects the software is also its greatest hindrance. It prevents the company from making the rapid-fire changes necessary to keep up with market trends. The size and scale of the infrastructure, which were once strengths, become enormous obstacles during deployment and delivery. Running at high speed through a forest is a bad idea — you will almost certainly trip over roots, get whacked by branches, and find your progress slowed as you weave through a mix of legacy technology, complex processes, regulatory concerns, compliance overhead, and much more.

By making a clearing in the forest, enterprises can create a realm where it’s possible to run without the constraints of so many trees. This gives them the ability to mimic the key advantage of smaller companies by creating the freedom to quickly build, deploy, and deliver what they want — without the tethers of legacy infrastructure.

For example, I have worked with a multinational retailer that, in addition to operating 7,800 stores across 12 markets, manages 4,500 IT employees around the world — which translates to 7 million emails and 300 phone calls per day from distributed operation centers in nine different countries. The major issue was that notification processes were inconsistent on a global level, and frequently failed to get relevant information to the right people at the right time. This, of course, translated into slower response times to issues affecting their customers.

In order to modernize its IT force, the company reorganized into a service-oriented architecture (SOA), featuring separate service groups that owned the design, development, and run of each of their respective systems. This meant that many IT members were given new roles with responsibilities; though most had worked on developing systems, most hadn’t worked on supporting systems. They also integrated tools to enable automation and self-service for end-users. Today, they have a more consistent and collaborative digital work environment, and the result is greater efficiency, happier customers, and more growth opportunities for the future.

Similarly, I worked with a retail food chain that presented a challenge in improving the communication and collaborative capabilities of its teams in food risk management. Prior to IT modernization, in-store staff manually monitored freezer temperatures every four hours — a complex and time-consuming task that was highly prone to human error. If an incident arose, the escalation process couldn’t identify the correct team member to address the temperature issues, so a mass email would be blasted out. There was no way of knowing if the correct team member has been made aware of the issue and had addressed it.

The company tackled this challenge by creating a more robust process for incident management involving SMS messages to identified staff, emails and phone calls to management, and automated announcements over the in-store system. In addition, they implemented an Internet of Things (IoT) program to completely automate and monitor refrigerator and frozen food temperature management. The result has been significantly increased efficiency, transparency, and accountability — not to mention a safer experience for their customers.

As you can see, these companies were able to identify target areas and problems, and create new spaces within their existing infrastructures to allow them to communicate better, and ultimately become faster, nimbler, and more responsive. Any enterprise looking to move toward agile software development and operations should look at technology-based projects and initiatives that will be most impactful in enhancing team focus and culture. Before you even start thinking about the problems you want to solve with agile and DevOps, you should identify and initiate the conversations that will provide the starting points for adoption. Without a detailed map of your infrastructure and the activities within it, you cannot clear a path to complete, end-to-end DevOps adoption.

Powered by WPeMatico

Summertime And Living In The Cloud Is Easy

Welcome to Cloud Strategy’s 2016 Summer issue! We really outdid ourselves this time.

To begin, Allan Leinwald of ServiceNow is here with an in-depth look at cloud architecture for our cover story. But there is more! Kiran Bondalapati from ZeroStack writes about the commoditization of infrastructure; Sumeet Sabharwal of NaviSite writes on the opportunities available to independent software vendors in the cloud; Mark Nunnikhoven of Trend Micro talks about the trend of the everywhere data center and the danger of dismissing the hybrid cloud; Alan Grantham of Forsythe writes about the cloud conversations companies should be having; Peter Matthews of CA Technologies, Anthony Shimmin of AIMES Grid Services, and Balazs Somoskoi of Lufthansa Systems share their tips for selecting the right cloud services provider; Adam Stern, founder and CEO of Infinitely Virtual writes about the importance of cloud storage speed; Shea Long of TierPoint tackles the hot topic of DRaaS; and Steve Hebert, CEO of Nimbix writes on the challenges CIO face in balancing public, private, and hybrid clouds.

In addition, we have a case study from Masergy on its successful implementation of a high-speed network to implement Big Data analytics.

Another great issue, if we say so ourselves.

Powered by WPeMatico

Hyper-scale data center eliminates IT risk and uncertainty

In June 2016, CyrusOne completed the Sterling II data center at its Northern Virginia campus. A custom facility featuring 220,000 sq ft of space and 30 MW of power, Sterling II was built from the ground up and completed in only six months, shattering all previous data center construction records.

The Sterling II facility represents a new standard in the building of enterprise-level data centers, and confirms that CyrusOne can use the streamlined engineering elements and methods used to build Sterling II to build customized, quality data centers anywhere in the continental United States, with a similarly rapid time to completion.

CyrusOne’s quick-delivery data center product provides a solution for cloud technology, social media, and enterprise companies that have trouble building or obtaining data center capacity fast enough to support their information technology (IT) infrastructure. In trying to keep pace with overwhelming business growth, these companies often find it hard to predict their future capacity needs. A delay in obtaining data center space can also delay or stop a company’s revenue-generating initiatives, and have significant negative impact on the bottom line.

The record completion time of the Sterling II facility was the result of numerous data center construction principles developed by CyrusOne. These include standardized data center design techniques that enable CyrusOne and its build partners to customize the facility to optimize space, power, and cooling according to customer needs; effective project management in all phases of design and construction, thanks to CyrusOne’s established partnerships with data center architects, engineers, and contractors; advanced supply-chain techniques that enable CyrusOne to manufacture or pre-fabricate data center components and equipment without disrupting work at the construction site; and the use of Massively Modular® electrical units and chillers to enable rapid deployment of power and cooling at the facility according to customers’ IT capacity needs.


In late December 2015, CyrusOne broke ground on the Sterling II data center, the second facility at its Northern Virginia campus. Built for specific customers, the Sterling II facility is a 220,000-sq-ft data center with 30 MW of critical power capacity. The facility was completed and commissioned in mid-June 2016. Its under six-month construction time frame is the shortest known time to completion ever achieved by CyrusOne for an enterprise-scale data center of its size. The 180-day build time shattered all known industry construction records.

CyrusOne had previously set another industry record by delivering a 120,000-sq-ft, 6MW facility in Phoenix, Arizona, in 107 days, or just over three months. The Sterling II facility is almost twice the size of the Phoenix facility, offers five times more power capacity, and took only twice as long to deliver. Its record time to market represents a new industry standard in the construction and deployment of built-to-suit enterprise data centers.

The Challenge

Many large-scale cloud, internet, social media and enterprise companies are growing at an unprecedented and unpredictable rate, with their IT footprints often doubling or tripling in size in just a few years. But rapid growth makes it harder for these companies to predict or plan for future IT infrastructure expansion.

“When enterprises determine how much IT capacity they will require to handle future business growth, it often turns out that they needed it ‘yesterday,’” explains John Hatem, CyrusOne’s executive vice president of data center design, construction. and operations. “But they can’t build new data centers or buy colocation space fast enough to meet their skyrocketing IT infrastructure demands. In addition, the quest to build or obtain new data center space is a distraction from the company’s core business, whether that’s software development, cloud technology, social media. or other business applications.”

The Solution

CyrusOne Solutions™ build-to-suit IT deployments can deliver a completed, high-quality data center product, often in the same amount of time it takes enterprises to order and receive the computing equipment that will operate inside the facility. This rapid time to delivery helps relieve the customer’s risk of not having adequate IT capacity to support their key business growth, or the infrastructure demands of new initiatives. Significantly, CyrusOne is typically able to deliver this data center product with lower construction, engineering and operational costs to the customer.

The Sterling II and Phoenix enterprise data centers were completed in record time thanks to CyrusOne Solutions’ streamlined construction and IT deployment approach, which includes:

  • CyrusOne’s signature Massively Modular engineering disciplines, which employ standardized data center design using pre-fabricated components and template construction techniques.
  • Effective project management by the CyrusOne Solutions team through productive and collaborative relationships with experienced data center architects, engineers and contractors involved in the project.
  • Advanced supply-chain techniques that enable CyrusOne to manufacture or pre-fabricate data center components with time-saving efficiency.
  • CyrusOne’s Massively Modular approach, which uses modular electrical units and chillers to provide flexible power and cooling deployments for the facility.

Massively Modular Construction 

“We think of building our data centers as a manufacturing process, not a construction process,” Hatem says. “We deliver the same high-quality product to all of our customers, which is a reliable data center with space, power and cooling. Using a standardized data center design and components enables us to deploy a similar product anywhere in the continental United States, with the fastest time to market available.”

Through its Massively Modular construction/engineering methods, CyrusOne builds data centers in standardized building blocks with 60,000 sq ft of infrastructure and 4.5 MW of power. For customized data center projects, CyrusOne builds as many blocks as the customer requires. The Phoenix data center consists of two building blocks, while the Sterling II data center consists of five building blocks (with additional power capacity added). Using this standardized layout as a basis, CyrusOne can then customize the design of a built-to-suit data center to optimize space, power and cooling according to the individual customer’s IT needs.

Effective Project Management through Industry Parnerships

To build the Sterling II facility, CyrusOne Solutions put together a project-management team that included outside architects, engineers, and contractors who had worked with CyrusOne on previous data center builds. By working with these industry experts, CyrusOne was able to plan and execute the Sterling II project so the facility could be built in a very short time.

“I can’t say enough about the entire team that worked on the project,” says Laramie Dorris, CyrusOne’s vice president of design and construction. “That includes the architect and engineering team, general contractors, third-party consultants, structural and civil engineers, and local contractors in Northern Virginia, who all pulled together to manage and execute this project. A project like this runs 24/7 for the entire duration, and it was incredible to watch everyone working together in a collaborative, cohesive effort to meet the project requirements and finish the facility within the established six-month time frame.”

Corgan, a Dallas firm, is the architect of record for the Sterling II facility. According to Mike Connell, who served as Corgan’s project manager on Sterling II, “One reason for CyrusOne’s success is they don’t try to micromanage a data center project from the top down. Instead, they hire the right people, build the right teams and empower project managers to make important decisions based on their roles. It makes their construction projects run more smoothly and efficiently.

“For Sterling II, CyrusOne provided Corgan with the basis of design, a budget and a time frame for building the data center, and let our engineers take care of the rest. We were able to give them several design options and tell them the impact on construction, schedule and cost for each option. The confidence that CyrusOne showed in our engineers enabled them to use their creativity to meet the challenge and solve the problems of building a facility in just six months. Our engineers are able to work smarter and harder when they aren’t being overly managed by the client.”

Advanced Supply-Chain Techniques

“In Northern Virginia, CyrusOne made an educated decision to go with an all-precast structural concrete building with modular power and cooling units,” Dorris explains. “This enabled us to set up advanced supply-chain operations to manufacture or pre-fabricate the components we needed for the data center, which gave us significant savings in time and costs.

“For example, a normal data center building has tilt-up concrete walls, which are cast on-site at the construction site. But for the Sterling II data center, we set up a separate off-site facility where we could cast pre-fabricated concrete wall panels. We then brought those panels to the construction site on trucks and used them to set up the data center building. It saved time because we didn’t have to stop work at the building site while the concrete walls were being cast.

“Also, we decided to use pre-fabricated concrete supports in the data center building, which we could also cast off-site. This saved additional time and money because we didn’t have to buy a reinforced steel framework for the building or wait for it to be delivered to us. Using pre-cast concrete walls and supports shaved a couple of months off our time to market for Sterling II.”

Modular Power and Cooling

“To provide power and cooling to the Sterling II facility, we used CyrusOne’s Massively Modular engineering approach,” Dorris says. “We set up another off-site facility where we could assemble modular power units. Each unit included an uninterruptible power supply (UPS), a backup generator, and a utility transformer, all housed in weatherproof containers. We brought the modular units to the Sterling II site and set them up in ‘lineups’ outside the facility. Using modular power units speeds up construction, saves money and reduces the building’s footprint because we don’t have to build additional rooms inside the data center to house power equipment. Also, we used modular cooling units from Stulz at the Sterling II facility, which saved us from having to build a large centrifugal cooling plant on-site.

“The Massively Modular approach provides flexible power and cooling options for Sterling II. If our customer needs to change their IT deployment within the facility, we can bring in additional power units and chillers, and increase power density and cooling with no negative impact or downtime on their current environment. The modular cooling units help lower operating costs because they’re cheaper to operate and maintain over a regular on-site cooling plant. Also, the Massively Modular approach provides redundancy. If a power or cooling unit breaks down, the others will take up the slack until the broken unit can be repaired or replaced.”


CyrusOne Solutions’ built-to-suit data center product is the best solution for cloud, internet, or enterprise customers who need quality data center facilities built in the shortest time possible. The standardized construction approach is a repeatable process employable in multiple locations to ensure rapid speed to market for data center projects, with significant cost savings for customers.

By delivering data centers like the Sterling II and Phoenix facilities in record times, CyrusOne is continuously setting the bar higher for the data center industry. Additionally, CyrusOne is helping ensure its customers are able to scale at hyper-speed to meet their data center capacity needs by removing the risks of running out of space or power.

“CyrusOne has a culture of dedication to client service that starts with their executives and permeates throughout their company,” Connell adds. “When a customer asks them to do something, instead of saying no, they try to figure out ways to make it happen.”

*This case study first appeared on the CyrusOne website.

Powered by WPeMatico