- 1 Cloud Service Delivery Models
- 2 Overview
- 3 DevOps
- 4 CICD
- 5 Blue/Green Deployment
- 6 A/B Deployments
- 7 Twelve-Factor Application
- 8 Semantic Versioning
- 9 Good Reads
- 10 Developing Applications for the Cloud
- 11 Microservices
- 12 Infrastructure as Code (IaC)
Cloud Service Delivery Models
With any of the delivery modes below, the provider controls and manages some portion of the technology stack. The customer manages the portion of the technology stack that is not managed by the provider. The benefit is that the customer controls the design of its portion of the stack.
- NIST definition of Cloud Computing http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf
The IaaS delivery model lets the user of the service to provision processing, storage, networking and other computing resources on which they can run O/S and applications. This includes the hardware and the virtualization layers. The service users do not control the underlying computing infrastructure except select networking configuration or perhaps the physical location of the resources at gross geographical level. On the other hand, they control - but they must install and manage - the operating system, the middleware and the application code. Infrastructure as a service is targeted at teams that are building out infrastructure.
Example: Amazon Web Service, IBM Cloud.
"Platform as a Service" describes an additional level of services layered on top of an infrastructure as a service foundation. These services include operating systems, database, middleware, etc. "Platform as a Service" are platforms for building and running custom applications, and are targeted at application development teams. The customer controls the design of the application, but the management of the platform stack is abstracted away. The customer can focus on functionality design and coding.
PaaS is also named "cloud application platform".
Example: OpenShift, Google app engine.
- Salesforce - What is PaaS? http://www.salesforce.com/paas/
- Netflix Adrian Cockcroft on Architecture for the Cloud http://www.infoq.com/interviews/Adrian-Cockcroft-Netflix
In this model, the software is the actual service offered on the web (salesforce.com, Intuit Quickbooks). The customer does not need to manage anything, but they also do not control anything, including the design of the application. This works well, unless the customer needs functionality that is not available in the application.
A collaborative process enabled by automation where application development, QA and Operations teams jointly accelerate delivery of new business application and services. DevOps emphasizes collaboration and cooperation.
Continous Integration (CI)
Continous Integration is a software development practice that involves the following:
- Verifies build integrity by checking if the source code can be pulled from repository and built for deployment. The build process may include compilation, packaging and configuration.
- Runs and validates the unit tests: executes all unit tests created by developers and validates the test results. This step insures that the source code was not broken as a side effect of the commit.
- Runs and validates the integration tests.
- Identifies problems and alerts the teams.
In the DevOps culture, CI is mandatory, and it performed automatically by a tool that runs automation scripts to eliminate all human intervention during the CI process.
The CI process requires a source code repository and a continuous integration server, that pulls code from the source repository and runs the build. Developers must check in as often as possible, every time a new piece of functionality that is verified by unit tests that pass is added. The build must be completely automated and must run without human intervention, and it must be fast.
Testing - especially the integration testing - must be done in an environment that is as close to production as possible.
The CI process provides rapid feedback on the state of the project, each unit test or integration test-verified assertion that gets broken by a commit is immediately shared with the entire development team. The process is run every time there's a commit, presumably many times a day. Every member of the team must be able to easily access the build results.
The build process should generate software that can be deployed at any time - a good release candidate.
Jenkins is a CI/CI engine.
SonarQube is a static code analysis tool.
Continous Delivery (CD)
Continuous delivery is a software development discipline where you build software in such a way that it can be released in production at any time.
CD best practices:
- version code and configuration
- version environment
- build binaries once
- automate everthing
- smoke test deployments
- deploy to all environments the same way
- create disposable environments
Continous Delivery Pipeline
A continous delivery pipeline is the automated expression of the process for getting software from version control through building, testing and deployment to the end users, in production. One tool that provides continuous delivery pipeline functionality is Jenkins.
Commit, Acceptance, UAT, Production.
Developing Applications for the Cloud
Infrastructure as Code (IaC)
Infrastructure as Code is an approach to IT systems infrastructure management, where various elements of the underlying hardware infrastructure are represented as programming constructs rather than physical hardware. This approach can be used in combination with automation tools to provide the ability to provision infrastructure in a repeatable and reliable manner.