How to (and how not to) design REST APIs · stickfigure/blog Wiki
Jeff Schnitzer's Blog. Contribute to stickfigure/blog development by creating an account on GitHub.
Infrastructure
A story about HTTP status codes and why you should read documentation
Learn four things to consider when building APIs related to HTTP status codes. And when consuming APIs, don’t do what I did. Read the documentation, understand how the API is designed, and code defensively around unexpected results.
How a 3rd Party API Can Ruin Your Weekend
Lessons from my longest production crisis
Creating great online services: how we test services in our research lab
How we built a Streaming SQL Engine | Epsio
Vectors are the new JSON in PostgreSQL
A new demand for storing an old data type in PostgreSQL.
Converting stateful application to stateless using AWS services | Amazon Web Services
Designing a system to be either stateful or stateless is an important choice with tradeoffs regarding its performance and scalability. In a stateful system, data from one session is carried over to the next. A stateless system doesn’t preserve data between sessions and depends on external entities such as databases or cache to manage state. […]