Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Deploying APIs With a Click of a Button

DZone's Guide to

Deploying APIs With a Click of a Button

It shouldn't just be API frameworks that have deployment buttons. Specialized API designs in a myriad frameworks should be available for deployment with a single click.

· Integration Zone
Free Resource

Today’s data climate is fast-paced and it’s not slowing down. Here’s why your current integration solution is not enough. Brought to you in partnership with Liaison Technologies.

There have been many advances in the way that we deploy APIs in the last couple of years, but I still want more of an embeddable, push-button way to deploy generic or even more specialized APIs. This is something I've ranted about before, asking where the deploy to AWS and Google buttons. I'm seeing more AWS solutions emerge, helping deploy from GitHub using AWS Codeploy and the regular number of deploy to Heroku buttons, but not the real growth I'd like to see occur — making it a drum I will keep beating until I get what I want.

Image title

I was working on my OpenAPI toolbox, cataloging open-source tools that put the OpenAPI specification to work, and came across a deploy with Heroku button for the Grape Doorkeeper, which helps you "create an awesome versioned API, secured with OAuth2 and automatically documented." 

This should be the default for all server-side API deployment frameworks, allowing push button deployment of any open source API framework to the cloud platform of your choosing.

If I have my way, it won't just be API frameworks that will have deployment buttons. Specialized API designs available in a variety of frameworks will be available for deployment with a single click of a button. We should be able to deploy a product API, or a user API, to AWS, Heroku, Google, or Microsoft with a single click. There should be a wealth of open-source templates for us to choose from on GitHub with deploy buttons and easy-to-follow wizards that help us set things up properly.

Smells like an opportunity to me. I'll have to think more about where the revenue would come from in such a model, but I'm sure it would be easy enough to upsell deployments to some premium features and services. I understand that both the areas of API design and API deployment are playing catch-up with API management at the moment, but someone needs to get to work on streamlining the API deployment button experience across all major cloud platforms and get to work on crafting some useful API server deployments that people can put to work instantly. 

Is iPaaS solving the right problems? Not knowing the fundamental difference between iPaaS and iPaaS+ could cost you down the road. Brought to you in partnership with Liaison Technologies.

Topics:
integration ,api ,api deployment ,heroku ,aws

Published at DZone with permission of Kin Lane, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}