<

The Situation

>

The EasyBook platform had grown into a black box. It ran on AngularJS 1.x on the frontend and an outdated .NET backend built with WCF and Telerik OpenAccess ORM.

Critical business logic was also embedded in SQLCLR, while external integrations with Oracle, Axapta, and DIBS added another layer of hidden complexity.

The system was maintained by a single original developer, with no documentation and no shared internal understanding of how the platform actually worked.

Key challenges included:

Loading

6,000+ files in a legacy monolith

Loading

AngularJS 1.x, WCF, and outdated .NET stack

Loading

No documentation and heavy knowledge silo

Loading

Hidden SQLCLR logic and Oracle, Axapta, DIBS integrations

The platform was difficult to maintain, difficult to understand, and difficult to evolve.

<

The Solution

>

Instead of assigning a team of developers to manually read through thousands of files, we deployed Kodebaze to scanned the codebase, identified architecture patterns, mapped service boundaries, and turned fragmented technical detail into usable documentation.

The system scanned the full EasyBook codebase and mapped:

Loading

Domain boundaries

Loading

Business logic

Loading

API endpoints

Loading

System architecture

From that analysis, Kodebaze created a structured recovery package for the platform.

case-1.png

Documenter Agent

Scanned all 6,000+ files, identified domain boundaries, business logic, API endpoints, and architecture signals, then tagged them into a searchable knowledge graph.

case-2.png

Documenter Compiler

Aggregated fragmented technical findings into a cohesive architectural narrative, bridging raw code analysis with real system intent.

Human validation acted as the final quality layer, verifying interlinks, resolving ambiguities, and ensuring the AI-generated output matched operational reality.

<

The Transformation

>

The key shift was how the work got done.

Instead of spending months manually untangling legacy code, Kodebaze turned the recovery effort into a structured workflow: analyze the platform, map the architecture, document the APIs, audit technical debt, and define the modernization path.

Loading

Analyze the platform

Scan the full EasyBook codebase, classify technical assets, and identify architecture, domains, APIs, and embedded business logic.

Loading

Map the architecture

Create a complete view of the layered system, from WinForms and Angular presentation layers to the SQLCLR processing core.

Loading

Document the APIs

Map WCF and REST endpoints, including request and response structures, service boundaries, and authentication flows.

Loading

Audit technical debt

Identify tightly coupled modules, ‘God functions,’ unused code, and performance issues such as inefficient OQL queries.

Loading

Build the roadmap

Define a practical path from AngularJS v1 and deprecated WCF services toward modern frontend architecture, REST/gRPC services, and domain-based microservices.

In less than one week, Kodebaze turned a black-box legacy system into a documented, actionable recovery path.

What normally takes a human team 3 to 6 months was compressed into 5 business days.

<

The Result

>

Sol Og Strand ended up with more than documentation. For the first time, the team had a functional overview of how EasyBook actually worked across architecture, APIs, business logic, and dependencies.

Instead of operating inside a black box, they now had a realistic foundation for modernization, a clearer understanding of technical debt, and a practical roadmap toward a microservice-based future.

Loading

Complete architecture overview

Loading

Full API documentation

Loading

Technical debt and performance audit

Loading

Clear path to a microservice-based architecture

Most importantly, the project gave Sol Og Strand its first real functional overview of EasyBook, replacing uncertainty with structure and creating a safer path to modernization.

<

Why This Matters

>

Legacy systems don't only create technical debt. They create uncertainty.

When critical knowledge lives inside one developer’s head, business change slows down, risk increases, and modernization becomes guesswork.

Kodebaze changes that.

By analyzing existing systems and converting hidden code into usable technical understanding, companies can move from legacy uncertainty to a documented, modern architecture without starting blind.

For Sol Og Strand, that meant replacing a black box with clarity, speed, and a realistic path forward.

Ready to understand your legacy system?

We help teams uncover hidden architecture, document complex systems, and build a practical path to modernization.

Loading
Loading

Claus Villumsen

Chief "What If AI Could Do This?" Officer

Loading

AI + Human software Solution

Follow us
Loading

© 2026 Kodebaze. All Rights Reserved.