One of our customers recently had tasked us with building a microservices thing. And I already thought that was kind of bullshit, because they had only vague plans for actually scaling it, but you know, let's just start the project, figure out what the requirements really are and then recommend a more fitting architecture.

Well, that was 3 months ago. We were working on it with 2 people. Then at the end of last month, they suddenly asked us to "pause" work, because their budget situation was dire (I assume, they had to re-allocate budget to other things).

And like, fair enough, they're free to waste their money as they want. But just why would you start a microservice project, if you can't even secure funding for it for more than a few months?

[–] [email protected] 12 points 6 months ago (1 children)

Because some marketing asshole told them that they better be prepared to scale to a bazillion users.

[–] [email protected] 8 points 6 months ago

In this case, the colleague who had talked to the customers told me, they wanted microservices, because they'd have different target systems which would need differing behavior in places.

So, I'm guessing, what they really needed is:

a configuration file,
maybe a plugin mechanism, and
a software engineer to look at it and tell them the behavior is actually quite similar.