DuckRails

seriously though this solves a very common problem. me gusta mucho. star'd and will be forking

@thekyleduck LOL

@sridhar_kondoji No idea how you build APIs that fast. you'll have to share your secret with us. Building an API isn't a simple task. I think this is very smart & I see this as valuable for the prototyping stage. You never really know everything that your API needs before you start building. I like that this allows you to prototype/try things out/see how it works before writing code. Potentially even get feedback from users of the API before deploying it. Once deployed & being used, APIs are very hard to change.

@mscccc Agree, API implementation is not simple. We built Maven archetypes for Spring Restful and Apache CXF projects. The endpoints, request and response contracts are defined part of the design phase, so we add these to our projects and quickly deploy to QA environment for UI developers to consume and code as per the contract. While the UI developer is consuming the deployed webservices (with dummy/mocked implementation), the backend developer will continue to work on implementing the logic of APIs. This task might take longer depending on the complexity. Again a lot of it depends on the process. We build many many microservices and the above process has helped us. I do see a benefit in Duckrails at design phase and for architects to quickly build something and deploy even before Developers come into picture. I will give it a try for my next sprint project and provide more feedback.