Users always love new features. What most users don't see is how adding new features increase internal complexity. The hallmark of strong software architecture is when internal complexities don't leak out to users and make the product tough to use.
Using the Twilio API architecture as an example, this session will discuss how you can build ever-evolving software. Specifically, this session examines how API design decisions support new products and changes in the underlying architecture. You will walk away with lessons we learned that you can apply when designing for:
- Forward compatibility
- Scaling by orders of magnitude
- Balancing product consistency & technical correctness