Microservices Architecture Report 2022

Running head: MICROSERVICES ARCHITECTURE
Microservices Architecture
Name of the student:
Name of the university:
Author Note

MICROSERVICES ARCHITECTURE
1
Executive summary
The report investigates the definition along with the introduction of the technology microservice
architectures for the case of Whiteboard, a leading company providing students and management
systems of learning. Apart from that, the examples of successful deployment of the innovation are
demonstrated here. Furthermore, the norms of service modeling and accessible tools to incorporate
like XML-RPC, REST, and SOAP are analyzed in this study. Additionally, the difficulties to
fragment the monolithic system at the backend in place of the noteworthy activities of Whiteboard’s
system are studied. Finally, the safety, permissible and moral complications to shift towards the
microservice architecture are assessed in this report.

MICROSERVICES ARCHITECTURE
2
Table of Contents
Introduction:..........................................................................................................................................2
Defining and introducing microservice architecture:............................................................................2
Discussion on successful deployment of microservice architecture at various companies:..................4
Discussion on various principle related to service technologies and modelling:..................................6
SOAP:................................................................................................................................................6
XML-RPC:........................................................................................................................................6
REST:................................................................................................................................................7
Problems in splitting backend monolithic system:................................................................................7
Ethical, legal and security problems while transitioning to the microservice architecture:.................8
Conclusion:............................................................................................................................................8
References:..........................................................................................................................................10

MICROSERVICES ARCHITECTURE
3
Introduction:
Whiteboard’s chief technology officer has decided to overhaul the strategy of technology and
managing the IT delivery teams. This is to assure that they deliver the dependable students and
management systems of learning of more than 600 universities and various institutions around the
globe. The following report demonstrates the definition along with an introduction to the
microservice architectures. The instance of the successful deployment of innovation is further
discussed in this study. Then, the principle of service modeling and available technologies to
integrate like REST, XML-RPC and SOAP and so on are evaluated. Further, the problems to split
the monolithic system at the backend representing the notable behavior of Whiteboard’s system are
investigated. Lastly, the security, legal and ethical problems to transition towards the microservice
architecture are evaluated.
Defining and introducing microservice architecture:
The microservice architecture also simply known as microservice, is a kind of distinctive
model. This is to develop the software systems trying to concentrate on developing the modules of
single-function having effective operations and interfaces. This trend has been growing popular in
recent days as the various enterprises have been trying more Agile and moving towards continuous
testing and DevOps. This has various advantages for the DevOps and Agile teams like PayPal
Twitter, Amazon, eBay and Netflix and various other tech businesses have come out from the
monolithic innovation toward the microservice architecture (Alshuqayran, Ali & Evans, 2016). This,
unlike the microservices, the monolithic application has been creating an autonomous and single
unit. It has been making changes to the application to become slow as that has been affecting the
total system. The changes done to the small area within the code are needed to deploy and build the
latest version of that software (Rademacher, Sorgalla & Sachweh, 2018). Again, the scaling of