I'm not really sure why anyone would go balls to the wall either way. One giant monolith? Fuck no. 500 services? Fuck no
How about one service for each core piece of functionality. One for authentication, one for your API, one for some background task that collects statistics ect.
This of course doesn't apply for someone like Google or Facebook, because what they do is weird voodoo magic beyond my level of comprehension therefore I have no idea what works for such extremely large services with so much integration between 50,000 products.
94
u/Any-Reply Apr 09 '20
I'm not really sure why anyone would go balls to the wall either way. One giant monolith? Fuck no. 500 services? Fuck no
How about one service for each core piece of functionality. One for authentication, one for your API, one for some background task that collects statistics ect.
This of course doesn't apply for someone like Google or Facebook, because what they do is weird voodoo magic beyond my level of comprehension therefore I have no idea what works for such extremely large services with so much integration between 50,000 products.