603 ASSG 1 MICRO SERVICES

profilemyeazyassignment
Module2a063X00001ZrEuZQAV.pdf

6/3/2020 Laureate International Universities

https://laureate-au.blackboard.com/webapps/blackboard/content/listContent.jsp?course_id=_89956_1&content_id=_8971655_1&mode=reset 1/4

MODULE 2 INTRODUCTIONMODULE 2 INTRODUCTION

Service Design

Introduction:

In 2015, Rob Brigham, a Senior Product Manager for Amazon’s AWS spoke about

processes adopted to increase agility and reliability at Amazon’s re:Invent 2015

conference. Amazon had originally been a monolith – ’If you go back to 2001, The

Amazon.com retail website was a large architectural monolith,’ but Amazon ’noticed

that it took a long time for a code change to go from a developer check-in, to be

running in production where customers could use it.’

eBay CTO, Steve Fisher says that eBay runs more than 1000 microservices that

support front-end experiences via API’s.

In 2009, Net�ix started their transition to ‘the cloud’. Adrian Cockcroft was one of the

architects responsible for this pioneering change and discussed the drivers for this

transition – ’The whole architecture of what Net�ix does as a business is oriented

6/3/2020 Laureate International Universities

https://laureate-au.blackboard.com/webapps/blackboard/content/listContent.jsp?course_id=_89956_1&content_id=_8971655_1&mode=reset 2/4

around speed.” He states that the aim is to “remove friction from product

development” with “no hand o�s between teams’.

Kevin Goldsmith, Chief Technology O�cer for Spotify, speaks to the environmental

requirements that drive a need for microservices architecture at Spotify: ’a need to

scale to millions of users, support multiple platforms, handle complex business rules

and be competitive in a fast moving market by reacting quickly and out-innovating the

competition.’

Clearly these technology giants share some common business drivers which have

in�uenced how they engineer and architect software: a need to operate �exibly, at

scale, in a manner that is autonomous from other services so that changes can be

deployed independently without impacting any existing services. This allows for the

faster shipping of code allowing for speed and safety.

However, this does not just happen …

Whether software engineers �nd themselves developing architecture in a ‘green�elds’

environment, where they are building a new solution from scratch or if they are

transitioning services from existing monoliths, we have seen that the process to

achieve this needs to be well considered and deliberate to ensure that the full

bene�ts of a microservices architecture can be achieved.

In this module we will discuss some of the principles of service design, service

modelling and what is required to ‘split a monolith’. While it can be argued that

service design extends beyond the source code, to component interfaces like APIs

and data stores, these will be covered in depth when we examine integration and

communications.

References

Amazon Web Services. (2015, October 15). AWS re:Invent 2015: DevOps at Amazon: A Look at Our Tools and Processes (DVO202). [Video �le]. Retrieved from https://youtu.be/esEFaY0FDKc

GOTO conference. (2014, August 11). GOTO 2014. Speed & Scale: How to get there. Adrian Cockcroft. [Video �le]. Retrieved from https://youtu.be/BeNrVl2_nyI

GOTO conference. (2015, December 23). GOTO 2015. Microservices at Spotify. Kevin Goldsmith. [Video �le]. Retrieved from https://youtu.be/7LGPeBgNFuU

Knorr, E. (2016, March 7). What eBay looks like under the hood. Retrieved from https://www.infoworld.com/article/3041064/what-ebay-looks-like-under-the-hood.html

This Module will cover:

Module 2.1 – Designing services

6/3/2020 Laureate International Universities

https://laureate-au.blackboard.com/webapps/blackboard/content/listContent.jsp?course_id=_89956_1&content_id=_8971655_1&mode=reset 3/4

Module 2.2 – Splitting the monolith

This Module will help you achieve the following outcomes:

a) Undertake research to demonstrate an understanding of microservices and how they contribute to business process.

b) Discuss core concepts of microservices architecture within a context of a business case study and summarise the advantages and disadvantages of adopting microservices architecture.

c) Communicate the bene�ts of microservices architecture to a diverse stakeholder audience by addressing complex business needs and aligning strategies to business priorities de�ned by changing business requirements.

Time Management:

Your workload expectation is 20 hours for this module.

12 Week Delivery:

20 hours per module (two weeks): facilitated study: 3 hours / week. Personal Study: 7 hours / week.

3 hours facilitated study consists of attending class, responding to facilitator feedback.

You are to allocate 7 hours of personal learning. This includes essential time spent on pre-reading and viewing materials, assessment progression and learning activities.

Assessment Progression:

Assessment 1 – Part A is due at the end of Module 2.2 (Week 4). Please refer to the

assessment briefs in the assessment area for more detail.

Tasks to undertake in this module to prepare for Assessment 1 – Part A include:

All learning activities that form part of Module 2.1 and 2.2

Viewing the learning resources that have been included in essential resources

Completing the readings in essential resources

Reviewing items in additional resources – while they are not essential, they will o�er you context base insights which will allow you to develop thinking that will prepare you to understand contemporary industry and workplace challenges.

6/3/2020 Laureate International Universities

https://laureate-au.blackboard.com/webapps/blackboard/content/listContent.jsp?course_id=_89956_1&content_id=_8971655_1&mode=reset 4/4

Class Expectation:

You are expected to have worked through the essential learning resources and activities for this module before attending the facilitated session (face to face or online session) – this enables informed discussion and full participation in learning activities.

Participate in all scheduled facilitated sessions.

This time is intended to be used by you and your learning facilitator to work through activities and engage in discussion about the module content.

These sessions provide a space for you to raise questions about the module content and seek guidance on writing your assessments.

You will review, explore and discuss more deeply the information presented in the learning resources.