CI Tools and Best Practices in the Cloud

Continuous Integration

Subscribe to Continuous Integration: eMailAlertsEmail Alerts newslettersWeekly Newsletters
Get Continuous Integration: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Continuous Integration Authors: Karthick Viswanathan, XebiaLabs Blog, Liz McMillan, Mehdi Daoudi, Automic Blog

Related Topics: Continuous Integration

Blog Feed Post

Cloud Native Enterprise – Vendor Capability Map

blueprintFor each solution guide we identify an associated ‘VCM’ – Vendor Capability Map.

This is an organized list of how vendor products enable increasing levels of organizational maturity, as defined within an overall Enterprise Cloud adoption program.

TRANSFORM Reference Documents

The overall adoption and transformation framework for Cloud Native capabilities is defined by a number of industry reference documents, including:

Cloud Native Maturity Model – Industry gurus have collectively defined a maturity model for Cloud Native Application Architectures and working practices.

Enterprise PaaS provides a foundation for these practices, and in their white paper A Practical Guide to PaaS the CSCC define a break down and analysis of this approach.

Microservices Continous Deployment

At its core the principle represents a shift to a new approach for software architecture and development, headlined by Microservices Continuous Deployment.

Keynote Case Study: Netflix

netflixNetflix offer the pinnacle case study for Microservices Continuous Deployment best practices, because they pioneered the design and then also released the enabling tools they built as open source software, enabling others to do the same.

One such example is Nike, also documented here as a case study, who adopted these components to also achieve a greatly improved continuous deployment capability. They describe making use of components like dynamic discovery with Eureka.

Indeed their case study highlights just how powerful the combination of Cloud and microservices can be – For example he explains how “scaling concerns do not cross functional boundaries”, meaning that capacity for one service can expand elastically without affecting any other services.

Pivotal : Cloud Foundry PaaS & Microservices – Netflix best practices

These are practices you can repeat on other Cloud platforms, like Cloud Foundry, a technology that enterprises like JP Morgan are adopting for their Enterprise PaaS strategy.

Pivotal offers a Cloud Foundry implementation, especially with a view to microservices, as they explain in Deploying a Microservices Architecture with Cloud Foundry, and describe how it can accelerate projects like new mobile applications.

This includes packaging of the Netflix open source modules built for running their microservices.

Cloudify – TOSCA orchestration of microservices

Martin Fowler describes how infrastructure automation is a key enabler of microservices:

“Many of the products or systems being build with microservices are being built by teams with extensive experience of Continuous Delivery and it’s precursor, Continuous Integration. Teams building software this way make extensive use of infrastructure automation techniques. This is illustrated in the build pipeline shown below.”

This highlights the role orchestration platforms like Cloudify from Gigaspaces can play.

In this blog Uri Cohen of their product team describes how some microservice scenarios will feature more complexity, in terms of also provisioning stateful applications and supporting components that aren’t microservices, such as a central data repository.

Uri explains Cloudify is a platform that can automate the provisioning of this increased complexity through the use of TOSCA open standards.

Apprenda

Apprenda introduce the Enterprise PaaS concept in an early white paper – Private PaaS explaining how it is introduced into the enterprise environment,

In this blog, CEO Sinclair Schuller says of the relationship between Enterprise PaaS and Microservices:

“Essentially, the smarts should be in the app components, and the communication between those components must be as simple as possible. Without that requirement, architectures will bloat and become monolithic. When asked, “How does your PaaS support microservices?” most enterprise PaaS vendors offer little more than deployment agility. While agility is an important piece of the puzzle, application bootstrap policies directly support both the smart-endpoints / dumb-pipes visionand the implementation of microservices.”

Microsoft Azure

Bob Familiar introduces microservices, discussing their architecture and outlining cloud deployment scenarios, exemplified by a live demo on Microsoft Azure. The Microsoft Academy also offers a webinar introduction – Exploring Microservices in Docker and Azure.

 

The post Cloud Native Enterprise – Vendor Capability Map appeared first on Cloud Best Practices.

Read the original blog entry...

More Stories By Cloud Best Practices Network

The Cloud Best Practices Network is an expert community of leading Cloud pioneers. Follow our best practice blogs at http://CloudBestPractices.net