API Digest #82. Which kind of API is the right one for your next project?
API Digest is back with the traditional at-a-glance survey of recent API news, articles, and insights. In today’s issue you will find a brief overview of the following articles:
- API the Docs, London
- Review of APIStrat in Portland
- Kin Lane talks APIs with Matthew Reinbold and DevExchange
- Why Do Companies Build APIs?
- Key Steps to Building and Managing an Effective API Marketplace
- Which kind of API is the right one for your next project?
- How to avoid pitfalls when implementing microservices
- 5 Reasons You Should Use OpenAPI/Swagger for your APIs
- A painless intro to working with APIs
- Good API Documentation Is Not About Choosing the Right Tool
1. API the Docs, London
Eight API professionals shared their stories during the one-day conference API the Docs which took place in London. During the event, speakers discussed all aspects of API documentation: trends, practices and strategies. Follow the link to reach the recordings and key insights from their presentations.
2. Review of APIStrat in Portland
Another great gathering of API enthusiasts has happened in Portland lately. API Strategy & Practices is a series of events where opinion leaders share their main successes and challenges. Take a glance at the best moments in a review by NordicAPIs.
3. Kin Lane talks APIs with Matthew Reinbold and DevExchange
An interview with Kin Lane, API evangelist, about the past, present and future of APIs.
4. Why Do Companies Build APIs?
Alex Wilson discusses the reasons why companies build APIs including the financial reasons and the desire for digital transformation.
5. Key Steps to Building and Managing an Effective API Marketplace
Mifan Careem is instructing on how to manage API marketplace, monetize APIs and implement a developer portal. What is the scenario to building an API marketplace and which components is it comprised of? Look for the answers in the article.
6. Which kind of API is the right one for your next project?
James Higginbotham suggests APIs could be divided into groups according to their nature. There are utility, SaaS, platform, partner and private APIs. Each has its own strengths and weaknesses. A massive piece of consideration is required before launching any, otherwise you simply would not be able to address the needs of the consumers.
7. How to avoid pitfalls when implementing microservices
What can go wrong when a business is migrating to microservices? Plenty. The reason may be hiding in the most unexpected place. Check out the commentaries given by five industry experts.
8. 5 Reasons You Should Use OpenAPI / Swagger for your APIs
If you develop software today, chances are you are developing Web APIs as well. There are some common good-case practices on how to do this effectively, and using OpenAPI/Swagger for your API is one of them. Read about the benefits you may get in the article by BlazeMeter.
9. A painless intro to working with APIs
Understanding APIs properly is one of the big milestones in programming career. Maxime LaBoissonniere, a full stack developer at Snipcart, makes an attempt to bring a painless introduction to working with APIs. He believes (and we fully share his view) learning to use APIs dramatically increases your development effectiveness.
10. Good API Documentation Is Not About Choosing the Right Tool
What tool are you using to build your documentation? The question might not be the correct one. Instead of focusing on which tool to use, a better option is to focus on whether you are doing everything possible to be as little software-dependent as possible.
If you are interested in getting latest news in the API world, check our digest #80 and #81 as well as stay tuned for the new blog posts.
P.S. In case you are interested in trying API2Cart, you can create an account and see how the API works on live stores.