4 ms·
This is a really weird article. The solution is not to say "Services Suck" or "Monolithic yay!", it's to realise that you should start with a monolithic app bu
by nemesisj 14y ago
This is a really weird article.
The solution is not to say "Services Suck" or "Monolithic yay!", it's to realise that you should start with a monolithic app built in a good framework, then see how your app's internals are used/accessed as you grow THEN split out to logical well designed services.
Or in other words: Premature optimisation is the root of all evil.
- swah 14y agoMore or less what the article said: > Start merging services until you come to the bare essentials that have to be discrete. He's giving an heuristic for finding the right granularity of services - that is what is up for criticism, IIUC. I totally agree with you, start "monolithic", SQL + a lightweight Python web framework for most simple apps.
- z92 14y ago> Start merging services until you come to the bare essentials that have to be discrete. I thing GP advised to: start with a monolithic system and then split up the services as your system grows and as you feel the need. That sounds more solid advice.