The following diagram illlustrates microservice and event-driven architecture for a blockchain application:

We've labeled this pattern as microservice and event-driven because this is the pattern most often seen for those types of architectures. However, the particularity of this pattern comes from the gateway. Such a system will not perform any data mapping; it will leverage a common communication protocol (HTTP) and data format (typically JSON, but it could be XML). There is also an expectation that the services will already be designed to understand the semantics of the data being transacted. Events are also propagated through the same protocol and data format.

Again, microservice applications tend to be newer applications, and they benefit from a more fine-grained interface. As such, they tend to evolve more quickly and be in a position to adapt and adhere to the transactions from the network. Similarly, event-driven applications will benefit from their low coupling to the other components of the system, and so are good candidates for this pattern.