Technology, in context

The stack behind the systems.

Technologies I have worked with across production applications, modernization, integrations, testing, and cloud delivery. Azure is my primary cloud; AWS is deliberately shown as limited production exposure.

C#, .NET, ASP.NET Framework, ASP.NET Core, Blazor, Windows Forms, React, jQuery, Syncfusion; Azure Functions, Service Bus, Event Hubs, App Service, Azure SQL, Cosmos DB, Redis, Key Vault, Azure Monitor, Log Analytics, Azure DevOps and Pipelines; SQL Server, MySQL, PostgreSQL, Entity Framework Core, Dapper, NHibernate, EventStoreDB; RabbitMQ, Docker, REST APIs; xUnit, bUnit, Moq, Fluent Assertions; limited production exposure to AWS KMS and Amazon RDS.

Microsoft Azure service artwork comes from Microsoft’s official Azure Architecture icon set. Recognizable product artwork is used where available; restrained text marks identify libraries without a suitable published product icon.

Architecture & engineering practices

The decisions around the tools matter just as much.

These are applied approaches, separated from product logos because they are engineering practices rather than vendors.

CQRSDomain-driven designMicroservicesEvent-driven systemsAsynchronous workflowsEvent schedulingObservabilityUnit testingIntegration testingCI/CDPR reviewsRefactoringPerformance analysisSprint planningTechnical mentoringStakeholder communication