AI accelerated releases. Now the system must withstand failures

The techniques in the book have been known for years. AI turns them from good practice into a basic requirement. ###

Timeouts and retries Every external call needs an explicit waiting limit.

Retry requests with exponential backoff and jitter, so a thousand clients do not hit the service simultaneously as it recovers. ###

Circuit breakers and bulkheads A circuit breaker works like the breaker in an electrical panel.

After repeated errors, it stops sending requests to the failing service and returns a fallback response. A bulkhead gives each dependency its own resource pool: slow catalogue search consumes only its own threads, leaving checkout threads unaffected. ### Idempotency

An operation is idempotent when repeating it does not change the result.

A payment message with a unique key can be delivered twice, but the charge is made only once.

Without idempotency, every retried request can create a duplicate order.

In KT.Team projects, we build these safeguards into the architecture from the first sprint.

Adding them to an operating system after the first incident takes longer and costs more.

Model calls go through LLM & Security Gateway.

The gateway enforces timeouts and limits, counts tokens and switches to a backup model. If Claude does not respond in time, it routes the request to Qwen or GigaChat.

The gateway routes tasks involving personal data only to the required CIS environment.

The application does not need to know about that choice; it simply receives a response.

We use queues for exchanges with accounting systems: Apache Kafka or a message bus Datareon.

If 1C is unavailable for half an hour, messages wait in the queue while the site continues accepting orders.

Message consumers are idempotent, so redelivery does not create duplicates. In AI-native development the agent writes code, but automated tests, a canary release to a small traffic share and automatic rollback on increased errors decide what reaches production.

The agent supplies speed; only commits that pass the gates reach customers.