What distributed application can not be "philosofed" into essentially being a distributed database, and I feel like I'm just repeating your question.
With that in mind, I believe it boils down to where is the logic located, with the data, or not. Because a lot of "databases" are just used as a datastore.
So let me try to create some scenarios:
1. To push out a product(Startup/Prototype/POC): Develop in the technology you know, and let the stake holders know you are acquiring Technical Debt.
After startup/prototype product is a success. Explain to stake holders why you need to move to a better technology stack that supports distributed systems "better".
2. If you have a design or product, develop directly in a distributed technology stack.
It boils down to use the correct tool for the correct job, but you will mostly only know if you used the correct tool later in the development of the product.