Monolith First (2015)
I just wonder what kind of organization or project faces this kind of decision.<p>I've worked on workflow/crud-type web applications whose computational needs could be met using a single server with a couple of GB of RAM using a single database, indefinitely into the future.  I don't see why it would occur to someone to split one of those into multiple services.<p>I've worked on systems for which many such servers were required in order to provide the expected throughput and, in such a case, writing a monolith is really not an option.<p>Is there a significant middle ground?