Service
Improve existing .NET systems without rewriting everything: incremental migration from .NET Framework, less complexity, and backend performance and reliability problems investigated to their cause.
What I build
Systems that already run the business cannot stop for a rewrite. I led the modernization of five related subsystems from .NET Framework to .NET 7 on a platform of more than ten interconnected subsystems, one subsystem at a time.
.NET Framework to modern .NET, subsystem by subsystem, with shared data and integrations kept stable.
Where complexity comes from, which changes pay off first, and a staged path to get there.
Stored procedures, triggers and spatial queries optimized where the time is actually spent.
Failing background jobs, slow APIs and unreliable integrations investigated before committing to a rewrite.
Experience
Projects where I worked on the same kind of problem.
Contributed to the development and modernization of an enterprise municipal software platform containing more than ten interconnected subsystems.
Read the case study 2017 – 2024Delivered a citizen-facing municipal services portal and Building Violation Commission software, covering online payments, request workflows, property maps, financial calculations, reporting and digital signatures.
Read the case studyFrom my work before founding ArtaPattern. Client names and confidential details are left out, and diagrams are conceptual.
How to start
Every engagement starts small and ends with written outputs. Not 24/7 on-call support or managed operations.
For a new product or major capability, before serious development starts: clear system boundaries and an implementation direction.
Not included Full implementation, UI design and infrastructure provisioning.
Ask about system designFor a team with a running system, often on .NET, that is unsure about its structure or where to take it next: what to improve, what to keep, and where to start.
Not included Executing the full migration or refactoring, which can follow as a separate engagement.
Ask about a reviewFor slow responses, recurring errors or failing background processing, investigated before committing to a major rewrite.
Not included Ongoing production support or 24/7 on-call.
Ask about an assessmentScope, duration and pricing are agreed after a first conversation, once the problem is clear.
FAQ
Usually not. I prefer migrating subsystem by subsystem while the system stays in use, as I did for five related subsystems moving to .NET 7.
With an Architecture Review: issues ranked by impact, options including what to keep, and recommended next steps with a first slice.
Yes. A Backend Reliability Assessment investigates the problem, tests hypotheses and gives corrective actions in priority order.
Start a conversation
Describe the system and the problem. I'll reply by email with questions or a suggested starting engagement.