Why I removed REST APIs from my SaaS architectures
How reactive state with ActualLab Fusion changes user experience: no polling, no manual cache invalidation, no duplicated state.
English summary
Using OneRP and later SaaS builds as examples, the article explains how Fusion compute methods and invalidation can replace a pile of request/response endpoints for state-heavy products.
Key takeaways
Repeated reads are often the hidden cost in SaaS UX.
Reactive invalidation can remove manual cache choreography.
The pattern is powerful but requires team discipline.
Original long-form article
The long technical article is available in French with code, context and detailed examples. The English page gives the recruiter-readable summary and the main engineering points.
Open the French articleNext step
Sounds like something you need shipped? Let's talk.
I take on critical technical work — from scoping to production, no debt or lock-in once it's handed over. Fastest way to see if it fits: a 30-minute call.
I reply within 24h — often sooner.