Application architecture
Business-critical systems where operational data is created: workflows, permissions, transactional models, APIs and interfaces built around how people actually work.
Edmonton, Canada · Microsoft Fabric · Azure · Data & AI
Business applications. Data platforms. AI-enabled workflows.
I design and build solutions across the systems that create operational data, the Microsoft Fabric platform that turns it into trusted information, and the AI capabilities that bring that intelligence back into day-to-day work.
My current specialization is Microsoft Fabric and Data & AI solution architecture, backed by hands-on application experience with Python/Django, React, PostgreSQL, Power BI and Azure.
20+ yearsacross software, business systems and data
1,000+practitioners trained across 12 countries
End-to-endrequirements → architecture → build → handover
What I work on
Three connected parts of the same business system.
My work is broad by design, but the centre of gravity is clear: solution architecture around Microsoft Fabric, data, operational applications and practical AI.
Microsoft Fabric data platforms
Ingestion, lakehouse architecture, transformation, dimensional modelling, semantic models and Power BI — with governance and operational handover considered from the start.
AI-enabled workflows
AI added where it improves an existing process rather than as a separate demo. The patterns I design to: assisted casework, document intelligence on intake, PII redaction before anything reaches a model, and human review before any output counts.
Selected work
Three systems, three layers of the same stack.
The application, the data platform beneath it, and the AI layer on top — described by architecture and by what I designed and built.
Financial workflow application
Designed and built a custom business application for requisitions, approvals, budget workflows and financial operations using Python/Django, React, PostgreSQL and Azure.
One workflow
requisition, approval and budget in a single system of record
Microsoft Fabric data platform
Built ingestion and transformation pipelines using medallion architecture, PySpark and SQL, dimensional modelling, governed semantic models and Power BI reporting.
Bronze → gold
ingestion through to semantic model and reporting
Client-services application
Designing a custom operational application around structured workflows and PostgreSQL-backed data, with AI-assisted workflow concepts handled at the level of pattern rather than implementation.
Apps → AI
AI designed into the workflow, not beside it
Architecture perspective
I work on both sides of the data platform.
01
Operational systems
Custom business apps · SaaS · external sources
02
Microsoft Fabric
Ingest · Bronze/Silver/Gold · model
03
Analytics
Semantic models · Power BI · decisions
04
AI in the workflow
Assist · review · act
How I work
Architecture is useful only when it survives delivery.
The consulting pattern I bring to technical work is simple: understand the problem, make the trade-offs explicit, build close enough to the technology to test the decisions, then leave the system operable by others.
Understand
Start with users, process, constraints, data and outcomes before choosing the technology.
Architect
Design the application, data, integration, analytics and AI decisions as one connected system.
Build
Stay hands-on enough to validate the architecture in code, pipelines, models and deployed systems.
Enable
Documentation, runbooks and training are part of delivery so the system does not depend on its original builder.
Featured writing
Architecture decisions from production work.
Case studies and technical notes on Microsoft Fabric, data architecture and AI — focused on the trade-offs behind systems that have to work beyond the demo.
Fabric
How Azure Automation Cut Microsoft Fabric Cost by 78%
Four schedules, one Fabric capacity, and a simple decision to stop paying for idle compute.
168 → 9.5
Fabric capacity hours per week, before and after
Case study
From PostgreSQL to Conversational Analytics
Designing a governed analytics and AI architecture in Microsoft Fabric, from a read-only ingestion boundary to natural-language questions that reuse the same definitions as Power BI.
One-person data team
Ship one report before you build the platform
When you are the entire data function, the sequence matters more than the architecture.
Career perspective
Twenty years of context behind the architecture.
My route into Data & AI architecture was not a straight line through one toolset. It came through building systems, leading delivery and working with the business problems around the technology.
2000sOracle & web applications
2010sClient delivery & technical leadership
2015–20E-commerce & business systems
2021–24BI consulting & training
NowMicrosoft Fabric · Data & AI architecture
Teaching & knowledge transfer
Technical depth is only useful if you can make it understandable.
I have trained 1,000+ practitioners across 12 countries, mostly non-technical audiences. That experience now shows up in workshops, documentation, handover and stakeholder communication.
Teaching & training →1,000+practitioners trained
12countries
Connect
Based in Edmonton. Working across application, data and AI architecture.
I am always interested in thoughtful conversations about Microsoft Fabric, Data & AI architecture, enterprise solution delivery and the systems behind real business workflows.