GraphQL, gRPC and REST, Oh My! A Method for Unified API Design • APIs are the glue that hold modern software together. One that doesn't pre-determine implementation details such as REST, GraphQL, gRPC, and others. Based on materials in Mike's book Design and Build Great Web APIs, Mike will share his experience, tips and best practices. You'll learn: How to significantly improve the quality of your API process; Which API style fits best to the needs of your company
Mike Amundsen - The (API) uncle you wish you had — the ultimate expert
ABSTRACT Join the API expert to skyrocket the quality of your APIs.
APIs are the glue that hold modern software together. If your API fails, it all fails. Folks also tend to overcomplicate the API design. Mike will teach you how write solid APIs without overdoing it.
Once your API is released out into the wild, you'll see users using it in new and creative ways — often in ways that weren't intended in the first place. Which is how we get to versioning — you can't just change the original without violating all those creative initiatives.
Companies that adopt a single API definition format (OpenAPI, AsyncAPI, Schema Definition Language, Protobuff, etc.) are likely to find their options limited as their API ecosystem grows and matures over time.
In order to avoid forcing the entire company to adopt a single API style or format, no matter the requirements of providers and consumers, we need a solid, simple and repeatable way to design APIs. One that doesn't pre-determine implementation details such as REST, GraphQL, gRPC, and others.
Based on materials in Mike's book Design and Build Great Web APIs, Mike will share his experience, tips and best practices.
Who should attend:
In this talk, you'll learn:
I’ve been working with Restful APIs for some time now and one thing that I love to do is to talk about APIs.
What is REST? The REST acronym is defined as a “REpresentational State Transfer” and is designed to take advantage of existing HTTP protocols when used
APIs can be as simple as 1 endpoint for use by 100s of users or as complex as the AWS APIs with 1000s of endpoints and 100s of thousands of users. Building them can mean spending a couple of hours using a low-code platform or months of work using a multitude of tools. Hosting them can be as simple as using one platform that does everything we need or as complex as setting up and managing ingress control, security, caching, failover, metrics, scaling.
GraphQL, gRPC, REST and WebHooks are among a bewildering array of technologies and architectural styles that are available to API developers today. Join me on a tour of these API styles where we will cut through this noise, demonstrate where each style shines (plus where they don't!) and ultimately resolve this dilemma of choice.
APIs - the current “big thing” - offer the opportunity for modern organizations to unlock new and lucrative business models. The article below covers some tips on how to spin the API flywheel and leverage its possibilities.