Skip to content
Docs

Edge Caching

APIs are crucial in the digital world, where response times are measured in milliseconds. Traditional API gateways, primarily designed as routers for microservices, often treat performance optimization as a secondary aspect. Their typical approach to caching revolves around TTL (Time-to-Live) based mechanisms coupled with manual invalidation processes. This traditional method, while functional, falls short in dynamic environments where data changes frequently.

Traditional API Gateway Caching Limitations

In conventional API gateways, TTL-based caching involves setting a predetermined time after which the cached data expires. This approach can lead to challenges with stale data, particularly when changes occur before the TTL expires. The reliance on manual cache invalidation further complicates the process, requiring additional effort and often leading to delays in reflecting updated data.

Resilis’ Edge in Caching and Performance

Resilis distinguishes itself from traditional API gateways with its sophisticated approach to caching:

  1. Edge Optimization for Performance: Utilizing over 300 global edge servers, Resilis optimizes API responses by caching data closer to users. This strategy significantly reduces latency and improves response times in high traffic scenarios, a critical advantage over traditional gateways where performance is not the primary focus.

  2. Innovative Caching Strategy: Resilis employs a dual caching mechanism. For endpoints with dynamic data, it combines long TTL values with mutation-based invalidation, ensuring that any data change triggers an immediate cache update. For endpoints with infrequent data changes, long TTL settings are used, optimizing efficiency while maintaining data freshness. This approach provides a significant edge over traditional TTL-based caching, where data staleness and manual invalidation are common challenges.

  3. Multi-Level Caching System: Further enhancing its caching strategy, Resilis implements a multi-level caching system - private caches for user-specific resources, protected caches for authenticated users, and public caches for general access. This tiered approach optimizes caching based on access rights and resource types, aligning with modern security and performance needs.

  4. Efficient Handling of API Traffic: Resilis is designed to manage large volumes of API requests effectively, maintaining consistent performance during peak periods and efficiently offloading requests from origin servers to prevent overloads.

In contrast to traditional API gateways, where performance is a secondary feature, Resilis emerges as a leader in API performance optimization. Its advanced caching strategies, edge optimization, and focus on both security and efficiency make it a superior choice in modern API-driven environments.