Making Integration Suck Less: 2018 Trends and API Design Best Practices
In Partnership with Dzone
Let’s face it. API integrations suck. Well one at a time, not so bad. But it’s never just a one-and-done scenario. If you are designing and building at least one API integration, odds are you’re building 5+ integrations. Each one of those APIs has its own learning curve, its own nuances, its own reasons for going down (or getting updated).
We’ll look at some of the trends we are seeing among service providers that improve the developer experience and make some recommendations to ensure the APIs we’re building today are fit for purpose tomorrow.
What you’ll learn:
- Integration trends for 2018
- Good, usable API design: Eventing, Security, Documentation
- Recap and learnings from The State of API Integration Report 2017
- Sneak peek of The State of API Integration Report 2018, coming in March 2018
Ross Garrett, VP of Marketing @ Cloud Elements:
Ross Garrett is the VP of Marketing at Cloud Elements - responsible for market strategy, product positioning and evangelism. He is a well-known speaker at developer events and other industry conferences. Ross has over 10 years of product and marketing leadership experience in the integration space, most recently at Push Technology and previously with Axway, CA and Layer 7.
Raphael Barbo, Developer Experience Engineer @ Cloud Elements
Raphael Barbo is a Developer Experience Engineer at Cloud Elements who works closely with CTOs, Product Managers, and Developers to assist in designing, assessing, developing, and refining their API Integration to quickly turn time into value. Raphael is an enthusiastic and energetic Software Developer with over 10 years of expertise in Technology, Supply Chain, and International Trade, previously at LockState, Turing School of Software and Design and MSC.
About the AuthorMore Content by Ross Garrett