I'm fully okay with that when the goal is throwing commodity infrastructure at a problem. I still use AWS for most things; the point of DO, for me, is that for "worker"-based tasks, I can do a lot more with 8 $5/mo DO droplets than with one $40/mo on-demand EC2 instance (esp. regarding network-IO-bound tasks.)
I don't need my infrastructure to live in DO; I just need my, well, elastic compute to happen there. Oddly enough, DO is better than EC2 at being an Elastic Compute Cloud. (EC2's advantage, meanwhile, lies in how configurable it is for the non-elastic parts of your workload. It's great for being the host for the infrastructure components that form the "skeleton" of a service, with known work-pool sizes; it's not-so-great for just being a cheap place to offload a bunch of work.)
I don't need my infrastructure to live in DO; I just need my, well, elastic compute to happen there. Oddly enough, DO is better than EC2 at being an Elastic Compute Cloud. (EC2's advantage, meanwhile, lies in how configurable it is for the non-elastic parts of your workload. It's great for being the host for the infrastructure components that form the "skeleton" of a service, with known work-pool sizes; it's not-so-great for just being a cheap place to offload a bunch of work.)