A Successful API is More Than The Sum of its Parts
I recently spoke at QConSF on the topic of “Using Microservices to Build an API That Lasts”. This conference had several excellent sessions and speakers that get into the technical details you need to know about microservices. There is also lots of great information – books and blogs – on the languages and tools you need to build and run your microservices. But a successful API is more than the sum of its parts. So while I do mention some technology, I go beyond that and touch on important product and process considerations. In the talk, I walk you through some strategies we use at SparkPost to continuously evolve our API even as we go through rapid growth and adoption. I hope some of these may be useful in your own API development.
Using Microservices to Build an API That Lasts
This talk covers several topics including:
- REST Is Best: Be Practical not Pedantic
- API Versioning
- API First
- Documentation as Code & Documentation First
- Separating Deployment from Release
- Breaking Changes Bad! API Versioning Good!
- When are breaking changes OK?
- Client Libraries
- Listen and Respond to the Developer Community
And if you’re interested, we’ve included the slides from my talk below as well.
Slides from QConSF
- RESTful API Versioning Best Practices: Why v1 is #1
- Our DevOps Journey: Achieving Continuous Delivery and Improvement
- Our DevOps Journey: Focusing on Deployment Automation
- Configuration Management and Provisioning in AWS with CloudFormation, Ansible, and Puppet