603 ASSG 1 MICRO SERVICES

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 1 RESOURCES AND ACTIVITIESMODULE 3 TOPIC 1 RESOURCES AND ACTIVITIES

What is DevOps

Introduction:

Newman (2015, p. 192) discusses the concepts inherent in Conways’ Law and how the

structure of organisations can be either tightly or loosely bounded. As microservices

architecture focuses on loosely coupled services, a tightly bounded organisational

structure may need to be rethought to allow the full bene�ts of microservices to be

achieved. So, why are we focussing on DevOps?

In Nadareishvili et al. (2016, p. 92) they make the following assertion:

’Microservice architecture is leveraging the most advanced achievements in DevOps

and continuous delivery, making the bene�ts of the architectural style available and

cost e�ective to much wider audiences than just a handful of large early adopters….’.

From this statement it is clear the DevOps is considered the compatible ‘how to do

things’ alongside the ‘what things to do’ of microservices and its architecture. While it

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

is not imperative to do one to achieve the other, there is substantial information in

the literature about how the synergies that can be achieved via combining these

philosophies and their methods delivers exponential improvement in delivery

capability.

Part of the bene�ts identi�ed in adopting a DevOps approach relates to challenging

the ways monoliths have echoed organisational structure and how rigid this makes

them for developing and deploying new functionality and code. The view is that by

adopting DevOps, a nimbleness is unlocked which then allows microservices

architecture to reach its true potential.

So, what is DevOps? How is it de�ned?

Wicketts and Mueller (2016) discuss the fundamentals of what DevOps aims to

achieve via a continuous delivery pipeline and we can see how Nadareishvili et al.

(2016) can align microservices architecture and DevOps. Sharma’s ‘The DevOps

Adoption Playbook’ o�ers good insights into the frustrations of developing and

deploying code in his ‘Rant of a Development Manager’ (2017, p. 1). This is a good

place to start on understanding what DevOps was in response to. As such, Sharma

places cycle time – the time from origination of a requirement until it is ready to be

deployed to a customer – and its minimisation at the core of DevOps objectives. And

to improve cycle time, he identi�es the capabilities of continuous integration and

continuous delivery as vital capabilities within DevOps practice. As represented by the

DevOps in�nity loop – DevOps is about enabling continuous delivery, via teams with

oversight over both code and systems, development and operations to achieve

seamless delivery via loosely coupled services with teams focused on a service within

a bounded context – a microservice with an architecture optimised for rapidly

deployment into a DevOps environment. Thus, our focus in the next module is on the

bene�ts that are achieved by both DevOps and microservices architecture by the

‘in�nity loop’ of continuous pipelines, integration and delivery.

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

Nadareishvili, I., Mitra, R., McLarty, M., & Amundsen, M. (2016). Microservice architecture: Aligning principles, practices, and culture. California, USA: O’Reilly. Retrieved from https://ebookcentral-proquest-com.ezproxy.laureate.net.au/lib/think/detail.action?

docID=4602504

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

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

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

Resources and Activities:

Conway’s Law and System Design

Please read pp. 191 – 199, where Newman explains the meaning of

Conway’s Law and how the communication structure can in�uence how

code may be built and how it creates relatively rigid structures which

impede speed and progress in shipping code. He then explains how these

impacts on adapting to communications pathways and identifying services

for which the team will have full ownership. This is ideologically consistent

with the principles of DevOps which sees continuous ownership of a service

over a service in both development and operations and how this reduces

delivery bottlenecks. This in�uences team structure along di�erent lines to

that for a monolithic service which would be broken up into components

instead of along the lines of a bounded context. The case studies are not

compulsory reading but will o�er you additional insights of value.

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=50 (https://ebookcentral-proquest-

com.ezproxy.laureate.net.au/lib/think/reader.action?

docID=1938300&ppg=50)

Ownership and Conway’s Law

Please watch the following video from DevOps foundations: Microservices

series:

2.Service readiness: Ownership and Conway’s Law (2m 28s)

Conway’s law re�ects how organisations which designs systems copy the

organisation’s communication structure and how this is not necessarily the

most �exible way to build services. It discusses how building services along

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

the lines of a bounded context, makes sense in that one team can be

responsible for all elements of that one service including building, testing,

deploying and monitoring that service to achieve speed of delivery. Thus,

moving to microservices architecture requires a shift in thinking in the

organisation. Please note how it identi�es that a shift to microservices

architecture is as much a shift of culture as a way of structuring services.

Reference:

Stone, L. (2019, February 27). Service readiness: Ownership and Conway’s

Law [Video �le]. Retrieved from https://www.linkedin.com/learning-

login/share?

forceAccount=false&redirect=https%3A%2F%2Fwww.linkedin.com%2Flearning%

foundations-microservices%3Ftrk%3Dshare_ent_url&account=56744473

(https://www.linkedin.com/learning-login/share?

forceAccount=false&redirect=https%3A%2F%2Fwww.linkedin.com%2Flearning%

foundations-microservices%3Ftrk%3Dshare_ent_url&account=56744473)

What is DevOps?

Please watch the following video in the DevOps series:

1.DevOps Basics: What is DevOps? (3m 27s)

As Wickett and Mueller discuss what DevOps is, you will start to see

parallels arise with the concepts you have covered in understanding the

concepts and bene�ts of microservices architecture. It becomes apparent

that DevOps structures teams to support the development and

operationalisation of services which are formed along the principles of

bounded contexts and microservices architecture – they work together

‘hand in glove’ to achieve the same goals. They discuss the bene�ts that

DevOps helps to achieve, and these too are compatible with the aims of

microservices architecture.

Reference:

Wickett, J. & Mueller, E. (2016, November 22). DevOps Basics: What is

DevOps? [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)

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

Rant of a Development Manager

Please read Chapter 1 DevOps: An overview – Rant of a development

manager (p.1). This is a very brief one-page reading to o�er you an insight

into the context and conditions to which DevOps arose in response.

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=35 (https://ebookcentral-proquest-

com.ezproxy.laureate.net.au/lib/think/reader.action?

docID=4789057&ppg=35)

Process and Tools, and Organization

Leading on from ‘The microservice system design model’ in Figure 3-1 (p.

27), DevOps is inherent in aligning Process and Tools, Organisation and

Culture components of the model. These 3 brief paragraphs serve as a lead

into further readings and have been included to help you follow the

associations as we delve deeper into these concepts.

Reference:

Nadareishvili, I., Mitra, R., McLarty, M., & Amundsen, M. (2016). Microservice

architecture: Aligning principles, practices, and culture. California, USA:

O’Reilly. Retrieved from https://ebookcentral-proquest-

com.ezproxy.laureate.net.au/lib/think/reader.action?

docID=4602504&ppg=43 (https://ebookcentral-proquest-

com.ezproxy.laureate.net.au/lib/think/reader.action?

docID=4602504&ppg=43)

Culture

Wickets and Mueller (2016) identify a change of culture as vital for the

success of DevOps. This aligns to this reading from Nadareishvili et al.

(2016, pp. 54-57) which focuses on the required culture and

communications required for fostering of innovation.

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

Reference:

Nadareishvili, I., Mitra, R., McLarty, M., & Amundsen, M. (2016). Microservice

architecture: Aligning principles, practices, and culture. California, USA:

O’Reilly. Retrieved from https://ebookcentral-proquest-

com.ezproxy.laureate.net.au/lib/think/detail.action?docID=4602504

(https://ebookcentral-proquest-

com.ezproxy.laureate.net.au/lib/think/detail.action?docID=4602504)

De�ning DevOps

Sharma ponders the de�nition of DevOps and re�ects on two de�nitions.

However, he does not arrive at a hard and fast de�nition, rather a number

of key points that once again reference philosophical points: replacement

of software development method by culture or practice; the importance of

deployment automation and an advance on the original software

engineering goal of rapid development of software to ‘building, testing, and

releasing software which can happen rapidly, Frequently and more reliably’.

It is of interest that in all the novel ways of working that less emphasis is

placed in the method, and more emphasis is placed on achieving goals.

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=1 (https://ebookcentral-proquest-

com.ezproxy.laureate.net.au/lib/think/reader.action?

docID=4789057&ppg=1)

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.

DevOps delivers, but requires new skills – and a whole new mindset

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

This article is a brief explainer as to the shift in mindset to transition to a

DevOps way of working. Once the preserve of Unicorns like Spotify, Net�ix

and Etsy the bene�ts of DevOps are starting to attract attention by

mainstream IT departments regarding the bene�ts they can o�er but a

change of thinking is required to achieve a transition to this way of working.

Reference:

McKendrick, J. (2019, November 23). DevOps delivers, but requires new

skills – and a whole new mindset. ZDNet. Retrieved from

https://www.zdnet.com/article/devops-delivers-but-requires-new-skills-and-

a-new-mindset/ (https://www.zdnet.com/article/devops-delivers-but-

requires-new-skills-and-a-new-mindset/)

Learning Activity 1: DevOps and microservices - Discussion forum

post

Collaborative learning activity - Culture

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.