5 Developer Tips for Surviving API-First - Githubissues

postman-open-technologies / lifecycle

Defining the API lifecycle in a modular, reusable, and machine readable way that can help others learn about what the API lifecycle could be, as as define their own evolving API lifecycle.

https://apis.how/products/web-design/

Apache License 2.0

15 stars 9 forks source link

5 Developer Tips for Surviving API-First #135

Closed kinlane closed 2 years ago

kinlane commented 2 years ago

URL - https://swiber.dev/5-developer-tips-for-surviving-api-first

Elements:

Know your audience
Speak the language
Understand the building blocks
Design with intention
Use the network
Caching strategy

Questions:

What are our scalability vectors?
Where can we find performance opportunities?
How can our APIs evolve?
Which component owns application state?
What are the trade-offs related to storage, compute, and data transfer?
What are our API consumer use cases?
How do we measure success when moving to an API-First strategy?

kinlane commented 2 years ago

Added the questions.

kinlane commented 2 years ago

I added all of the elements except for "Understand the building blocks" -- working on several iterations of this.