Microservices Architecture Report: Whiteboard Company Analysis

This report delves into the microservices architecture, examining its structure, benefits, and challenges, while also assessing its practical implementation. The report begins with an executive summary and an introduction to the Whiteboard Company, a provider of IT services for learning management systems. The core discussion covers the advantages of microservices, such as easier deployment, fault isolation, and the ability to use various programming languages. It also explores the challenges like management complexity, monitoring difficulties, and the need for DevOps culture. The report then examines service modeling, SOAP, REST, and XML-RPC protocols, and the challenges of splitting monolithic systems. The analysis includes examples of successful microservices implementations and concludes with recommendations for the Whiteboard Company and discusses ethical and legal issues related to microservices architecture. The report is supported by a comprehensive list of references.

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

1MICROSERVICES ARCHITECTURE
Executive Summary
This report will discuss the micro services architecture in detail. It is also discusses regarding the
White board company and it also discusses regarding how the microwave architecture is going to
be implemented in this company. This report also discusses regarding the examples of the
successful implementation of the micro service architecture for at least three different
companies. It also discusses regarding the principle for the service modeling and also discusses
different protocols like REST, SOAP, and XML. This report also concludes regarding the
challenges faced for the splitting of the monolithic system and also discusses regarding the
ethical and legal issues regarding the microwave architecture.

2MICROSERVICES ARCHITECTURE
Table of Contents
Introduction......................................................................................................................................3
Discussion........................................................................................................................................3
Conclusion.......................................................................................................................................9
Recommendation.............................................................................................................................9
References......................................................................................................................................11

3MICROSERVICES ARCHITECTURE
Introduction
The Whiteboard Company delivers the information technology services for providing the
learning management system (Balalaie, Heydarnoori & Jamshidi, 2016). It is for the students of
the six hundred universities and also different institutions across the globe.
This company wants to restructure the process that they had implemented earlier (Abts,
2013). They are trying to break the system into the micro wave services so that they can release
the code
This report discusses regarding the brief overview micro service architecture (Balalaie,
Heydarnoori & Jamshidi, 2016). This report also discusses regarding the successful
implementation of the micro service architecture in three different companies (Baranov et al.,
2016). It also discusses regarding the benefit of the micro service architecture. This report
discusses different technologies which are available for the integration like REST, SOAP, XML-
RPC and also the splitting of the monolithic system (Bloomberg, 2013).
Discussion
Micro service is used to structure the application as the different combination of the
services which are highly testable and also maintainable in nature (Buchan et al., 2013). It is also
loosely coupled and it is also developed in an independent manner.
The companies that implemented the micro service architecture in Australia include
Fujitsu Global, Martin Fowler, and InfoQ.
The benefits of the micro services architecture include:

4MICROSERVICES ARCHITECTURE
 Software developed using the micro services architecture is divided into
many smaller parts so that each of the services can be deployed very easily
(Bülthoff & Maleshkova, 2014).
 It also gives the better isolation regarding the fault (Dmitry & Manfred,
2014). If a micro service fails, then the others will continue working with
the software.
 Code for the several services can be written in various languages.
 The services can be easily integrated and it can be deployed automatically
(Dospinescu & Perca, 2013). This can be done by using the continuous
tools such as the Jenkins etc.
 This architecture will provide the user the continuous delivery of the
software.
 This type services are very easy to understand because it represents the
small functionality and developers can change the functionality very
easily.
 The code is organized in such that it can be altered according to the
business capabilities.
 It will make the monitoring of the micro services very simple because the
various part of the application is isolated (Esposito, Castiglione & Choo,
2016).
 It will increase the productivity of the development team within a
company because the idea can be implemented and also developed without

5MICROSERVICES ARCHITECTURE
the coordination of devliary function related to the information
technology.
Challenges of the micro services include:
 Managing the micro services
If the number of the micro services increases those managing the
micro services become more challenging (Esposito et al., 2017). It is
very vital that the management is discussed regarding the micro
services before it is being implemented (Hashmi et al., 2013).
 Monitoring
The traditional forms of the monitoring and also the diagnostic will not
able to align with the micro services because, the company have the
services of the same functionality (Koubaa, 2014).
 Embracing DevOps Culture
Every team needs the autonomy; agility and also the delivery of the
services in continuous manner are not able to deliver the initial
delivery of the software (Malavalli & Sathappan, 2015).
 Fault tolerance
It is very important that the individual services are not responsible for
the failure of the entire system (Mumbaikar & Padiya, 2013). The
complexity of application is already pre known to the developer
(Namiot & Sneps-Sneppe, 2014). The failure of the application is

6MICROSERVICES ARCHITECTURE
guaranteed and also un avoidable in nature. Micro services can able to
tackle the inside as well as the outside failures of the application.
 Testing
Testing of the micro services architecture is very much complex than
the others because of the various services, integration among those,
and the dependency among them (Nolan & Lang, 2014). The
asynchronous micro service makes the test cases very difficult in the
lower environment (Sharma et al., 2015).
 Design with failed mentality
When more failure situations are determined by the development team
then the various number of the exception handling mechanism has to
be designed and also different resolution of the issues will be handled.
 Cyclic dependency
Management of the dependency among many services are very
important (Sundvall et al., 2013). The cyclic dependencies can be very
difficult if the difficulties are not properly identified as well as solved.
Service modeling is a kind of the modeling for the business as well as the software. It is
used for purpose of the design and also specifies the business systems which are service oriented
in the various types of the architectural styles (Wolff, 2016). It involves the modeling language
that can be implemented from the ‘problem domain of the organization’ and also ‘solution
domain of the organization’ (Wu & Zhu, 2016).
SOAP is a messaging protocol. It has the specification for exchanging the information in
the category of the web services in the domain of the computer networking. The purpose of this

7MICROSERVICES ARCHITECTURE
service includes extensibility, neutrality and also the independence. It uses different protocols
includes ‘Hyper Text Transfer Protocol’, ‘Simple Mail transfer Protocol’. SOAP was developed
to work with the XML and also with the HTTP (Wolff, 2016). The SOAP has two elements-
Envelop elements and header elements. The envelop element detects the XML document in the
form of the SOAP message. It is used for the encapsulation of all the details in the SOAP
message (Sudvall et al., 2013). The header element only contains the header information of the
particular application (Sharma et al., 2015).
REST is a stateless protocol. It is also cacheable in nature (Nolan & Lang, 2014). The
client, server and the intermediate components can have the resources related to the cache for
improving the performances.
XML-RPC is the protocol for using the XML for encoding the HTTP calls for the
transport mechanism (Balalaie, Heydarnoori & Jamshidi, 2016). SOAP is the successor of the
XML-RPC protocol. There is framework named Liberant that provides the creation of the RPC
servers as well as clients.
There are different kinds of the challenges that are involved in the system (Baranov et al.,
2016). When a company wants to shift from the monolithic to the micro services than it creates
many small modules. Tracking the performance for these kinds of the business transactions can
be very difficult (Bloomberg, 2013). This can be tackled with the different kinds of the methods
which includes the ‘tokens’, ‘ids’ and the ‘headers’. Micro services are very in effective in nature
because of its statelessness. The developer can generate various numbers of the logs for finding
out the problem in a very easiest manner (Buchan et al., 2013). It gives the extra effort on the
operations of the application (Bülthoff & Maleshkova, 2014).

8MICROSERVICES ARCHITECTURE
There are lots of the legal issues related to relate to the micro services architecture. For
resolving this company has to implement the ‘Conway’s law’ (Dmitry & Manfred, 2014). The
law is about the on the reason that in order for the module of the software to the function.
There are lots of security issues related to the micro services architecture (Dospinescu &
Perca, 2013). The most common problems related to the micro services are the issues related to
the implementation. Majority of the times these issues are injected by the developer in the
application (Esposito, Castiglione & Choo, 2016).
The ethical problems that are faced by the developer of the micro services architecture is
the delivery of the ultimate software, the process of the designing that application, and also
human to software interaction and many others.
Conclusion
This report concludes that the implementation of the micro services architecture is one
that nobody can think it off. For the advancement of the technology it is very important to
implement this kind of the technology in the software development industry. But it has some
legal, security and ethical issues. Many companies successfully implement the micro services
architecture in a very efficient way. This technology is using the concept of web services i.e.
‘REST’, ‘SOAP’, and ‘XML-RPC’. There are lots of challenges that can be faced by the
software company which is discussed above. There are lots of legal, ethical and security issues
related to the micro services architecture. The White board company should tackle these very
efficiently. In the micro services architecture the monolithic system can be a great factor. It can
be abused by the workers of the software company. For that the White board company can
implement the strong security measures in that application.

9MICROSERVICES ARCHITECTURE
Recommendation
Before implementing the micro services architecture an organization should follow the
following recommendations:
 The Whiteboard Company should detect the horizontal scale point.
 The Whiteboard Company should roll the updates and also the releases in the
week.
 The Whiteboard Company should understand the importance of the micro
services implementation.
 The Whiteboard Company should know the important reason for implementing
the micro services architecture is to communicate with the human.
.

10MICROSERVICES ARCHITECTURE
References
Abts, D. (2013). Aufbaukurs Java: Client/Server-Programmierung mit JDBC, Sockets, XML-
RPC und RMI. Springer-Verlag.
Balalaie, A., Heydarnoori, A., & Jamshidi, P. (2016). Microservices architecture enables devops:
Migration to a cloud-native architecture. Ieee Software, 33(3), 42-52.
Baranov, A. V., Balashov, N. A., Kutovskiy, N. A., & Semenov, R. N. (2016). JINR cloud
infrastructure evolution. Physics of Particles and Nuclei Letters, 13(5), 672-675.
Bloomberg, J. (2013). The agile architecture revolution: how cloud computing, rest-based SOA,
and mobile computing are changing enterprise IT. John Wiley & Sons.
Buchan, D. W., Minneci, F., Nugent, T. C., Bryson, K., & Jones, D. T. (2013). Scalable web
services for the PSIPRED Protein Analysis Workbench. Nucleic acids research, 41(W1),
W349-W357.
Bülthoff, F., & Maleshkova, M. (2014, May). RESTful or RESTless–Current state of today’s top
Web APIs. In European Semantic Web Conference (pp. 64-74). Springer, Cham.
Dmitry, N., & Manfred, S. S. (2014). On micro-services architecture. International Journal of
Open Information Technologies, 2(9).
Dospinescu, O., & Perca, M. (2013). Web Services in Mobile Applications. Informatica
Economica, 17(2).
Esposito, C., Castiglione, A., & Choo, K. K. R. (2016). Challenges in delivering software in the
cloud as microservices. IEEE Cloud Computing, 3(5), 10-14.
Esposito, C., Castiglione, A., Tudorica, C. A., & Pop, F. (2017). Security and privacy for cloud-
based data management in the health network service chain: a microservice approach.
IEEE Communications Magazine, 55(9), 102-108.

11MICROSERVICES ARCHITECTURE
Hashmi, N., Myung, D., Gaynor, M., & Moulton, S. (2013). A Sensor-based, Web Service-
enabled, Emergency Medical Response System. EESR, 5, 25-29.
Koubaa, A. (2014, February). A service-oriented architecture for virtualizing robots in robot-as-
a-service clouds. In International Conference on Architecture of Computing Systems (pp.
196-208). Springer, Cham.
Malavalli, D., & Sathappan, S. (2015, November). Scalable microservice based architecture for
enabling DMTF profiles. In 2015 11th International Conference on Network and Service
Management (CNSM) (pp. 428-432). IEEE.
Mumbaikar, S., & Padiya, P. (2013). Web services based on soap and rest principles.
International Journal of Scientific and Research Publications, 3(5), 1-4.
Namiot, D., & Sneps-Sneppe, M. (2014). On micro-services architecture. International Journal
of Open Information Technologies, 2(9), 24-27.
Nolan, D., & Lang, D. T. (2014). XML and web technologies for data sciences with R. New
York: Springer.
Sharma, A., Goyal, T., Pilli, E. S., Mazumdar, A. P., Govil, M. C., & Joshi, R. C. (2015,
December). A secure hybrid cloud enabled architecture for Internet of Things. In 2015
IEEE 2nd World Forum on Internet of Things (WF-IoT) (pp. 274-279). IEEE.
Sundvall, E., Nyström, M., Karlsson, D., Eneling, M., Chen, R., & Örman, H. (2013). Applying
representational state transfer (REST) architecture to archetype-based electronic health
record systems. BMC medical informatics and decision making, 13(1), 57.
Wolff, E. (2016). Microservices: flexible software architecture. Addison-Wesley Professional.

12MICROSERVICES ARCHITECTURE
Wu, X., & Zhu, H. (2016). Formalization and analysis of the REST architecture from the process
algebra perspective. Future Generation Computer Systems, 56, 153-168.

13MICROSERVICES ARCHITECTURE