How kannappansomasundaram1/testingresiliency works
Project type and purpose
• This is a .NET solution (TestingResiliency.sln) demonstrating a resilient HTTP API with fault injection via ToxiProxy and automated chaos tests (SimmyChaosTests).
• Key purpose: show how an ASP.NET Core “Todo” API client experiences downstream failures (latency, resets), use policies (circuit breaker, retries), and verify behavior under load and chaos.
File structure
• Top-level solution “TestingResiliency.sln” contains:
• ApiUsingToxiProxy – ASP.NET Core Web API project (Program.cs, appsettings, TodoClient, TodoItem).
• Aspire.AppHost – a reusable app host project with default host configuration and middleware.
• Aspire.ServiceDefaults – a class library for common DI/extension methods (service defaults, resilience pipeline).
• SimmyChaosTests – xUnit test project using Simmy to inject chaos into policies.
• Notice build configs (launchSettings.json, appsettings.{Development}.json), a load test script (loadtest.js), and HTTP query file (WebApplication1.http).
README for insights
• API → DummyJson.com
• API → ToxiProxy → DummyJson.com
• Steps to install/run ToxiProxy, create proxy “todo,” inject latency/reset faults, exercise circuit breaker under load (k6), and tests.
Main components
a. Backend API (ApiUsingToxiProxy)
• ASP.NET Core application hosted via Aspire.AppHost
• Uses Aspire.ServiceDefaults for default services and resilience pipeline (Polly/Simmy)
• Contains TodoClient which calls external API
b. Resilience Library (Aspire.ServiceDefaults)
• Extension methods registering retry, timeout, circuit-breaker policies
c. Chaos Test Suite (SimmyChaosTests)
• Simmy policies testing pipeline behavior under injected faults
d. ToxiProxy Server
• HTTP/TCP proxy sitting between API and DummyJson.com
• Configured via toxiproxy-cli to induce latency, resets
e. External API (DummyJson.com)
• Upstream service providing /todos endpoints
f. Load-Test Client (k6 / loadtest.js)
• Generates concurrent requests to API to trigger circuit-breaker
Relationships and data-flow
• Load-Test → HTTP → API
• API → (over configured HTTP client) → ToxiProxy → DummyJson.com
• SimmyChaosTests → in-process HTTP client pipeline (inject faults via Simmy policies)
• API uses Aspire.ServiceDefaults to wire resilience policies around TodoClient
Architectural patterns & design principles
• Layered components: Host, Service Defaults (DI & middleware), Business logic (TodoClient & controllers)
• Dependency Injection & extension-method modules for reuse
• Resilience patterns: retry, timeout, circuit-breaker (Polly + Simmy)
• Separation of concerns: Proxy layer (ToxiProxy) kept external, tests isolated
Technology & frameworks
• .NET 7/ASP.NET Core, C#
• Aspire.AppHost (generic host builder)
• Aspire.ServiceDefaults (custom library)
• ToxiProxy server & CLI (Shopify) for network chaos
• Simmy (Chaos injection in Polly pipelines)
• k6 load testing (JavaScript)
• xUnit for SimmyChaosTests