Micro Services Architecture

Running Head: MICROSERVICES
0
Micro services Architecture
IT Write Up
(Student Details: )
4/3/2020

MICROSERVICES 1
Executive Summary
The report is aimed at researching the key benefits of using Micro-services
Architecture (Micro-Services Architecture) while including, core knowledge, and challenges
faced by the organizations which are already using Micro-Services Architecture for the better
business development and growth. The paper is going to use three examples of well-known
organizations include Uber, Coca-Cola, and Amazon, as they are working in different
industries effectively. The companies have been chosen to explain the key aspects of Micro-
Services Architecture because they have transitioned to Micro-Services Architecture since
long. Therefore, in the modern business environment, how the chosen company Whiteboard
can become more successful and remove key bugs from their software architecture will be
explained in this report. For advising Whiteboard, this report is going to cover key benefits as
well as challenges of Micro-Services Architecture in relation to better business functions
efficiency.

MICROSERVICES 2
The paper is emphasized on examining a case and advising a company in the
transition to microservices architecture (Bakshi, 2017). The paper is going to advise the
Company Whiteboard on the transition to microservices architecture (Micro-Services
Architecture).
In the context of the chosen company, it can be said that Whiteboard is one of the
leading system providers in relation to student and learning management while supporting
over 10 million learners or students all across the world. The company is leading among the
platforms for student learning in the whole world as it allows them to measure their efforts. In
this way, the report is suggesting the company to shift to a microservices system from a
monolithic system. Thus, the discussion will include benefits as well as challenges while
transitioning to microservices architecture from monolithic architecture (Balalaie,
Heydarnoori, & Jamshidi, 2016).
Source: (Divante, 2019)
Micro-services Architecture
In order to define Micro-Services Architecture, first monolithic architecture needs to
define so that the key difference can be seen. In general, a monolithic architecture is typically
designed for lightweight and simple applications and hence these monolithic applications
have become an obstacle for constant and sustainable development in teaching and student
learning. In this era, modern enterprises are drifting further away from monoliths and closer
towards micro-services architecture (erl, 2016). They are doing it for every website, app, and
digital experiences. Sometimes, such applications using monolithic architecture are difficult
to scale hence use of Micro-Services Architecture has become necessary.

MICROSERVICES 3
In this context, in place of creating a single huge as well as complex application, the
app can be split into a suite of services that are independently scalable and deployable
(Zimmermann, 2017). It is worth knowing that microservices architecture is needed because
of the requirement of deploying new changes quickly, efficiently, and reliably on
infrastructure with optimal cost. Micro-Services Architecture is a solution to the problems of
competing demands for novel features as well as better performance from businesses and
users alike. From the definition perspective, Micro-Services Architecture is a common
pattern of software development through the practices of so many leading modern
organizations. Such business practices include technologies, principles, methodologies,
organizational tendencies, as well as cultural characteristics. Presently, all of the modern
companies are taking steps for further implementing microservices and thereby reap the key
benefits requite to consider Micro-Services Architecture as a broad scope (Divante, 2019).
In other words, Micro-Services Architecture is a method of developing software apps
with an independently deployable component of the bounded scope which helps
interoperability from message-based communication. In addition to that, the definition of
Micro-Services Architecture suggests that microservices architecture refers to a style of
engineering extremely automated, changeable software systems which is usually made up of
capability-aligned microservices (Wolff, 2016).
Examples
There are so many big companies which have implemented the Micro-Services
Architecture and thereby paved the way for other businesses also. It is well-known that
international firms like Netflix, Bestbuy.com, eBay, Coca-Cola, Amazon, and Uber, have
already transformed their IT infrastructure into a Micro-Services Architecture (Divante,
2019). Out of all the above famous business giants, the report is going to highlight the three
examples of successful implementation of Micro-Services Architecture as Amazon, Uber,
and Coca-Cola (Ismail, 2018). Apart from this, it can be said that these companies are
effectively rebuilding the internal organizational structures while pushing their business
operations far ahead of the competition. It has been found that adopting Micro-Services
Architecture gave so many useful answers to key problems of complex and big IT systems.
For these three companies, Micro-Services Architecture can be seen as a technique of
developing apps built as a suite of micro-services in which Micro-Services Architecture is the
answer to every question. Micro-Services Architecture used by these chosen companies

MICROSERVICES 4
communicates with each other with the help of API gateways (Thones, 2015). The journey of
such companies from monolithic to Micro-Services Architecture is explained as below:
Amazon
In this context, Amazon is one of the top companies that started using Micro-Services
Architecture and hence the company plays an important role in transforming the eCommerce
field with the use of new Micro-Services Architecture. In other words, Amazon as the global
giant also achieved their marvellous success when monolithic architecture was the only way
of developing software and IT systems. In 2001, Amazon.com was a huge monolithic
architectural website and all of its services, as well as components, were tightly linked with
each other. For overcoming barriers of the monolithic system like complex, stability and
scalability issues, Amazon started using Micro-Services Architecture for further simplifying
as well as shortening the pipeline (Ismail, 2018). It is because while using monolithic
architecture by Amazon, all major changes were stuck in the pipeline of development for
several weeks prior to consumers could use them (Divante, 2019). To overcome such
problems, Amazon decided to transition their IT system from monolithic to micro-services.
Thus, Amazon got success with the open-source solutions, like AWS.
Coca-Cola
It is well-aware that the Coca-Cola Company is selling more than 3800 products all
across the world (Divante, 2019). When the company faced the challenge of connecting their
entities on diverse continents to support the company’s overall growth, then they started
using Micro-Services Architecture. It was the time when Coca-Cola decided to get benefitted
from microservices as well as APIs so that the company can achieve organizational goals and
they gradually replace the legacy software (Ismail, 2018).
Therefore, Coca-Cola used a new architecture using the Dev-Ops model to move
towards Micro-Services Architecture. In doing so, the company Coca-Cola introduced a
newly made software structure divided into a single app, so that company could address so
many issues which arise related to speed and agility (Ismail, 2018).
Uber
In the case of Uber, initially, the company was operating in a single city and hence
there was no need for big and efficient software architecture. Later on, Uber expanded their
business and the monolithic architecture used by Uber started causing issues related to
continuous integration as well as scalability. Thus, at that point in time, the transport

MICROSERVICES 5
Company Uber decided to shift from a monolithic architecture to Micro-Services
Architecture for getting better business growth and efficiency (Divante, 2019).
Source: (Divante, 2019)
It is worth knowing that with the new architecture Micro-Services Architecture, Uber
introduced a completely new API Gateway as well as so many independent services. Such
independent services have individual functions and they can be deployed as well as scaled
separately hence it ultimately allowed the company to grow, expand and earn more profit
worldwide (Dragoni, Lafuente, Montesi, & Safina, 2017).
Key benefits
 Micro-Services Architecture provides continuous deployment to these companies
 Micro-Services Architecture eradicates scalability issues and micro-services apps are
not difficult to scale

MICROSERVICES 6
 There are no stability issues in Micro-Services Architecture used by these companies
 Micro-Services Architecture is completely adaptable to new frameworks and
technologies (Dragoni, Lafuente, Montesi, & Safina, 2017)
 While using Micro-Services Architecture, micro-services are very easy to deploy
 In Micro-Services Architecture, micro-services are organized all-around functional
capabilities
 In Micro-Services Architecture, micro-services are independently deployable and at
the same time they are fully encapsulated (Wolff, 2016)
 In addition, micro-services services can be implemented with diverse database,
languages, and hardware
 Micro-Services Architecture lends itself to continuous delivery all the time (Sun, Li,
& Memon, 2017)
 In Micro-Services Architecture, there are so many enhancements as well as fixes that
can be isolated to the only service which requires the modification. In this way,
Micro-Services Architecture reduces the regression risk as well.
Challenges
As we know, all software architecture comes with its inherent challenges hence there
are drawbacks to this approach as well. These key challenges are as follows:
 The foremost challenge during Micro-Services Architecture implementation is that
there are various components of such services as well as the management of the
volume and dependencies are huge (Sill, 2016).
 While implementing Micro-Services Architecture, it has been found that the
companies got it difficult to get an architect in less time effectively.
 In addition to that, it has been found that testing, as well as building test scripts, were
challenging particularly at the time of unit test level.
 The most important challenge while implementing Micro-Services Architecture
against monolithic architecture is to decide what and when to implement this
architecture (Jaramillo, Nguyen, & Smart, 2016).
Technologies for integration
Principles of service modelling and technologies are SOAP, XML-RPC, and REST
(SmartBear, 2020). Such principles are:

MICROSERVICES 7
SOAP
In this context, SOAP relies completely on XML to offer messaging offerings.
Microsoft, in the beginning, evolved SOAP to overtake older technology that cannot work
well over the internet like DCOM and CORBA. It has been found that such technologies
failed due to binary messaging dependency. Furthermore, the XML messaging which is
typically employed by SOAP works higher across the internet (Ivak, 2011).
XML-RPC
It is a useful tactic that provides and consumes web services efficiently and
effectively. The XML-RPC uses HTTP for transport as well as XML for decoding and
encoding the remote process c Apart from this, there are so many key challenges in splitting
the backend monolithic system, which is as follows:all all across with the parameters. It is a
simple designed architecture that allowed complex data structure for being processed,
transmitted and returned as well (Ivak, 2011).
REST
In this context, REST is the easiest technology which has been developed for web
services. In REST, there is no requirement of data interchange through XML for request as
well as response. There are some key advantages such as easier to use, highly flexible,
smaller learning curve and fast response (SmartBear, 2020).
Splitting Challenges
The major splitting challenges for monolithic system are as follows:
 While splitting monolithic architecture into Micro-Services Architecture, there is a
need for efficient automation technology
 While splitting monolithic architecture into Micro-Services Architecture, there is a
need for quick set up
 While splitting monolithic architecture into Micro-Services Architecture, there is a
need for configuration management (Mauersberger, 2019)
 While splitting monolithic architecture into Micro-Services Architecture, there are
visibility complexities
 While splitting monolithic architecture into Micro-Services Architecture, there is a
challenge of dynamic scale up and scale down

MICROSERVICES 8
 While splitting monolithic architecture into Micro-Services Architecture, there are
debugging challenges need to be addressed
 While splitting monolithic architecture into Micro-Services Architecture, there is a
need for consistency
 While splitting monolithic architecture into Micro-Services Architecture, there is a
need for swift up (Newman, 2015)
 While splitting monolithic architecture into Micro-Services Architecture, there is a
need for a pack of cards
Ethical, security and legal issues
There are ethical, legal and security related issues because the process of IT system
transforming into a new form of architecture may require recruiting completely new skilled
employees having specific system knowledge and at the same time terminating the old
employees (Namiot & Sneps-Sneppe, 2014). In this way, this whole process of hiring new
employees in place of old loyal employees often creates legal issues. On the other hand, the
new technology and architecture such as Micro-Services Architecture often architect the
entire system which is highly from the employees’ perspective and hence it creates ethical
issues. Additionally, micro-services architecture is not at all secure and thus, adopting Micro-
Services Architecture (Namiot & Sneps-Sneppe, 2014). Thus, splitting the monolithic system
into micro-services can pose a data breach risk. The key issues are as follows:
Key ethical issues are reliability, integrity, security, data privacy. In addition to that,
other ethical issues are data staleness, tracing, fault tolerance, as well as some key security
issues.
Key ethical issues raised in the transitioning to micro-services architecture are identity
fraud, identity theft, redundancy maintenance, user privacy and data risks, standardization
challenges and others (Nadareishvilli, Mitra, Mclarty, & Amundsen, 2016).
Key ethical issues raised in the transitioning to micro-services architecture are data,
complexity, data monitoring, new skill-set, and knowledge. Furthermore, the proliferation of
Micro-Services Architecture often leaves more soft targets for security breakers such as
crackers, hackers, and other Therefore, by ensuring that the system is not vulnerable to the
security viewpoint becomes a great challenge while transitioning to micro-services
architecture as it often creates a risk of data hacking (Namiot & Sneps-Sneppe, 2014).

MICROSERVICES 9
Conclusion
In whole, with the help of this in-depth research on the transition of monolithic
architecture to micro-services architecture, an introduction of the original intent of the micro-
services architecture concept has been done effectively. It has been found that the major aim
of Micro-Services Architecture is to replace complex monolithic applications with software
systems made of replaceable components. This report has successfully explored the key
benefits and several advantages of using Micro-Services Architecture over a monolithic
system with the help of real-life examples like Uber, Amazon, and Coca-Cola throughout the
discussion. Additionally, the discussion has also introduced some key concerns as well as
challenges faced by first-time implementers in the context of Micro-Services Architecture. In
this way, the micro-services architecture has been highlighted as a goal-driven approach in
order to build adaptable, reliable and more efficient software. In other words, Micro-Services
Architecture has been found as a balanced way of understanding the essence of micro-
services as the speed and safety at scale is the key within Micro-Services Architecture which
has been shown by major companies like Uber, Amazon, and Coca-Cola.
Future Recommendations
Based on the above research, there are some future recommendations for other
modern businesses, as follows:
• Modern organizations should always identify if there is a need for Micro-Services
Architecture within their business functions.
• Evaluating organizational needs prior to transitioning to Micro-Services Architecture
is essential as Micro-Services Architecture typically helps companies to gain agility
and scale.
• Furthermore, the companies should be prepared for the operational complexity of
Micro-Services Architecture while deciding to shift their IT system to Micro-
Services Architecture.
• Post identifying all of the above system needs, firms should determine when and
where to implement Micro-Services Architecture.
• In this era, companies need to have skilled labor and employees as there are so many
complexities in Micro-Services Architecture too.

MICROSERVICES 10

MICROSERVICES 11
References
Bakshi, K. (2017). Microservices-based software architecture and approaches. IEEE
Aerospace Conference, 1-8.
Balalaie, A., Heydarnoori, A., & Jamshidi, P. (2016). Microservices architecture enables
devops: Migration to a cloud-native architecture. IEEE Software, 33(3), 42-52.
Divante. (2019). 10 companies that implemented the microservice architecture and paved the
way for others. Retrieved 2020, from https://divante.com/blog/10-companies-that-
implemented-the-microservice-architecture-and-paved-the-way-for-others/
Dragoni, N., Lafuente, A., Montesi, F., & Safina, L. (2017). Microservices: yesterday, today,
and tomorrow. Present and ulterior software enginnering , 195-216.
erl, T. (2016). Service-oriented architecture: analysis and design for services and
microservices. UK: Prentice Hall Press.
Ismail, K. (2018). 7 Tech Giants Embracing Microservices. Retrieved from CMS Wire:
https://www.cmswire.com/information-management/7-tech-giants-embracing-
microservices/
Ivak, M. (2011). REST vs XML-RPC vs SOAP – pros and cons. Retrieved from Max Ivak:
https://maxivak.com/rest-vs-xml-rpc-vs-soap/
Jaramillo, D., Nguyen, D., & Smart, R. (2016). Leveraging microservices architecture by
using Docker technology. IEEE.
Mauersberger, L. (2019). Why Netflix, Amazon, and Apple Care About Microservices.
Retrieved from LeanIX: https://blog.leanix.net/en/why-netflix-amazon-and-apple-
care-about-microservices
Nadareishvilli, I., Mitra, R., Mclarty, M., & Amundsen, M. (2016). Microservice
architecture: aligning principles, practices, and culture. UK: O'Reilly Media Inc.
Namiot, D., & Sneps-Sneppe, M. (2014). On micro-services architecture. International
Journal of open information technologies, 2(9), 24-27.

MICROSERVICES 12
Newman, S. (2015). Building microservices: designing fine-grained systems. UK: O'Reilly
Media Inc.
Sill, A. (2016). The design and architecture of microservices. IEEE Cloud Computing, 3(5),
76-80.
SmartBear. (2020). SOAP vs REST. What's the Difference? Retrieved from SmartBear:
https://smartbear.com/blog/test-and-monitor/soap-vs-rest-whats-the-difference/
Sun, L., Li, Y., & Memon, R. (2017). An open IoT framework based on microservices
architecture. China Communication, 14(2), 154-162.
Thones, J. (2015). Microservices. IEEE Software, 32(1), 116-116.
Wolff, E. (2016). Microservices: flexible software architecture. UK: Addison-Wesley
Professional.
Zimmermann, O. (2017). Microservices tenets. Computer Science Research and
development, 32(3-4), 301-310.