What kind of scaling decisions can this skill help with?

It helps evaluate the trade-offs between vertical and horizontal scaling, ensuring you only move to distributed systems when the coordination costs are justified.

Can it help with database performance and sharding?

Yes, it provides specific guidance on shard key selection, hash/range/geo-based sharding, and managing replication lag in distributed databases.

When should I use the CQRS pattern with this skill?

This skill follows the core principle of applying CQRS only when read and write patterns significantly diverge, helping you avoid premature complexity.

Does it include capacity planning features?

Absolutely. It uses back-of-the-envelope formulas to estimate QPS, storage, bandwidth, and memory requirements to prevent architectural under-engineering.

Scalability Analysis Architect

Name: Scalability Analysis Architect
Author: rnavarych

byrnavarych

•

Infraestructura en la Nube

Analyzes system architecture to optimize for high-scale workloads using sharding, caching, and capacity estimation strategies.

The Scalability Analysis skill transforms Claude into a senior system architect capable of designing robust, high-performance infrastructures. It provides specialized guidance on choosing between vertical and horizontal scaling, designing complex sharding strategies, and implementing patterns like CQRS and read/write splitting with replication-lag awareness. By performing precise back-of-the-envelope calculations for QPS, storage, and bandwidth, it helps developers avoid the pitfalls of both over-engineering and performance bottlenecks during the design phase.

Características Principales

01Caching layer design with invalidation strategy optimization

02Database sharding and shard key selection strategy

03Back-of-envelope capacity math for QPS and storage

04Horizontal vs. vertical scaling trade-off analysis

0511 GitHub stars

06Implementation patterns for CQRS and eventual consistency

Casos de Uso

01Calculating infrastructure requirements and memory limits for an upcoming high-traffic launch

02Designing a database architecture for an application approaching its single-node performance limit

03Refactoring data access layers to support read/write splitting while managing replication lag

Características Principales

01Caching layer design with invalidation strategy optimization

02Database sharding and shard key selection strategy

03Back-of-envelope capacity math for QPS and storage

04Horizontal vs. vertical scaling trade-off analysis

0511 GitHub stars

06Implementation patterns for CQRS and eventual consistency

Casos de Uso

01Calculating infrastructure requirements and memory limits for an upcoming high-traffic launch

02Designing a database architecture for an application approaching its single-node performance limit

03Refactoring data access layers to support read/write splitting while managing replication lag