Case Study Deskcasestudydesk.com
Automation platform (SaaS)Sourced

Case Study: How Procesio cut execution latency 60% with Redis

Procesio Case StudySourced & dated by Case Study Desk
Key facts · TL;DR
Company
Procesio
Industry
Automation platform (SaaS)
Challenge
A move to microservices created bottlenecks, and open-source caching lost data at scale.
Headline result
60% reduction in execution latency

Key results

60%
Reduction in execution latency
80%
Fewer calls to the primary database
<50 ms
Data-access latency
2x
Platform usage supported
Doubled in three months

The challenge

Procesio's shift from a monolithic to a microservices architecture created performance bottlenecks, and its MySQL database could not deliver the low-latency access needed for real-time service communication. An open-source Redis cache used initially experienced data-loss incidents at scale, unacceptable for mission-critical work such as government e-invoicing.

The solution

Procesio adopted Redis Cloud as a high-throughput caching layer across its multi-cloud architecture spanning AWS, Azure, and on-premises. It caches process templates and execution states accessed by microservices in milliseconds, acting as the central backbone of the platform.

Redis is the backbone of Procesio. Its speed and reliability are fundamental to our promise of being the world's fastest automation platform.

AG
Alexandru Gal
CTO, Procesio

The results, in context

Procesio reports a 60% reduction in execution latency and an over-80% reduction in calls to its primary database with Redis Cloud, while delivering data-access latency of under 50 milliseconds. The platform supported a doubling of usage within three months without compromise.

Products used

Redis Redis Cloud