Meta’s Microservice Architecture [pdf]

Re:Meta’s Microservice Architecture [pdf] by treis on Tuesday July 11, 2023 @11:56AM (#36682834)

You do spawn a new monolith. You make one group the CPU intensive one and route that traffic there. Same concept as a microservice except that it comes with a bunch of dead code. But the dead code is not that resource expensive these days.

[ Parent | on HN ]

Re:Meta’s Microservice Architecture [pdf] by RicDan on Tuesday July 11, 2023 @12:00PM (#36682905)

I see, so basically we are applying scaling, but instead of scaling the bottleneck as its own part we scale everything.

I somewhat fail to see how that saves much effort; routing setup sounds like a hassle.

What we‘re using at my work is just a mono repo with all services in it, which works pretty well, and we‘re like 7 BE devs

[ Parent | on HN ]

Re:Meta’s Microservice Architecture [pdf] by treis on Tuesday July 11, 2023 @12:14PM (#36683115)

You don't have to write an API layer and get type checking among some other benefits. Is it a ton of savings? No, but I'd describe it as a significant amount of effort and lower complexity.

[ Parent | on HN ]

Re:Meta’s Microservice Architecture [pdf] by philjohn on Wednesday July 19, 2023 @11:45AM (#36788296)

To be fair, with libraries the API layer can be essentially zero code, and with type checking. That's how it worked when I was at my previous gig.

[ Parent | on HN ]