Subhas, That section on distributed transaction and locking is very true for monolithic applications. Actually i would say it varies greatly on the kind of applications being built. Wrapping up every thing as part of request as a single transaction in monolithic systems is the simplest thing one could do, but its a recipe for disaster when the application is expected to scale out because we are trading scalability for strong consistency.
BTW, Shripad wrote an interesting article on building for eventual consistency, which kind of suits microservices based applications. Its at http://shripad-agashe.github.io/2015/12/Building-on-quicksand/