API Descriptions

Listen to Erik Wilde and guest Kin Lane discuss API descriptions Show Notes Listen to our latest podcast featuring Academy member Erik Wilde and special guest, Kin Lane, as they weigh in on popular standards used to define and describe APIs including  Swagger (now the Open API specification), hypermedia, and how tools can support interface description language.

Designing Culture for Microservices Teams

Don’t underestimate the impact of culture in your architecture Show Notes In the fifth episode of the API Academy’s podcast series, Ronnie Mitra and Mike Amundsen discuss why culture is important for application development. They also explore the challenges around designing and executing a supportive culture for microservices.

What Exactly is REST?

Learn how REST is used and find out what’s in a name Show Notes In the fourth episode of the API Academy’s new podcast series, Erik Wilde, Mike Amundsen and Ronnie Mitra work towards a complete and precise definition of REST. They also talk about how REST is used and pose the question: “What’s in a name?”

Should Your APIs be Open?

Dive into the pros and cons of implementing open APIs Show Notes In the third episode of our new podcast series, Erik Wilde , Mike Amundsen, Matt McLarty and Ronnie Mitra dive into the pros and cons of implementing open APIs—exploring how offering a public API might impact your organization, from a business and strategy perspective.

Service Landscaping

Learn a technique for managing services in your Web architecture Show Notes In the second episode of our podcast series, Erik Wilde explains his concept of service landscaping. When the services in your Web architecture proliferate, you need a way to manage them. Erik describes his philosophy for “landscaping” services to improve the overall architecture and the organization they live in.


Explore a new query language for APIs Show Notes In the first episode of our podcast series, we take a close look at GraphQL―an emerging query language for APIs, which has already been adopted by some high-profile digital enterprises. But is it a good choice for building API-powered apps? And could it even be a replacement for REST?

Scroll to top


Get exclusive content, webcasts, how-to videos, and event invitations