
The Microservices ManifestNO,
Dutch Edition
• Being antifragile.
• Being darwinian in nature.
• Being exactly 100 lines long.
• Be in its own process.
• Using lightweight mechanisms to work with other microservices.
• Being independent.
• Do one thing, and do it well (as opposed to not doing it well…)
• Being independently deployable
• Being small and self-contained
• Being consumer-driven contacts
• Being clearly bounded
• Being discrete (and discreet?)
• Have “just enough” validation
• Being one business capacility
• Being isolated, and separate from other things
• Being named
• Being a sub-process
• Being able to scale well
• Being small
• Being small enough to throw away
• Have no shared DTOs
• Use REST at all times
• Use the right protocol for the context
• Being organic
• Being hot and new, and confusing
• Embrace fall-back
• Being self-healing
• Being about components
• Being the smallest level of abstraction possible, but no smaller
• Being resilient
• Being decentralised