Skip to content

MIS603 Microservices Architecture

The Microservices are a cutting-edge breakthrough in the field of programming development.
It is capable of maintaining the overall business at a high level with low level help and
freedom to operate. Therefore, we can conclude that this is a development variation of a good
programming application that quickly resolves the present business difficulties. Numerous
features, like flexibility, freedom, and loose coupling, are included in this engineering. This
aid engineering also makes it possible to deal with security and administration that facilitates
cloud computing. This design has been made in consideration of several components,
including framework skills and group association.

They have also developed using agile programming development and DevOps. As a result,
each organisation has a variety of legal obligations for data protection. Microservices design
is a practical approach for a large number of programming tasks. The main goals of this
engineering are adaptive and have a high level of adaptability. The programme may degrade
into multiple components, each of which would function independently. The microservices
application was segregated from the stone structures and operated by a single person.
In microservices, a large, substantial application is divided into roughly linked, free, and
independent services that collaborate with one another to provide solutions to extremely
complicated business problems. In the IT industry, microservices are becoming more and
more prevalent. Amazon, Netflix, and Spotify are really just a few examples of enterprises
that use microservices-based systems to manage their operations.
This article aims to discuss the fundamental principles and concepts of microservices design,
as well as its advantages and disadvantages.

Body of the report
Microservices design is a practical approach for a large number of programming tasks. The
main goals of this engineering are adaptive and have a high level of adaptability. The
programme may degrade into multiple components, each of which would function
independently. The microservices application was segregated from the stone structures and
operated by a single person.

The key principles are :

  1. Single Responsibility Principle
  2. Work around Business Capabilities
  3. You Build It, You Own it
  4. Framework Automation
  5. Plan for Failure
  6. Microservices Architecture Benefits and Drawbacks

Microservices engineering is growing in popularity these days because of its features, which
include flexibility, versatility, and many others that are clearly superior than stone monument
design. Nevertheless, despite its benefits, the microservices design requires a few different
points of view. The benefits and drawbacks of the architecture of microservices are shown in
the table below.


  1. Microservices provide these kinds of help with amazing nimbleness.
  2. Bilingual programming is made possible via microservices.
  3. Administrations become independent thanks to decentralised information and management.
  4. Microservices allow for more rapid project development.
  5. Traditional services are less adaptable than microservices.


  1. The complexity of microservices exceeds that of a solid.
  2. Microservices demand societal change.
  3. Solid services cost less than microservices.
  4. Microservices may be more defenceless in the face of security threats.
  5. The board of distributed applications and administrators

Engineering with microservices has several benefits. Microservices allow for very flexible
planning, creation, testing, and various administrations. Changes can be made quickly as a
result of more conservative administration.Because the services in the microservices are
independent of one another, if one stops operating, it won't affect the other services, which is
not always the case with granite monument architecture. Overall, microservices have
numerous shortcomings (Francesco., 2019). There is no compelling necessity to replace
the entire code because the administrations in microservices are independent. The only area
that needs alteration is modified, tested, and communicated, which speeds up the user's
communication. Since multilingual programming is made possible by the administrations,
programmers may choose the best language to carry out their work. The inexact coupling of
the microservices allows for great group flexibility (Kuprenko, 2019).

Microservices design, which is loosely connected as compared to solid engineering, is rising
to fame in the product development space and is frequently used by the organizations. The
adoption of microservice architecture has changed as a result of the problems with solid that
have been found. Microservices provide the organisation a number of benefits that aid in
increasing agility and flexibility. Although switching from solid to microservices is
advantageous for the organisation, actually putting microservices into practise is challenging
as well.

Microservices Architecture Benefits
Programming for microservices may be divided into several component advantages, enabling
each of these administrations to be supplied and then repurposed free without endangering
the security of an application. In other words, developers may dynamically build and deploy
administrations thanks to the microservices architecture.
Better problem segregation ensures that even if one of the microservices fails, the others will
continue to function.
Code for various administrations might be written in many languages.
Simple integration and pre-planned setup; use of open-source continuous reconciliation
technologies like Jenkins, etc.
The idea of microservices makes persistent delivery possible.

The code is based on the capabilities of the organization, and it must be flexible and reusable
in addition to being effective. Integration with third-party services and scaling are both
simple processes.
The distribution of parts among many servers or even network infrastructure is possible.
Excellently work with compartments, like Docker.
Because the many components of a programme are decoupled, microservices focus on
security monitoring.

Case studies and examples of successfully implemented microservices architecture
Large-scale websites and apps like Netflix, eBay, Amazon, the UK's Government Digital
Service, Twitter, PayPal, The Guardian, and a plethora of others have all made the transition
from traditional solid architecture to microservices engineering. To examine the results, let's
look at some examples of people who overcame hardships:
A superb user experience is made possible by Spotify's usage of microservices.
Kevin Goldsmith, Spotify's VP of Engineering, is aware from personal experience that a
project requiring scalability need a design that can adapt rapidly and continue to be inventive
in a cutthroat market. As a consequence, Spotify came to the conclusion that you should
design your framework such that you can easily scale individual components if you're
worried about scaling to a high number of customers. Spotify sought to maintain these
limitations to a minimal because they presently have around 90 teams, 600 designers, and
five development offices working on a comparable product across two continents.

Amazon Embraced the DevOps Philosophy with Microservices
Amazon has also embraced microservices. Their prior, two-layered architecture would have
been practically unable to manage the constant requests they receive from a number of
sources, including apps that interface with the web administration API in the same manner
that they interact with the live site. In 2001, the ecommerce site was still under
construction. It was built on a number of levels, each of which included a sizable number of
rooms, yet they were all securely connected to one another and functioned as an one
enormous stone monument.

These significant adjustments started structurally, when Amazon switched their robust
application to a Service Oriented Architecture. Amazon also changed the way their company
conducted business. They split up into smaller "two-pizza groups" their primary, developing
item development group.After making these adjustments, Amazon greatly enhanced the
lifetime of front-end innovation. Currently, item groups are able to make decisions on and
deploy new microservice provisions fast. The organisation now completes 50 million
arrangements annually thanks to microservice engineering and its never-ending conveyance

Ethical factors in particular security and privacy concerns
The issue should be notably upright in the first place and questionable in the second.
In applied morality, we apply regularising criteria from a more pragmatic perspective. The
following are probably the most well-known examples of such criteria being used in applied

Rule of generosity: Be kind to people who are unfortunate.
Rule of authenticity: Don’t deceive people.
Damage rule: Don’t injure other people.
Paternalisms guiding principle is to assist others in pursuing their general interests when they
are unable to do it on their own.

PC morality also referred to as data morals or cyber ethics—is the framework through
which the ethical implications of data security are thought through. PC ethics is a branch of
applied morality that has received significant attention from ethicists as well as from experts
in data innovation. A significant component of this curiosity is the expected outcome of the
rapid change in PC innovation, its applications, and its recommendations. Despite the term
"PC Ethics"

Many businesses have switched between solid to microservices engineering. Microservices
provide a lot of advantages over traditional applications, but because they integrate several
different services into a single application, security and protection are a concern.

Instead of incorporating such services into a single monumental stone structure,
microservices engineering focuses on creating several independent, limited-scope
arrangements of Microservices. Microservices are an alternative to stone monuments that
overcome the challenges posed by deteriorating solid designs dividing a single application
into smaller microservices Due to its potential advantages, such as versatility and
adaptability.Microservices for computerised transmission and readiness are widely accepted
in the IT industry. It cannot, in any case.Never forget that, compared to traditional services,
microservices are more complicated, expensive, and vulnerable to security risks with strong.
However, many companies already do so, with the advantages weighing more heavily than
the disadvantages now started operating their firm in a microservices structured manner.

Di Francesco, Paolo, Patricia Lago, and Ivano Malavolta. 2019. “Architecting with
Microservices: A Systematic Mapping Study.” Journal of Systems and Software
150(4):77–97. Retrieved from https://www-sciencedirect-
GOTO conference. (2015, December 23). GOTO 2015. Microservices at Spotify. Kevin
Goldsmith. [Video file]. Retrieved from James Lewis,
Martin Fowler. 2014. Microservices: A Definition of this New Architectural Term. Retrieved
Koschel, A., Astrova, I., & Dotterl, J. (2017). Making the move to microservice architecture.
2017 International Conference on Information Society (I-Society).
Lokesh Gupta. 2019. Microservices – Definition, Principles and Benefits. Retrieved from
Phil Witmer. 2019. The Top Microservices Disadvantages & Advantages. Retrieved from
Vitaly Kuprenko. 2019. 6 key benefits of microservices architecture. Retrieved from

6 Key Benefits of Microservices Architecture