Presentation: Using Microservices to Build an API That Lasts
Abstract
Steve Jobs once said, “Simple can be harder than complex: You have to work hard to get your thinking clean to make it simple.” This is certainly true when it comes to building a simple and easy-to- use API. SparkPost used microservices to build v1 of their email API. Since launching three years ago it continues to grow in functionality and gather more developer fans. Chris shares some lessons learned and best practices for building an API that developers will love for years to come. Some topics covered include:
- Breaking Changes Bad! API Versioning Good!
- REST Is Best
- API Governance
- Getting your API ready for the big v1.0
- Accurate Documentation & Documentation First
- API First
- Separating Deployment from Release
- Using API gateway or proxy for authentication and rate limiting
- Using community feedback to build the best email API
- When are breaking changes OK?
- Technical Excellence and Community Transparency
- Listen and Respond to the Developer Community
- Client Libraries
Similar Talks
Stateful Programming Models in Serverless Functions
Principal Engineering Manager @Microsoft, helping lead the Azure Functions Team
Chris Gillum
Evolution of Edge @Netflix
Engineering Leader @Netflix
Vasily Vlasov
Future of Data Engineering
Distinguished Engineer @WePay
Chris Riccomini
User & Device Identity for Microservices @ Netflix Scale
Senior Software Engineer in Product Edge Access Services Team @Netflix
Satyajit Thadeshwar
Observability in the Development Process: Not Just for Ops Anymore
Cofounder @honeycombio
Christine Yen
Data Mesh Paradigm Shift in Data Platform Architecture
Principal Technology Consultant @ThoughtWorks
Zhamak Dehghani
Scaling Patterns for Netflix's Edge
Playback Edge Engineering @Netflix
Justin Ryan
Architectures Panel
Playback Edge Engineering @Netflix
Justin Ryan
Secrets at Planet-Scale: Engineering the Internal Google KMS
Software Developer @Google