[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FAS2KWG2M32F12VN695321":3,"skill-same:01M7FAS2KWG2M32F12VN695321":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7FAS2KWG2M32F12VN695321","tech-matrix",null,"Reference document for monopoly tech-matrix.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fmonopoly\u002Ftech-matrix\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: tech-matrix\ndescription: Reference document for monopoly tech-matrix.\nsource: community\ndate_added: \"2026-09-04\"\nrisk: safe\nreports-to: monopoly\n---\n\n# MONOPOLY — Technology Decision Matrix\n\n## When to Use\n- Use this skill when the task matches this description: Reference document for monopoly tech-matrix.\n\n## Table of Contents\n1. Database Selection\n2. Cache Selection\n3. Message Queue \u002F Event Streaming\n4. API Protocol\n5. Search Engine\n6. Object Storage\n7. Container Orchestration\n8. Load Balancer\n9. Observability Stack\n10. CDN\n\n---\n\n## 1. Database Selection\n\n### Relational (SQL)\n\n| Database | Best For | Avoid When | Scale Ceiling |\n|----------|----------|------------|---------------|\n| **PostgreSQL** | Complex queries, JSONB, GIS, strong consistency, most default use cases | Ultra-high write throughput (>100K writes\u002Fs) | ~10TB single node; use Citus for horizontal |\n| **MySQL \u002F MariaDB** | Read-heavy apps, legacy systems, WordPress\u002FDrupal ecosystem | Complex queries, full ACID at scale | ~10TB; use Vitess for sharding |\n| **CockroachDB** | Global distributed SQL, geo-partitioning, multi-region | Simple single-region apps (overkill) | Petabyte-scale |\n| **PlanetScale** | MySQL-compatible, serverless, branch-based workflow | Complex JOINs (foreign keys removed by design) | Very high — Vitess based |\n| **Amazon Aurora** | AWS-native apps, managed PostgreSQL\u002FMySQL, high availability | Non-AWS environments | Up to 128TB, 15 replicas |\n\n### NoSQL\n\n| Database | Best For | Avoid When | Scale Ceiling |\n|----------|----------|------------|---------------|\n| **MongoDB** | Flexible schema, document model, prototyping | Financial transactions requiring ACID | Petabyte-scale with sharding |\n| **DynamoDB** | Key-value at massive scale, AWS-native, serverless, predictable latency | Complex queries, ad-hoc analytics, JOINs | Unlimited (AWS-managed) |\n| **Cassandra** | Write-heavy, time-series, wide-column, geographically distributed | Read-heavy with complex queries | Petabyte-scale; used at Apple, Netflix |\n| **Redis** | Cache, sessions, leaderboards, pub\u002Fsub, rate limiting | Primary data store for complex models | ~1TB per node; cluster for more |\n| **Elasticsearch** | Full-text search, log aggregation, analytics | Primary database (durability risk) | Petabyte-scale with clusters |\n| **InfluxDB** | Time-series metrics, IoT, monitoring data | General-purpose data | Very high write throughput |\n| **Neo4j** | Graph data, social networks, recommendation engines, fraud detection | Non-graph data (overhead not worth it) | Billions of nodes |\n\n### Decision Framework\n\n```\nIs your data relational (joins, foreign keys, transactions)?\n  YES → Start with PostgreSQL\n  NO  → Continue below\n\nIs your primary access pattern key-value?\n  YES, need extreme scale → DynamoDB or Cassandra\n  YES, need speed\u002Fcache → Redis\n\nIs your data document-shaped (nested, flexible schema)?\n  YES → MongoDB\n\nIs it time-series (metrics, logs, IoT)?\n  YES → InfluxDB or TimescaleDB\n\nIs it graph (relationships are the data)?\n  YES → Neo4j\n\nIs it search?\n  YES → Elasticsearch \u002F OpenSearch\n```\n\n---\n\n## 2. Cache Selection\n\n| Technology | Best For | Max Single Node | Cluster Support |\n|------------|----------|----------------|----------------|\n| **Redis** | Sessions, leaderboards, pub\u002Fsub, complex data structures, Lua scripting | ~1TB RAM | Yes (Redis Cluster, Redis Sentinel) |\n| **Memcached** | Simple key-value, multi-threaded, large object cache | ~64GB RAM | Yes (client-side sharding) |\n| **Varnish** | HTTP reverse proxy cache, full-page caching | RAM bound | Limited |\n| **CloudFront \u002F CDN** | Static assets, edge caching globally | N\u002FA (distributed) | Built-in global distribution |\n\n**Default recommendation: Redis** — more features, better ecosystem, active development.\n\nUse **Memcached** only when: you need multi-threading for CPU-bound caching workloads and don't need data structures beyond string.\n\n---\n\n## 3. Message Queue \u002F Event Streaming\n\n| Technology | Model | Best For | Throughput | Retention |\n|------------|-------|----------|------------|-----------|\n| **Apache Kafka** | Log-based streaming | Event sourcing, high-throughput pipelines, replay, audit | Millions msg\u002Fs | Days to forever |\n| **RabbitMQ** | AMQP message broker | Task queues, RPC, routing, fanout | 50K–100K msg\u002Fs | Until consumed |\n| **AWS SQS** | Managed queue | AWS-native, simple task queue, serverless | Very high (managed) | Up to 14 days |\n| **AWS SNS** | Pub\u002Fsub notification | Fan-out to many subscribers (email, SMS, Lambda, SQS) | Very high (managed) | No retention |\n| **Google Pub\u002FSub** | Managed streaming | GCP-native, global, serverless | Very high (managed) | Up to 7 days |\n| **Redis Pub\u002FSub** | In-memory pub\u002Fsub | Real-time notifications, low latency, fire-and-forget | Very high | None (no retention) |\n| **NATS** | Lightweight messaging | IoT, microservices, low latency | Very high | JetStream adds retention |\n\n### Decision Matrix\n\n```\nNeed event replay \u002F audit trail?\n  YES → Kafka or Kinesis\n\nNeed simple task queue with retries and DLQ?\n  AWS shop → SQS\n  Self-hosted → RabbitMQ\n\nNeed real-time pub\u002Fsub with no persistence?\n  Redis Pub\u002FSub or NATS\n\nNeed fan-out to multiple consumers?\n  Kafka (consumer groups) or SNS → SQS fan-out\n\nNeed \u003C 5 minutes guaranteed delivery, AWS-native, zero ops?\n  SQS\n\nVolume > 1 million messages\u002Fsecond?\n  Kafka (self-hosted) or Kinesis (managed)\n```\n\n---\n\n## 4. API Protocol\n\n| Protocol | Best For | Avoid When |\n|----------|----------|------------|\n| **REST (HTTP\u002FJSON)** | Public APIs, CRUD, browser clients, simplicity | Strict typing required; high-performance internal services |\n| **GraphQL** | Complex client data requirements, mobile (reduce over-fetching), BFF pattern | Simple CRUD; not worth the complexity |\n| **gRPC (HTTP\u002F2 + Protobuf)** | Internal microservice communication, low latency, strict contracts, streaming | Public browser APIs (needs gRPC-web) |\n| **WebSocket** | Real-time bidirectional (chat, live dashboards, multiplayer games) | One-way server push (use SSE instead) |\n| **SSE (Server-Sent Events)** | Server → client push (notifications, live feeds) | Bidirectional communication |\n| **GraphQL Subscriptions** | Real-time with GraphQL schema consistency | Simple push scenarios |\n\n**Default recommendation:**\n- External \u002F public: **REST**\n- Internal service-to-service: **gRPC**\n- Real-time features: **WebSocket** or **SSE**\n\n---\n\n## 5. Search Engine\n\n| Technology | Best For | Avoid When |\n|------------|----------|------------|\n| **Elasticsearch** | Full-text search, log analytics (ELK), complex aggregations | Simple lookups; operational overhead is high |\n| **OpenSearch** | AWS-native Elasticsearch alternative | Non-AWS preferred setups |\n| **Typesense** | Simple, fast full-text search, typo tolerance, easy ops | Complex aggregations at massive scale |\n| **Algolia** | Managed search-as-a-service, fast setup, great UI | High volume (expensive); self-hosted preference |\n| **Meilisearch** | Self-hosted, developer-friendly, fast relevancy | Enterprise-scale analytics |\n| **PostgreSQL FTS** | Basic full-text search, already using PostgreSQL | High relevancy requirements or large datasets |\n\n**Rule of thumb:** Use PostgreSQL FTS under 1M documents. Move to Typesense or Elasticsearch above that.\n\n---\n\n## 6. Object Storage\n\n| Service | Best For | Egress Cost |\n|---------|----------|------------|\n| **AWS S3** | AWS-native apps, de facto standard, massive ecosystem | $0.09\u002FGB (expensive) |\n| **Cloudflare R2** | S3-compatible, **zero egress cost**, global | $0.00 egress |\n| **GCS** | GCP-native | $0.12\u002FGB |\n| **Azure Blob** | Azure-native | $0.087\u002FGB |\n| **Backblaze B2** | Cost-sensitive, S3-compatible | Free with Cloudflare |\n| **MinIO** | Self-hosted S3-compatible | Self-managed |\n\n**Cost optimization tip:** Use **Cloudflare R2** for user-facing media delivery (zero egress). Use **S3** for internal\u002FAWS-integrated storage.\n\n---\n\n## 7. Container Orchestration\n\n| Technology | Best For | Avoid When |\n|------------|----------|------------|\n| **Kubernetes (K8s)** | Large teams, complex deployments, multi-cloud, full control | Small teams (ops overhead is very high) |\n| **AWS ECS + Fargate** | AWS-native, serverless containers, simpler than K8s | Multi-cloud or K8s ecosystem tools needed |\n| **AWS EKS** | Managed K8s on AWS, best of both | Small teams; Fargate may be enough |\n| **GKE (Google)** | Best managed K8s, GCP-native, Autopilot mode | Non-GCP environments |\n| **Docker Compose** | Local dev, small single-server deployments | Production at any meaningful scale |\n| **Nomad** | HashiCorp ecosystem, simpler than K8s, multi-workload | K8s ecosystem tools required |\n\n**Startup default:** ECS + Fargate (zero cluster management).\n**Scale default:** EKS or GKE once team > 5 engineers or services > 10.\n\n---\n\n## 8. Load Balancer\n\n| Technology | Layer | Best For |\n|------------|-------|----------|\n| **AWS ALB** | L7 (HTTP\u002FHTTPS) | AWS apps, path-based routing, WebSocket, HTTP\u002F2 |\n| **AWS NLB** | L4 (TCP\u002FUDP) | Ultra-low latency, static IP, non-HTTP protocols |\n| **GCP GLB** | L7 global | GCP apps, global anycast, single IP worldwide |\n| **Nginx** | L4\u002FL7 | Self-hosted, reverse proxy, flexible config |\n| **HAProxy** | L4\u002FL7 | High performance self-hosted, advanced routing |\n| **Cloudflare** | L7 global + DDoS | DDoS protection + CDN + load balancing combined |\n| **Traefik** | L7 | Kubernetes-native, automatic SSL, service discovery |\n\n---\n\n## 9. Observability Stack\n\n### Metrics\n| Tool | Best For |\n|------|----------|\n| **Prometheus + Grafana** | Self-hosted, open-source, Kubernetes-native |\n| **Datadog** | Managed, APM + infra + logs unified, expensive |\n| **CloudWatch** | AWS-native, zero setup, integrated with AWS services |\n| **New Relic** | APM-focused, good for application-level insights |\n\n### Logging\n| Tool | Best For |\n|------|----------|\n| **ELK Stack** (Elasticsearch + Logstash + Kibana) | Self-hosted, powerful, high volume |\n| **Loki + Grafana** | Lightweight, Kubernetes-native, cheap |\n| **Splunk** | Enterprise, compliance, expensive |\n| **AWS CloudWatch Logs** | AWS-native, zero setup |\n| **Datadog Logs** | Unified with metrics, expensive |\n\n### Distributed Tracing\n| Tool | Best For |\n|------|----------|\n| **Jaeger** | Open-source, Kubernetes-native, OpenTelemetry |\n| **Zipkin** | Simple, lightweight, good integrations |\n| **AWS X-Ray** | AWS-native, integrates with Lambda, ECS |\n| **Datadog APM** | Managed, unified with metrics and logs |\n| **Honeycomb** | High-cardinality event-based observability |\n\n**Recommended open-source stack:** Prometheus + Grafana + Loki + Jaeger (all integrate via OpenTelemetry)\n**Recommended managed stack:** Datadog (expensive but unified) or Grafana Cloud\n\n---\n\n## 10. CDN\n\n| Technology | Best For | Edge Locations |\n|------------|----------|----------------|\n| **Cloudflare** | DDoS protection + CDN + DNS, best free tier, edge workers | 300+ |\n| **AWS CloudFront** | AWS-native, deep S3 and API GW integration | 450+ |\n| **Akamai** | Enterprise, highest performance, expensive | 4000+ |\n| **Fastly** | Real-time purging, streaming, VCL customization | 90+ |\n| **Vercel Edge \u002F Netlify** | Jamstack, frontend-first, zero config | 100+ |\n\n**Default recommendation:** Cloudflare for most use cases (best value, DDoS included, free SSL, Workers for edge compute).\n\n---\n\n## Scale Benchmarks Quick Reference\n\n| Technology | Write Throughput | Read Throughput | Notes |\n|------------|-----------------|----------------|-------|\n| PostgreSQL (single) | ~10K writes\u002Fs | ~50K reads\u002Fs | With connection pooling |\n| PostgreSQL (replicas) | ~10K writes\u002Fs | ~200K reads\u002Fs | 4 replicas |\n| MySQL (single) | ~15K writes\u002Fs | ~60K reads\u002Fs | |\n| Cassandra | ~1M writes\u002Fs | ~500K reads\u002Fs | 10-node cluster |\n| Redis | ~1M ops\u002Fs | ~1M ops\u002Fs | Single node in-memory |\n| Kafka | ~1M msgs\u002Fs | ~1M msgs\u002Fs | Per partition |\n| Elasticsearch | ~50K docs\u002Fs | ~10K queries\u002Fs | Per node |\n| MongoDB | ~50K writes\u002Fs | ~100K reads\u002Fs | Per replica set |\n\n*All benchmarks are approximate and depend heavily on hardware, payload size, and query complexity.*\n\n\n## Limitations\n- This is a reference document and may not cover all edge cases. Always verify architectures before production.\n","# MONOPOLY — Technology Decision Matrix\n\n## When to Use\n- Use this skill when the task matches this description: Reference document for monopoly tech-matrix.\n\n## Table of Contents\n1. Database Selection\n2. Cache Selection\n3. Message Queue \u002F Event Streaming\n4. API Protocol\n5. Search Engine\n6. Object Storage\n7. Container Orchestration\n8. Load Balancer\n9. Observability Stack\n10. CDN\n\n---\n\n## 1. Database Selection\n\n### Relational (SQL)\n\n| Database | Best For | Avoid When | Scale Ceiling |\n|----------|----------|------------|---------------|\n| **PostgreSQL** | Complex queries, JSONB, GIS, strong consistency, most default use cases | Ultra-high write throughput (>100K writes\u002Fs) | ~10TB single node; use Citus for horizontal |\n| **MySQL \u002F MariaDB** | Read-heavy apps, legacy systems, WordPress\u002FDrupal ecosystem | Complex queries, full ACID at scale | ~10TB; use Vitess for sharding |\n| **CockroachDB** | Global distributed SQL, geo-partitioning, multi-region | Simple single-region apps (overkill) | Petabyte-scale |\n| **PlanetScale** | MySQL-compatible, serverless, branch-based workflow | Complex JOINs (foreign keys removed by design) | Very high — Vitess based |\n| **Amazon Aurora** | AWS-native apps, managed PostgreSQL\u002FMySQL, high availability | Non-AWS environments | Up to 128TB, 15 replicas |\n\n### NoSQL\n\n| Database | Best For | Avoid When | Scale Ceiling |\n|----------|----------|------------|---------------|\n| **MongoDB** | Flexible schema, document model, prototyping | Financial transactions requiring ACID | Petabyte-scale with sharding |\n| **DynamoDB** | Key-value at massive scale, AWS-native, serverless, predictable latency | Complex queries, ad-hoc analytics, JOINs | Unlimited (AWS-managed) |\n| **Cassandra** | Write-heavy, time-series, wide-column, geographically distributed | Read-heavy with complex queries | Petabyte-scale; used at Apple, Netflix |\n| **Redis** | Cache, sessions, leaderboards, pub\u002Fsub, rate limiting | Primary data store for complex models | ~1TB per node; cluster for more |\n| **Elasticsearch** | Full-text search, log aggregation, analytics | Primary database (durability risk) | Petabyte-scale with clusters |\n| **InfluxDB** | Time-series metrics, IoT, monitoring data | General-purpose data | Very high write throughput |\n| **Neo4j** | Graph data, social networks, recommendation engines, fraud detection | Non-graph data (overhead not worth it) | Billions of nodes |\n\n### Decision Framework\n\n```\nIs your data relational (joins, foreign keys, transactions)?\n  YES → Start with PostgreSQL\n  NO  → Continue below\n\nIs your primary access pattern key-value?\n  YES, need extreme scale → DynamoDB or Cassandra\n  YES, need speed\u002Fcache → Redis\n\nIs your data document-shaped (nested, flexible schema)?\n  YES → MongoDB\n\nIs it time-series (metrics, logs, IoT)?\n  YES → InfluxDB or TimescaleDB\n\nIs it graph (relationships are the data)?\n  YES → Neo4j\n\nIs it search?\n  YES → Elasticsearch \u002F OpenSearch\n```\n\n---\n\n## 2. Cache Selection\n\n| Technology | Best For | Max Single Node | Cluster Support |\n|------------|----------|----------------|----------------|\n| **Redis** | Sessions, leaderboards, pub\u002Fsub, complex data structures, Lua scripting | ~1TB RAM | Yes (Redis Cluster, Redis Sentinel) |\n| **Memcached** | Simple key-value, multi-threaded, large object cache | ~64GB RAM | Yes (client-side sharding) |\n| **Varnish** | HTTP reverse proxy cache, full-page caching | RAM bound | Limited |\n| **CloudFront \u002F CDN** | Static assets, edge caching globally | N\u002FA (distributed) | Built-in global distribution |\n\n**Default recommendation: Redis** — more features, better ecosystem, active development.\n\nUse **Memcached** only when: you need multi-threading for CPU-bound caching workloads and don't need data structures beyond string.\n\n---\n\n## 3. Message Queue \u002F Event Streaming\n\n| Technology | Model | Best For | Throughput | Retention |\n|------------|-------|----------|------------|-----------|\n| **Apache Kafka** | Log-based streaming | Event sourcing, high-throughput pipelines, replay, audit | Millions msg\u002Fs | Days to forever |\n| **RabbitMQ** | AMQP message broker | Task queues, RPC, routing, fanout | 50K–100K msg\u002Fs | Until consumed |\n| **AWS SQS** | Managed queue | AWS-native, simple task queue, serverless | Very high (managed) | Up to 14 days |\n| **AWS SNS** | Pub\u002Fsub notification | Fan-out to many subscribers (email, SMS, Lambda, SQS) | Very high (managed) | No retention |\n| **Google Pub\u002FSub** | Managed streaming | GCP-native, global, serverless | Very high (managed) | Up to 7 days |\n| **Redis Pub\u002FSub** | In-memory pub\u002Fsub | Real-time notifications, low latency, fire-and-forget | Very high | None (no retention) |\n| **NATS** | Lightweight messaging | IoT, microservices, low latency | Very high | JetStream adds retention |\n\n### Decision Matrix\n\n```\nNeed event replay \u002F audit trail?\n  YES → Kafka or Kinesis\n\nNeed simple task queue with retries and DLQ?\n  AWS shop → SQS\n  Self-hosted → RabbitMQ\n\nNeed real-time pub\u002Fsub with no persistence?\n  Redis Pub\u002FSub or NATS\n\nNeed fan-out to multiple consumers?\n  Kafka (consumer groups) or SNS → SQS fan-out\n\nNeed \u003C 5 minutes guaranteed delivery, AWS-native, zero ops?\n  SQS\n\nVolume > 1 million messages\u002Fsecond?\n  Kafka (self-hosted) or Kinesis (managed)\n```\n\n---\n\n## 4. API Protocol\n\n| Protocol | Best For | Avoid When |\n|----------|----------|------------|\n| **REST (HTTP\u002FJSON)** | Public APIs, CRUD, browser clients, simplicity | Strict typing required; high-performance internal services |\n| **GraphQL** | Complex client data requirements, mobile (reduce over-fetching), BFF pattern | Simple CRUD; not worth the complexity |\n| **gRPC (HTTP\u002F2 + Protobuf)** | Internal microservice communication, low latency, strict contracts, streaming | Public browser APIs (needs gRPC-web) |\n| **WebSocket** | Real-time bidirectional (chat, live dashboards, multiplayer games) | One-way server push (use SSE instead) |\n| **SSE (Server-Sent Events)** | Server → client push (notifications, live feeds) | Bidirectional communication |\n| **GraphQL Subscriptions** | Real-time with GraphQL schema consistency | Simple push scenarios |\n\n**Default recommendation:**\n- External \u002F public: **REST**\n- Internal service-to-service: **gRPC**\n- Real-time features: **WebSocket** or **SSE**\n\n---\n\n## 5. Search Engine\n\n| Technology | Best For | Avoid When |\n|------------|----------|------------|\n| **Elasticsearch** | Full-text search, log analytics (ELK), complex aggregations | Simple lookups; operational overhead is high |\n| **OpenSearch** | AWS-native Elasticsearch alternative | Non-AWS preferred setups |\n| **Typesense** | Simple, fast full-text search, typo tolerance, easy ops | Complex aggregations at massive scale |\n| **Algolia** | Managed search-as-a-service, fast setup, great UI | High volume (expensive); self-hosted preference |\n| **Meilisearch** | Self-hosted, developer-friendly, fast relevancy | Enterprise-scale analytics |\n| **PostgreSQL FTS** | Basic full-text search, already using PostgreSQL | High relevancy requirements or large datasets |\n\n**Rule of thumb:** Use PostgreSQL FTS under 1M documents. Move to Typesense or Elasticsearch above that.\n\n---\n\n## 6. Object Storage\n\n| Service | Best For | Egress Cost |\n|---------|----------|------------|\n| **AWS S3** | AWS-native apps, de facto standard, massive ecosystem | $0.09\u002FGB (expensive) |\n| **Cloudflare R2** | S3-compatible, **zero egress cost**, global | $0.00 egress |\n| **GCS** | GCP-native | $0.12\u002FGB |\n| **Azure Blob** | Azure-native | $0.087\u002FGB |\n| **Backblaze B2** | Cost-sensitive, S3-compatible | Free with Cloudflare |\n| **MinIO** | Self-hosted S3-compatible | Self-managed |\n\n**Cost optimization tip:** Use **Cloudflare R2** for user-facing media delivery (zero egress). Use **S3** for internal\u002FAWS-integrated storage.\n\n---\n\n## 7. Container Orchestration\n\n| Technology | Best For | Avoid When |\n|------------|----------|------------|\n| **Kubernetes (K8s)** | Large teams, complex deployments, multi-cloud, full control | Small teams (ops overhead is very high) |\n| **AWS ECS + Fargate** | AWS-native, serverless containers, simpler than K8s | Multi-cloud or K8s ecosystem tools needed |\n| **AWS EKS** | Managed K8s on AWS, best of both | Small teams; Fargate may be enough |\n| **GKE (Google)** | Best managed K8s, GCP-native, Autopilot mode | Non-GCP environments |\n| **Docker Compose** | Local dev, small single-server deployments | Production at any meaningful scale |\n| **Nomad** | HashiCorp ecosystem, simpler than K8s, multi-workload | K8s ecosystem tools required |\n\n**Startup default:** ECS + Fargate (zero cluster management).\n**Scale default:** EKS or GKE once team > 5 engineers or services > 10.\n\n---\n\n## 8. Load Balancer\n\n| Technology | Layer | Best For |\n|------------|-------|----------|\n| **AWS ALB** | L7 (HTTP\u002FHTTPS) | AWS apps, path-based routing, WebSocket, HTTP\u002F2 |\n| **AWS NLB** | L4 (TCP\u002FUDP) | Ultra-low latency, static IP, non-HTTP protocols |\n| **GCP GLB** | L7 global | GCP apps, global anycast, single IP worldwide |\n| **Nginx** | L4\u002FL7 | Self-hosted, reverse proxy, flexible config |\n| **HAProxy** | L4\u002FL7 | High performance self-hosted, advanced routing |\n| **Cloudflare** | L7 global + DDoS | DDoS protection + CDN + load balancing combined |\n| **Traefik** | L7 | Kubernetes-native, automatic SSL, service discovery |\n\n---\n\n## 9. Observability Stack\n\n### Metrics\n| Tool | Best For |\n|------|----------|\n| **Prometheus + Grafana** | Self-hosted, open-source, Kubernetes-native |\n| **Datadog** | Managed, APM + infra + logs unified, expensive |\n| **CloudWatch** | AWS-native, zero setup, integrated with AWS services |\n| **New Relic** | APM-focused, good for application-level insights |\n\n### Logging\n| Tool | Best For |\n|------|----------|\n| **ELK Stack** (Elasticsearch + Logstash + Kibana) | Self-hosted, powerful, high volume |\n| **Loki + Grafana** | Lightweight, Kubernetes-native, cheap |\n| **Splunk** | Enterprise, compliance, expensive |\n| **AWS CloudWatch Logs** | AWS-native, zero setup |\n| **Datadog Logs** | Unified with metrics, expensive |\n\n### Distributed Tracing\n| Tool | Best For |\n|------|----------|\n| **Jaeger** | Open-source, Kubernetes-native, OpenTelemetry |\n| **Zipkin** | Simple, lightweight, good integrations |\n| **AWS X-Ray** | AWS-native, integrates with Lambda, ECS |\n| **Datadog APM** | Managed, unified with metrics and logs |\n| **Honeycomb** | High-cardinality event-based observability |\n\n**Recommended open-source stack:** Prometheus + Grafana + Loki + Jaeger (all integrate via OpenTelemetry)\n**Recommended managed stack:** Datadog (expensive but unified) or Grafana Cloud\n\n---\n\n## 10. CDN\n\n| Technology | Best For | Edge Locations |\n|------------|----------|----------------|\n| **Cloudflare** | DDoS protection + CDN + DNS, best free tier, edge workers | 300+ |\n| **AWS CloudFront** | AWS-native, deep S3 and API GW integration | 450+ |\n| **Akamai** | Enterprise, highest performance, expensive | 4000+ |\n| **Fastly** | Real-time purging, streaming, VCL customization | 90+ |\n| **Vercel Edge \u002F Netlify** | Jamstack, frontend-first, zero config | 100+ |\n\n**Default recommendation:** Cloudflare for most use cases (best value, DDoS included, free SSL, Workers for edge compute).\n\n---\n\n## Scale Benchmarks Quick Reference\n\n| Technology | Write Throughput | Read Throughput | Notes |\n|------------|-----------------|----------------|-------|\n| PostgreSQL (single) | ~10K writes\u002Fs | ~50K reads\u002Fs | With connection pooling |\n| PostgreSQL (replicas) | ~10K writes\u002Fs | ~200K reads\u002Fs | 4 replicas |\n| MySQL (single) | ~15K writes\u002Fs | ~60K reads\u002Fs | |\n| Cassandra | ~1M writes\u002Fs | ~500K reads\u002Fs | 10-node cluster |\n| Redis | ~1M ops\u002Fs | ~1M ops\u002Fs | Single node in-memory |\n| Kafka | ~1M msgs\u002Fs | ~1M msgs\u002Fs | Per partition |\n| Elasticsearch | ~50K docs\u002Fs | ~10K queries\u002Fs | Per node |\n| MongoDB | ~50K writes\u002Fs | ~100K reads\u002Fs | Per replica set |\n\n*All benchmarks are approximate and depend heavily on hardware, payload size, and query complexity.*\n\n\n## Limitations\n- This is a reference document and may not cover all edge cases. Always verify architectures before production.\n",{"name":5,"risk":24,"source":25,"date_added":26,"reports-to":27,"description":7},"safe","community","2026-09-04","monopoly","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","06-前端与设计\u002Fmonopoly\u002Ftech-matrix",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill tech-matrix",{"tool":42,"command":43},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill tech-matrix",{"tool":45,"command":46},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill tech-matrix","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fmonopoly\u002Ftech-matrix\u002FSKILL.md",true,[],[51,58,63,70,77,84],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":59,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]