3 ms·
I am skeptical of blanket statements like that. I’ve yet to meet a (real) language or tool or architecture that doesn’t have merit.
by macintux 7y ago
I am skeptical of blanket statements like that. I’ve yet to meet a (real) language or tool or architecture that doesn’t have merit.
- Groxx 7y agoEven "Big Ball of Mud"-design has some benefits: http://www.laputan.org/mud/ http://www.laputan.org/mud/
- ChicagoDave 7y agoIf you have a simple system, fine. If you have a complex system, any hint at a monolithic future has the makings of bad architecture. Data storage should reflect a bound context and its domains. It could be relational, graph, document, or key/value. Putting all data in one place just because it’s convenient is ignoring your business capabilities. DDD proves that aligning your technology to our business, reducing complexity, having real boundaries, is the way forward.