4 ms·
I want to love it but: 1 - only MySQL. 2 - the per row pricing model is ridiculous. I’ve got small applications with well over 5 million rows, running on few
by techdragon 9y ago
I want to love it but:
1 - only MySQL.
2 - the per row pricing model is ridiculous. I’ve got small applications with well over 5 million rows, running on few Megabytes of SQLite, I’ve got medium size ones using an order of magnitude more rows running on AWS RDS with cross AZ redundancy for about $150. If I want a json API I’ll slap an instance in front of it for $50 running PostgREST or Sandman, or one of the other SQL/REST tools. I’ve got plenty of free database browsing tools, and AWS Lambda does the rest for fractions of a dollar. Why on earth would I ever pay these guys $250? Their pricing model tells me before I even try the product that they haven’t solved any of the problems I have with running a database.
- kuceram 9y agoThen love it and wait for improvements. ;-) I think they will implement something on top of MySQL. And every-time you can ask startup for different pricing model am pretty sure they will be very flexible with it.
- appdrag 9y agoIndeed, we do have plans to support nosql in the next few months. Our Pricing for nosql will be really different and a lot lower for the storage. We started with relational db first because a lot of developers have existing skills with RDB and it was requested by ALL our beta testers. Our platform is a fully automated system with high availability & zero maintenance required. So you don't have to setup a RDS box + front end server for the api + load balancer + .... maintain / update all that stack. And YES, we are very flexible and open to suggestions related to our pricing This is also why we posted here, to get valuable suggestions and comments :)