This approach doesn't prevent doing things well - there's lots to like about eventing and async processing. The distribution of the business logic among asynch

This approach doesn't prevent doing things well - there's lots to like about eventing and async processing. The distribution of the business logic among asynchronous actors (the serverless message-driven elements) will likely increase the potential for consistency issues at runtime and might increase the cognitive burden on the team at dev time ("where's the right place to put function X", "how do I test scenarios now that they're distributed", "what should my unit do if a collaborator didn't process its events in a timely fashion or at all"). These are all tractable problems, but problems nonetheless.