Microservices Management Question Answer 2022

Microservices management
Name
Institution
Professor
Course
Date

Q1: The client wants you to write a monolithic application supporting all of the above
functionalities. State whether you agree with this request or not and why?
Answer:
I absolutely disagree with the customer request. The requirements provided by the client
are quite dynamic, and the requirements can be achieved by adopting a microservices
architecture. The monolithic application adopts monolithic architectural design in the software
development process, which composes all modules into one (Baboi, Iftene, & Gifu, 2019). It is a
tightly-coupled and it is must that all associated modules be present in order to compile the code
successfully. Monolithic applications have most of the functionalities coupled into one process,
and all components containerized to libraries.
Typically, monolithic applications should have a User Interface layer to capture and
present user data. The business application logic layer which defines functional behaviour of the
application, and data access layer which is used to communicate with database hosting
organizational data. Monolithic architecture can be the best methodology to start application
development because it is faster during the early stages of application development (Baboi,
Iftene, & Gîfu, 2019). Despite monolithic offering, the outlined benefit, the growth of codebase
brings code maintenance challenge. Notably, it is possible to develop an application with
required and manageable modularity and achieve clean code. However, the challenge is to
maintain the adopted modularity working in monolithic nature.
Similarly, microservices are defined as the collection of services that exist in an
ecosystem but work independently to achieve desirable results. By using microservices,
flexibility is guaranteed. It becomes easier to make changes in one of the product function

without affecting other coupled services in the organization (Di-Francesco, Lago, & Malavolta,
2019). Smooth monitoring can be achieved through microservice architectural design because
each service can be built in various technologies and APIs. It is easier to make changes into the
application, track changes being done by different team members, test application, and debug
errors.
From the client requirements, some of the applications such as employees' details will not
adopt the relational database. Some other services would adopt the relational database and this
makes it impossible to adopt the monolithic architectural design. With the client requirements,
adopting monolithic means developing two sets of databases, which is quite difficult to maintain
due to the tightly coupled nature of monolithic (Di-Francesco, Lago, & Malavolta, 2019).
Considering the client's requirements, some services like payroll and employee data are
interrelating and would keep changing. Therefore, changes from one service would affect all
other correlated services. In monolithic design, changes in one service require specific changes
to be done in other services to keep the application running effectively. As a result, changing all
interacting application due to changes from one application increases project development time
and cost. To resolve challenges associated with monolithic, developers should adopt
microservices which advocates for module modular design, and code reusability. A good
example can be observed when making changes from payroll reporting services and employee
attendance because changes from one module would not necessarily require changes from other
modules. In this regard, scalability, ability to integrate with other future technologies,
modularity, and loose coupling approach makes microservices suitable for the client's need.