3 ms·
tl;dr: * Release early, release often, evolve fast or even pivot. What is good for performance and availability is often bad for simplicity and flexibility. Bu
by nine_k 12y ago
tl;dr:
* Release early, release often, evolve fast or even pivot. What is good for performance and availability is often bad for simplicity and flexibility. Build with an intention to rebuild when the time comes.
* It's like throw-away prototypes, only in production. When your business grows, you may have to throw away some or all of your previous code base (as eBay did, twice). This does not mean that the previous solutions were bad: not at all, they were adequate for the previous step.
* Modularity (e.g. microservices) is good, but it may add complexity. A monolith may be a fine sacrificial architecture, to be eventually replaced with something better (and more complex and expensive to build).
- ansgri 12y agoThe last point is especially good, and from my experience I can say: leave the most complicated part of the system as a monolith until it's functional, and do detailed design of the easy parts. You never can really predict which dependencies will arise within the complex part.
- xg15 12y agoI believe the "e.g." in the last point is especially important: Even if you don't use microservices, you can (and should!) still make your architecture modular.