Disaster #1 is too small services, and Disaster #4 is huge, shared databases (between many services).

Which reaffirms my overall opinion that most people writing services have no idea what's a service and what it encapsulates (it encapsulates its own state, for example, it's basically distributed OOP).

BTW, remember when "your service should be 100 lines of code top" was considered a best practice?

Why is it so hard for most to resist this hype nonsense wave when its oncoming and it's so hard to resist the anti-hype wave that inevitably follows it? Because hype and anti-hype are simply the oscillation of a sea of empty minds in look for a solution to a problem they don't understand.

I've been writing service oriented apps for decades. In my "world" nothing has changed.