University Report: MIS603 Micro Services and Architecture Assessment

This report delves into the realm of microservices architecture, exploring its evolution from historical computing paradigms to its contemporary relevance in information systems. The report focuses on the application of microservices within contemporary suites, emphasizing the crucial role of software architects in designing and customizing information systems to meet specific needs. It examines various software architectural patterns, including the master-slave, broker, and peer-to-peer patterns, and assesses their suitability for modern business environments. The discussion covers the software architecture's key responsibilities, such as system design, risk analysis, and ensuring quality attributes like maintainability and user experience. The report highlights the significance of selecting appropriate patterns to facilitate efficient client management, online booking, and data security. It also examines the importance of aligning software design with current market trends and legal requirements to enhance the competitiveness and reliability of contemporary suites.

Running head: MICRO SERVICES AND ARCHITECTURE
MICRO SERVICES AND ARCHITECTURE
Name of the Student:
Name of the University:
Author Note:

1Micro Services and Architecture
Executive Summary
Now-a-days it has become very important to use specific software by the contemporary suite for
booking and keeping record of the clients. Software architects are hired for that purpose to
design and customize the needs of the suit which will be easier and convenient to handle by the
suite personnel. This report shows the types of software architectural patterns for contemporary
suits.

2Micro Services and Architecture
Table of Contents
1.1 Introduction................................................................................................................................3
1.2 Discussion..................................................................................................................................3
1.3 Conclusion...............................................................................................................................10

3Micro Services and Architecture
1.1 Introduction
During 300 B.C. abacus was used by people to calculate certain numbers. Technology
has improved and travelled a lot to reach the present era. From Calculator to mobiles everything
has changed. Computing is basically the activity which involves the usage of computers by the
business officials to manage, communicate, and keep record or information and process. Since
decades, the technology for computing has evolved and being in use by the software engineers,
information systems, computer science and information technology. Since then everything has
become digital and business of every type is mainly supported by software technologies. The
information system used in the contemporary suite is quite different from the various generations
of technology even with the usage of it because the information system used there only possesses
simple technology of customized software which records the customer’s information, their
check-in records and check-out records and informs them before the check-out time exceeds. If
any extra essential was ordered by the customer then it is also recorded in the system so that at
the final billing all the expenses along with their information can be recorded. This is used
differently from other technologies because it is easier to handle by receptionists.
1.2 Discussion
Every contemporary suite needs to hire a software architecture so that they can design a
proper and required information system which will be easier to handle and understand by the
receptionist of the suite. The software architecture have to keep in mind the present need of that
suite, the history of issues that the suite faces and their future needs as well (The Balance Small
Business., 2020).

4Micro Services and Architecture
A software architecture is someone who would describe the main components, the
structure and the relationship as well as interacting with each other. They prepare any blueprint
of a system which will be used by the business for their purpose. While designing an information
system and software the software architecture have to keep in mind regarding the business
strategy, their attributes, their IT environment, design of their enterprise and human dynamics
(Tutorialspoint.com., 2020). The main work of the architecture is to provide the enterprise with a
digital solution for properly coordination and communication mechanism among the
components. They have to select the required structural elements along with the interface with
which the system in connected. There are many points which needs to be kept in mind by the
software architecture like negotiating system requirements and also to put expectations of the
business from their customers, management personnel and the market. They have to guide
implementation tasks, manage coding part, do integration, and include detailed design and also
the testing part as well.
Apart from these works, the software architecture also have to do risk analysis so that if
there is any loophole in the system then it can be identified and solved accordingly. Some of the
goals of Software architecture while doing the work is to explain the system structure as well as

5Micro Services and Architecture
hide all the implementation details of the contemporary suite (Völter et al., 2013). The history of
the suite shall be properly realized by the architecture so that a proper software can be
developed. The needs and requirements of the stakeholders also have to be kept in mind and
addresses. The software must be designed in a very modern way so that market position can be
improved with the help of the software system. They have to handle both the quality and
functional requirements of the business. One of an important goal of the software is to develop
the external confidence of the organization through the help of the system and the work which
are confidently managed by the suite.
It is important for the contemporary suites to get the help form the software architecture
because a specific design is needed to manage and record the information of the customers by the
suite personnel and it has to be properly customized according to the need of the contemporary
suite. The main role of software architecture is to provide a proper technical solution for their
entire application. The software architecture should be expert is designing a proper information
system which will include the required approaches and different methods like event-driven
design, object-oriented designs and etc. the software architecture will also develop a team and
coordinate their efforts for the purpose of developing the software (Medium., 2020). The
architecture will review the prepared design by the team and then evaluate the needs before the
tradeoff part. The process will start from investigating and extracting the required information
and data form the records and then evaluate & analyze it so that a proper blueprint of the plan
can be made which will be complete and consistent. The team will then coordinate and divide
different portion of the work between them so that their will not be clash among them and the
technology is available in a short time span.

6Micro Services and Architecture
The team will consist of the technology experts who will be developing and customize
the software according to the need of the suite. The experts will have to coordinate their work
while selecting the programming language, then planning a proper blueprint, maintaining all the
framework and revising the database and platforms. Some other works which the software
architecture have to keep in mind are to facilitate some technical work and the reinforcing their
trust over each other. The deliverables of software architecture is to provide a functional
description of the information system to the suite.
The quality which must be possessed by the software architecture is to have a great
knowledge of the software types and technologies so that they can understand the needs of the
contemporary suite and design the software according to that. They must know the
implementation system so that they can differentiate between the good one and the bad one. This
overall factor depends upon the system design, the runtime behavior of the system and the user
experience from it. Although the quality attributes can be easily classified as static or dynamic
quality attributes. Static quality reflects the system and organizational structure which are
considered to be directly related to source code and the design of the system (Taylor & Francis.,
2020). Dynamic quality attribute reflects the behavior of that specific system while it was in
execution. Dynamic qualities are directly related with the system’s architecture, configuration,
source code, deployment parameters of the system, the environment and the platform of system.
Both the quality attributes are visible to end-users however, static quality can affect the
maintenance and development cost of the system like the testability, maintainability, modularity
and etc.
The quality scenario of the system can specify what attributes to be prevented to
eliminate failure. These can be divided according to their specification:

7Micro Services and Architecture
 The external and internal source like the people, software, hardware and the physical
infrastructure of the contemporary suite which creates stimulus.
 Any of the condition which can be considered after it arrives on the system.
 The environment speaks about when the stimulus occurs and in which kind of conditions.
 Some of the parts of that system can be the attribute like the persistent storage, processor,
processors, channels, processes and etc. (Richards, 2015)
 The responses like the detection of faults, disabling the event source and etc. and the
measure of those responses which occurred while testing.
It is important for the business of contemporary suite to keep every record of every
customers so that is the customer repeats their trip then they can be availed with special offers
and some of the important preferences can also be recoded which helps the suite personnel to
customize the service for them specially (Meeting Tomorrow., 2020). Master-Slave pattern of
the software design might be the best suited for any contemporary suite because this pattern
consists basically of just two parties the master and the slave and no other third party can access
the software form any device (Synopsys.com., 2020). The master component of this software
allows the work to get distributed into identical slave components and then compares the results
with the returned result from slaves. The pattern shows that how the software architecture would
work (NordicIT., 2020). The master is the authoritative source and every slave database gets
synchronized with it. Only one master is there that means only one device will be termed as the
authoritative source. However, slave device can be more than two and they will be operated and
controlled by the master device. This pattern can be beneficial for the contemporary suite to
manage their operations and client booking form online or offline sources (martinfowler.com.,
2020).

8Micro Services and Architecture
Clients these days tends to book their suite form online sources and hence another kind of
pattern needs to be mixed with the Master pattern so that the contemporary suite can accept the
online bookings and the details of the customer (Kircher & Jain, 2013). However, some legal
details must be fulfilled by the customers when they physically reach the suite because the
database needs to keep record of some legal frameworks and client’s authenticity. Another kind
of pattern which can possibly be beneficial in this digital era is the Broker pattern which can be
mixed up and customized as per the business (Garcia, Ivkovic & Medvidovic, 2013, November).

9Micro Services and Architecture
This pattern involves a third party that is the broker in between clients and the suite. This
can be quite risky for the business because some of the information can easily be hidden by the
broker or the customer (Kotlarsky & Zhu, 2016). However, it is necessary to involve the broker
in between and some of the access should also be hidden form the broker so that it cannot be
illegally used. Clients prefers to contact the suites through different brokers they provide the
information of every suites along with special offers (Kotlarsky & Zhu, 2014).
The business have to maintain some kind of spreadsheet and presentation directly from
the application so the software needs to be designed in such a way so that the suite personnel can
easily access whenever any record is needed at any point of time (Bijvank, Wiersema & Köppe
2013, October). The software have to be much developed in comparison with other
contemporary suits in competition because clients prefers those suits which offers fast check-ins
and check-out and also offers them with amazing deals and offers. However, the legal processes
cannot be compromised and it also increases the authenticity of the suits which is again one type
of requirement of the customers as well while booking (Almorsy, Grundy & Ibrahim, 2013,
May).
There are many types of broker software like Apache ActiveMQ, RabbitMQ, JBoss
Messaging and Apache Kafka. The software architect have to have good knowledge regarding
the current trend and need in the market for the client and design a proper software which will be
beneficial for both the parties and they can use it conveniently. However, another kind of pattern
can also be mixed which is Peer-to-peer pattern so that the clients can easily and directly contact
the suite for any important and personal information without any middle person. The multimedia
protocols which can be involved like P2PTV and PDTP.

10Micro Services and Architecture
1.3 Conclusion
After the discussion on the definition, work and the duties of the software architecture, it
can be concluded that a software architecture is considered to be the important personnel because
an architecture knows the market trend and need from the suite. The convenience and the legality
of the booking procedures and record keeping must be kept in mind by the software architecture
while designing the most appropriate model of information system. The system must be easy to
handle and the access should be specified and restricted to specific people. There are different
types of software architectural patterns which can be presented as an option to the contemporary
suite like the layered pattern, Client-server pattern, Pipe-filter pattern, Master-slave pattern,
Broker pattern, Event-bus pattern, peer-to-peer pattern, Model-view-controlled, Blackboard
pattern and Interpreter pattern. However among all these options the mixture of Client-server
pattern and Broker pattern seems to be the most suited for the contemporary suit business
because the customer have to contact the broker when doing online booking and the access by
the suite personnel should be allowed to them only and not to any other third party. The legal
proceedings should also be kept in mind while designing the software.

11Micro Services and Architecture
References:
Almorsy, M., Grundy, J., & Ibrahim, A. S. (2013, May). Automated software architecture
security risk analysis using formalized signatures. In 2013 35th International Conference
on Software Engineering (ICSE) (pp. 662-671). IEEE.
Bijvank, R., Wiersema, W., & Köppe, C. (2013, October). Software architecture patterns for
system administration support. In Proceedings of the 20th Conference on Pattern
Languages of Programs (pp. 1-14).
Garcia, J., Ivkovic, I., & Medvidovic, N. (2013, November). A comparative analysis of software
architecture recovery techniques. In 2013 28th IEEE/ACM International Conference on
Automated Software Engineering (ASE) (pp. 486-496). IEEE.
Kircher, M., & Jain, P. (2013). Pattern-oriented software architecture, patterns for resource
management (Vol. 3). John Wiley & Sons.
Kotlarsky, A., & Zhu, X. (2014). U.S. Patent No. 8,844,822. Washington, DC: U.S. Patent and
Trademark Office.
Kotlarsky, A., & Zhu, X. (2016). U.S. Patent No. 9,355,288. Washington, DC: U.S. Patent and
Trademark Office.
martinfowler.com. (2020). Software Architecture Guide. Retrieved 8 March 2020, from
https://www.martinfowler.com/architecture/
Medium. (2020). 10 Common Software Architectural Patterns in a nutshell. Retrieved 8 March
2020, from https://towardsdatascience.com/10-common-software-architectural-patterns-
in-a-nutshell-a0b47a1e9013
Meeting Tomorrow. (2020). History of Computing. Retrieved 8 March 2020, from
https://meetingtomorrow.com/blog/history-of-computers-and-computing/