603 ASSG 1 MICRO SERVICES
myeazyassignment
Module3a063X00001ZrEuZQAVPart3.pdf
6/3/2020 Laureate International Universities
https://laureate-au.blackboard.com/webapps/blackboard/content/listContent.jsp?course_id=_89956_1&content_id=_8971656_1&mode=reset 1/7
MODULE 3 TOPIC 2 RESOURCES AND ACTIVITIESMODULE 3 TOPIC 2 RESOURCES AND ACTIVITIES
The build, test and deploy process
Introduction:
No doubt, you will have seen the image of the DevOps in�nity loop – but what does
this image mean? Why is this a symbol of the revolution that is allowing developers to
ship code at a rate that is unheard of in the world of monoliths? How has the build,
test and deploy process been transformed to enable this? This symbol is a reference
to the nature of continual development inherent in DevOps, where the development
process is broken into smaller components to improve e�ciency and ensure
continual delivery. These principles can be found in both DevOps and microservices
where there is aligned thinking of how to build pipelines for continuous delivery and
continuous integration which tightly aligns practices to achieve rapid �re build, test
and deploy cycles which are then monitored for performance.
Sharma (2017) goes so far as to say that cloud-native apps are possible because of
the convergence of DevOps, microservices and containers (we will discuss containers
6/3/2020 Laureate International Universities
https://laureate-au.blackboard.com/webapps/blackboard/content/listContent.jsp?course_id=_89956_1&content_id=_8971656_1&mode=reset 2/7
in upcoming modules). Wickett and Mueller (2016) discuss how continuous
integration enables continuous delivery which in turn enables continuous
deployment. There are clear bene�ts of continuous delivery in terms of rapidly being
able to deploy code into a production environment, however this depends on good
practices in continuous integration to ensure that small incremental changes are well
integrated via the build, test and deploy process. Newman (2015) discusses both the
concepts of continuous delivery and continuous integration and how to build
pipelines that help those building micro services to achieve this. Unsurprisingly,
Sharma (2017) also discusses these concepts from the perspective of practice within
the world of DevOps. Once again, we see the convergence of concepts from
microservices architecture and DevOps in ensuring that code that has been built is
tested and can be successfully deployed in a manner that reduces errors and points
of failure – powered by the immediacy of an innate feedback loop that keeps code
‘always working’.
References
Newman, S. (2015). Building microservices: Designing �ne-grained systems. California, USA:
O’Reilly Media. Retrieved from https://ebookcentral-proquest-
com.ezproxy.laureate.net.au/lib/think/reader.action?docID=1938300&ppg=50
Sharma, S. (2017). The DevOps Adoption Playbook: A Guide to Adopting DevOps in a Multi-
Speed IT Enterprise, Indiana, USA: John Wiley & Sons, Incorporated. Retrieved from
https://ebookcentral-proquest-com.ezproxy.laureate.net.au/lib/think/reader.action?
docID=4789057&ppg=1
Wickett, J. & Mueller, E. (2016, November 22). What is DevOps? [Video �le]. Retrieved from
https://www.linkedin.com/learning-login/share?
forceAccount=false&redirect=https%3A%2F%2Fwww.linkedin.com%2Flearning%2Fdevops-
foundations%3Ftrk%3Dshare_ent_url&account=56744473
Resources and Activities:
Small + fast=better
Please watch the following video in the DevOps Foundation series:
5. Continuous Delivery: Small + fast = better (4m 55s)
This video outlines the top �ve bene�ts of continuous delivery: i) on every
code commit the application built automatically, ii) unit test are run and the
application is deployed into a production like environment, iii) acceptance
tests are automated, iv) code either passes or fails minutes after it is
checked in, and v) code is always in a working state with continuous
6/3/2020 Laureate International Universities
https://laureate-au.blackboard.com/webapps/blackboard/content/listContent.jsp?course_id=_89956_1&content_id=_8971656_1&mode=reset 3/7
delivery. Also pay attention to the relationships between continuous
integration, delivery and deployment. The reasons will prove to be
important in your major assessment so pause and understand these
reasons for adopting these practices.
Reference:
Wickett, J. & Mueller, E. (2016, November 22). Continuous Delivery: Small +
fast = better [Video �le]. Retrieved from https://www.linkedin.com/learning-
login/share?
forceAccount=false&redirect=https%3A%2F%2Fwww.linkedin.com%2Flearning%
foundations%3Ftrk%3Dshare_ent_url&account=56744473
(https://www.linkedin.com/learning-login/share?
forceAccount=false&redirect=https%3A%2F%2Fwww.linkedin.com%2Flearning%
foundations%3Ftrk%3Dshare_ent_url&account=56744473)
Continuous Integration Practices
Please watch the following video in the DevOps Foundation series:
5. Continuous Delivery: Continuous Integration Practices (3m 51s)
Please note the primary objective of continuous integrations, and the
bene�ts of this. Pay attention to the process which creates a fast feedback
loop should the build have a �aw. There are 6 practices that o�er you an
insight into sizing of code changes within continuous integration and how
you set culture for performance.
Reference:
Wickett, J. & Mueller, E. (2016, November 22). Continuous Delivery:
Continuous Integration Practices [Video �le]. Retrieved from
https://www.linkedin.com/learning-login/share?
forceAccount=false&redirect=https%3A%2F%2Fwww.linkedin.com%2Flearning%
foundations%3Ftrk%3Dshare_ent_url&account=56744473
(https://www.linkedin.com/learning-login/share?
forceAccount=false&redirect=https%3A%2F%2Fwww.linkedin.com%2Flearning%
foundations%3Ftrk%3Dshare_ent_url&account=56744473)
The Continuous Delivery Pipeline
Please watch the following video in the DevOps Foundation series:
6/3/2020 Laureate International Universities
https://laureate-au.blackboard.com/webapps/blackboard/content/listContent.jsp?course_id=_89956_1&content_id=_8971656_1&mode=reset 4/7
5. Continuous Delivery: The Continuous Delivery Pipeline (5m 13s)
Pay attention to the de�nition of what continuous delivery means. There
are 5 practices that enable the deployment of code changes to a production
environment, performing integration and testing synchronously. While you
do not need a speci�c understanding of these processes, understanding
how these processes operate and interact with each other will o�er you
valuable insights into how the continuous delivery pipeline e�ectively
functions.
Reference:
Wickett, J. & Mueller, E. (2016, November 22). Continuous Delivery: The
continuous delivery pipeline [Video �le]. Retrieved from
https://www.linkedin.com/learning-login/share?
forceAccount=false&redirect=https%3A%2F%2Fwww.linkedin.com%2Flearning%
foundations%3Ftrk%3Dshare_ent_url&account=56744473
(https://www.linkedin.com/learning-login/share?
forceAccount=false&redirect=https%3A%2F%2Fwww.linkedin.com%2Flearning%
foundations%3Ftrk%3Dshare_ent_url&account=56744473)
Continuous Integration
Please read pp. 123 -127. This will give you a clear idea on how continuous
integration relies on delivery by all their code into the integration stream as
per the cadence of the team. This is intended to ensure that while
developers may be working in isolation, that they understand that their
code is part of a continuous build which contributes to the overall
continuous integration of the broader team which is achieved through
team-wide cadence.
Reference:
Sharma, S. (2017). The DevOps adoption playbook: A guide to adopting
DevOps in a multi-speed it enterprise. Indiana, USA: John Wiley & Sons,
Incorporated. Retrieved from https://ebookcentral-proquest-
com.ezproxy.laureate.net.au/lib/think/reader.action?
docID=4789057&ppg=157 (https://ebookcentral-proquest-
com.ezproxy.laureate.net.au/lib/think/reader.action?
docID=4789057&ppg=157)
Continuous Delivery
6/3/2020 Laureate International Universities
https://laureate-au.blackboard.com/webapps/blackboard/content/listContent.jsp?course_id=_89956_1&content_id=_8971656_1&mode=reset 5/7
Please read pp. 128 – 138. Note how Sharma di�erentiates
between delivery and deployment – this is a key di�erentiation.
Delivery requires a speci�c type of deployment process and
depends on automation of key functions. Please note the section on p. 135
where the need for production-like environments is identi�ed as key to the
success of the build and test part of the process.
Reference:
Sharma, S. (2017). The DevOps adoption playbook: A guide to adopting
DevOps in a multi-speed IT enterprise. Indiana, USA: John Wiley & Sons,
Incorporated. Retrieved from https://ebookcentral-proquest-
com.ezproxy.laureate.net.au/lib/think/reader.action?
docID=4789057&ppg=162 (https://ebookcentral-proquest-
com.ezproxy.laureate.net.au/lib/think/reader.action?
docID=4789057&ppg=162)
A brief introduction to Continuous Integration
Please read pp. 103 – 104 and pp. 105 – 107. Pay attention to how Newman
introduces and explains the principles of continuous integration. Thereafter
progress to the section where Newman discusses how to map services. You
will see similarities to how Wickett and Mueller (2016) mapped services.
Reference:
Newman, S. (2015). Building microservices: Designing �ne-grained systems.
California, USA: O’Reilly Media. Retrieved from https://ebookcentral-
proquest-com.ezproxy.laureate.net.au/lib/think/reader.action?
docID=1938300&ppg=123 (https://ebookcentral-proquest-
com.ezproxy.laureate.net.au/lib/think/reader.action?
docID=1938300&ppg=123)
Build pipelines and Continuous Delivery
Please read pp. 107 - 108. You should note that both Newman (2015) and
Wickett and Mueller (2016) refer to Humble and Farley’s writing about
Continuous Delivery. Note how Newman explains how the process should
be undertaken and the value that it o�ers in modelling the entire path in
building quality software.
Reference:
6/3/2020 Laureate International Universities
https://laureate-au.blackboard.com/webapps/blackboard/content/listContent.jsp?course_id=_89956_1&content_id=_8971656_1&mode=reset 6/7
Newman, S. (2015). Building microservices: Designing �ne-grained systems.
California, USA: O’Reilly Media. Retrieved from https://ebookcentral-
proquest-com.ezproxy.laureate.net.au/lib/think/reader.action?
docID=1938300&ppg=127 (https://ebookcentral-proquest-
com.ezproxy.laureate.net.au/lib/think/reader.action?
docID=1938300&ppg=127)
Additional Learning Resources
If you would like to learn more about the topics covered in this module, here are
some additional resources. These resources will contribute to further develop
understanding of the topics covered. However, these resources are not essential
to complete this module or the assessments associated with this subject.
6 Steps to DevOps success
With all of the news of the bene�ts that DevOps and microservice
architecture o�er in driving new products to market by an exponential
increase in the deployment and delivery of code changes – and CIO would
be under pressure to examine what bene�ts this way of working o�ers.
This article is a quick explainer to help CIO’s understand some of the
elements that will be required to achieve DevOps success.
Reference:
Bertram, A. (2017, October). Six steps to DevOps success. CIO. Retrieved
from https://www.cio.com/article/3234105/6-steps-to-devops-success.html
(https://www.cio.com/article/3234105/6-steps-to-devops-success.html)
Learning Activity 1: Interactive Knowledge check
Learning Activity 2: Continuous Delivery Discussion forum post
Collaborative learning activity - Continuous integration
6/3/2020 Laureate International Universities
https://laureate-au.blackboard.com/webapps/blackboard/content/listContent.jsp?course_id=_89956_1&content_id=_8971656_1&mode=reset 7/7
Note: The Learning activities above are not part of summative/graded assessment;
however they are designed to prepare you for incremental graded assessment and
expand your learning.
These activities encourage a community learning experience between peers, and
provide opportunities for facilitators to o�er formative feedback, throughout a
module, to the student cohort.
