athola/architecture-paradigm-space-based
plugins/archetypes/skills/architecture-paradigm-space-based/SKILL.md
Applies data-grid architecture for high-traffic stateful workloads. Use when a single database cannot scale and in-memory partitioning is needed.
$ install --global
skillsauthnpx skillsauth add athola/claude-night-market architecture-paradigm-space-basedInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 8, 2026, 3:23 AM110.6s1 file scanned
SKILL.md
- name:
- architecture-paradigm-space-based
- description:
- Applies data-grid architecture for high-traffic stateful workloads. Use when a single database cannot scale and in-memory partitioning is needed.
- alwaysApply:
- false
- category:
- architectural-pattern
- dependencies:
- []
- tools:
- []
- complexity:
- high
- model_hint:
- deep
- estimated_tokens:
- 800
The Space-Based Architecture Paradigm
When To Use
- High-traffic applications needing elastic scalability
- Systems requiring in-memory data grids
When NOT To Use
- Low-traffic applications where distributed caching is overkill
- Systems with strong consistency requirements over availability
When to Employ This Paradigm
- When traffic or state volume overwhelms a single database node.
- When latency requirements demand in-memory data grids located close to processing units.
- When linear scalability is required, achieved by partitioning workloads across many identical, self-sufficient units.
Adoption Steps
- Partition Workloads: Divide traffic and data into processing units, each backed by a replicated data cache.
- Design the Data Grid: Select the appropriate caching technology, replication strategy (synchronous vs. asynchronous), and data eviction policies.
- Coordinate Persistence: Implement a write-through or write-behind strategy to a durable data store, including reconciliation processes.
- Implement Failover Handling: Design a mechanism for leader election or heartbeats to validate recovery from node loss without data loss.
- Validate Scalability: Conduct load and chaos testing to confirm the system's elasticity and self-healing capabilities.
Key Deliverables
- An Architecture Decision Record (ADR) detailing the chosen grid technology, partitioning scheme, and durability strategy.
- Runbooks for scaling processing units and for recovering from "split-brain" scenarios.
- A monitoring suite to track cache hit rates, replication lag, and failover events.
Risks & Mitigations
- Eventual Consistency Issues:
- Mitigation: Formally document data-freshness Service Level Agreements (SLAs) and implement compensation logic for data that is not immediately consistent.
- Operational Complexity:
- Mitigation: The orchestration of a data grid requires mature automation. Invest in production-grade tooling and automation early in the process.
- Cost:
- Mitigation: In-memory grids can be resource-intensive. Implement aggressive monitoring of utilization and auto-scaling policies to manage costs effectively.
Concrete Components
These vocabulary items name the concrete tools and abstractions
that show up when the paradigm is implemented. They are not
required dependencies and they are not part of the skill's
tools: frontmatter (which is reserved for Claude Code tool
restrictions). Use this list to disambiguate during architecture
discussions.
data-grid-platform: Hazelcast, Apache Ignite, or similar; in-memory partitioned data storereplication-manager: moves writes asynchronously to durable storage and across regionsload-tester: drives the grid past its single-region ceiling to validate scale-out
Related Skills
athola/ideate
research
VerifiedTrustedCommunity
Generate diverse solution candidates with category-spanning ideation methods and rotation. Use when stuck on a design or fighting repetitive LLM output.
304SKILL.mdUpdated Jun 8, 2026
athola/plugins/sanctum/skills/validate-pr
tools
VerifiedTrustedCommunity
--- name: validate-pr description: Use when you need a diff-derived test plan for a PR: reads the diff, groups changes by area, runs targeted verifications, and proves revert-tests are genuine guards, not dead assertions. alwaysApply: false category: validation tags: - pr - validation - test-plan - diff - revert-test - evidence tools: [] usage_patterns: - diff-derived-test-plan - revert-test-quality-check - evidence-capture complexity: intermediate model_hint: standard estimated_tokens: 650
304SKILL.mdUpdated Jun 8, 2026
athola/decision-journal
development
VerifiedTrustedCommunity
Contract for the project decision journal (tradeoffs and lessons-learned logs). Use when recording a decision, tradeoff, or lesson, or building a consumer hook.
304SKILL.mdUpdated Jun 8, 2026
athola/graduated-implementation
development
VerifiedTrustedCommunity
Ramps implementation ambition a notch only after the prior increment is understood. Use when building a feature you must understand, not just ship.
304SKILL.mdUpdated Jun 8, 2026