Microservices Architecture: Benefits, Challenges, and Implementation

This report provides a comprehensive overview of microservices architecture, a modern approach to software development that contrasts with monolithic architectures. It begins with a definition and introduction to microservices, emphasizing its role in creating loosely coupled, independently deploy...Read More

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

1MICROSERVICES ARCHITECTURE
Executive Summary
Microservices architecture is the latest development in the business environment about the
primary principles that has certainly replaced the monolithic development procedures which
was primarily followed previously for developing any application. The agile and easy to build
smaller modular units for microservice architecture was easily accepted by different business
environment as they wanted to protect the business organisations from facing down times or
poor reliabilities. This is why it has been found that various modern business has been
accepting the microservices architecture since the four reliability can have a negative impact
on the business environment in achieving long-term success. Therefore, the following report
would be e based upon the detailed structure of the microservice architecture and all the
information regarding the successful implementations in different business organisations
about the development architecture. it would also have the benefits and challenges along with
the ethical, security and legal issues while the development of the services.

2MICROSERVICES ARCHITECTURE
Table of Contents
Introduction................................................................................................................................3
A definition and introduction to microservice architecture...................................................3
Examples of successful implementation of microservice architecture..................................5
Benefit of the microservice architecture................................................................................6
The challenges faced in the implementation of microservice architecture............................7
Principles of service modelling and technologies available for integration..........................9
Challenges in splitting the backend monolithic system that represent substantial amount of
the behaviour of the Company’s system................................................................................9
Ethical, legal and security issues in the transitioning to microservice architecture.............10
Conclusion................................................................................................................................10
References................................................................................................................................12

3MICROSERVICES ARCHITECTURE
Introduction
Microservices, or the word microservices architecture is also referred to as a
technique for developing a software which mostly is regarded as a variety of the service-
oriented architecture for a SOA. This variant service-oriented architecture which is regarded
as microservices is an architectural stride that has been developed for providing an
application with services that are loosely based on each other, but they are at a coupled
position (Balalaie, Heydarnoori & Jamshidi, 2016). This is a structure that is mostly made up
of the structure for development of several applications. it also abides by a collection of
different services that can be established as highly maintainable and testable loosely coupled,
independently deployable comma organised around the business capability as or even owned
by a small team. The report as it would be created as below would have all the requirements
about the general and detailed information about microservices architecture with several
points of introduction (Jaramillo et al., 2016). The report would have a formal definition and
introduction about the microservice architecture. It would also provide several examples of
successful implementation where microservice architecture has been presented in companies
consisting of various industries. It would also have a proper benefit of the microservice
architecture and also the challenges that has been faced with the implementation of
microservice architecture. report for the move to the principles of service modelling and the
technology that would be available for the integration of microservices architecture
(Aderaldo et al., 2017). The challenges in the splitting of the backend monolithic system
which would represent the substantial amount of the behaviour for company system would
also be described along with the ethical and legal and security issues that is positioned along
the transition meaning of the microservice architecture.

4MICROSERVICES ARCHITECTURE
A definition and introduction to microservice architecture
Microservices architecture can properly be defined as a distinctive method that is used
for the development of software system but it specifically tries to shift the focus on building
up of single function module used (Pahl & Jamshidi, 2016). This singly functioning modules
are coupled with well-defined interfaces and operations as well. right now, the trend for
developing a software with the help of microservices architecture has been a popular trend in
the past few years and it has started accepting a much for agile technique for moving
forwards with the DevOps and continuous testing structures.
Microservices are mostly e identified to be the latest techniques by which the different
forms of software development are coming into being. Organisations have also been found to
be utilising the microservice architecture for the development of various form of software
according to the requirement of the organisation (Bakshi, 2017). The monolithic systems that
were utilised as a module previously for developing software where facing several challenges
that was finally solved by the microservices architecture. Various organisations started
discarding the monolith application and started using microservices discarding the single
autonomous unit. this requires the simplest form of building up an application that suits the
smallest of services and health in the running down of all the processes which can
independently be deployable. The ways by which the services are different in different
programming languages also uses the different data storage techniques as well (Rahman &
Gao, 2015). The development style in these systems are flexible enough to make a random
change or a proper makeover as well. however, it also needs to be pointed out that the
microservices are often connected with the help of APIs so that all the solutions and tools are
found in a web service ecosystem. therefore, it is also possible that the testing of all the API
would help in validating the data flow and the information flow all throughout the

5MICROSERVICES ARCHITECTURE
deployment of the multiple benefits provided by the micro service architecture deployment
(Sun & Memon, 2017).
Examples of successful implementation of microservice architecture
there have been various examples of different organisations where microservice
architecture has been used as a successful implementation amongst different industries over
the past few years (Alshuqayran, Ali & Evans, 2016). The examples that would be presented
in this regard would not be based upon any single industry or the examples of the
organisations that probably belong to the similar format of development. Netflix has utilized
microservice architecture for an evolved format of developing the software for the website
that usually depends upon streaming of online videos and movies. the ways by which one
account can be handled by four different people and at the same time the same video can be
streamed from a single account by two people casted on different screens is a possibility that
monolithic development could never have done (Guo et al., 2016). It was only possible
through to the development and the successful implementation of the microservice
architecture.
Twitter is a social networking site that mostly deals with people posting and sharing
their thoughts and pictures all over with the implementation of the flexibility of using the
services from various connecting devices and even on smart TVs. the way by which the
autonomous singular unit can now be casted on different areas and also used on various
different platforms is due to the use of the successful implementation of micro service
architecture (Evans, Young & Perry, 2019). It is also useful to know that there are various
operations that a person can perform in Twitter at the same time with the use of different
devices is also something that could not have been done with the monolithic development of
the software.

6MICROSERVICES ARCHITECTURE
eBay is another website that has been develop with the utilisation and successful
implementation of the microservice architecture. eBay has always been one of the most used
websites for e-commerce (O'Connor, Elger & Clarke, 2017). The buying and selling of
different products or services over internet has been served by eBay and this is another
development that could not have been done by the monolithic services since eBay does not
only allow people to buy and sell products and services from their website but also has
developed a mobile friendly app which is working both on Android and iOS versions.
therefore, these have been presented as the examples of successful implementation of
microservice architecture.
Benefit of the microservice architecture
As per the development of the software described as above and the various ways by
which different organisations are accepting the utility of the microservice architecture for the
software presented by the organisations, it is needless to specify that there are numerous
benefits of the microservice architecture (Salah et al., 2016). The benefits of microservices
needs to be specified categorically as described as below:
 Microservices architecture are especially simple for the deployment process as
it can be deployed in pieces, literally pieces without the services affecting each
other even if they are broken into different pieces (Wolff, 2016).
 It is extremely simple to understand as the person who is developing the codes
for the software architecture would find it even simpler to isolate the functions
as they do not depend upon each other.
 It is also very easy to reuse across different organisations. This is because the
small services of payment on login systems are shared throughout the business
in smaller services so that there would be no problem in, we using the same
service across different business functions.

7MICROSERVICES ARCHITECTURE
 The isolation of the defected pieces is much faster than the previous
monolithic versions because when a test fail or any test service happens to
deteriorate it or defective, it can be quickly isolated with the microservices
easily.
 It has also been identified that the risk of change is much minimised as there is
no locking technologies or languages that it provides any potential risk for
understanding.
The challenges faced in the implementation of microservice architecture
As far as the benefits of the microservice architecture, there are innumerable ways by
which the new development practice has been benefiting the organisations one after another.
However, the world right now living in microservices has changed entirely from monolithic
development to microservice architecture. there have been more than 70% technological
organisations that have adopted the implementation of microservice architecture. there have
been many well documented benefits pointed out for the microservice architecture regarded
the enhancement of the resilience, improvement of the scalability and the fastest way of
implementation (Levcovitz, Terra & Valente, 2016). However, the transformational trend
also has its challenges while the implementation process goes down. It has been identified
that the challenges are understood to be e one of the topmost problems that organisations face
during the implementation of the microservices architecture for the development of their
websites for software. Following would be the challenges recorded or document according to
the microservice architecture and their implementation procedure:
 The management of the microservices force and impending challenge on the
implementation of microservice architecture as the managing of the
microservices becomes much more difficult than the increase in number. The
management is important to be planned before the development of the

8MICROSERVICES ARCHITECTURE
microservices because it can go out of hand very easily if these are not
managed well (Mitchell & Jones, 2019). There are many challenges that has
being faced by the engineers regarding the mismanagement of the services
since the problem has been face to write during the initial stages of the
transformation. The transformation phase mostly was regarded to the
transformation of the applications from being developed from the monolithic
to microservice.
 It is difficult to monitor the microservice architecture when there is a
transformation happening from the traditional forms. This is because the
traditional forms of diagnostic and monitoring the software is not
synchronised with the microservices architecture as there are numerous
multiple services that comes with the same personality and functionality for a
single application (Sundberg, 2019). Therefore, for every problem there are
numerous solutions for which the root causes need to be find out. If the part of
the cause is not finding out it would be very difficult to monitor in case of a
microservice architecture.
 Fault tolerance is important as individual services but as an entire system of
microservice architecture it does not go down well. this is because the fault
tolerance is much more rigid at service level and the overall solution level for
microservice architecture can be extremely critical as it is a much complex
process and environment. therefore, fault tolerance in case of microservice
architecture is susceptible to failure.
 Testing of the process is very complex when it comes to microservice
architecture since it has different service and integration along with different
sort of interdependencies. also, the team members that would be responsible

9MICROSERVICES ARCHITECTURE
for ensuring the quality of the developed software has to have a proper
knowledge of the microservice architecture and all the channels that have been
communicating the services for the test cases (Carrasco, Bladel & Demeyer,
2018). If there is any fault in the synchronous aspect of the microservices it
would be very hard to test the lower environment and therefore the prediction
and validation of the working structure for the microservices architecture
would be difficult to handle.
 The development of the software always has a tendency of feeling which is
why the person who is developing the software always has a failure impending
in the mind which is an issue that should be handled better. However, it is
difficult to attain as it is theoretically placed.
Principles of service modelling and technologies available for integration
The REST model is one of the principles that is followed across different
organisations for the development of the web service ecosystem. this is the way by which the
microservices are connected with the help of API and it can leverage the same number of
tools and solutions that it a developed in a web service ecosystem (Camargo et al., 2016). The
testing process of the API in rest is what helps the development of the software much more
linear but multifaceted at the same time.
Challenges in splitting the backend monolithic system that represent substantial
amount of the behaviour of the Company’s system
There is a challenge in testing the different ways of the monolithic system
representing substantial amount of the behaviour of the system of the company since that are
certain problem in understanding the proper functioning of microservices architecture. The
API testing which is the core of software development is regarded to the transfer of data and

10MICROSERVICES ARCHITECTURE
logic in disparate systems and applications (Erl, 2016). This is a format that is not followed
so far in the design of microservice architecture since it is not yet been properly understood
by the developers yet.
Ethical, legal and security issues in the transitioning to microservice architecture
There are big vulnerabilities regarding the ethical legal and security issues of the
transition of microservice architecture as there are a wide array of security issues associated
with microservices architecture. These are mostly found to be listed as below:
 Ethical Issues: Among the ethical issues it can be said that the monolithic
architecture being extremely sidelined by this architecture has made the
engineers fall out of their own path.
 Security Issues: It has been found that there are various security issues
centralising the microservice architecture. These are associated with the
resilience, scalability and flexibility that the microservice architecture
provides but it also does not adhere to the acceptance of security.
 Legal Issues: There is also a legal obligation for developing a particular
application or software according to the Microservices Architecture. This is
known as “Convey Law” where the law states that when an organization
designs a system using the Microservices Architecture and that system is
elaborate enough to define the working structure of the business, then the
design of the structure for the system would have a copy of the
communication structure of the organization or else the system would not be
regarded as viable.

11MICROSERVICES ARCHITECTURE
Conclusion
Therefore, in conclusion it can be said that the microservice architecture is one of the
most excruciating and the newest development method that has been designed which has the
potential of replacing the monolithic structures of software development that were previously
followed. the report as above describes in details all the probable features of the microservice
architecture as it has been placed along with the researchers done for finding out the detailed
information about microservice architecture. This has been identified to be one of the most
widely accepted development of technologies beyond the discrimination of different
organisations as it has been found. starting from Netflix to eBay, Amazon, people and various
other organisations who have developed their website are found to be using the microservice
architecture to support the development of their website. the agility and the fast process that
is associated with the development of the software with the help of this particular method is
what makes it extremely acceptable amongst the different organisations. however, it also has
its benefits and its challenges that has been also mentioned above along with the reasons why
organisations are found to be accepting this architecture for the development of the software
for their benefit. it has been found how the ability of the development process has made it one
of the most economic and less time-consuming way of developing an agile software.

12MICROSERVICES ARCHITECTURE
References
Aderaldo, C. M., Mendonça, N. C., Pahl, C., & Jamshidi, P. (2017, May). 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.
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.
Bakshi, K. (2017, March). Microservices-based software architecture and approaches.
In 2017 IEEE Aerospace Conference (pp. 1-8). IEEE.
Balalaie, A., Heydarnoori, A., & Jamshidi, P. (2016). Microservices architecture enables
devops: Migration to a cloud-native architecture. Ieee Software, 33(3), 42-52.
Carrasco, A., Bladel, B. V., & Demeyer, S. (2018, September). Migrating towards
microservices: migration and architecture smells. In Proceedings of the 2nd
International Workshop on Refactoring (pp. 1-6). ACM.
de Camargo, A., Salvadori, I., Mello, R. D. S., & Siqueira, F. (2016, November). An
architecture to automate performance tests on microservices. In Proceedings of the
18th International Conference on Information Integration and Web-based
Applications and Services (pp. 422-429). ACM.
Erl, T. (2016). Service-oriented architecture: analysis and design for services and
microservices. Prentice Hall Press.

13MICROSERVICES ARCHITECTURE
Evans, J., Young, A., & Perry, R. (2019). Studying Courseware Using Microservices
Architecture Methodologies. Computer Science and Information Technology
Journal, 5(1).
Guo, D., Wang, W., Zeng, G., & Wei, Z. (2016, March). Microservices architecture based
cloudware deployment platform for service computing. In 2016 IEEE Symposium on
Service-Oriented System Engineering (SOSE) (pp. 358-363). IEEE.
Jaramillo, D., Nguyen, D. V., & Smart, R. (2016, March). Leveraging microservices
architecture by using Docker technology. In SoutheastCon 2016 (pp. 1-5). IEEE.
Levcovitz, A., Terra, R., & Valente, M. T. (2016). Towards a technique for extracting
microservices from monolithic enterprise systems. arXiv preprint arXiv:1605.03175.
Miller, E., Levine, C., Martin, K., & Bradley, C. (2019). The Influence of Microservices
Architecture Archetypes on. Computer Science and Information Technology
Journal, 6(1).
Mitchell, R., & Jones, C. (2019). Microservices Architecture, Bayesian Theory for Context-
Free Grammar. Computer Science and Information Technology Journal, 4(1).
O'Connor, R. V., Elger, P., & Clarke, P. M. (2017). Continuous software engineering—A
microservices architecture perspective. Journal of Software: Evolution and
Process, 29(11), e1866.
Pahl, C., & Jamshidi, P. (2016, April). Microservices: A Systematic Mapping Study.
In CLOSER (1) (pp. 137-146).
Rahman, M., & Gao, J. (2015, March). 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.

14MICROSERVICES ARCHITECTURE
Salah, T., Zemerly, M. J., Yeun, C. Y., Al-Qutayri, M., & Al-Hammadi, Y. (2016,
December). The evolution of distributed systems towards microservices architecture.
In 2016 11th International Conference for Internet Technology and Secured
Transactions (ICITST) (pp. 318-325). IEEE.
Sun, L., Li, Y., & Memon, R. A. (2017). An open IoT framework based on microservices
architecture. China Communications, 14(2), 154-162.
Sundberg, A. (2019). A study on load balancing within microservices architecture.
Wolff, E. (2016). Microservices: flexible software architecture. Addison-Wesley
Professional.