Analysis of Alternative Applied Cloud Concepts in AWS Report

This report provides an analysis of alternative applied cloud concepts in AWS, focusing on the transition from a monolithic architecture to a microservice approach for a travel booking application, DTGOV. The report begins by evaluating existing modules and identifying the best fit for the application, and then explores the need for refactoring to address workload peaks and improve fault isolation. The transition to microservices is discussed, including the benefits of improved flexibility, simplicity, and resource utilization through the use of containers and virtual machines. The report details the refactoring strategy, emphasizing the extraction of modules based on their benefit to the application and the changes needed to break dependencies. Finally, the report presents an architectural overview of the travel booking application after the transition to a microservice approach, providing a comprehensive understanding of the concepts discussed.

Running head: ALTERNATIVE APPLIED CLOUD CONCEPTS IN AWS
Alternative Applied Cloud Concepts in AWS
Name of the Student
Name of the University
Author’s Note

1
ALTERNATIVE APPLIED CLOUD CONCEPTS IN AWS
1. Module Assessment
1.1. Answer to Question 1
The module “cart” is proved to be the best according to its stability after the above
mentioned modules are evaluated representing the application for travel booking for
DTGOV. This module is regarded as the best because this module lets the customer to add
the selected items in the cart and later the combination of it with other modules is possible
(Guidi et al., 2017). To check the communication of data between the modules an integration
test can be done.
1.2. Answer to Question 2
Frequent modification is required in the travel-recommending engine as because the
data of the travel requirement engine is needed to be checked and thereafter recommendation

2
ALTERNATIVE APPLIED CLOUD CONCEPTS IN AWS
is required to be provided. Users fill up the travel requirement and this data is compared to
the database of DTGOV by the accommodation engine in such a way that will pass the data
to the accommodation and travel processing engine for the provision of recommendation to
the user.
1.3. Answer to Question 3:
Workload peaks may be experienced by the travel accommodation processing engine
as it requires data which will be processed and if the number of requests increase then it is
likely for the user to wait for longer period of time to receive the recommendation.
2. Transition to Microservice Approach
2.1. Refactoring is done in order to have the transformation from monolithic approach to
microservice approach to have the opportunity of building new applications with
microservice. Further development in this sector would make the monolithic functions of
application disappear and it will transform to have microservice functions Butzin, Golatowski
& Timmermann, 2016). The first module to be refactored will be the travel requirement
module because of its easy designing and thereafter user inputs can be received by it, which
will be stored in the database, and with the help of legacy monolith the data can be integrated.
2.2. The problem of workload peaks can be removed with the help of microservice approach.
The microservice approach leads to the improvement of the fault isolation and the failure of a
single module will result into no effect at all. The elimination of the technology lock can also
be done by it and trying new technology for the need of service becomes more flexible. The
modules become less dependent to each other and any changes can be reverted back applied
to the module (Bloch et al., 2017). The addition of simplicity is done and it makes the
functions of the service easily understandable to the users. The hardware resources could be
used for the implementation of microservice when dedicated access will be provided to the

3
ALTERNATIVE APPLIED CLOUD CONCEPTS IN AWS
resources and that could be done by using the containers, which will isolate the processes.
Virtual machine those are available in AWS can be used in the implementation of
microservice and the packages of lightweight microservices cannot make any difference in
the VM and thus reducing the cost effectiveness. The implementation of the codes can be
done using Open Service Gateway Initiative and the configuration of the services are done in
such a manner that it can run in a Java Virtual Machine (van der Geest et al., 2018). The
model that is existing at the moment requires to be converted into a Standalone microservice
and most of the modules are when converted the monolithic approach is seemed to disappear
or it become a service.
3. Moving to microservice approach for improving DTGOV’s ability for maintaining
high availability for the application – For the conversion of the monolith module existing
at the moment to a standalone microservice the usage of refactoring strategy is used. The
extraction of the module is done and for shrinking the monolith the module is turned into a
service. It is challenging to sort out the modules that need to be extracted and the one on
which the extraction could be done easily is extracted first. The identification and thereafter
the extraction of the module is done based on the highest benefit that a module can serve to
the application. The ranking of the modules is done considering the amount of benefit they
are serving to the application and then the extraction of the module is done followed by its
development and its implementation for the acceleration of theprocess of development
(Cerny, Donahoo & Trnka, 2018). Modules having different resource requirement from that
of the rest of the monolith can be extracted for scalability increment of the application. There
are some important changes that needs to done for the breakage of dependency to turn the
module into a standalone service (Kuo et al., 2017).

4
ALTERNATIVE APPLIED CLOUD CONCEPTS IN AWS
4. Architecture of Travel Booking Application after transition to microservice approach

5
ALTERNATIVE APPLIED CLOUD CONCEPTS IN AWS
References
Bloch, H., Fay, A., Knohl, T., Hoernicke, M., Bernshausen, J., Hensel, S., ... & Urbas, L.
(2017, September). A microservice-based architecture approach for the automation of
modular process plants. In 2017 22nd IEEE International Conference on Emerging
Technologies and Factory Automation (ETFA)(pp. 1-8). IEEE.
Butzin, B., Golatowski, F., & Timmermann, D. (2016, September). Microservices approach
for the internet of things. In 2016 IEEE 21st International Conference on Emerging
Technologies and Factory Automation (ETFA) (pp. 1-6). IEEE.
Cerny, T., Donahoo, M. J., & Trnka, M. (2018). Contextual understanding of microservice
architecture: current and future directions. ACM SIGAPP Applied Computing
Review, 17(4), 29-45.
Guidi, C., Lanese, I., Mazzara, M., & Montesi, F. (2017). Microservices: a language-based
approach. In Present and Ulterior Software Engineering (pp. 217-225). Springer,
Cham.
Kuo, J. H., Ruan, H. M., Chan, C. Y., & Lei, C. L. (2017). Toward High Throughput
Backend Provision for Mobile Apps with A Microservice Approach. In Proceedings
on the International Conference on Internet Computing (ICOMP) (pp. 59-64). The
Steering Committee of The World Congress in Computer Science, Computer
Engineering and Applied Computing (WorldComp).
van der Geest, J., van den Broek, C. C., Bastiaansen, H. H., & Schenk, M. M. (2018).
Enabling a Big Data and AI Infrastructure with a Data Centric and Microservice
Approach: Challenges and Developments. In NATO STB IST-160 Specialists’
Meeting.

6
ALTERNATIVE APPLIED CLOUD CONCEPTS IN AWS