Microservice Architecture

—

• Offers an architectural model to develop your modules to be compatible to microservice development and deployment.
• Provides to develop your module standards-compliance.
• Provides base infrastructure to implement Domain Driven Design in your microservices.
• Provide services to that makes easy to consume your services from another service/application.
• Provides a distributed event bus to communicate your services.
• Provides many other services to make your daily development easier.

One common advise to start a new solution is always to start with a monolith, keep it modular and split into microservices once the monolith becomes a problem. This makes your progress fast in the beginning especially if your team is small and you don’t want to deal with challenges of the microservice architecture.

ABP can help you in that point by offerring a microservice-compatible, strict module architecture where your module is splitted into multiple layers/projects and developed in its own VS solution completely isolated and independent from other modules. Such a developed module is a natural microservice yet it can be easily plugged-in a monolithic application. See the that offers a microservice-first module design. All standard ABP modules are developed based on this guide. So, you can use these modules by embedding into your monolithic solution or deploy them separately and use via remote APIs. They can share a single database or can have their own database based on your simple configuration.