Microservices Architecture

The architecture of micro-services allows the rapid, reliable as well as frequent delivery of huge applications. Micro-services further allows an organization to evolve the stack of technology that is owned by them. This report provides a detailed description of the software architecture, and why it is important for contemporary enterprise. This report would highlight the benefits as well as challenges that would be provided to the business with the usage of micro-services architecture.

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

1MICROSERVICES ARCHITECTURE
Executive summary
The architecture of micro-services allows the rapid, reliable as well as frequent delivery of
huge applications. These applications are usually complex in nature. Micro-services further
allows an organization to evolve the stack of technology that is owned by them. The shift to
micro-services has numerous impacts on the culture of the team along with the morale of the
employees. Successful micro-services could not be built without a good team culture. Micro-
services have a lifecycle that is independent in nature. This represents the fact that every
service is improved as well as released without proper and extensive communication among
the teams. This report provides a detailed description of the software architecture, and why it
is important for contemporary enterprise. This report would highlight the benefits as well as
challenges that would be provided to the business with the usage of micro-services
architecture.

2MICROSERVICES ARCHITECTURE
Table of Contents
Introduction................................................................................................................................4
Discussion..................................................................................................................................5
Summary of my role...............................................................................................................5
History of computing.............................................................................................................6
Software architecture.............................................................................................................8
Why is software architecture important for contemporary enterprise?................................10
Main types of software architecture.....................................................................................11
Conclusion................................................................................................................................12
References................................................................................................................................14

3MICROSERVICES ARCHITECTURE
Introduction
Micro-services are also known as the architecture of micro-service, this is also an
architectural style which helps in structuring a certain application in the form of a collection
of numerous services which are highly testable as well as maintainable, loosely coupled,
deployable in an independent manner, organized around the capabilities of the nature and is
owned by a small team (Dragoni, Giallorenzo & Lafuente, 2017). The architecture of micro-
services allows the rapid, reliable as well as frequent delivery of huge applications. These
applications are usually complex in nature. Micro-services further allows an organisation to
evolve the stack of technology that is owned by them. Micro-services have been gaining
popularity along with providing various new strategies for companies that make use of
various technologies within their operations. This particular architecture is used by
organizations for the purpose of improving the services that are provided by them to the end
users. The shift to micro-services has numerous impacts on the culture of the team along with
the morale of the employees. Successful micro-services could nt be built without a good team
culture. This particular report contextualizes as well as explains the high level concepts of
micro-services architecture to the technical as well as non-technical people. This report
would further highlight the benefits as well as challenges that would be provided to the
business with the usage of micro-services architecture.

4MICROSERVICES ARCHITECTURE
Figure 1: micro-services architecture
(Source: González, Gascó & Llopis, 2016, p. 175)
Discussion
Summary of my role
My role in this particular hypothetical professional context is to present a report
which would brief to the employer of the consulting client for introduction or for continuation
of the usage of micro-services within the organization. I am a micro-services developer in a
certain origination since four years. I am skilled in numerous fields like Java/ J2EE, Spring
Boot, Spring, REST, JSON, 12 Factor Applications, Apache and Micro Services. I have a
very strong understanding of the architecture of micro services. I have sufficient knowledge
that I use in designing, developing and implementing scalable as well as elastic platforms that
are based on micro-services. Besides these I also have demonstrated knowledge regarding

5MICROSERVICES ARCHITECTURE
authentication protocol that is based on OAuth token along with demonstrated knowledge of
PCI as well as security coding standards. Along with these experiences I also have more than
8 years of experience in technical lead role.
History of computing
From various papers it could be found that with the evolution of technology, the
information systems had also faced evolution along with changes in its usage. This evolution
had brought about changes in the organizational structure as well (Richards, 2015). The
information systems have been categorized on the basis of their topology or architecture
which are usually set of nodes or interconnections in a specific network. Categorization of
information systems in an architectural format had been very appealing because it is not
idiosyncratic to a particular set of settings (Hao, Novak & Yi, 2017). Further these
architectures have been well established as well as accepted in future generations. There are
four categories of information systems that have been evolved and are being used since
numerous generations. the four types of information systems topologies include centralized,
decentralized, stand alone and distributed systems.
Combination of software, data, hardware and communication had contributed in
forming the base of information systems. As generations passed by these dimensions had
developed as well as integrated, this had further resulted massive changes in the design,
concept and capability of the information systems (Wolff, 2016). The traditional systems
were known as classic centralized systems, these systems had been characterized with the
help of a specific host computer. This host computer was supported by a set of array of
peripherals which included “dumb” terminals. These terminals had allowed various activities
that were responsible for processing information and were interactive as well as transactional
in nature (Yang, Liang & Avgeriou, 2016). The centralized systems had been of modest size

6MICROSERVICES ARCHITECTURE
in the previous generation. They had grown from small, medium up to large centralized
systems over generations. This had been the trend up to 1970, for next 20 years the discussion
on the concept of systems and data included the techniques that are used for the purpose of
managing data in a particular environment that is centralized in nature.
In the initial part of 1960s, the major concern between the manufacturer of hardware
as well as data processing managers had been the concept of obtaining efficiency in a certain
machine (González, Gascó & Llopis, 2016). With the increased demand as well as
sophistication of numerous users of data along with the availability of the personal
computers, activities within the process of data processing had been more distributed in
nature. Distributed systems have provided chance to the decentralized information systems,
in n this case the role of the users had been paramount in nature (Liu & Yuan, 2015). This
trend has been carried out through the 1990s and is continuing till now. In this generation, the
least common category of information systems had been stand-alone systems, this is utilized
in individual sections or in the form of information systems in small size of enterprises.
The use of information system throughout the ages had been mentioned below in the
tabular format
1950 - 1960 1960 - 1970 1970 - 1980 1980 - 1990 1990 - 2000 2000 –
present
Processing
of data
Management
reporting
Decision
support
Executive
support
Management
of knowledge
E-Business
Collecting,
storing,
modifying as
well as
Preparing
reports that
are pre
specified and
Provides as-
hoc support
that is
interactive in
Provides
internal as
well as
external data
Tends to
support
creation,
dissemination
Provide
better
connectivity,
high level of

7MICROSERVICES ARCHITECTURE
retrieve
transactions
that are
carried out
daily basis
within a
certain
organization
display them
for
supporting
decision
making in
the business
nature for
the process
of decision
making.
that is
related to the
strategic
goals of the
enterprise
and
organization
of the
business
knowledge.
integration
throughout
various
applications
Helps
workers
Helps the
middle
managers
Helps the
senior
managers
Helps
executives
Helps the
available
enterprise
wide
Helps the
entire field
of e-business
Table 1: evolution of uses of information system
(Source: González, Gascó & Llopis, 2016, p. 196)
Software architecture
A specific architecture of a certain system tends to describe its vital components,
relationships among them along with the way they interact with one another. Software
architecture includes numerous contributory aspects like quality attributes, business strategy,
human dynamics, IT environment and design.

8MICROSERVICES ARCHITECTURE
Figure 2: attributes of software architecture
(Source: Granchelli, Cardarelli & Di Francesco, 2017)
Software architecture and software design are completely two different phases. In the
software architecture phase, various nonfunctional decisions that are to be undertaken are cast
and then separated with the help of requirements that are functional in nature (Balalaie,
Heydarnoori & Jamshidi, 2016). These functional requirements are actually accomplished in
the phase of design. Software architecture tends to serve as a vital part for a certain system. It
helps in providing abstraction for the purpose of managing the complexity of a particular
system and hence initiate communication along with coordination mechanism among
numerous components (Thönes, 2015). The software architecture defined a specific
structured solution for the purpose of meeting the operational as well as technical
requirements at the time of optimization of various quality attributes such as security and
performance. Software architecture further tends to involve a specific set of numerous
decisions regarding the organization related to development of software and every decision
that is included in the set has the chance to have a considerable impact on maintainability,

9MICROSERVICES ARCHITECTURE
quality, performance as well as overall success of the overall product (Wolff, 2016). The
decisions usually comprise of the behavior as it is specified along with the collaboration
among the elements, composition of the behavioral as well as structural elements into a huge
subsystem. It further comprises of selection of numerous structural elements along with the
interfaces with the help of which a particular system gets composed, architectural decisions
which are aligned with the objectives of the business and architectural styles which helps in
guiding a certain organization.
The basic goals of software architecture is identification of requirements which tend
to affect the structure of a certain application. An architecture that is properly laid helps in
reducing the risks that are involved in a certain business which deals with looking for a
particular technical solution and hence remove the gap between technical requirements as
well as business (Dragoni, Giallorenzo & Lafuente, 2017). Some other goals that belong to
software architecture includes exposing the structure of a certain system besides hiding the
details regarding its implementation.
Why is software architecture important for contemporary enterprise?
Software architecture is important for contemporary enterprise due to numerous reasons,
these reasons are mentioned below
1. Communication among stakeholders within the organization: software architecture
tends to represent a mutual abstraction of a certain system which most if not all the
stakeholders of the system are able to utilize as a base for the understanding,
consensus communication and negotiation among them (Aderaldo, Mendonça & Pahl,
2017).
2. Undertake decisions regarding early designing: software architecture tends to
manifest the decisions of the eldest designs regarding a certain system. These

10MICROSERVICES ARCHITECTURE
bindings usually carry a particular weight that is far out of the promotion to the
individual gravity (Bakshi, 2017). This is done with the respect to the development,
deployment as well as maintenance of the system that has not been brought about yet.
3. Transferable abstraction of a certain system: software architecture usually establishes
a comparatively small model that is intellectual as well graspable in nature (Pahl &
Jamshidi, 2016). This model is introduced for the purpose of understanding the way a
certain system had been structured and how the elements contribute in working
together. This particular model is transferable across numerous systems (Pautasso,
Zimmermann & Amundsen, 2017). This model can also be applied to many more
systems which exhibit attributes that are of same quality as well as functional
requirements and hence would be helpful in promoting the large scale re use.
Main types of software architecture
Software architecture design tends to consider the system structure as well as the
requirements for the purpose of getting a systems architecture that is successful in nature.
This makes it very important to consider and focus on things that would help in creating the
architecture (Evans, Young & Perry, 2019). There are for types of architectures along with
their explanation are mentioned below
Business architecture: business architectures define the techniques that are used by a
certain business, organization, governance along with the major business processes that
persists within a particular enterprise (Balalaie, Heydarnoori & Jamshidi, 2016). This
particular architecture tends to focus on the design as well as analysis of the business
processes.

11MICROSERVICES ARCHITECTURE
Application architecture: application architecture usually serves as a blueprint for a
certain application system, their interactions as well as relations with the business processes
that are used by a particular organization (Yang, Liang & Avgeriou, 2016).
Information architecture: information architecture aims in defining the physical as
well as logical data assets along with the assets of data management resources.
Information technology architecture: IT architecture usually defines the software as
well as hardware building blocks which contributes in making up the entire information
system within the organization (Granchelli, Cardarelli & Di Francesco, 2017).
Figure 3: types of software architecture
(Source: González, Gascó & Llopis, 2016, p. 186)
Conclusion
From the above discussion, it could be concluded that if micro-services architecture
are implemented in an appropriate manner could be resilient to various malfunctions within
the hardware. This is usually considered as an important quality because micro-services are
deployed on hardware that are cheap. Micro-services have a lifecycle that is independent in
nature. This represents the fact that every service is improved as well as released without

12MICROSERVICES ARCHITECTURE
proper and extensive communication among the teams. The nature of micro-services would
guarantee the fact that most of the changes would affect numerous components positively
across the entire system. This particular report presents my role in the hypothetical
professional context. it further discusses regarding the history of the computing where the
evolution of the information services is mentioned in details. It further presents the use of
information system throughout the ages in a tabular format. This report provides a detailed
description of the software architecture, and why it is important for contemporary enterprise.
These above mentioned points are described in details in the discussion part of the report.

13MICROSERVICES 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.
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.
Dragoni, N., Giallorenzo, S., Lafuente, A. L., Mazzara, M., Montesi, F., Mustafin, R., &
Safina, L. (2017). Microservices: yesterday, today, and tomorrow. In Present and
ulterior software engineering (pp. 195-216). Springer, Cham.
Evans, J., Young, A., & Perry, R. (2019). Studying Courseware Using Microservices
Architecture Methodologies. Computer Science and Information Technology
Journal, 5(1).
González, R., Gascó, J., & Llopis, J. (2016). Information systems outsourcing reasons and
risks: review and evolution. Journal of Global Information Technology
Management, 19(4), 223-249.
Granchelli, G., Cardarelli, M., Di Francesco, P., Malavolta, I., Iovino, L., & Di Salle, A.
(2017, April). Towards recovering the software architecture of microservice-based
systems. In 2017 IEEE International Conference on Software Architecture
Workshops (ICSAW) (pp. 46-53). IEEE.

14MICROSERVICES ARCHITECTURE
Hao, Z., Novak, E., Yi, S., & Li, Q. (2017). Challenges and software architecture for fog
computing. IEEE Internet Computing, 21(2), 44-53.
Liu, S. M., & Yuan, Q. (2015). The evolution of information and communication technology
in public administration. Public Administration and Development, 35(2), 140-151.
Pahl, C., & Jamshidi, P. (2016, April). Microservices: A Systematic Mapping Study.
In CLOSER (1) (pp. 137-146).
Pautasso, C., Zimmermann, O., Amundsen, M., Lewis, J., & Josuttis, N. M. (2017).
Microservices in Practice, Part 1: Reality Check and Service Design. IEEE
Software, 34(1), 91-98.
Richards, M. (2015). Software architecture patterns. O'Reilly Media, Incorporated.
Thönes, J. (2015). Microservices. IEEE software, 32(1), 116-116.
Wolff, E. (2016). Microservices: flexible software architecture. Addison-Wesley
Professional.
Yang, C., Liang, P., & Avgeriou, P. (2016). A systematic mapping study on the combination
of software architecture and agile development. Journal of Systems and
Software, 111, 157-184.