Architecture and Infra on ThecoreGrid covers the foundations of designing and operating scalable, reliable systems at BigTech level. This category brings together system design and infrastructure practices: distributed architectures, highload patterns, cloud-native platforms, and core layers such as compute, networking, and storage. We focus on real engineering decisions — how to balance reliability, performance, cost, and long-term system evolution. Topics include Infrastructure as Code, Kubernetes, multi-region deployments, traffic management, and platform design. Content is grounded in production experience: incident post-mortems, large-scale migrations, and lessons from operating infrastructure under heavy load. Instead of abstract theory, you get practical trade-offs, proven patterns, and insights drawn from real-world systems. Architecture & Infra is built for architects, backend and platform engineers, DevOps teams, and SREs responsible for complex distributed systems and mission-critical infrastructure.
The profiler in kernel space only sees addresses. Useful insights emerge only after symbolization—and in Go, this stage is structured differently than in other languages. The problem arises when the profile has already been collected, but it cannot be interpreted. The eBPF profiler captures stack traces at the kernel level and obtains a set of … Read more
When component specifications lag behind implementation, the team starts building the system based on assumptions. At Uber, this turned into a systemic, large-scale problem—and was solved through agent-based automation. The problem does not arise at the moment of writing specifications, but later—when the system begins to evolve faster than the documentation. The Uber Base design … Read more
Higress enters the CNCF Sandbox as an API gateway with the aim of consolidating multiple layers of traffic. The key question is whether this reduces complexity or merely shifts it elsewhere. Systems begin to degrade when the traffic management layer becomes fragmented. Ingress operates separately, the gateway for microservices operates separately, and solutions for AI … Read more
The increase in developer productivity has not led to a comparable acceleration of releases. The reason is that the bottleneck has moved higher up the stack: into the area of requirements formalization and result verification. With the advent of AI coding, teams expected a linear acceleration in delivery. In practice, only one stage sped up—the … Read more
In live streaming, an error is not a degradation but an instant user-facing incident. Netflix addresses this by moving quality control and prioritization directly into the origin layer. The main limitation arises where VOD approaches stop working. In live, there is no time buffer: a segment must be encoded, delivered, and cached within seconds. Any … Read more
Digital sovereignty in engineering practice boils down to a single question: how quickly can you switch providers without breaking the system? The answer is almost always determined by architecture. A system does not start to degrade at the moment a provider fails, but much earlier, when dependency on that provider becomes implicit. This shows up … Read more
When the number of containerized services grows faster than the platform team, the bottleneck is not Kubernetes itself, but its operation. Generali faced exactly this challenge—and shifted the focus from cluster management to application management. The main limitation was not performance, but operations. The microservices portfolio was expanding, multi-tenant scenarios emerged, and with them—manual scaling, … Read more
As LLM production workloads grow, it becomes clear: classic Kubernetes mechanisms do not understand the nature of inference. llm-d is an attempt to bridge this gap at the platform level. The main limitation becomes apparent when inference goes beyond a “stateless HTTP service.” Requests to LLMs have different costs: prompt length, generation phase, KV-cache hits. … Read more
When LLM becomes part of production infrastructure, traditional monitoring is no longer sufficient. The bottleneck is no longer the application code, but the routing and model selection layer — and that’s exactly where observability is needed. In LLM systems, degradation doesn’t start with HTTP endpoint failures, but with the accumulation of subtle effects: increased latency … Read more
The Spring milestone release cycle shows a shift in focus: from the framework as runtime to the framework as a layer for managing protocols, data, and behavior. This is crucial where integrations and configuration become the main sources of failures. The main point of tension is not in business logic, but at the interfaces: messaging, … Read more
Controls: ← → to move, ↑ to rotate, ↓ to drop.
Mobile: use buttons below.