I’ve been working on a deeper analysis and consolidation of XCore, and one thing is becoming increasingly clear:
XCore is no longer just a plugin layer for FastAPI.
The vision is much bigger.
🧩 XCore turns application capabilities into autonomous, manageable plugins, with:
• Plugin-first architecture
• Lifecycle management
• Dependency Injection & Service Container
• Event Bus
• Trusted & Sandboxed Plugins
• AST Security Scanner
• Tenant-aware resource isolation
• Hot Reload
• Ephemeral Execution & Warm Pool
• OpenTelemetry with tracing propagated through sandbox IPC
• Prometheus Metrics
• Schema Registry & Contract Validation
• Redis / Tiered Cache
• CLI for administration and diagnostics
The idea is simple:
Build modular applications without turning every feature into a microservice.
Today, XCore V1 and V2 provide a solid runtime foundation.
The next step is much more ambitious: distribution.
🌐 XCore V3 is focused on:
→ Cluster IPC
→ Inter-node Routing
→ Distributed Event Bus
→ Federation
→ Circuit Breakers
→ Failover
→ Distributed Resilience
The goal is to allow multiple XCore instances to operate as one distributed runtime.
And this is where things get really interesting.
Moving from:
Application → Plugins
to:
Platform → Runtime → Plugins → Distributed Infrastructure
I see XCore as an attempt to build a third path between:
Modular Monoliths ↔ Microservices
A runtime designed to handle modularity, isolation, observability, and eventually distributed execution — without immediately paying the operational cost of a full microservices architecture.
The journey continues. ⚡
🔗 https://github.com/traoreera/xcore
Top comments (0)