14 comments

[ 0.26 ms ] story [ 27.2 ms ] thread
I'm curious to see more about how this gets implemented and adopted, i haven't seen an option like it before.
What a great idea for connectivity. Really opens up alot of possibilities.
This is really cool, extremely good for non-devs.

Personally, I like writing HttpClient code, but it can be a PITA, especially trying to figure out the shape of the data and what verbs are supported. It's nearly impossible for non-devs to accomplish this.

Lol, I agree. The fact that there is no set guidelines for these APIs makes it all the more harder to wrap an API in SQL...especially if we have to do it over and over again!
Something user Were looking to easily have powerful access to all the datas via REST. A new good feature added to help on the field
This would a boon when everything is getting connected through REST and micro services is the design norm.
This article was very useful for me!
Automatically wrap (no code) all your REST APIs in a unified ODBC/JDBC/OData layer, so other tools (like dashboarding or other bi tools) can access their data.
Pretty slick, already got it connected to my api!
Sounds amazing and what a cool name, too.