We’ve been going off about API Strategies this week. It’s because these strategies can play a key role in the success of failure of business, large or small. If executed properly, you can open up new lines of business, deploy powerful integrations that eat your competition’s market share for lunch.
So, let’s start with some of the big ideas.
Some of the most successful companies are focusing on their API Strategy right now to win. As such, we’ve put together three primary considerations.
When it comes to API Strategies in the Enterprise, let’s dig in.
Are your SDKs accessible?
When you look at some of the most successful API strategies, it’s pretty clear. First and foremost, success with any API strategy means giving your community tools and flexibility. So, SDKs are one way to reach developers and help drive adoption.
“After some initial publicity when moving to a general availability release, Contentful has since been able to drive adoption of its API product through its GitHub library of SDKs.” (source: Programmable Web)
Additionally, it’s a no brainer. If you put yourself in the shoes of developer teams, wouldn’t a straightforward guide and documentation make it easy for you?
So, one key takeaway would be to reduce the friction whenever possible and wherever you can. This also includes aspect of your APIs and Microservices like the API Gateway.
Hand Roll or Out-of-the-Box?
One important decision you’ll have to make isn’t just about your design. It’s also about how you’re going to build your APIs. The market is flooded with new composition, management and curation tools. It can be tempting to grab the remote and just tune it all out.
Do you build it yourself or buy it from someone else? What if you can do both?
In fact, that’s exactly why we started building Express Gateway, an open source API Gateway built entirely on Express.js. Express Gateway powers the “manage” part of the API lifecycle within LunchBadger. If you’re interested, we’re looking for more contributors and maintainers for the project.
Using open source can have the following benefits:
- Accelerate your time to value by not starting from scratch
- By building on something that is already familiar in the community, it’s even more accessible.
- Tapping into connected, passionate and pre-existing communities
Are you investing in your Community?
Don’t be afraid to make investments into growing your Community. For instance, one of the key reasons why we are building Express Gateway on ExpressJS is because of an existing ecosystem of 3,000+ middleware modules already in production with Express.js. Not all Express.js modules are relevant to the API gateway use case – but many are.
Developers recognize commitment from 300 yards.
Believe it or not, communities of developers and technical practitioners can recognize when you appreciate and contribute back to their community. Choosing open source that is simple, flexible and familiar can demonstrate growing alignment with their use case.
Moving On – API Strategies are a go!
So, how about that? Have questions? Have answers? We’re collecting more information about APIs, Microservices and potential use cases. It’s certainly nothing new, but as more data because available – we’ll keep you posted so stay tuned.
- Sign up for our private beta – your feedback helps prioritize our roadmap with the most value realized within the shortest amount of time
- Check out our Open Source Initiative: The Express Gateway
- Learn about the inaugural feature set we’re striving for to make APIs repeatedly fast, easy and manageable as you evolve through the API lifecycle itself.
- Sign up for the latest development on APIs and microservices.