First off, we’re giving away a few free tickets to the SF APIdays conference on July 31st. Comment about your favorite API on this post for a chance to win a free ticket!
With the freebie out of the way, we’re huge fans of APIdays (and API’s in general) and love to reference this landscape diagram. If the landscapes weren’t moving so fast, we’d probably have a copy printed on our office wall alongside the Cloud Native Landscape diagram.
API’s are everywhere
As engineers, most of us are inherently API minded. Others, not so much. It’s only been in the last 5 or 6 years that the idea behind API’s has gained public mindshare. Following Executive Order 13571 in 2011, the Obama administration directed federal agencies to deploy Web APIs which put API’s in the public spotlight. There’s been a lot of progress in the public sector, and now we’re holding conferences about API’s in general. These are steps in the right direction.
Iron <3’s API’s
We build all of our products with API’s in mind. All of our client libraries for each of our products use our HTTP API’s, and we’ve received a lot of praise for building API centric and cloud agnostic services. Internally we rely on a lot of API’s as well. We use API management solutions like DreamFactory to coordinate data sources, RingCaptcha for SMS verification and Zapier to tie disparate services together. We obviously use all of the public cloud API’s directly as well.
What API’s do you use?
There are many others API’s that we use that I didn’t list. What are some of your favorite API’s? Comment below and you might be sent a free ticket to APIdays. If you’re already going, let us know as we’d be happy to meet up!