HW04 | Advanced software engineering | University of Western Australia

Question 1 (Microservices Architecture)

a) Three Points of Impression

In this consideration, the three specific points that have been most impressing are stated below for proper understanding:

  1. The consideration and assessment of monoliths and microservices have been most impressing. The aspect of graphic presentation have been directed effectively

  2. The detailed description of Conway’s laws of action has been another impressing aspect of the specific article under consideration. The three layer structure associated with people and systems have been commendable (Martinfowler.com, 2020)

  3. Another highly impressing factor within this article is the appropriate presentation of the comparative structure of a monolithic database of single approach and a specific microservices database on an application structure

b) Presentation of Monolithic Applications

Monolithic applications are related with proper definition and development of a single database architecture and consideration. The presentation of the functionalities within a single process has been stated through direct application and determination. The direct conceptual approaches for such static systems have been improper under application (Martinfowler.com, 2020). In case of major applications, the monolithic structures and systems have to be processed through inclusion for the same range of functions for the considerable division within the structures and their values.

c) Comparison and Contrast (Component Libraries and Web Services)

            In this tabular structure, the strategic comparison has been related with appropriate determination and adjustment for the structures.

Component Libraries

Web Services

In case of Component Libraries, they are not deployable

In case of Web services, they are effectively deployable

In case of component libraries, if any one component has to be changed, the entire application needs to be redeployed

In case of web services, the approach of multiple services makes it effective to change a single service without redeploying the entire application

In terms of microservices architecture, minimization through cohesive services are not applicable here

In terms of microservices architecture, minimization through cohesive services are effectively applicable here

Table 1: Comparison and contrast table

d) Comparison and Contrast (Centralized Governance/data management and Service oriented applications)

Centralized data management

Service oriented application

In this structure, the presented application is static and is associated with only one approach

In this structure the services are associated with multiple ways of application and assessment

There is only one conceptual model for every service through a centralized structure

In this prospect, there are multiple models under consideration for the structures and approaches

This type of data management is related with strategic consideration and assessment of the structures

The service oriented approach, as the names states is a consideration of the relevant analogy of service-specific data requirements

Table 2: Comparison and contrast table

Question 2 (Microservices Architecture)

In this particular association, the tabular structures are associated with presentation of breakdown designing for the approach of two factor authentication and password recovery.

Two Factor Authentications

Enter Username and Password

Match username and password

Enter registered Phone Number

Send OTP to registered phone number

Enter OTP for second authentication

Evaluate and Confirm User


Password Recovery

Enter Username and Password

Password Does not match

Enter registered email for password recovery

Send recovery link to registered email

Enter and confirm new password

Enter Username and new Password

Evaluate and confirm user


Question 3 (Microservices Architecture)

            In this particular approach, the direction has been associated with presentation of a RESTful design for the systems of photo printing through the micro services architecture consideration. The diagram presented below would suffice. The input and output have been depicted through specific arrows.


Figure 1: RESTful approach

Question 4 (Cloud Computing)

a) Key Issues

            In this particular consideration, the key issues related with both multi-tenant and multi-instance database have been associated for implementation of proper SaaS architecture under processing and management. The presentation of key issues related with multi-tenant systems have been stated initially:

  1. The non-flexible nature of such database management systems while implementing SaaS structure acts as a major disadvantage for the systems

  2. Among another major issue, the consideration of strategic planning and assessment of the systems security is a critical factor for such multi-tenant applications

  3. In terms of complexity, the multi-tenant systems are much more complicated in their various approaches compared to other types of database operations

The application of major issues within multi-instance database management systems have been stated below:

  1. One of the major issues with such systems are their highly expensive nature of operations for the implementation of SaaS architectures

  2. Another major issue with the multi-instance database structure are the application of update management perspectives that are necessary for operations

b) Comparison of most important factor

            In terms of choosing a cloud system for development and software delivery, the structure of cost and budget is not necessary to be considered as a big factor because of the four reasons that have been stated below:

  1. Expensive cloud operations come with enhanced application of flexibility and ease of operation through their highly simple yet sophisticated structure capable of doing various applications

  2. The consideration of costlier solution also comes equipped with proper data security and secure operational capability for the systems for processing necessary secure links

  3. Another concept that needs to be kept into consideration is the structure of scalable nature of the clod operations that the expensive variants provide better than the cost-effective ones

Question 5 (Microservices Architecture)

a) Advantages of using the services

            In this particular consideration, the valid points of discussion have been depicted to determine the proper approach and analysis of using services as a fundamental component in distributed system software:

  • Services are highly flexible and operational considering specific approach to valid requirements can be done through determination of what service is required and why

  • In terms of using cloud application systems, services provide a specific path for each layer of operation and adjustment for the systems architecture to abide through

  • The consideration of management of services are highly efficient for the fundamental requirement of processing certain changes and adaptations to the systems as required

  • Service operations also provide proper scalable nature of approach and definition to the systems through direct analysis and adjustment for the valid specifics of operation

b) Principles problems and their mitigation

            In this strategic concept, there are two principle problems that have been associated with multi-tier software architecture. The operations are necessary to be stated for the mitigation systems under management and requirement through microservices application as stated below:

  1. In case of adaptation and change management, the entire structure has to be reshaped, rebuilt and re-deployed fort the multi-tier architecture. Microservices provide the path for operation and development of service-specific adaptation or change without having to harm the structure of the entire system

  2. In case of increase in specific demand of the operational capability of multi-tier software systems, they require to be scaled up through detailed processing for each of layers under deployment. Microservices help through scaling specific service structures that would suffice for the growing demand of the systems

Question 6 (Microservices Architecture)

a) Explanation of data requirement

            Each microservices should maintain its own data because that would increase the amount of data accountability and consistency throughout the systems and their applications. The direction of data control and management is necessary to be done even at the minute level of operations for any system. The way to keep data service replicas consistent into the systems is by operating through direct assessment of the inclusion of certain mechanism that would simultaneously keep on data copies for the replication of services within the system.

b) Timeout and its uses

            A timeout is associated through specific application of a counter that is stated with request of services and their initiation. The consideration of preferred value in seconds is then counted and the service request failure is assumed after the passage of that countdown. Failure management is stated with the help of time preference through such service. A circuit breaker acts more efficiently as it specified the exact requirement of service through the request. The timeout countdown slows the systems and the circuit breaker take immediate action for the failed services and their approaches, thus keeping the systems up and running smoothly.

Question 7 (Cloud Computing)

            Continuous deployment is needed to be used in microservices architecture because it is an advanced system that depends on automation technique and keeps the system continuously updated with the proper operations. The modification of any service prospect is automatically re-deployed with such a system. The brief presentation and explanation of the stages in the continuous deployment pipeline has been stated below:

  1. Running Unite Tests is the initial approach that is related with proper consideration of the basic changes to be implemented

  2. Building Test Systems is the initial presentation of change in physical design for the service through prototyping

  3. Running Integration Tests is the approach that is done to ensure that the operations are highly operations with the service

  4. Containerizing services is done after the previous operations are successful and the new changes are ready for packaging

  5. Deploying service containers is done after the packaging is complete and the main service is replaced with the new changes

  6. Running acceptance tests is the final evaluation done after basic consideration of the deployed packages working efficiently

  7. Replacing Current Service is the final structure of entire application of replacing the service with the respective changes

You may also like similar pages such as Engineering AssignmentEngineering Assignment | Best Assignment Experts


Martinfowler.com, 2020. Microservices. Retrieved from https://martinfowler.com/articles/microservices.html [20/08/2020]



No Need To Pay Extra
  • Turnitin Report

  • Proofreading and Editing

    Per Page
  • Consultation with Expert

    Per Hour
  • Live Session 1-on-1

    Per 30 min.
  • Quality Check

  • Total


New Special Offer

Get 25% Off


Call Back