Hexagonal Architecture in Microservices Patterns

An example of a hexagonal architecture, which consists of the business logic and one or more adapters that communicate with external systems. The business logic has one or more ports. Inbound adapters, which handled requests from external systems, invoke an inbound port. An outbound adapter implements an outbound port, and invokes an external system.

An important benefit of the hexagonal architectural style is that it decouples the business logic from the presentation and data access logic in the adapters.

The business logic doesn’t depend on either the presentation logic or the data access logic. Because of this decoupling, it’s much easier to test the business logic in isolation.

Another benefit is that it more accurately reflects the architecture of a modern application.

The business logic can be invoked via multiple adapters, each of which implements a particular API or UI.

The business logic can also invoke multiple adapters, each one of which invokes a different external system.

The FTGO application has a hexagonal architecture. It consists of business logic surrounded by adapters that implement UIs and interface with external systems, such as mobile applications and cloud services for payments, messaging, and email.


Hexagonal architecture is a great way to describe the architecture of each service in a microservice architecture.

#hexagonal #architecture #microservice #patterns


要查看或添加评论,请登录

Pankaj Gajjar的更多文章

社区洞察

其他会员也浏览了