The title here is wrong, I believe. The APIs produced by this tool are not REST APIs. It doesn't seem possible to be able to satisfy the HATEOAS constraint, and a few other REST conditions are not satisfied. See: http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hyperte...
Deployd: Create RESTful JSON APIs using a GUI interface
31–40 of 46 posts
Re: Deployd: Create RESTful JSON APIs using a GUI interface
#32Where's the hypermedia?
Re: Deployd: Create RESTful JSON APIs using a GUI interface
#33This looks like it could be pretty good for prototyping, or maybe a small, low-risk project. It gives the user JS event handlers for server-side events, and there's a simple API for behavior ("protect('model_attr')", "error('the message')"). Not bad.
(I work at deployd) Yes, it's perfect for prototyping. We use it extensively for prototyping on projects where the ultimate API has to be supported in another stack. Saves tons of time compared to developing the API as you go in Java or the like.
Re: Deployd: Create RESTful JSON APIs using a GUI interface
#34I feel like you played techphrase roulette to come up with this idea.
Re: Deployd: Create RESTful JSON APIs using a GUI interface
#35"By removing the complexity of backend development, Deployd lets you focus on the part of your app that really matters: the front-end" /sigh.
Why the /sigh? Is it because you don't agree that backend development is complex? Or do you feel differently about the front-end being the part that really matters? Personally, I'm impressed by this. It seems to me a compromise between MeteorJS/FireDB and "traditional" stacks. It also comes with its own environment to organize my code? Something about that is a little appealing. Maybe limiting too, but appealing.
Probably the /sigh because it looks like a great framework if the problem you're trying to solve is to build the simplest possible TODO-list app.
Re: Deployd: Create RESTful JSON APIs using a GUI interface
#36Are you running your website with deployd? Because it's down :) An error has occurred: {"code":"ECONNREFUSED","errno":"ECONNREFUSED","syscall":"connect"}
I'm getting -
An error has occurred: {"code":"ENOTFOUND","errno":"ENOTFOUND","syscall":"getaddrinfo"}
Re: Deployd: Create RESTful JSON APIs using a GUI interface
#37Great Work. suggestion: I would frame it differently - the coolness of what you are doing has nothing to do with the GUI part, but rather, the fact that it is a BaaS (backend as a service) open source. It's a simplified meteor, or an open source parse. BTW - it is funny how things circle back - we are coming back to a client-server era. Much like the VB6 days :)
(I work at deployd) Yes, the cycle is funny. We don't usually focus on the GUI when talking about deployd; someone outside the company posted with this headline. Open source was a no-brainer for us. There are some other key concepts that make it a compelling tool, particularly how easily extensible the platform is.
Jeff, has deployd considered adopting a JSON-based media type like Collection+JSON or HAL or JSON-LD (and there are others, or you could roll your own) so that the JSON APIs are properly RESTful?
Re: Deployd: Create RESTful JSON APIs using a GUI interface
#38Having played around with Parse and StackMob, I agree with fellows HNers that the great importance of Deployd is that it is an open source BaaS. I loved the interface and the custom server side code validation, just like the feature that Parse recently launched. Keep it up!
Re: Deployd: Create RESTful JSON APIs using a GUI interface
#39Earlier quoted context omitted.
You can, it's open source. The environment just needs to support Node and Mongo.
> The environment just needs to support Node and Mongo. Shouldn't this be displayed on the homepage somewhere?
This is one of my biggest issues with a lot of the projects being posted lately - they look great but I don't know the tech stack until I finally look at the code. Would be great if people at least mention if their project requires node.js, ruby or what not on their homepage.
Re: Deployd: Create RESTful JSON APIs using a GUI interface
#40Great Work. suggestion: I would frame it differently - the coolness of what you are doing has nothing to do with the GUI part, but rather, the fact that it is a BaaS (backend as a service) open source. It's a simplified meteor, or an open source parse. BTW - it is funny how things circle back - we are coming back to a client-server era. Much like the VB6 days :)
Funny you mentioned VB6 days, that was the first thing that came up at work when we saw it.
I haven't downloaded it yet, so perhaps I'm missing something. But our thought was that it mimicked the VB6 "Place Code Here" mentality.