Architecture patterns
As a forward proxy between your applications and the remote APIs they call, HARP is a natural place to apply common reliability and integration patterns. Each pattern below explains the idea and how it fits into that proxy layer.
Backend-for-Frontend (BFF)
Create dedicated backend services for each frontend to improve performance and maintainability.
Learn moreCircuit Breaker
Prevent cascading failures in distributed systems by stopping requests to failing services.
Learn moreHealth Monitoring
Monitor the health and performance of your services to ensure they are functioning correctly.
Learn moreRate Limiting
Control the rate of requests to your services to prevent overloading and ensure fair usage.
Learn moreRetry
Automatically retry failed requests to improve resilience and reliability.
Learn moreStrangler Fig
Gradually replace legacy systems with new ones by incrementally migrating functionality.
Learn moreTime limiting
Set time limits on operations to prevent long-running tasks from blocking resources.
Learn more