The Aggregator Pattern provides a way for a client to obtain combinations of data from each microservice of a microservice-based application. However it is not exactly the same as an API Gateway.
The API Gateway Pattern provides a way for a client to obtain combinations of data from each microservice of a microservice-based application.
Problem Statement When upgrading from a monolithic architecture to a microservice-based architecture, the designer(s) can encounter situations where one service depends upon another. Upgrading the dependency can potentially disrupt the service, and in an extreme situation, the entire system, and possibly affect the development of the system. The solution to this problem is the Proxy
The Factory Method pattern is extremely useful when a class cannot decide in advance the class of objects it must create. The task of specifying the objects is given to the subclasses, instead. The class delegates responsibility to one of several helper subclasses, and the user localizes the knowledge of the delegate. Factory Method Pattern
Scope and context define not only roles but decision levels and rigor. It is an essential part in the objective development of an architecture.
Learning to present as an architect is as important as any design or technology skill. This module will help you improve your stakeholder outcomes and presentation skills.
An introduction to different types and elements of building an effective engagement model.
The technical loan request combines the concept of Technical Debt with a repayment schedule in work days, payment, or other means and allows the architect to ensure technical debt is both deliberate and prudent.
Stakeholder motivation helps in understanding the status of stakeholders in respect of a particular set of proposed changes. This can be used to understand how stakeholders position themselves in relation to a portfolio of assignments but it can also be used to assess how stakeholders will react to proposed changes in the architecture, and assess if these changes are feasible.
When delivering many services within a large organization, services have to be placed within some sort of organizational structure, otherwise it would be difficult to know who owns the service, where services can be found and how to get access to services. The description of how services are organized is the service landscape. The service landscape is rather like a map for services and contains number of service domains, where a service domain is a logical grouping of services.