Minitable vs. Presto

Some scenarios where it has helped me was where there was a large group of customers on sight who all wanted to eat but we wanted to provide individual meals to them, so we used Minitable to show them the menu in the morning and have them submit their order by 10:30 am to put in the order and have it ready by 11:30. It was not so appropriate for smaller groups where some did not have an account to Minitable.

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

• Easy ordering.
• No waiting in line.
• No processing fees.

• 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

• Some menus are proven difficult.
• Not everyone has an account so they do have to make one to use.
• Sometimes communications are a bit much through emails.

• 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

I do not like using Airkit at all, but I would say Minitable is comparable to DoorDash.... just cannot reserve a table on DoorDash like you can on Minitable. Minitable is more business-friendly than DoorDash and Airkit. I would only use Minitable in a business setting and I would use DoorDash in a personal setting.

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

• There are no processing fees, so company does not have to pay for ordering.
• Paying for customers meals is never great on ROI but must be done.
• Customers enjoy picking their own meal and having it delivered.

• 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