DigitalOcean Droplets vs. Presto

DigitalOcean Droplets are the best choice for developers teams that need reliable Linux servers to deploy their projects, the ability to create a droplet for testing purposes then destroy it, and only get charged for the few hours used makes the chances of messing up very slim. DigitalOcean Droplets is a great solution because the servers are scalable and the process of adding more resources like CPU or RAM to an existing droplet takes only a few minutes and once a server is scaled up it can also be scaled down if necessary which is perfect for supporting a temporary peak in traffic for example.

Incentivized

Presto is for interactive simple queries, where Hive is for reliable processing. If you have a fact-dim join, presto is great..however for fact-fact joins presto is not the solution.. Presto is a great replacement for proprietary technology like Vertica

Incentivized

• Simplicity to scale services--the interface is very quick and effective to use
• Reliability--this is key for us, as any downtime effects our reputation
• Keeps the costs down--hosting our own equivalent infrastructure would cost a lot more

Incentivized

• Linking, embedding links and adding images is easy enough.
• Once you have become familiar with the interface, Presto becomes very quick & easy to use (but, you have to practice & repeat to know what you are doing - it is not as intuitive as one would hope).
• Organizing & design is fairly simple with click & drag parameters.

Incentivized

• In terms of an availability zone, they have limitations not available in most of the geographical locations.
• No live support is available which can cause problem if you have outage.
• Number of service is quite limited.

Incentivized

• Presto was not designed for large fact fact joins. This is by design as presto does not leverage disk and used memory for processing which in turn makes it fast.. However, this is a tradeoff..in an ideal world, people would like to use one system for all their use cases, and presto should get exhaustive by solving this problem.
• Resource allocation is not similar to YARN and presto has a priority queue based query resource allocation..so a query that takes long takes longer...this might be alleviated by giving some more control back to the user to define priority/override.
• UDF Support is not available in presto. You will have to write your own functions..while this is good for performance, it comes at a huge overhead of building exclusively for presto and not being interoperable with other systems like Hive, SparkSQL etc.

Incentivized

Other platforms dashboard console is more difficult to use. DigitalOcean's dashboard is clean, simple, and straightforward

Incentivized

DigitalOcean Droplets is continuously evolving to be more and more powerful. It has great features and has low cost options, which is really great for developers. Its CDN, Loadbalancer, etc. make it a good place to host a high-traffic application. Moroever, DigitalOcean Droplets has a nonprofit program that helps nonprofit sites to run their infrastructure, which is tremendous and no competitor of DigitalOcean Droplets does that.

Incentivized

Presto is good for a templated design appeal. You cannot be too creative via this interface - but, the layout and options make the finalized visual product appealing to customers. The other design products I use are for different purposes and not really comparable to Presto.

Incentivized

• Digital Ocean has been great helping us move web apps to the cloud
• Digital Ocean has been really helpful when hiring contractors
• The interface could use some work, but overall its not terrible

Incentivized

• Presto has helped scale Uber's interactive data needs. We have migrated a lot out of proprietary tech like Vertica.
• Presto has helped build data driven applications on its stack than maintain a separate online/offline stack.
• Presto has helped us build data exploration tools by leveraging it's power of interactive and is immensely valuable for data scientists.

Incentivized