2 ms·
Even Martin Fowler writes that DDD is for large, complex software. He also recommends monoliths before microservices. If you're writing something that should t
by bcrosby95 7y ago
Even Martin Fowler writes that DDD is for large, complex software. He also recommends monoliths before microservices.
If you're writing something that should take you one month it is not large and complex. It is not suitable for DDD or microservices.
Microservices are not always micro. It's a bad name. Teams of 5-10 oftentimes work on only a single microservice. 1 microservice can be millions of lines of code.
- neya 7y agoSee, this is the problem. See, the definition of microservice (in DDD context) is so vague, it keeps varying, but according to books on microservices, they're supposed to be simple and broken down parts of a larger system. Definitely not a million lines of code.
- bcrosby95 7y agoI think you're reading a lot into those books. Microservices were pioneered at companies with thousands of engineers. That is where they shine. Small is relative. The point of a microservice is to allow a smallish team of 5-10 people make their changes independent of all other teams. That is their primary purpose. To make sure your thousands of engineers aren't stepping on each other's toes. All other benefits range from minor to bullshit, especially if you don't have a huge engineering department. The above applies even if you don't use DDD. DDD oftentimes goes along with microservices because their bounded contexts are a good way to split your microservices.