Microservices are risk mitigation. If you know what are you doing - Monolith is optimal way.
We use microservices, because we acknowledge that we don't know how final product would look like, and we mitigate risks associated with adding and removing unknown number of features.
Facebook was creating clone of Twitter, well known product, well known path. There is no need for microservices.
I wonder if customer support and warranty is part of the calculation. If they sell open platform – they will have to provide support and potential warranty for it.
But I guess that most people are not interested in open platform, only tinkers like us are. And if they make it officially closed platform, they don't have to deal with our complaints, when something does not work, or more likely underperforms.
The article talks a lot about technology choice, but not about given product. I do tend to agree – that SPAs are not necessary, but I would not use this article as an argument.
And if somebody would present this article to me – I would not take it seriously. The fact that author is using very interesting language when refering to React and Angular does not help. I'd love to hear customer-centric or product-centric reasoning.
* Don't use SPA because customers hate it when you change entire app on them.
* Don't use SPA, because customers of our particular product require faster turn-around.
* Don't use SPA, because they are harder to test in our organisation.
I had a similar problem with my Windows gaming PC after I upgraded CPU cooler. Motherboard/BIOS decided that I've upgraded my CPU and it would not proceed without me pressing "F2" key on my keyboard.
Obviously my BT keyboard did not yet connect to the computer, since it was before BT drivers loaded or something, so I had to buy a wired keyboard to press "F2" and proceed. Would be nice to have 2-3 buttons right on a case to interact with BIOS. Or you know…load BT drivers.
I think I'm in the minority, but I just would not order a delivery in 90% of the cases. If I remember myself say in 2005-2010 I would order Pizza once in 1.5 months, and I was ready to come downstairs to receive a package.
These days I order food, knowing that it will allow me uninterrupted work (I'll just receive a package and get back to work). If I have to interrupt my "flow-ish" state anyway, I'll just go out or make an omelette in 10 minutes.
Context: I live 10 minutes away from a high street in London.
We use microservices, because we acknowledge that we don't know how final product would look like, and we mitigate risks associated with adding and removing unknown number of features.
Facebook was creating clone of Twitter, well known product, well known path. There is no need for microservices.