FractalX Blog is now live

The FractalX Blog is officially live. After spending the past months building and refining the framework itself, we’re ready to start writing about what we’ve learned along the way.

FractalX started as a straightforward question: why does migrating a Spring Boot monolith to microservices require so much hand-written scaffolding? Every team goes through the same motion — writing Dockerfiles, configuring service discovery, wiring Resilience4j, generating gRPC definitions, setting up distributed tracing. None of that is product code. All of it takes weeks.

We built FractalX to automate that entire class of work. You annotate your bounded contexts, run one Maven command, and get a fully-wired distributed system as output. The blog is where we’ll explain the decisions behind it.

---

What you can expect here

We’ll write about three things primarily:

• Technical deep-dives. How the AST analysis pipeline works, how NetScope generates gRPC clients without proto files, how the saga orchestrator gets built from a single annotation, and the design choices behind the 30+ code generators that run on every decomposition.
• Architecture guides. Practical writing on structuring Spring Boot monoliths for decomposition, bounded context identification, database isolation strategies, and operating the generated distributed system in production.
• Project updates. New releases, new features, and changes to the framework as FractalX continues to develop.

---

Start with the first post

If you’re new to FractalX, the best place to start is our first post: The Core Science Behind FractalX. It covers the full picture — how static AST analysis works, what the 30+ code generators produce, how NetScope handles inter-service gRPC communication, and how distributed sagas are generated from a single @DistributedSaga annotation.

FractalX is open source under Apache 2.0. The framework, documentation, and the working e-commerce example are all on GitHub.