Somewhat interesting post, but it was very unclear to me if the author has actually implemented any of this. It reads like a How-To but if the author hasn’t actually done it the whole post goes out the window.
But I do really like the idea of services that are in the order of hundreds of lines of code. I’m guessing this general principle plays well with something like Mesos?
Also, I think the author really underplays testing. The author refers to testing an individual service as not hard, which sounds right, but testing the integration of all of these things together sounds rather complicated, depending on how well you do it.
Agreed on the lack of a depth. From my personal experience, all the interesting challenges with service oriented architectures were either glossed over or not mentioned in the article. A nice overview, but I want more meat!
In particular, I would love to hear more detail on the feasibility of the proposed size of these components (~100 LOC). My gut reaction to that number is that it would force you to split up single concerns into a few partial services, just because otherwise you aren’t a micro-service. I’ve always had good luck with making service boundaries correspond to meaningful separation of concerns, even when the resulting component ends up significantly larger.