RPC to REST : Concrete Case on Payment APIs
summary
Klarna moves from XML‑RPC to a hypermedia REST stack to reduce coupling and library churn, shrinking an RPC surface that once neared ~100 methods down to about 30 real RPC calls and avoiding constant client library rewrites. Tooling includes Erlang/webmachine style servers, a homemade Jesse JSON schema validator, and a RestPie documentation hub that generates API blueprints and mocks via APIary, plus a small hypermedia client prototype; result: Checkout reaches REST public beta with automated docs and workable mocks.
AI-written summary · about
chapters (4)
related talks
46mREST API vs gRPC, which one should you use in breaking a monolith
31mRPC Frameworks Overview
01h 00mGraphQL, REST or RPC? Making the choice!
43mTUTORIAL: We've "REST"ed long enough -- let's have an API adventure!
38mAdvanced API Design for Scalable Distributed Systems
34mThe API Evolution
30m2004-2024 : Two Decades of Web Services, A Retrospective
04mSneak peek into the API world outside REST