MIS603: Microservices Architecture Assessment - Detailed Report

This report provides a comprehensive analysis of microservices architecture, examining its principles, implementation, and challenges. It begins with an executive summary outlining the core concepts and benefits of microservices, emphasizing its role in modern software development. The report delves into the architecture's application in three prominent industries: Walmart, Spotify, and Amazon, detailing how each company successfully adopted microservices to overcome specific challenges and improve performance. The report then discusses the technical principles of service modeling and technologies, including XML-RPC, SOAP, and REST, highlighting their roles in facilitating communication and integration. Furthermore, it addresses the complexities of splitting a monolithic backend system, a crucial step in transitioning to microservices. Finally, the report considers the ethical, legal, and security implications of adopting a microservices architecture, providing valuable insights for businesses considering this transition.

Running head: MICROSERVICES ARCHITECTURE
MIS603 Microservices Architecture
Assessment 2
Microservices Architecture
Name of the Student
Name of the University
Author Note

1
MICROSERVICES ARCHITECTURE
Executive summary
This report is all about the architecture of the microservices which is the techniques of
development of software which is an architecture of the service orientation variant. It is basically
an architectural style. It basically deals with helping the companies to become strong in the areas
in which they lack. It operates on the basis of the communication which in turn is stateless in
nature. The most common example of the architecture of microservices can be the electronic
commerce. Most of the well- known companies that have been benefitted by the architecture of
the microservices are Amazon, Spotify as well as Walmart. The principles of REST, SOAP as
well as XML-RPC have also been taken into account.

2
MICROSERVICES ARCHITECTURE
Table of Contents
Introduction......................................................................................................................................4
Three industries with successful implementation of the microservice architecture........................4
Walmart...................................................................................................................................5
Spotify......................................................................................................................................6
Amazon....................................................................................................................................7
Discussion of the principles of service modelling and technologies...........................................8
XML-RPC................................................................................................................................8
SOAP.......................................................................................................................................9
REST........................................................................................................................................9
Challenges in splitting the backend monolithic system.............................................................10
Ethical, legal and security issues in the transitioning to microservices architecture.................11
Conclusion.....................................................................................................................................12
Recommendation...........................................................................................................................12
Data offloading:.........................................................................................................................12
Using ASP.NET:........................................................................................................................13
Monitoring:................................................................................................................................13
References......................................................................................................................................14

3
MICROSERVICES ARCHITECTURE

4
MICROSERVICES ARCHITECTURE
Introduction
This report deals with the concepts of microservices or the micro services architecture and the
examples of the architecture of the microservices which is implemented successfully. The report
also deals with the discussion of the various principles of the technologies as well as the
modelling of the services which are available for the purpose of the integration like the SOAP,
REST etc. [1]. Microservices which can also be termed as the microservices architecture are
techniques of development of software which is an architecture of the service orientation variant.
It is basically an architectural style. Here, an application is structured in the form of a collection
and the collection consists of the services that are loosely couple in nature. The protocols are of
light weight as well as the services are finely grained in an architecture of micro services. The
collection of services are testable and highly maintainable too [2]. The collection of the services
is deployable independently which in turn are organized around the capabilities of the business.
The microservices architecture is very important and is always needed because it helps in
maximization of the velocity of deployment as well as the reliability of the application by the
process of helping an individual in order to move at that particular market speed [3]. As each and
every applications run in the environment of their own which in turn is containerized in nature
and all the applications without altering their own environment can be moved and possess the
tendency to be moved at any place.
Three industries with successful implementation of the microservice
architecture
There are many companies that got benefitted from the architecture of micro services
brought to them. There are several numbers of examples of industries that describe the successful

5
MICROSERVICES ARCHITECTURE
implementations of the architecture of the microservices. The examples of three such companies
and the challenges that were faced by these companies in the microservices implementation are
also mentioned as follows:
Walmart
With the help of the architecture of the microservices, the company Walmart was able to
revitalize the failing architecture of it. In case of Walmart, the problem was it was not able to
handle the pageviews which per minute counted up to a number which was equal to six billion
[4]. These large numbers of the pageviews had made the system of the company next to
impossible to retain or to keep any sort of positive kind of the user experience any further in days
followed by [5]. Walmart consisted of an architecture which comprised for the connection of the
networks of the year 2005 which in turn were designed all around the laptops, desktops as well
as the monoliths.
In the year 2012, this company made a decision to replat form the legacy system because
the legacy system was very old and also because it was not able to scale up for the pageviews as
the whooping amount of pageviews per minute was equal to six billion [6]. It was also not up for
the peak events that took place for most part of the days. They were planning for making four
billion people whom would remain connected as well as they were planning for the availability
for over twenty-five million applications as they were planning to take the preparation and get
ready to cope up with the world by the year2020.
Hence, according to the prepared plan the company replat formed to the architecture of
microservices keeping the intention in mind of achieving the goal with a closure of hundred
percent costs being reasonable as well as same in case of the availability. When the company
migrated to the architecture of microservices, notable results were witnessed.

6
MICROSERVICES ARCHITECTURE
These notable results includes the conversions which were literally upgraded overnight
by twenty percent. The orders of the mobile were instantly upgraded by 98%. This saw followed
by cancellation of downtime that is there was no down time anymore on the eve of Boxing Day
or Black Friday [7]. Since the company totally moved off the hardware of their own that were
expensive too onto the hardware of commodity and there were significant saving of the
operations also. 40% of the power of the computing was saved and 20-50% cost of the savings
were experienced overall.
The above mentioned scenario is one of the best examples which in turn can be applied in
the situation where the architecture that is aging starts affecting the business in a negative
manner altogether.
Spotify
With the help of the microservices architecture, this company named Spotify was
successful in building outstanding experience of the users. The vice president of engineering at
Spotify, Kevin Goldsmith has a knowledge from his own experience an enterprise that stays
innovative in a market that is highly competitive intends to move faster also requires an
architecture which can scale also[8]. The company per month serves over 75 million users that
are active and on the average the length of the session is of 23 minutes and at the same time
complex business roles in an incredible way performed behind the scenes. Hence, the company
came up with the conclusion that if any user is worried in order to scale to uncountable of users ,
the individual builds a system in such a way that the users can independently scale all the
components as well [9]. This company built the architecture of the microservices with the help of
the teams that were fully stacked as well as autonomous which were in charge for the avoidance

7
MICROSERVICES ARCHITECTURE
of the hell of synchronization within that organization. There is no overlapping of the mission
among the various teams.
Following this process the company now has around 600 developers, 9 teams, 2
continents, 5 development offices who are concerned for building that same product. This is why
they always needed minimized dependencies to the best possible ways. The feature of the
architecture of the microservices that is really liked by Spotify is the microservices do not have
large failures as it commonly known that the big services fail at a very big scale and the vice-
versa that is small businesses fail at a very small scale [10].
Amazon
With the help of the architecture of the microservices, the company Amazon also embraced the
philosophy of DevOps. This company too has migrated to the architecture of the microservices.
A various number of applications call the company countless number of times and also includes
all sorts of applications that helps in managing the services of the web as well as the application
program interface as well as the it manages the web itself which would be next to impossible to
handle the old and two-tiered architecture as well [17]. Amazon.com is a retail website which
was a large architectural monolith. In multiple layers it was architecture and these tiers contained
multiple numbers of components within them but the behavior was like a single monolith were
very tightly coupled together.
One big monolith required a large number of developers and in spite of each of the
developers working on a very small piece of information, still there was a need of them to deal
with everyone regarding the overhead of the changes that were coordinating who were working
on the same project [18]. This particular change was never going to ruin as well as break

8
MICROSERVICES ARCHITECTURE
something else on that particular project was made sure whenever a new feature was added or
whenever any kind of bug fix were made.
They had to convince everyone in case they wanted to take advantages of new features
with the help of updating a library which can be a shared library also. They convinced everyone
on that particular project in order to upgrade themselves at that same time to a shared library that
is new [19]. In order to push out their own customers as soon as possible or if there was any need
to fix anything quickly, they were unable to perform that according to their schedule and in turn
was bound to coordinate with various developers at the same point of time who were there for
the changes that were processed.
The company went through the big changes on a level of architecture as Amazon went
through the application which was monolithic and converted into a service oriented architecture.
It also implemented the changes in the operations of it. After steps of operations, the front-end
development cycle of Amazon improved dramatically [20]. Hence, the decisions can be quickly
taken by the product teams and can crank out the fresh features for the microservices of their
own. After this phase, 50 million deployments were made by the company and all of this is
possible only because of the microservices.
Discussion of the principles of service modelling and technologies
XML-RPC
The principles of service modelling as well as technologies like SOAP, REST, XML-
RPC are in case XML-RPC what happens is RPC is performed by a client with the process of

9
MICROSERVICES ARCHITECTURE
sending a frequent that is related to http to that particular server that implements XML-RPC as
well as receives the response of the http. Multiple parameters can be present in a single call with
a single [17]. It is based on XML based protocol which is a very simple protocol that used for the
exchanging of information over a week between several computer systems. It is a call with a
remote procedure and which also uses XML for encoding the calls. This XML-RPC uses http for
the purpose of transportation.
SOAP
Both SOAP as well as REST allows in creating API of the individuals. SOAP is a
specification of the messaging protocol which is used in order to exchange the structured
information [18]. It provides with the layer of the message protocol of a protocol of the web
services which is a stack for the web services. The processing model of the SOAP defines the
rules for the processing of the SOAP.
REST
REST can also be termed as Representational State Transfer which is the architectural
style of the software and also defines a bunch of constraints which is to be used for the creation
of the services of the web [19]. The services of the web which conform to the architectural style
of the REST are also called as RESTful services of web which can also be abbreviated in the
form of RWS also provides with the interoperability on the internet between the various
computer systems. The principles of RESTful are the resources that are addressable.

10
MICROSERVICES ARCHITECTURE
Challenges in splitting the backend monolithic system
A monolithic system is a system software that have distinguishable aspects such as data
processing, output and input of data, interface of the user and error handling all these aspects are
interwoven and it does not consist of separate constituents in the architectural system [11].
Also, a monolithic system is a hardware system that is the processor of multi-core in the
electronic system of the company. An integrated circuit is developed integrating the components
of that monolithic system [14]. These types of systems consist of components that are
architecturally separated, therefore multi-core systems have discrete components till they stay on
single die.
Monolithic systems are large system of separate components, therefore, dealing these
system becomes hectic for many companies as a result splitting them into architectural style of
microservices become the ultimate option for the company [13]. In the splitting of these
monolithic systems, simple and small services come in the queue first and then drawn out to the
vertical capability services. The resultant services are large and independent of the persistent
monolithic. Rewriting of monolithic application into microservices involves repressive amount
of expansion effort of the overall system.
There are several challenged faced by the company in splitting the backend of the
monolithic system like automation is required for every small activity occurring in the
microservices, great visibility is required as the smaller components are of large numbers,
therefore identification and monitoring of problems should be automatic [15]. Then the
configuration management would be great challenge as the splitting would result in hundreds of
microservices across environments, debugging would be a great limitation in the microservices
as the developers have to look into multiple small components and address those problems

11
MICROSERVICES ARCHITECTURE
individually [12]. The arrangement of different tools, platforms, languages would increase as
wide variety of problems can occur.
Ethical, legal and security issues in the transitioning to microservices architecture.
As decomposition of monolithic application occur to convert it into microservices,
several security issues arise, the security structure for a monolithic application may not be same
for the microservices, therefore, providing security to all the separate components becomes an
issue for the company [17]. In the transition from monolithic application to microservices ethical
issues like originality of the monolithic application may disappear in the microservices, using
copy of the transformed microservices without acknowledging the first copy may affect the
redundancy of the original copy [16]. The occurrence of legal issues like illegal use of
microservices, such as without the permission of the company microservices are pirated and
renamed to utilize for other companies.

12
MICROSERVICES ARCHITECTURE
Conclusion
Thus, it can be concluded from the report that with the help of the architecture of the
microservices the big multinational companies like Amazon, Spotify, Walmart have made
themselves unbreakable in the market place. These architecture of microservices have helped
these companies to become giants in their own field. From helping Walmart to revitalize the
failing architecture to helping Spotify for succeeding in building the outstanding experience for
their users and last but not the least helping Amazon to embrace the philosophy of DevOps[6].
Moreover the various principles of the modelling of the services as well as technologies have
been discussed like the principle of the service modelling and technologies like REST, SOAP as
well as the principles of XML-RPC has also been discussed which are the messaging protocols
[20]. The architecture of microservices is the application of the electronic commerce which in
turn is developed using the microservices architectures. The presence of the microservices allows
this particular company in order to have numerous as well as large number of services down
without the knowledge of the users at the same time. The system is built by them along with the
assumptions of the failure of the services at all times. Moreover the microservices are mainly
focused on capability of the single businesses. The communication that takes place between the
microservices can be termed as the communication which is stateless. In case if the
communication is stateless what happens is each and every pair of the response as well as the
request is independent of each other.

13
MICROSERVICES ARCHITECTURE
Recommendation
Data offloading:
The vagaries and erratic traffic of the applications that are related to microservice, the accurate
data can be found. Moreover, it is not a time taking process. This is because the data is stored in
small parts can found within minutes and the data is achieved is accurate in nature. This is one of
the time saving processes. This is why it is beneficial for the big giants like Amazon, Walmart
etc. In future also this can be useful for many of the companies as well to maintain their position.
Naturally the catching system are becoming another service in the architecture of application.
Using ASP.NET:
Use of the ASP.NET Zero application as the Access API, as well as the front-end. This
Access API manages authorization, authentication. Use of the ASP.NET Zero application API
part as the base, for another API - the logic of own business, but developers need to re-route the
process of authentication, authorization part for using the above Access API.
Monitoring:
The decomposition of one monolithic application along with the insertion of the data
layer that is offloaded as well as caching for increasing the performance. The monitoring system
need to have the ability to capture the log information of the applications that will be created. All
of these data will be able to migrate a centralized database where the system will allow the
monitoring alerts to track the data event that are important.

14
MICROSERVICES ARCHITECTURE
References
[1] A. Balalaie, A. Heydarnoori and P. Jamshidi, Microservices architecture enables devops:
“Migration to a cloud-native architecture,” Ieee Software, 33(3), pp.42-52, 2016.
[2] D.Jaramillo, D.V.Nguyen and R. Smart2016, “ Leveraging microservices architecture by
using Docker technology” In SoutheastCon (pp. 1-5), IEEE,2016, March.
[3] C.M. Aderaldo, N.C. Mendonça, C. Pahl and P. Jamshidi ,Benchmark requirements for
microservices architecture research,In “Proceedings of the 1st International Workshop on
Establishing the Community-Wide Infrastructure for Architecture-Based Software Engineering”
(pp. 8-13), IEEE Press, 2017 May.
[4] M. Rahman and J. Gao, A reusable automated acceptance testing architecture for
microservices in behavior-driven development, In 2015 IEEE “Symposium on Service- Oriented
System Engineering” (pp. 321-325). IEEE, 2015, March.
[5] L. Sun, Y. Li, and R.A. Memon, An open IoT framework based on microservices
architecture, “China Communications”, 14(2), pp.154-162, 2017.
[6] N. Alshuqayran, N. Ali and R. Evans, A systematic mapping study in microservice
architecture, In “IEEE 9th International Conference on Service-Oriented Computing and
Applications (SOCA)” (pp. 44-51), IEEE, 2016
[7] K. Bakshi, Microservices-based software architecture and approaches. In “IEEE Aerospace
Conference” (pp. 1-8). IEEE, 2017.

15
MICROSERVICES ARCHITECTURE
[8] D. Guo, W. Wang, G. Zeng and Z. Wei, Microservices architecture based cloudware
deployment platform for service computing, In “IEEE Symposium on Service-Oriented System
Engineering (SOSE)” (pp. 358-363), IEEE, 2016.
[9] N. Viennot, M. Lécuyer, J. Bell, R. Geambasu and J. Nieh, Synapse: a microservices
architecture for heterogeneous-database web applications, “In Proceedings of the Tenth
European Conference on Computer Systems” (p. 21), ACM, 2015.
[10] T. Salah, M.J. Zemerly, C.Y. Yeun, M. Al-Qutayri, and Y. Al-Hammadi, The evolution of
distributed systems towards microservices architecture, In “11th International Conference for
Internet Technology and Secured Transactions (ICITST)” (pp. 318-325), IEEE, 2016.
[11] N. Dragoni, , S. Giallorenzo, A.L Lafuente, M. Mazzara, F. Montesi, R. Mustafin, and L.
Safina, Microservices: yesterday, today, and tomorrow, In “Present and ulterior software
engineering” (pp. 195-216), Springer, Cham, 2017.
[12] S. Alpers, C. Becker, A. Oberweis and T. Schuster, Microservice based tool support for
business process modelling, In “IEEE 19th International Enterprise Distributed Object
Computing Workshop” (pp. 71-78), IEEE, September 2015.
[13] G. Kecskemeti, A.C. Marosi and A. Kertesz, The ENTICE approach to decompose
monolithic services into microservices, In “International Conference on High Performance
Computing & Simulation (HPCS)” (pp. 591-596), IEEE, July, 2016.
[14] K. Bakshi, Microservices-based software architecture and approaches, In “IEEE Aerospace
Conference” (pp. 1-8), IEEE, March, 2017.
[15] S. Newman, “Building microservices: designing fine-grained systems”, " O'Reilly Media,
Inc." 2015.

16
MICROSERVICES ARCHITECTURE
[16] M. Osbakk, Architectural Design of Loosely Coupled Services: A Case Study, 2015.
[17] E. Wolff, “Microservices: flexible software architecture”, Addison-Wesley Professional,
2016.
[18] C. Tangmanee, Comparisons of Visit Behavior at Amazon. com between Purchase
Outcomes, “Knowing Enough to Be Dangerous: The Dark Side of Empowering Employees with
Data and Tools”, p.26.
[19] D. Abts, “Aufbaukurs Java: Client/Server-Programmierung mit JDBC, Sockets, XML-RPC
und RMI”, Springer-Verlag, 2013.
[20] M. Silva, M.R. Hines, D. Gallo, Q. Liu, K.D. Ryu, and D. Da Silva, Cloudbench:
Experiment automation for cloud environments. In “IEEE International Conference on Cloud
Engineering (IC2E)” (pp. 302-311). IEEE, March, 2013.