Post

API Enhancement Proposals (AEPs) are a specification and tooling for building best-in-class resource oriented APIs. Where did the AEPs come from? What are the underlying motivation and philosophies of the project? In our latest post, @y.tsutsumi.io explains that and more! aep.dev/blog/history...

1. AEPs are a API design specification for gRPC and REST APIs, with a heavy focus on resource-oriented design and standard methods that operate on them.

2. AEPs include design patterns for common use cases such as long-running operations, resource revisions, filtering, with best practices aggregated from API design experts with experience at Google, Microsoft, Meta, Roblox, and DataBricks.

3. AEPs provide an ecosystem of server-side and client-side tooling to produce and consume AEP-compliant APIs.

They build upon Google's AIPs with a stronger formalization of the API design guidance itself, to: - Act as a reference point for organization-agnostic best practices. - Enable an official ecosystem of tooling to make best-practice APIs easier to build and consume.