News for hackers. Stuff that matters.
Re:Building Domain Driven Microservices by hinkley on Tuesday July 07, 2020 @03:14AM (#23756561)
But what happens is you end up with a ton of them, fulfilling the same prophecy you were trying to avoid, or you keep trying to cram more “volume” behind the same surface area, until you eventually tear a hole in the fabric of space time and/or your business.

The way to succeed is to do fewer things but make them count. Except that looks awful on your annual review, so the real way to succeed is to Defect. Be seen doing as much as you can and get out before they figure out you consumed all of the oxygen in the room.

Re:Building Domain Driven Microservices by sriku on Tuesday July 07, 2020 @04:59AM (#23757101)
I think John Ousterhout's recommendation of 'thin' interfaces and 'thick' implementations is a good heuristic that's worked well in my experience. This acts as a force that resists service proliferation that hides behind "modularity".

https://web.stanford.edu/~ouster/cgi-bin/cs190-spring16/lect...

Re:Building Domain Driven Microservices by hinkley on Tuesday July 07, 2020 @01:08PM (#23761353)
What I'm saying is that this works great for a while. But if you want to keep it working, four years in, you still have to say No a lot.