apidays LIVE Paris 2021 - API design is where culture and tech meet each other by Aleksei Akimov, Adyen
0 likes•105 views
The document discusses the intersection of culture and technology in API design, emphasizing that organizational development culture heavily influences API decisions. It highlights the importance of prioritizing current merchant experiences, using collaborative approaches, and establishing effective API governance frameworks. Additionally, it advocates for good tooling and practices to simplify the API lifecycle and encourage developer engagement.
apidays LIVE Paris 2021 - API design is where culture and tech meet each other by Aleksei Akimov, Adyen
- 1. API design is where culture and tech meet each other Aleksei Akimov
- 2. About me Aleksei Akimov Head of API at Adyen Amsterdam https://www.linkedin.com/in/alex-akimov/ https://twitter.com/AlexeyAkimov API strategy API governance & design Technical documentation Developer relations Dev tooling Developer Experience 🧡
- 3. API as a language API API 👩💼 🧑💼
- 4. Most API design discussions are focused on API consumers
- 5. It's the development culture of your organization that influences API design more than anything else
- 7. Point of Sale & eCommerce eCommerce Local acquiring on a global scale
- 9. xw
- 10. Adyen APIs
- 11. Dozens of public APIs Thousands of internal services Technology Security Scalability Availability ... AdyenAPIlandscape Web, mobile, terminals/etc Hundreds of thousands API calls per minute Private cloud distributed across EMEA, NA, APAC and LATAM €303.6 BN processed in 2020 exponential growth Available 24/7
- 13. Payments never sleep: Availability 24/7
- 14. Existing customers & history of decisions
- 19. Embedding API design into the company culture
- 20. Culture is “how we do things here”
- 21. We prioritize current merchant experience over future features To think like the merchant we go meet them We design for 20x Expose your work early We are all designers, architects, coders, testers, security officers and operations engineers We all make mistakes, but we seek help as soon as we find out You own when, where, and how your code goes live Your code should be understandable at 4am under stress We embrace new technology when it has clear benefits Our tech stack is open source or built in-house
- 22. We prioritize current merchant experience over future features To think like the merchant we go meet them We design for 20x Expose your work early We are all designers, architects, coders, testers, security officers and operations engineers We all make mistakes, but we seek help as soon as we find out You own when, where, and how your code goes live Your code should be understandable at 4am under stress We embrace new technology when it has clear benefits Our tech stack is open source or built in-house
- 23. API decisions are complex and impactful: - require diverse knowledge - should be made fast - definition of done
- 24. Your {public} API is "done" when... it is used in production {by customers}
- 25. Road to successful API governance
- 26. API Review Group / API Board API Design API Reviews API ideation and feedback, before development. Evaluate the use of existing APIs and come up with improvements Style guide & tools Create a style guide and drive API tool adoption.
- 28. API Review Tool: Stoplight
- 29. API Style guide
- 30. Enforce style guide with linting
- 31. OpenAPI, contract testing and design-first JSON YAML
- 32. Evolution and versioning strategy
- 33. Value of good tooling If you want developers to use your frameworks in a certain way, you must invest your time in making it easier for them
- 34. "Make the right thing to do the easiest thing to do. Rest assured, when given options, software developers and architects in your organization will choose the easiest option every single time." (Matt Stine) "Energy is precious and the human brain is wired to conserve it whenever possible. As a result, we often find ourselves sliding into the most convenient option, not necessarily the best option." (James Clear) "We spend far more time doing what's easy than doing what's right." (Shane Parrish)
- 35. API design API consumers Collaboration is a key: Stoplight OpenAPI API-design first or API- design-ASAP Always be in between Educate, measure, listen to feedback, improve Developer Advocacy is a key API development Evaluate the entire A-Z API lifecycle Automate/support all the steps Remove bottlenecks Enforce the style guide with linting
- 36. You never know what's next
- 37. Thank you!