3 ms·
At one point I was using DO for everything but then I got to the point where spending time on server config just wasn't productive so I moved everything over to
by siquick 7y ago
At one point I was using DO for everything but then I got to the point where spending time on server config just wasn't productive so I moved everything over to AWS Elastic Beanstalk and RDS and never looked back.
I know DO do now have dedicated DBS products but really feel they're missing a trick with nothing similar to Elastic Beanstalk or GCP App engine - this is exactly the kind of products smaller dev teams and one-person operations need, and these are most likely the kind of people who would be willing to give DO a go over AWS and its perceived complexity.
- Doxin 7y agoIMO what DO offers is ahead of Elastic Beanstalk and GCP App engine in many ways. Instead of offering a single service they have opted to provide easy to install images for deploying services. These days if I wanted to set up a small service on DO I'd simply go to the DO marketplace and click a button to launch a docker instance. For a larger or more complex service I'd probably opt to use DOs kubernetes support, it's similarly a couple button presses to boot up a cluster. In either case I can then just point kubernetes to the right address and get going with spinning up my application. It's a bit less polished than what elastic beanstalk or app engine provides, but it is a lot more flexible without being more complex. If anything it's a lot simpler than any of AWSs offerings because DO actually has a sane dashboard unlike AWS. I can't comment on app engine since I haven't used it but I can heartily say that the last day I need to touch that abomination of an AWS dashboard is the day I'm having a party.