Microservices are Loosely coupled service oriented architecture with Bounded Contexts.

If we are knowing too much about the other services to build a new Microservice then we are not having Bounded Context. If every service has to be updated at the same time it’s not loosely coupled

In Service oriented architecture, we have dummy services and smart enterprise service bus, most of the validation, routing and transformation is handled in enterprise service bus, as the number of services grow and changes to one service will effect the others and Continuous deployment will not be feasible.

In MicroServices services are smart they do validation,transformation and handle business logic, and they use only Message Brokers like ActiveMQ or RabbitMQ but not enterprise service buses, with this they are loosely coupled from other services and easy to implement Continuous deployment.

Principles of MicroServices

  • Domain – Bounded Contexts can help you find stable, reusable boundaries
  • Culture Of Automation
    • Continuous Delivery, Integration
    • Docker
    • Vagrant
  • Abstraction (Hide Implementation Details)
  • Decentralise All The Things
  • Deploy Independently
  • Consumer First
  • Isolate Failure -[Circuit Breakers]
  • Highly Observable