3 ms·
To reduce the initial investment, usually it is decided that the application should designed to be one holistic piece of software containing all the required fe
by dasil003 17y ago
To reduce the initial investment, usually it is decided that the application should designed to be one holistic piece of software containing all the required features. This represents a potential point of failure if the software becomes very popular in a short timeframe. I have painful memories of refactoring existing codebases that have not scaled well.
Great, but I don't see how this pattern gives any kind of predictable scalability improvement over plain ol' MVC for arbitrary applications. In my Rails app, the bottleneck is the database—the application servers trivially scale out horizontally. In the diagram here there is a single DB creating a bottleneck as well, splitting it up is a traditional sharding problem with or without this pattern.
In fact, this looks like a service oriented architecture with constraints (ie. MVC) on each service that are arbitrarily chosen rather than reflecting the true scalability profile of the application.
I'm hard-pressed to understand how you could justify building a greenfield application this way.