Can they generate API to get me the connection path between two people on facebook :) :)
Show HN: Generate REST APIs for Existing Applications
21–30 of 32 posts
Re: Show HN: Generate REST APIs for Existing Applications
#22Nice application but I think it would be something like library because it doesn't seem a good idea that sharing database credentials to a startup.
Re: Show HN: Generate REST APIs for Existing Applications
#23I would have killed for this a few months back and actually googled around without much success.
I look forward to experimenting with this, I think it's a great idea.
Re: Show HN: Generate REST APIs for Existing Applications
#24Would love to see mongodb support.
Re: Show HN: Generate REST APIs for Existing Applications
#25Maybe you should re-title this "Generate REST APIs for Existing Databases". IMO, database != application. I opened this in anticipation of something that would generate REST APIs for legacy (ws, corba, rmi, etc) interfaces.
Re: Show HN: Generate REST APIs for Existing Applications
#26I'm most excited about the idea of automatic Client Bindings. I've been thinking about how cool it would be if you could dynamically generate a Ruby gem for your REST API, as well as a documentation site.
There's already grape (https://github.com/intridea/grape) and grape_doc, so it looks like 'grape_client' is the only missing piece. Imagine being able to automatically generate versioned client libraries for ruby, php, iOS, android, etc.
Would be super awesome if emergentone could get behind an open source project like that.
EDIT: Welp, looks like 'swagger' is way ahead of me! http://swagger.wordnik.com/
EDIT2: The grape-swagger gem is even further ahead of me! https://github.com/tim-vandecasteele/grape-swagger
Re: Show HN: Generate REST APIs for Existing Applications
#27Love this, sorry about the hate brigade from HN. Anecdotally, it seems to be getting worse lately... To start, at Zapier, we and our customers have a huge need for something like this for any install of open source software with no API or crazy REST APIs. You should get in contact with us. Being the REST API for standard OS packages is something you should do yesterday. :-) The credential thing is something we fight…
Maybe the comments have changed since you wrote this but I see very little hate amongst the comments - only 1 could be deemed uncivil to my eyes.
[and I know I'm guilty of this at this precise moment but not sure if leading with a meta-comment is especially constructive in itself. If you don't like the tone, then lead by example]
Re: Show HN: Generate REST APIs for Existing Applications
#28A couple of philosophical objections:
1. There is a real benefit to building an API into the core of your app - it forces the kind of loose coupling that will improve your entire architecture.
2. Your db schema != your business logic. The API should mirror the latter and not the former.
Having said that... Automatic language bindings? I want some of that...
Re: Show HN: Generate REST APIs for Existing Applications
#29This should serve as a loosely coupled, managed API server which acts as a load balancer to a larger extent, if it can intelligently cache requests and act like memcached for API requests.
Worth mentioning, this can be a big time saver to generate APIs for legacy type websites, small new frameworks and languages that don't provide native framework level support to build API's.
Re: Show HN: Generate REST APIs for Existing Applications
#30my 2c: As a developer I wanted a one line explanation of what the technological solution is. "Generate a new API for your existing application!" is far too vague. It doesn't tell me any of the most important things I need to know about the product.
the Product page has the stuff on it that I wanted to read. IMO that should be a primary link from the front or part of that content should be on the front. at the moment its all "BUY NOW" and yet I have no idea what it is unless I watch the video. so that causes buyer suspicion.