Redpill me on microservices

?

Well one its micro and two its a server.

>>2
I'm confused, the OP claims it's the services that are micro; yet you claim it's the server that is micro. Which one is micro, the hardware or the software?

services = server
Micro = Micro

>>3
Servers are services. It is 2020.

It's the break the big problem into small programs strat from sicp.

It makes sense, if you work on a big 5 year projects, to break it down into maybe 10 subparts. If you build a car with 10 machines you can understand the complete car if you look at the machines as black boxes (eg you press the gas pedal > it sends a message to the command center > command center processes it > command center sends message to the engine which does its thing). If you work on the engine you can understand it as well because you don't have to think about the multimedia suite also.

Micro services is when you split these 10 machines into another 10 machines (eg the multimedia system is split into radio, bluetooth, video display, audio output, speakers etc).

People think it's bad, because big companies hire a large amount of dumb people which aren't good with abstraction. So instead of the gas pedal team sending messages to the command center the team is going to do a hack and send the message directly to the engine. Now the traction control doesn't work anymore because the command center cant process the message first.

It's great tbh and the only way to make a big project with a large workforce like a car or netflix, which is a good example of a good microservice project. They have talks about it if you care.

>>1
writing a program wouldn't cost you $thousands per use.
But with microservices and cloud computing its easy.

https://www.theregister.com/2020/12/10/google_cloud_over_run/

>>5
That's great! Were can I rent a Fujitsu M12?

>>8
Penis is hexed.

>>6
It's more like break a problem that wasn't really that big to begin with into lots of tinier ones, so each of them can then become even more bloated and inefficient.

This really only benefits cloud providers, since their profit is directly based on how much you use them. Tiny problems taking huge amounts of their resources is awesome from their perspective, because then they get to charge you more!

They just put out lots of propaganda about how much better it is to try to hide that. It doesn't take a genius to realise, but then again, the majority of developers are trendchasing idiots who will mindlessly regurgitate whatever the marketing campaigns spew...

Look at where the money is going. It's like a store having a sale --- they're not lowering their prices so you can pay less, they're doing it so you'll want to buy more and increase their overall profit.

>>10
This is the real answer. They're a neat idea, they introduce new problems and get rid of old ones, but the unavoidable reality is that they exist and are promoted in order to increase hosting costs.

Microservices are also blazingly great for stimulating innovative behaviour of the aggregate program by simplifying transactional data storage down to compare-and-swap, and thereby disrupting old-fashioned male-centric ACID guarantees. This enables women and minorities to architect enterprise QUALITY solutions for diverse customer audiences.

>>10,11
They're promoted because businesses want disposable teams and more people working on a single project.

Having too many people is a good thing. Imagine google were efficient and only had 1000 employees. It would've been abolished a long time ago. Having 100000s of people in your workforce justifies making billions.