POC: Custom proxy cache

[rishabhkailey]

Discription

• Evaluate the feasibility and effectiveness of building a custom Go application to act as a caching proxy for Grafana requests.
• Analyze the pros and cons of this approach, considering:
  • Cache efficiency: Effectiveness of caching strategies and data freshness management.
  • Resource utilization: Memory footprint, CPU overhead, and impact on other system resources.
  • Overall impact on application delivery: Consistency, reliability, and potential risks.

[rishabhkailey]

summary of using a custom Golang application for caching, highlighting its pros and cons:

Pros:

• Customizability: Offers granular control over cache strategies, logic, and integration with Grafana's specific needs.
• Potential for Distributed Caching: Can be integrated with Redis for scalable, shared caching across multiple instances.
• Slight Performance Edge: May outperform Nginx caching due to strictly in-memory storage for faster access.

Cons:

• Development Complexity: Requires significant effort to implement features like request handling, memory management, usage tracking, and cache eviction policies.
• Memory Intensive: Strictly in-memory caching can consume considerable memory resources, potentially impacting overall system performance.
• Maintenance Overhead: Ongoing testing, updates, and bug fixes are necessary for custom code, adding to maintenance workload.

[rishabhkailey]

we are going ahead with the nginx approach. check this comment for more details.