Microservice Architecture Report: Whiteboard's IT Transformation

This report examines microservice architecture, a software development approach that structures an application as a collection of loosely coupled services. The report focuses on the Whiteboard organization, a learning management system aiming to adopt microservices to improve its IT infrastructure. It explores the concept of microservices, contrasting them with monolithic architectures, and presents case studies of successful microservice implementations at Amazon, Uber, and Coca-Cola. The report also discusses principles of service modeling, including SOA, REST, and XML-RPC, and highlights the challenges of splitting a monolithic backend system. The report concludes with recommendations for Whiteboard's future technical involvement in microservices.

Running head: MICROSERVICE ARCHITECTURE
MICROSERVICE ARCHITECTURE
Name of the Student:
Name of the University:
Author’s Note:

1MICROSERVICE ARCHITECTURE
Executive Summary:-
Whiteboard is one of the most prominent students learning management organization in the
world. The chief technical officer of this organization is trying to install the microservice
architecture for better services. In this report are describing basic concepts of microservice
architecture and also deliver three organizations micro architecture adoption concept. Not only
that this report also provides some basic modeling principle which can be helpful for the
adoption of microservice architecture. The last part of this report recommends some concepts
which can be helpful for the whiteboard future technical involvement.

2MICROSERVICE ARCHITECTURE
Table of Contents
Introduction:-...................................................................................................................................3
Discussion:-.....................................................................................................................................4
Concept of microservice architecture:-........................................................................................4
Microservice architecture in AMAZON:-...................................................................................4
Microservice architecture in Uber:-.............................................................................................6
Microservice architecture in Coca-Cola:-....................................................................................7
Principles of service modeling and technologies available for integration:-...............................7
Challenges in splitting the monolithic backend system:-............................................................9
Conclusion:-...................................................................................................................................10
Recommendations:-.......................................................................................................................11
References:-...................................................................................................................................12
Appendix:-.....................................................................................................................................14

3MICROSERVICE ARCHITECTURE
Introduction:-
The microservice architecture is a developmental process that buildings and application
as a group of small autonomous facilities, demonstrated a commercial domain (Alshuqayran, Ali
& Evans, 2016). The supervisory standard of microservices is to construct an application by
splitting its commercial components in small facilities that can be operated and deployed
unconventionally from each other. The separation of distresses between facilities is termed as
service restrictions. Separate facilities may be secured to single teams, resources, and roadmaps.
Some instance service restrictions might be user verification and payment processing services.
Microservices fluctuate from inheritance software expansion practices in which all mechanisms
were pushed together. This report is mainly related to one organization named "Whiteboard."
It is a leading learning management system and student supplier, supporting over many
worldwide learners. The CTO of this organization decided to renovation its technology approach.
The administration of its IT distribution teams to confirm they deliver dependable learning
management structures to over 600 colleges and institutes throughout the world. The Method
whiteboard provides widely manage the whole student lifecycle, from student employment,
student registration, teaching fee payment, content management, and the qualification issuance
and certificate (Nadareishvili et al., 2016). For this reason, the technical department of CTO tries
to incorporate the microservice process, which is essential for their business benefit.
Microservices trust not just on the technical skill arranging to upkeep this perception but on a
business having the principles, know-how, and configurations in place for expansion teams to be
capable of accepting this model.

4MICROSERVICE ARCHITECTURE
Discussion:-
Concept of microservice architecture:-
It is one category of software architecture. The concept proceeds to this similar method
and extents it to the imprecisely coupled services. It can be positioning industrialized and
constant unconventionally. Each facility is responsible for separate charges and can link with
other facilities over a simple procedure to clarify a more important complex profitable problem.
There are exact standard features around financial ability, endpoint intelligence automatic
disposition, and reorganized regulator of languages and data (Krylovskiy, Jahn & Patti, 2015).
This organization, named whiteboard, have resolved their structural problem by accepting this
Microservices Architecture configuration. Instead of constructing a single monstrous, massive
application, the notion is to divide user application into a set of lesser, organized services.
In this report are describing three different organizations who are adopting this
architecture effectively. In modern times many organizations are accepting microservice
architectures. Amazon, Uber, and Coca-Cola three organizations are getting considerable
benefits to applying the microservice architecture.
Microservice architecture in AMAZON:-
This American based multinational organization emphasizes on cloud computing, e-
commerce, and artificial intelligence and digital streaming (Le et al., 2015). Previously, when
this organization was on a monolithic server, it was tough to forecast how to fulfill the
changeable traffic requests. As an outcome, this authority was bleeding cash, and most of the
server capability was misused during interruptions. Moving to the AWS cloud permitted
Amazon to scale when essential, decrease the number and period of outages and protect money.

5MICROSERVICE ARCHITECTURE
Microservice architecture permitted Amazon to evolve to incessant disposition, and currently,
Amazon arranges code every 11.57 seconds.
Amazon applied microservices to streamline and reduce the pipeline. Breaking down
configurations into solitary applications acceptable developers to comprehend where the
obstructions were, what the atmosphere of these stoppages was, and permitted developers to
reconstruct them as a facility oriented construction, every with a small group devoted to one
specific service (Pahl & Jamshidi, 2016). What ongoing such a cleanup of the structure ended up
as a development of one of the prominent online companies in contemporary architecture. Along
with this modification, Amazon concreted the technique for other businesses and unconstrained a
sequence of open-source explanations, like AWS, that are currently universal (Villamizar et al.,
2015). The services decoupling enabled the formation of one of the initial computerized
deployment structures, and the model for plenty of what Amazon proposes clients today. It
assisted present the pipeline structure to the Amazon culture, and it is perhaps here in the
meeting that Brigham sensibly applied some optional editing, because that procedure could not
have been unpretentious.
A standard method to decrease working efforts for distribution is a container-based
arrangement. Container machinery like Docker7 has augmented in reputation in the previous few
years due to paybacks like productivity, portability, and effectiveness. The learning curvature
with containers can be vertical, and the user has to think about safety fixes for their Dockers
pictures and monitoring. Amazon ECS8 and Amazon EKS9 remove the necessity to install,
activate, and scale user individual cluster management setup (Bogner & Zimmermann, 2016). In
the background of microservices architectures, incident sourcing allows decoupling several parts
of use by applying a publish decoration, and it feeds the similar event documents into different

6MICROSERVICE ARCHITECTURE
information models for isolated microservices. Event tracking is typically applied in combination
with the CQRS decoration to decouple from writing optimize and workload both for
presentation, scalability, and safety. In traditional information management structures,
instructions and questions are run against the same data source.
Microservice architecture in Uber:-
Uber also a very renowned organization, and they decided to pause its monolithic
architecture into several codebases to construct a microservice architecture. The critical
modification that people observe here is the outline of API Gateway over which all the
passengers and drivers are linked. From the API Gateway, all the core points are linked like
traveler management, trip management, and driver management (Rademacher, Sachweh &
Zündorf, 2017). For instance, the people all see that the number of persons searching for taxis is
more reasonable more than the persons actually reserving a cab and creating payments. This
becomes the user an implication that the quantity of processes functioning on the traveler
management microservice is more than the number of procedures functioning on payments.
The uber authority explained this difficulty by necessitating that authors of first facilities
submit a command request a high-level application of the innovative facility that sketches its
determination, construction, dependencies, and other application facts for the break of Uber
Engineering to converse. With different engineering groups at Uber functioning on
interoperating facilities, it's significant to confirm that their mass can both securely roll out
innovative changes and consistently separately recycle parts of the construction (Savchenko,
Radchenko & Taipale, 2015). These functionalities permit high originator velocity and rapid
release reversal times, giving the user the flexibility to construct on autonomous schedules while
still thoroughly filling service level contracts. This architecture helps users realize a variety of

7MICROSERVICE ARCHITECTURE
purposes on a simple microservice stack, counting a better-quality incorporation analysis
framework, shadow traffic routing, replaying and recording traffic, hermetic repetition of live
traffic for investigation, capacity development, realistic performance calculation, and even
running several product outlines at once.
Microservice architecture in Coca-Cola:-
Coca Cola's International IT group has decided to control microservices and APIs to
realize that objective, and progressively substitute their legacy software. In this circumstance, a
rapid modification would be difficult due to several solutions executed universally. The business
knew that there are several techniques to apply microservices and, in conclusion, has decided to
move near an innovative architecture applying the Dev-Ops structure (Messina et al., 2016).
Inside it, they have presented a structure distributed into a particular application, with which they
can locate any issues which arise concerning agility and speed. On the other side, GIT formed a
library of returnable modules prepared into domains that are accessible to all objects in the
collection. Thanks to the stand of ready-to-apply facilities, projects through the business, and
those of outside partners, can be executed in a shorter time and with a lesser cost.
Principles of service modeling and technologies available for integration:-
SOA: -
One of the most exciting new information systems operational methods in information
technology to come along is SOA. The appearance of the SOC example and Web service
knowledge, in specific, has produced a massive interest in SOA. As governments grow and
develop more difficult, clients make better demands of their commercial functions and
prototypes. Administrations have repeatedly improved and extended their IT structures more and

8MICROSERVICE ARCHITECTURE
more as evidence has become accessible in electronic formation. SOA actions focus on
theorizing new techniques of functioning by emerging practical application situations that
constructed on and exploit standing information methods and networking knowledge.
Rest:-
It is a client-server construction. The customer and the server both have a different set of
apprehensions. The server supplies or operates evidence and creates it accessible to the operator
in an effective manner. The consumer takes that evidence and shows it to the operator to perform
successive needs for evidence. This separation of apprehensions permits both the customer and
the server to progress individually as it only needs that the border stays similar. This process
delivers an identical boundary between apparatuses. This abridges architecture, as all
mechanisms follow similar rules to express to one other. It also creates it easier to realize the
connections between the altered system components. Several constraints are compulsory to
accomplish this.
REST is a closed system. Separate components cannot see outside the instantaneous layer
with which they are interrelating. This defines that a customer linking to an intermediate
element, like a proxy, has no information on what lies outside. This permits mechanisms to be
autonomous and thus effortlessly expendable or extendable. This is elective, but because the
customer may be unable to run or download this code, and so a REST module cannot trust on it
being implemented.REST optionally delivers on-demand code. It may be copied to spread
customer functionality. The data arrangement of an illustration is also identified as the media
category. Individual media types are envisioned for the shortest version to the operator, while
others are envisioned for automatic handling. The media category is a critical factor in the REST
construction.

9MICROSERVICE ARCHITECTURE
XML-RPC:-
A server or client system, RPCs have usually been actions named in command on one
machine that goes through the network to a particular RPC server that essentially apparatuses the
named process. The RPC server packages up the consequences of the process and directs those
consequences back to the visitor. The calling sequencer then remains implementing. Whereas
this system necessitates a proportion of upstairs and latency, it also permits less influential
machinery to access great powered sources (Namiot & Sneps-Sneppe , 2014). It also permits
presentations to harness the computational influence of a machine network. XML-RPC is
constructed on hypertext protocol, and, like regular Web traffic, its displaced discussions are of
the appeal and reaction variety. There is nothing built-in maintenance for dealings or encryption.
The other significant detail to recall is that XML-RPC has a limited set of data types. Customer
procedure opinions and auditor return ideals are charted in a non-extendable XML subsection.
Challenges in splitting the monolithic backend system:-
One of the significant disadvantages of moving from a particular application platform to
many is an essential rise in application difficulty. The "whiteboard" now have to fear about
several small uses as an alternative of one. Certification will also have to protect the new
facilities as well as integration opinions. Test strategies and the program will take to cover both
the lesser facilities as well as a packed integration test strategy every time authority operate their
services. The technical obligation will also rise meaningfully, and calculated determinations
must be prepared to make sure all team possessions understand the lesser facilities that power
organization applications.
All investors and designers must "buy-in". From customer to team associates, the
organization should make guaranteed that everybody involved trusts microservices are the

10MICROSERVICE ARCHITECTURE
precise way to progress. Immigration is the most involved procedure and might delay innovative
feature rollouts. Conservation may undergo, and formerly fixed bugs might be re-introduced
when drifting user applications. Continuous deterioration analysis is required (Taibi, Lenarduzzi
& Pahl , 2018). It needs a comprehensive shift of concept when it originates from system
architecture, and several people will not take a proposition that things are not easy as well. Make
this organization team companions and shareholders are conscious of the increased budget of
repairing after moving. One of the first disadvantages of the monolithic system is that if anybody
facility fails, it leads to the complete system letdown. A user wants to adjust the complete
operating system. Safety issues are continuously there because there is no separation among
several servers existing in the kernel. So, the organization will have to continue both the
microservices and monolithic until monolithic vanishes altogether; this is the main challenge the
organization will face, and they should have approached how they will maintain, for instance, the
outdated database and the fresh one.
Conclusion:-
Microservices are appropriate for extensive-scale applications. Reduced apps are
typically improved off with a monolithic command base. Although it’s easier to progress and
continue autonomous microservices, network management needs extra efforts. Container stages,
Dev Ops applies, and cloud computing can support a lot in accepting this architecture. This
report develops the case study of "whiteboard," which is the learning management organization.
This organization is trying to move its monolithic systems to microservice architecture.
In the previous time, many organizations are trying to launch this architecture and also
get huge business profit. In this report, the writer is describing three different organizations
named uber, amazon, and Coca-Cola, which are adept at the microservice architecture. Not only

11MICROSERVICE ARCHITECTURE
that in this report are also develops certain modeling principles which should be helpful to adopt
these organization's microservice architecture. In the final section develops some challenges
which are mostly affected any organization. If the organization is implementing this
microservice architecture, then they should avoid these challenges.
Recommendations:-
This report writer is recommending some advice, which is important for "Whiteboard."
One significant part of this architecture is that the budget for public concerns, like safety and
observe, must be shared by the entire organization. Taking each team build these possessions on
their individual will be very expensive. This report recommends that there must be more than a
one sustained platform from which every team can choose the one most appropriate for their
facilities. It must be treated with carefulness and a lot of frank approximation because it's a
dissimilar approach associated with adopting microservices from a group viewpoint.

12MICROSERVICE ARCHITECTURE
References:-
Alshuqayran, N., Ali, N., & Evans, R. (2016, November). A systematic mapping study in
microservice architecture. In 2016 IEEE 9th International Conference on Service-
Oriented Computing and Applications (SOCA) (pp. 44-51). IEEE.
Bogner, J., & Zimmermann, A. (2016, September). Towards integrating microservices with
adaptable enterprise architecture. In 2016 IEEE 20th International Enterprise Distributed
Object Computing Workshop (EDOCW) (pp. 1-6). IEEE.
Krylovskiy, A., Jahn, M., & Patti, E. (2015, August). Designing a smart city internet of things
platform with microservice architecture. In 2015 3rd International Conference on Future
Internet of Things and Cloud (pp. 25-30). IEEE.
Le, V. D., Neff, M. M., Stewart, R. V., Kelley, R., Fritzinger, E., Dascalu, S. M., & Harris, F. C.
(2015, July). Microservice-based architecture for the NRDC. In 2015 IEEE 13th
International Conference on Industrial Informatics (INDIN) (pp. 1659-1664). IEEE.
Messina, A., Rizzo, R., Storniolo, P., Tripiciano, M., & Urso, A. (2016, September). The
database-is-the-service pattern for microservice architectures. In International
Conference on Information Technology in Bio-and Medical Informatics (pp. 223-233).
Springer, Cham.
Nadareishvili, I., Mitra, R., McLarty, M., & Amundsen, M. (2016). Microservice architecture:
aligning principles, practices, and culture. " O'Reilly Media, Inc.".
Namiot, D., & Sneps-Sneppe, M. (2014). On micro-services architecture. International Journal
of Open Information Technologies, 2(9), 24-27.

13MICROSERVICE ARCHITECTURE
Pahl, C., & Jamshidi, P. (2016, April). Microservices: A Systematic Mapping Study. In CLOSER
(1) (pp. 137-146).
Rademacher, F., Sachweh, S., & Zündorf, A. (2017, April). Differences between model-driven
development of service-oriented and microservice architecture. In 2017 IEEE
International Conference on Software Architecture Workshops (ICSAW) (pp. 38-45).
IEEE.
Savchenko, D. I., Radchenko, G. I., & Taipale, O. (2015, May). Microservices validation:
Mjolnirr platform case study. In 2015 38th International convention on information and
communication technology, electronics and microelectronics (MIPRO) (pp. 235-240).
IEEE.
Taibi, D., Lenarduzzi, V., & Pahl, C. (2018). Architectural patterns for microservices: a
systematic mapping study. SCITEPRESS.
Villamizar, M., Garcés, O., Castro, H., Verano, M., Salamanca, L., Casallas, R., & Gil, S. (2015,
September). Evaluating the monolithic and the microservice architecture pattern to
deploy web applications in the cloud. In 2015 10th Computing Colombian Conference
(10CCC) (pp. 583-590). IEEE.

14MICROSERVICE ARCHITECTURE
Appendix:-
Amazon microservice model

15MICROSERVICE ARCHITECTURE
Uber micro service Architecture