> For many applications, it's easiest to start with a modular monolith talking to a shared database, one that natively supports transactions.
I don't think this handles "what if my app is a wrapper on external APIs and my own database".
You don't get automatic rollbacks with API calls the same way you do database transactions. What to do then?