Click here to close now.

Welcome!

@MicroservicesE Blog Authors: Pat Romanski, Elizabeth White, Lori MacVittie, Liz McMillan, XebiaLabs Blog

Related Topics: @CloudExpo, @MicroservicesE Blog, Containers Expo, @BigDataExpo, SDN Journal, @DevOpsSummit

@CloudExpo: Article

Best Practices for Leveraging Cloud Technology for Business Growth

Start with small, low-risk applications that can be easily tested and improved through an iterative approach

As businesses look to leverage cloud technology to drive growth, many times the questions IT leaders within the company ask are: "Where do I start? What part of my infrastructure should I move into the cloud first?" IT leaders must pick a place to begin with cloud adoption. The decision becomes easier when teams focus on incremental adoption, starting with small, low-risk applications that can be easily tested and improved through an iterative approach before fully launching. Here are some best practices businesses should consider when getting started with cloud technology.

Identify the true problem and define a solution
The most effective method for getting started with cloud adoption is to identify the greatest pain point in a company's IT ecosystem. The cloud solution should be targeted and architected to ease that pain point. Often times identifying the biggest IT challenge requires a deep dive into the business and its IT systems. For example, NaviSite recently worked with a company in Syracuse, N.Y., to implement a technology solution to help solve its business challenges. The company's IT team perceived its infrastructure as the biggest challenge, and was eager to deploy a full Infrastructure as a Service (IaaS) solution. However, as the IT team took a complete and objective inventory to understand their challenges at a very granular level, they came to realize that what the business truly needed was an enterprise-class file sharing solution designed to meet their specific challenges. As a result, instead of starting with a full-blown IaaS, the team began with a file sharing solution, and was able to immediately solve some of their business challenge with less investment. The key was understanding the challenge at the core, and implementing a cloud-based solution to solve that challenge.

As part of defining the problem when implementing cloud technologies, IT leaders should also define what a solution looks like. A useful exercise is identifying what the IT ecosystem looks like when the pain point is solved. That vision of the solution will guide the cloud team during implementation until it has achieved its vision of success.

Think of cloud adoption in terms of out tasking
When businesses and IT teams are determining where to begin with cloud adoption, it can be helpful to view the process as the migration of bite-sized, discrete pieces of an IT system onto the cloud. It is more about "out tasking" than out sourcing.

When defining and understanding out tasking, IT leaders can take a step back and look at cloud computing as a loosely integrated suite of complimentary services, such as IaaS, Software- as-a-Service (SaaS), Backup-as-a-Service (Baas), Desktop-as-a-Service (DaaS), etc. Building a cloud infrastructure to help a business grow, reduce costs and run more effectively is not a one time, all or nothing proposition. The most effective and low risk approach is to start with one solution to address one challenge. An IT leader is taking that problem, or ‘task', and solving it with a cloud solution. Once that solution is achieved, then an IT leader can take on a second challenge, or a broader area with high potential to drive efficiency, and out task that function of the IT system.

The approach of out-tasking lets each business and IT team strategically architect a cloud infrastructure that is highly customized to meet their unique business challenges. With the out-tasking approach, IT leaders can solve specific issues without needing to manage unnecessary aspects of a cloud infrastructure, and it avoids incurring costs for applications and infrastructure that is not being used. Out-tasking lets businesses solve pain points simply to begin driving value and seeing return on investment more quickly.

Unique solutions to solve unique problems
Take, for example, a large retail brand eager to solve its business challenges using cloud technology. The first step was identifying its pain points, which in this case involved a few different areas. First was managing a mobile, millennial and highly innovative and flexible workforce; the solution was implementing a virtual desktop infrastructure. The retailer tweaked and customized this solution so it met their needs. From there, the IT team identified a second pain point - the need to store and manage large image files for their design and branding work. Once that challenge was identified, the company expanded its cloud infrastructure to include storage so they could better store and manage their images and branding content.

From there, the retailer needed to ensure its systems had the resiliency in place so the files their teams stored and the virtual desktop their global workforce relied upon was secure and built to run through any disaster. The team was able to implement a disaster recovery plan architected to meet their unique needs using BaaS to ensure its global workforce would have uninterrupted access to their virtual desktops, and that the images stored and shared were secure according to the highest compliance and regulatory standards. This gave the global retailer the assurance it needed to continue to migrate increasingly larger workloads onto the cloud.

In this example, the business took an approach more aligned with out-tasking as opposed to a sweeping transition to an outsourced model. The team did not start moving into the cloud by turning their entire infrastructure over to a company with a 10 year contract. One of the benefits of cloud technology is that companies can choose one service to meet one need. Companies can apply that technology, evaluate the return, adjust course as needed, and move on to solve the next challenge. In the case of the global retailer, out-tasking allowed the team to grow accustomed to the new solutions, and for the technology to be absorbed by company culture to ease disruption.

Ultimately, the most important thing is simply that IT leaders take the first step in their company's cloud journey. Identifying the most significant pain points helps create a vision for moving ahead with solving one business challenge at a time. After determining where to start, teams can apply the out-tasking approach to refine their technologies, minimize risk, and arrive at a solution that truly solves a business challenge, drives growth and delivers value.

More Stories By Chris Patterson

Leveraging his technical background and consulting skills, Chris Patterson was a key player in building NaviSite’s cloud computing platform, NaviCloud, from the ground up and is responsible for overseeing its continual upgrades and improvement making sure it meets customers evolving needs from both a technical and business perspective. In addition he oversees the development and implementation teams for NaviSite’s Desktop-as-a-Service and NaviCloud Intelligent Storage solutions.

Prior to joining NaviSite, Patterson spent nine years at MTM technologies as the Director of Information Security Services, where he gained extensive experience developing and consulting on security policies in a variety of different industries including financial, retail, legal, health care, and public sector. Chris holds a Bachelors of Science in nuclear engineering from Worcester Polytechnic Institute and currently lives in Delaware

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
Overgrown applications have given way to modular applications, driven by the need to break larger problems into smaller problems. Similarly large monolithic development processes have been forced to be broken into smaller agile development cycles. Looking at trends in software development, microservices architectures meet the same demands. Additional benefits of microservices architectures are compartmentalization and a limited impact of service failure versus a complete software malfunction. ...
Manufacturing has widely adopted standardized and automated processes to create designs, build them, and maintain them through their life cycle. However, many modern manufacturing systems go beyond mechanized workflows to introduce empowered workers, flexible collaboration, and rapid iteration. Such behaviors also characterize open source software development and are at the heart of DevOps culture, processes, and tooling.
Containers have changed the mind of IT in DevOps. They enable developers to work with dev, test, stage and production environments identically. Containers provide the right abstraction for microservices and many cloud platforms have integrated them into deployment pipelines. DevOps and Containers together help companies to achieve their business goals faster and more effectively. In his session at DevOps Summit, Ruslan Synytsky, CEO and Co-founder of Jelastic, reviewed the current landscape of...
SYS-CON Events announced today that JFrog, maker of Artifactory, the popular Binary Repository Manager, will exhibit at SYS-CON's @DevOpsSummit Silicon Valley, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. Based in California, Israel and France, founded by longtime field-experts, JFrog, creator of Artifactory and Bintray, has provided the market with the first Binary Repository solution and a software distribution social platform.
Conferences agendas. Event navigation. Specific tasks, like buying a house or getting a car loan. If you've installed an app for any of these things you've installed what's known as a "disposable mobile app" or DMA. Apps designed for a single use-case and with the expectation they'll be "thrown away" like brochures. Deleted until needed again. These apps are necessarily small, agile and highly volatile. Sometimes existing only for a short time - say to support an event like an election, the Wor...
The cloud has transformed how we think about software quality. Instead of preventing failures, we must focus on automatic recovery from failure. In other words, resilience trumps traditional quality measures. Continuous delivery models further squeeze traditional notions of quality. Remember the venerable project management Iron Triangle? Among time, scope, and cost, you can only fix two or quality will suffer. Only in today's DevOps world, continuous testing, integration, and deployment upend...
Sharding has become a popular means of achieving scalability in application architectures in which read/write data separation is not only possible, but desirable to achieve new heights of concurrency. The premise is that by splitting up read and write duties, it is possible to get better overall performance at the cost of a slight delay in consistency. That is, it takes a bit of time to replicate changes initiated by a "write" to the read-only master database. It's eventually consistent, and it'...
"Plutora provides release and testing environment capabilities to the enterprise," explained Dalibor Siroky, Director and Co-founder of Plutora, in this SYS-CON.tv interview at @DevOpsSummit, held June 9-11, 2015, at the Javits Center in New York City.
The most often asked question post-DevOps introduction is: “How do I get started?” There’s plenty of information on why DevOps is valid and important, but many managers still struggle with simple basics for how to initiate a DevOps program in their business. They struggle with issues related to current organizational inertia, the lack of experience on Continuous Integration/Delivery, understanding where DevOps will affect revenue and budget, etc. In their session at DevOps Summit, JP Morgenthal...
Explosive growth in connected devices. Enormous amounts of data for collection and analysis. Critical use of data for split-second decision making and actionable information. All three are factors in making the Internet of Things a reality. Yet, any one factor would have an IT organization pondering its infrastructure strategy. How should your organization enhance its IT framework to enable an Internet of Things implementation? In his session at @ThingsExpo, James Kirkland, Red Hat's Chief Arch...
Data center models are changing. A variety of technical trends and business demands are forcing that change, most of them centered on the explosive growth of applications. That means, in turn, that the requirements for application delivery are changing. Certainly application delivery needs to be agile, not waterfall. It needs to deliver services in hours, not weeks or months. It needs to be more cost efficient. And more than anything else, it needs to be really, dc infra axisreally, super focus...
Discussions about cloud computing are evolving into discussions about enterprise IT in general. As enterprises increasingly migrate toward their own unique clouds, new issues such as the use of containers and microservices emerge to keep things interesting. In this Power Panel at 16th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the state of cloud computing today, and what enterprise IT professionals need to know about how the latest topics and trends affect t...
DevOps tends to focus on the relationship between Dev and Ops, putting an emphasis on the ops and application infrastructure. But that’s changing with microservices architectures. In her session at DevOps Summit, Lori MacVittie, Evangelist for F5 Networks, will focus on how microservices are changing the underlying architectures needed to scale, secure and deliver applications based on highly distributed (micro) services and why that means an expansion into “the network” for DevOps.
Containers are changing the security landscape for software development and deployment. As with any security solutions, security approaches that work for developers, operations personnel and security professionals is a requirement. In his session at DevOps Summit, Kevin Gilpin, CTO and Co-Founder of Conjur, will discuss various security considerations for container-based infrastructure and related DevOps workflows.
Summer is finally here and it’s time for a DevOps summer vacation. From San Francisco to New York City, our top summer conferences list is going to continuously deliver you to the summer destinations of your dreams. These DevOps parties are hitting all the hottest summer trends with Microservices, Agile, Continuous Delivery, DevSecOps, and even Continuous Testing. Move over Kanye. These are the top 5 Summer DevOps Conferences of 2015.
Cloud Migration Management (CMM) refers to the best practices for planning and managing migration of IT systems from a legacy platform to a Cloud Provider through a combination professional services consulting and software tools. A Cloud migration project can be a relatively simple exercise, where applications are migrated ‘as is’, to gain benefits such as elastic capacity and utility pricing, but without making any changes to the application architecture, software development methods or busine...
Many people recognize DevOps as an enormous benefit – faster application deployment, automated toolchains, support of more granular updates, better cooperation across groups. However, less appreciated is the journey enterprise IT groups need to make to achieve this outcome. The plain fact is that established IT processes reflect a very different set of goals: stability, infrequent change, hands-on administration, and alignment with ITIL. So how does an enterprise IT organization implement change...
While DevOps most critically and famously fosters collaboration, communication, and integration through cultural change, culture is more of an output than an input. In order to actively drive cultural evolution, organizations must make substantial organizational and process changes, and adopt new technologies, to encourage a DevOps culture. Moderated by Andi Mann, panelists discussed how to balance these three pillars of DevOps, where to focus attention (and resources), where organizations migh...
At DevOps Summit NY there’s been a whole lot of talk about not just DevOps, but containers, IoT, and microservices. Sessions focused not just on the cultural shift needed to grow at scale with a DevOps approach, but also made sure to include the network ”plumbing” needed to ensure success as applications decompose into the microservice architectures enabling rapid growth and support for the Internet of (Every)Things.
Mashape is bringing real-time analytics to microservices with the release of Mashape Analytics. First built internally to analyze the performance of more than 13,000 APIs served by the mashape.com marketplace, this new tool provides developers with robust visibility into their APIs and how they function within microservices. A purpose-built, open analytics platform designed specifically for APIs and microservices architectures, Mashape Analytics also lets developers and DevOps teams understand w...