GlueCon 2013 Notes: An Architectural Look at Designing e-commerce APIs – Saranyan Vigraham, BigCommerce
An Architectural Look at Designing e-commerce APIs – Saranyan Vigraham, BigCommerce (@saranyan) Bad Design Rigid – too hard to change, too many parts get affected by a change Fragile – unexpected breaks No re-usability – it’s part of the “core code” Everything is mobile, but is has forced us to re-think the important of the platform “Where is your API?” is now popular Commonly, each tier requires its own service stack (web, mobile) that all integrate to the datastore(s) API-first architecture approach gaining traction “Everything is a service” – all tiers/devices connect to the API layer Segregate interfaces and integration to the API (not the details) aka Liskov substitution
An Architectural Look at Designing e-commerce APIs – Saranyan Vigraham, BigCommerce (@saranyan)
- Bad Design
- Rigid – too hard to change, too many parts get affected by a change
- Fragile – unexpected breaks
- No re-usability – it’s part of the “core code”
- Everything is mobile, but is has forced us to re-think the important of the platform
- “Where is your API?” is now popular
- Commonly, each tier requires its own service stack (web, mobile) that all integrate to the datastore(s)
- API-first architecture approach gaining traction
- “Everything is a service” – all tiers/devices connect to the API layer
- Segregate interfaces and integration to the API (not the details) aka Liskov substitution