4 ms·
It's funny because the term "microservices" picked up in popularity because previously, most "service-oriented architecture" (the old term) implementations in l
by mjr00 3y ago
It's funny because the term "microservices" picked up in popularity because previously, most "service-oriented architecture" (the old term) implementations in large companies had services that were worked on by dozens or hundreds of developers, at least in my experience. So going from that to services that were worked on by a single development team of ~10 people was indeed a "microservice" relatively speaking.
Now, thanks to massive changes in how software is built (cloud, containers et al) it's a lot more standard for a normal "service" with no prefix to be built by a small team of developers, no micro- prefix needed.
- Scarblac 3y agoI can understand wanting to split things off so that one team handles one service, roughly. There was a recent thread here where someone mentioned he personally was responsible for about four of their microservices...
- nicoburns 3y agoYeah, my last company had 10 microservices (the entirety of their codebase) managed by a single team when I started. Some of them had fewer than 5 API endpoints (and weren't doing anything complex to justify that).
- deleted 3y ago[deleted]