1 of 13

25-26J-481 | IT4010 Progress Presentation 2

FractalX

A Framework for Static Decomposition of Modular

Monolithic Spring Boot Applications into Microservices

IT22602282 | Sathnindu Kottage

Service Decomposition

IT22353948 | Gayashaan Krishnamoorthy

Data Consistency

IT22356086 | Dinuvi Asithma

Observability & Monitoring

IT22077110 | Tharushika Kapugedara

Service Communication & API

March 2026

2 of 13

PROBLEM STATEMENT

The Migration Challenge

Microservice migrations take weeks of manual boilerplate wiring

Developers must individually configure discovery, resilience, tracing, and database isolation

High risk of inconsistency across services during migration

No tooling exists for static, annotation-driven decomposition of Spring Boot monoliths

Why It Matters

Weeks

typical migration time per service

100%

manual wiring without tooling

cross-cutting concerns to configure

existing static decomposition tools

3 of 13

SOLUTION OVERVIEW

Add 3 annotations. Run 1 command. Get a fully operational microservice platform.

Annotate

@DecomposableModule

@DistributedSaga

@ServiceBoundary

Decompose

mvn fractalx:decompose

AST analysis + code gen

Deploy

Docker Compose + generated

microservices platform

What FractalX Generates Automatically

Per-module Spring Boot services

API Gateway (port 9999)

Service Registry (port 8761)

Saga Orchestrator (port 8099)

Admin Dashboard (port 9090)

Logger Service (port 9099)

Docker Compose + Dockerfiles

Resilience4j + OpenTelemetry

4 of 13

SYSTEM ARCHITECTURE & INTEGRATION

External Client

API Gateway :9999 | Routing · CORS · Rate Limiting · Circuit Breaker

Order

Service

:8081

IT22602282

Payment

Service

:8082

IT22353948

Inventory

Service

:8083

IT22077110

User

Service

:8084

IT22356086

← NetScope gRPC →

Service Registry

:8761

Saga Orchestrator

:8099

Logger Service

:9099

Admin Dashboard

:9090

All services generated by mvn fractalx:decompose from annotated monolith source

Deployment: docker-compose.yml + start-all.sh auto-generated | Containers: Spring Boot 3.2 · Java 17+

5 of 13

COMPONENT SPECIALIZATIONS

Service Decomposition

IT22602282 — Sathnindu Kottage

▸ Service decomposition engine

▸ Dependency decomposition with NetScope

▸ Operations CLI and Verify Mojo

▸ Deployment configurations

▸ Overall library, documentation and release management

Data Consistency

IT22353948 — Gayashaan Krishnamoorthy

▸ Enforces per-service data ownership

▸ Detects illegal cross-service entity access

▸ Converts relationships to ID-based references

▸ Generates service-isolated DB configurations

▸ Saga-based coordination for cross-service writes

Observability & Monitoring

IT22356086 — Dinuvi Asithma

▸ Auto-generates Logger service per microservice

▸ OpenTelemetry distributed tracing (Jaeger)

▸ End-to-end correlation IDs across services

▸ Centralized log aggregation with trace IDs

▸ Service-level metrics: latency, error rate, throughput

Service Communication & API

IT22077110 — Tharushika Kapugedara

▸ API Gateway Generation with builder pattern port determination

▸ Zero-config service discovery & self-registration

▸ Resilience4j circuit breakers, retries, timeouts

▸ Spring Cloud Gateway with dynamic routing

▸ Admin – Network and Communication management

6 of 13

COMMERCIALIZATION & IMPACT

Target Market

▸ Mid-Size Tech Companies (Sweet Spot)

▸ Enterprise Modernization Programs

Value Proposition

Days → Seconds

Service scaffolding time

Zero config

Cross-cutting concerns auto-wired

100% static

No runtime agent or bytecode manipulation

Open Source

Apache 2.0 — community extensible

Market Sizing

Phase 1

Phase 2

Java is the dominant enterprise language millions of active Spring Boot apps globally.

The global microservices architecture market is projected to reach $10.86 billion by 2027, growing at a CAGR of 19.6%.

FractalX competes in the developer tooling and platform engineering space, not the cloud infra space.

▸ Digital Transformation Consultancies

▸ Startups Hitting Scale (Series B/C)

7 of 13

Multi-Tier Licensing & Open Core Strategy

Objective: Transition from Open Source to a sustainable commercial entity

The Open Core Split

OSS Community Apache 2.0

Core decomposition engine, CLI, basic generators

Commercial Proprietary

Saga orchestrators, Admin dashboards, Observability, Gateways

Release Channels

Edge (Enterprise+)

2-week sprints · 4 weeks early access · roadmap influence

Beta (Pro+)

Monthly releases · 2 weeks early access

GA (Everyone)

Quarterly stable releases

Commercial Tiers

Tier

License

Price

Primary Target

Community

Apache 2.0

Indie Devs & Startups

Pro

Commercial

$199/mo

Small Teams (≤10)

Enterprise

Comm + SLA

$1.5k–5k/mo

Mid-Large Companies

Enterprise+

Custom MSA

Negotiated

Fortune 500 / Regulated

8 of 13

Service Delivery & Support Ecosystem

Objective: Minimize churn through high-availability support and flexible deployment

SLA & Support Tiers

Response Times

48h (Pro) · 2h 24/7 (Enterprise+)

Enforcement

Auto SLA timer tags + PagerDuty escalations

Accountability

Monthly SLA reports · 10% credit per breach

Flexible Delivery Mechanisms

Maven Plugin (Hybrid)

Build-time license validation via Keygen.sh · lowest overhead

FractalX Cloud (SaaS)

Web-based decomposition · metered by runs · quick onboarding

On-Prem (Air-Gapped)

Dockerized images with offline keys · Finance & Healthcare

Strategic Go-To-Market

Months 1–3

Seed market with OSS · launch Pro tier via Stripe

Months 4–8

Convert Pro users to Case Studies · launch Enterprise SLA contracts

Year 1

Scale with Solutions Engineers · launch SaaS v2 platform

9 of 13

EVALUATION

Small

E-Commerce · 4 Modules

610 ms

Decomp. Time

456×

Productivity Gain

198

Files Generated

9.25×

Code Amplification

Medium

HR System · 6 Modules

916 ms

Decomp. Time

560×

Productivity Gain

272

Files Generated

7.89×

Code Amplification

Large

University · 9 Modules

1,480 ms

Decomp. Time

712×

Productivity Gain

347

Files Generated

9.60×

Code Amplification

✓

100% dep. detection

across 20 relationships

Non-functional caps

generated per system

Maven command

to decompose

≤9

Annotation lines

for any system size

10 of 13

CONFERENCE AND

COMPETITION

SUBMISSIONS

11 of 13

Enhancements:

CLI Tool for Operations
Maven Verify Mojo option.
Admin dashboard feedback on user experience.

Future Work Suggestions

Extend the same AST-driven algorithm to other backend development �platforms such as Python (FastAPI, Django), Node.js (Express.js), etc.
Implement a RAG-based model to drive development automatically and faster.

Strengths

Minimal token usage in AI-driven modern software development
Complexity abstraction and reduction of human resource requirements
Build-time decomposition provides greater control
Significant time-saving capability

FEEDBACKS

12 of 13

DEMO PLAN — 30 MINUTES

End-to-End Demo Flow

Step 1

Show annotated monolith source — @DecomposableModule, @DistributedSaga

Kottage N.S

5 min

Step 2

Run mvn fractalx:decompose — live code generation

Krishnamoorthy G.

5 min

Step 3

Start services via docker-compose up — all 7 services booting

Asithma K.D.D

5 min

Step 4

API Gateway routing demo — end-to-end request flow

Kapugedara A.K.T.R.

5 min

Step 5

Admin Dashboard — topology, traces, saga monitoring, logs

Kottage N.S

5 min

Step 6

Saga orchestration — trigger distributed transaction & rollback

Krishnamoorthy G.

5 min

Backup: Recorded demo video + pre-loaded test data ready. Screenshots available for all key features.

1 of 13

2 of 13

3 of 13

4 of 13

5 of 13

6 of 13

7 of 13

8 of 13

9 of 13

10 of 13

11 of 13

12 of 13

13 of 13