This looks like a pretty neat web app. Nice UI and promo video, also. I think the core audience for this, is people who are somehow locked in using MySQL, though. For someone starting out, it seems like a bad idea to use this because it is sort of encouraging bad habits, right?
For example if you making a new sandwich, why would you make a device that takes the peanut butter from the jar, puts it in a bigger jar, then you use a knife to get the peanut butter from the bigger jar to put on your PB&J? It just seems like a bad middle man, if you are starting a new project.
Maybe I'm wrong, but again, it looks neat for people maybe in old companies where they have no choice but I just hope this doesn't encourage people to start with MySQL just for this app or with a purpose to only turn it into an API.
Or maybe another application of this is turning an existing blog with WordPress (MySQL) into an API? Not sure...
We definitely built the product with existing applications (without an API) in mind. We found it much more difficult to add an API after-the-fact than if you design for one in the beginning. In fact, the idea came to us after attempting to build an API for a 10 year old PHP application at Rackspace.
For example if you making a new sandwich, why would you make a device that takes the peanut butter from the jar, puts it in a bigger jar, then you use a knife to get the peanut butter from the bigger jar to put on your PB&J? It just seems like a bad middle man, if you are starting a new project.
Maybe I'm wrong, but again, it looks neat for people maybe in old companies where they have no choice but I just hope this doesn't encourage people to start with MySQL just for this app or with a purpose to only turn it into an API.
Or maybe another application of this is turning an existing blog with WordPress (MySQL) into an API? Not sure...