Designing HTTP APIs for slow operations
We got used to having everything on the Web, and so many backend operations became HTTP APIs. That’s also the case in the areas of AI and optimization, because it gives an easy-to-understand interface for clients that can be used without having to learn new technologies. There’s a problem, however: Some of these operations are very slow, and at times systems become a brittle mess of regular timeout hits, latency optimizations, and support issues.





