Full Stack Development with JHipster

Architecture considerations

We have already discussed choosing a microservice or monolithic architecture in Chapter 1, Introduction to Modern Web Application Development. Here are some more points when it comes to architecture:

• Don't use a microservice architecture if you're a small team. Microservices are about scaling teams more than anything. It's often easier to break up your monolith than start with microservices.
• Use asynchronous messaging in your monolith if you think you may need to refactor to microservices in the future. JHipster provides support for Apache Kafka, which is a good solution for asynchronous messaging. 

Asynchronous messaging is the best way of building stateless systems. It is important in a microservice architecture ...