API (Application Programming Interface) is the front door to a server, allowing other applications to access data or trigger events. It's the interface that enables a jaded, highly technical software engineer to begrudgingly integrate disparate systems instead of writing new code from scratch.
"I just spent the last 3 days documenting our API (Application Programming Interface) so the new intern can understand it - I'm pretty sure my soul has left my body," grumbled the senior software architect.
"Oh great, the product manager wants us to expose a public API (Application Programming Interface) for our legacy monolith - I guess I'll cancel my weekend plans," sighed the tech lead.
Become a more technical product manager by Colin Matthews provides a good overview of application architecture and the role APIs (Application Programming Interfaces) play in connecting clients, servers, and databases.
API design by Martin Fowler dives into key concepts like public vs published interfaces, refactoring module dependencies, and why APIs (Application Programming Interfaces) should not be copyrightable.
Web services also by Martin Fowler covers topics like microservices architecture, enterprise integration using REST, and the Richardson Maturity Model for evolving APIs (Application Programming Interfaces).
Note: the Developer Dictionary is in Beta. Please direct feedback to skye@statsig.com.