I wouldn't be surprised to see DO either roll out DaaS next or partner with someone (Compose.io?) to do it. That's one of two things (the other being VPC, which I know they're working on per HN posts elsewhere) that make AWS/GCP tempting over DO for me.
That said, I kind of hope it's not Compose.io - they seem ridiculously overpriced for PostgreSQL compared to AWS's and GCP's offerings.
VPC on DO is the #1 feature request that stops my team from considering it.
I use DO personally for small things and like it a lot, but VPC is a hard requirement for company work.
We're actively building VPC =]
IBM owns Compose.io now, so I'd be a little surprised to see them launch anything on DO.
Using managed queues (SQS) from AWS. The rest is on Vultr. That mix-and-match works perfectly for my use-case. In other words, no need to be able to run everything on a single platform to get cost gains.
Re:Introducing Object Storage
by SamLevin88 on Tuesday June 20, 2017 @12:25PM
(#14595942)
Good to know. Am in the throes of choosing between both for a simple project
VPC is in the works at the moment, still a bit too early for a release date, but the team has been on it for about the past 3 quarters.
Seed-stage startup here that would love to start using more of our (time limited) DO credit where our cluster requires running in a VPC. Any way to sign up for early access to VPC when it does roll out?
Most likely we will have a similar beta to what we've done with Block and Object storage, but it's still to early to provide a time line that isn't in quarters with a marge of error of 1-2 quarters.
S3 sets a high bar in terms of durability and availability, so it will be interesting to see how well DO can compete, and it will take a long time to gain the same level of trust that S3 has earned.