Microservices Architecture: MIS603 Assessment 2 Report Analysis

This report, prepared for the MIS603 Microservices Architecture course, examines the transition of Whiteboard Company's learning system to a microservices architecture. It begins with an executive summary outlining the benefits of microservices, such as agile development and scalability. The report then delves into successful implementations at companies like UBER, Zalando, and Netflix, highlighting their experiences and the advantages gained from adopting microservices. It explores service modeling principles, including SOAP, XML-RPC, and REST, providing detailed explanations of each. The limitations of monolithic architecture are discussed, along with the challenges associated with microservices. The report concludes with recommendations for Whiteboard Company and offers a comprehensive overview of microservices architecture.

Running head: MICROSERVICES ARCHITECTURE
MIS603
MICROSERVICE ARCHITECTURE
Assessment 2
06/04/2020
2500 words
Name of the Student
Student ID
Torrens email address
Name of campus learning facilitator
Name of Subject coordinator

1MICROSERVICES ARCHITECTURE
Executive Summary
Whiteboard Company wants to implement the strategy of Microservices architecture for their
learning system for ensuring the reliable services to their potential students. With the help of
“little and move approach”, they can move to their Microservices architecture from their
monolithic based systems. It provides agile development of the software. Microservices
adopts some concepts regarding the service oriented architecture. It gives lots of benefit to
the Whiteboard Company compared to their monolithic system. It helps the IT team of the
company to develop the software at a faster rate. It helps to provide scalable software
solutions to the company. This report gives a clear overview regarding the transition of the
Microservices architecture of Whiteboard Company.

2MICROSERVICES ARCHITECTURE
Table of Contents
Introduction................................................................................................................................3
Three Successful implementation of Microservices architecture..............................................3
Service modelling principles......................................................................................................8
Limitations of monolithic architecture.....................................................................................15
Issues of Microservices architecture........................................................................................16
Conclusion................................................................................................................................17
Recommendation......................................................................................................................17
References................................................................................................................................19

3MICROSERVICES ARCHITECTURE
Introduction
Microservices architecture is a procedure of designing software for deploying services
in independent manner (Pahl, Jamshidi and Zimmermann, 2020). It is totally based on the
single function module. It has some outstanding interfaces and some excellent operations. It
is a very popular technology among various companies because they want to implement
agility in the software. It is also very helpful for DevOps teams.
In this report, at first, successful implementation of Microservices architecture is
discussed elaborately (Perkusich et al., 2020). After that, it will discuss some service
modelling principles such as REST, SOAP, XML-RPC are discussed. After that, it will
discuss regarding the challenges of the monolithic system. At the end, it will discuss
regarding the issues related to the Microservices architecture. This report will discuss
regarding some recommendations of the Microservices architecture.
Three Successful implementation of Microservices architecture
There are lots of companies who are using Microservices for implementing the
software. Among three most successful companies are:
 UBER
Like any other companies, initially UBER developed their cab booking system
by using the monolithic architecture. It was developed for the single offerings inside a
single city. They had one code base (Putra et al., 2020). It was quite enough to resolve
their business related issues. After that, their business had stated increasing. At that,
they felt that monolithic architecture was not at all sufficient for running their
business.

4MICROSERVICES ARCHITECTURE
Figure 1: Monolithic architecture of UBER
Source: https://medium.com/edureka/microservice-
architecture-5e7f056b90f1
In this architecture, REST API is used for establishing efficient
communication among their cab drivers as well as passengers. In this case, three
adapters are used with the REST API (Qiu et al., 2020). It gives lots of facilities to the
passengers such as billing, payments, email forwarding and many others. These

5MICROSERVICES ARCHITECTURE
activities can be performed when a passenger is willing to book a cab for him or her.
They use MySQL as a database to preserve all the records.
But, these features of their cab booking system were found inside a single
framework (Ranjan & Sahoo, 2020). But, when they increased their business in
the entire world, then they faced lots of difficulties because they used monolithic
architecture while developing the cab booking system. Some difficulties are as
follows:
 All features of system required to be developed again
 Resolving of the bugs became very difficult while using the monolithic
architecture.
 Faced difficulty to enhance the scalability inside the cab booking system of
UBER.
For resolving these problems, they decided to migrate from monolithic
architecture to Microservices architecture (Rumiński & Walczak, 2020). For example,
if a passenger wants to change his or her billing services, then he or she need to
deploy only that service. He or she does not require deploying other services of those
services. All the features of that software are scaleable.

6MICROSERVICES ARCHITECTURE
Figure 2: UBER Microservices architecture
Source: https://medium.com/edureka/microservice-
architecture-5e7f056b90f1
UBER Company mainly modifies their API gateway. With the help of
this gateway drivers and passengers are able to perform effective communication
among them while booking a cab (Siavashi, 2020). In their new system, an individual
module performs individual services.

7MICROSERVICES ARCHITECTURE
 Zalando
Zalando applies their Microservices architecture with the help of Amazon
Web Services for the purpose of provisioning (Sorgalla et al., 2020).
Unfortunately, a tiny amount of technology is used within this architecture. They
perform scaling in their new applications. Name of their new software is STRUMS.
It is open source software. They had one magneto based application. But that
application was not able to tackle a huge amount of load. For that reason, they
required new software (Takase et al., 2020). They shifted from monolithic to
Microservices in 2015. That new software was designed by keeping a closer touch
with the structure of Zalando. It was also related to the business logic as well as
culture. IT and business team wanted a new idea for their software. After the shift,
they designed as well as a global system. They also designed a latest work culture for
their management. By using their independent group, they increased their rate of
productions as well enhanced the number of innovations. They used four eye policies
while developing their software.
 Netflix
Ten years ago, Netflix developed their Microservices based applications. The
special feature of this application is that, it can not be shred with each other. They
used an application programmable interface (Wang et al., 2020). It had some tightly
controlled procedures which could be tackled by any programs. It helped the software
developer to perform certain changes within the software to ensure that it executed in
an efficient manner.

8MICROSERVICES ARCHITECTURE
The Company mentioned that they used around seven hundred Microservices
for every part of the Microservices architecture. One Microservices used to preserve
the videos watched by every user. Another service removed the monthly fee paid from
the authorised credit card of the user. They defined the Microservices for playing the
videos for the user (Siavashi, 2020). They wrote another service for the history and
guessing the available movies within the Netflix application. IT team of the
company modifies a lot within the software of Netflix. They have the ability to
perform modifications of the software without hampering the ongoing services
offered by the Netflix.
Service modelling principles
 SOAP
It stands for Simple Object Access Protocol. It is not dependent on any
platform and it is a messaging protocol. It is based on the XML. It helps to transfer
data within the web services (Ranjan & Sahoo, 2020). It has the ability to establish
connections to the client software with the remote servers. Main purpose of this web
services is to perform the remote procedure call. It contains four major elements.
These are as follows:
o Envelop
It helps to do the starting and ending of the SOAP messages.
o Header
It is not all a mandatory attribute in SOAP architecture. It is mainly
used for message processing (Rumiński & Walczak, 2020). It has a header
entry which is defined inside the namespace.

9MICROSERVICES ARCHITECTURE
o Body
Body of the message SOAP is entirely based on the XML. It can be
exchanged within the SOAP message (Putra et al., 2020). It is defined as the
child element. Semantics of the body is defined in the associated SOAP
schema.
o Fault
It is a mandatory element available inside SOAP (Marković &
Đorđević, 2020). It returns accurate information regarding the bugs involves
the predefined code, detailed description and addresses the SOAP processor
for calculating the outcome. It can carry one fault block. It is considered as an
optional part of the SOAP message. SOAP fault is associated with 500 to 599
ranges of status codes.
There are many advantages of SOAP web services. These are as follows:
 SOAP uses XML based data for the purpose of payload as well as
contract (Madampe, Hoda & Singh, 2020). So that it can be easily fit
with any type of technologies.
 It is accepted in the entire world. For that reason, it is considered as an
approach related to the industry standard. That is why; it is mainly use
in any type of open source applications offered by any organisation.
 It is a light weight protocol (Houmani et al., 2020). It is used for the
exchange of data among various types of applications offered by
different companies.

10MICROSERVICES ARCHITECTURE
There are some drawbacks of the SOAP based web services. These are as
follows:
o Only XML based protocol is used in SOAP web services (Araújo et al., 2020).
Other protocols such as JSON and other protocols are not used in this SOAP
web services.
o SOAP only uses the WSDL, but does not have any other procedure for using
these services.
Figure 1: SOAP web services
Source: https://medium.com/@dilshanramesh81/soap- web-
services-c62940e0de93
 XML-RPC

11MICROSERVICES ARCHITECTURE
It is a very simple version of the XML based protocol. It is used to shift the
information among the computers. It helps the computer programs to apply functions
in an efficient manner (Bora & Bezboruah, 2020). It helps the HTTP protocol for
shifting of information from one computer to another. A small XML vocabulary is
present in the XML-RPC. It has the ability to describe many responses. It has
three different parts. These are as follows:
o XML-RPC data model
o XML-RPC response structures
o XML-RPC request structures
There are some basic data types for XML-RPC. These are as follows:
o int or i64
o base64
o double
o Boolean
o dateTime.iso8601
If the developer wants to integrate more than one computing applications then
XML-RPC is the important way to perform this one. But they do not share any kind
of complicated data structures (Grambow et al., 2020). If the developer works within
a single platform, then RPC procedure makes it very easy to establish connection
among the programs. These programs may have various data models.
This architecture gives reusable logic for easy access. Basic data types are
enclosed with value elements (Heeager & Nielsen, 2020). Strings can also be
enclosed with the value elements but it can remove the string elements. In XML-RPC,
arrays contain some sequential information.