[seibelj]

> If you're doing more than taking a request, reading+writting into a database.. you're doing too much

And this is why micro-services are poor architecture. If you need an entire service for every DB activity you are in for a terrible time.

[throwaway894345]

It's not a service for every DB activity; this is a fundamental misunderstanding about what microservices are, how to use them, etc so of course you're going to have a bad time with them. :)

[seibelj]

Yes let's make every function call its own service with monitoring, a database, the network stack, management, and so on and then enjoy wonderful performance and easy management

[heax]

Hmmm, great idea that way cloud providers can extract insane amounts of money from unsuspecting organizations. Let's call it function as a service :)

[throwaway894345]

That doesn't seem advisable. Maybe you should try microservices instead?