Core service
Design new systems and make clearer architectural decisions: boundaries, data ownership, documented trade-offs and an implementation direction your team can follow.
What I build
Good architecture is not about introducing complexity. It is about making informed decisions that support business needs, maintainability and sustainable evolution, and staying close enough to the code to see them through.
Context and container views, module and service boundaries, main flows and quality attributes.
Options compared, the choice, its trade-offs and what would make you revisit it.
API structure, integrations, shared capabilities and service lifecycle for maintainable growth.
A first slice and an incremental plan, with hands-on engineering support if useful.
Experience
Projects where I worked on the same kind of problem.
Independently architected and delivered a plugin management and licensing platform, connecting backend services, administrative interfaces, and customer-side runtime components.
Read the case study 2017 – 2024Contributed to the development and modernization of an enterprise municipal software platform containing more than ten interconnected subsystems.
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 UI/UX design or infrastructure provisioning.
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.
Engineering notes
Start with the first meaningful scenario, enough architecture to reduce uncertainty, and room to evolve.
Server-Sent Events, separate command and event paths, and lifecycle isolation between workers, backend and browser.
FAQ
System boundaries and main flows, architecture decisions written down with their trade-offs, and an initial implementation direction for your team.
Both. I stay hands-on: I independently architected and delivered a MetaTrader plugin management platform from concept to V1.
Mainly C#/.NET, ASP.NET Core, EF Core, SQL Server and PostgreSQL, with DDD, CQRS, modular and distributed architectures.
Start a conversation
Describe the system and the problem. I'll reply by email with questions or a suggested starting engagement.