> Even the book on Microservices says “First build the Monolith”.\ And yet, funnily enough, the book on Monoliths says to break things up into smaller services

> Even the book on Microservices says “First build the Monolith”.\ And yet, funnily enough, the book on Monoliths says to break things up into smaller services! It says your data should be stored in its own service (possibly multiple services, if you need multi-paradigm access [e.g. relational, full-text search, etc.]). The user experience should use its own service. And, at very least, you should have another service in between (this is where Django and Rails usually fit). Optionally, it says, you will probably want to have additional services as well (auth, financial transitions, etc.)