Projects

Things I have built

A short list rather than a long one. These are the projects I can talk about in detail, including the parts that did not go to plan.

BusyBay

In development

Multi-tenant SaaS · sole architect and developer

BusyBay is a booking platform for Australian automotive workshops. A workshop signs up, sets its service bays and opening hours, and takes customer bookings through its own branded page. Every workshop is a separate tenant with isolated data on shared infrastructure.

What I did

  • Designed the multi-tenant data model and the tenant isolation strategy.
  • Built the API in .NET 8 with JWT authentication and request validation.
  • Built the front end in Next.js, including tenant onboarding and the booking interface.
  • Set up the Azure infrastructure and brought the running cost back under control after the database tier turned out to be far more expensive than it needed to be.

What I learned

Serverless pricing punishes an idle database that is not actually idle. The fix was straightforward once I measured it, but I would not have found it by reading the documentation. Multi-tenancy is also a decision you make once: retrofitting isolation into a design that assumed a single customer is far harder than starting with it.

  • .NET 8
  • Next.js
  • PostgreSQL
  • JWT
  • Azure
  • Multi-tenant

Enterprise integration work

Azure Integration Services · commercial engagements

Much of my commercial work has been message-based integration between line-of-business systems. The shape is usually the same: two or more systems that need to share data, no shared schema, no tolerance for lost messages, and a business process that cannot stop while you rebuild it.

  • Logic Apps for orchestration and the long-running steps.
  • API Management as the front door, handling authentication, throttling and versioning.
  • Service Bus for durable queueing, so a downstream outage delays work instead of losing it.
  • Event Grid for the fan-out cases where several systems react to the same event.

Optional: name a specific client project here, with the problem, what you built and the measurable result. One concrete story is worth more than a list of services.

  • Logic Apps
  • API Management
  • Service Bus
  • Event Grid
  • .NET

This website

Static site · no framework

Hand-written HTML and CSS, no build step and no dependencies. It loads in one round trip, works without JavaScript, and follows your device’s light or dark setting unless you tell it otherwise. The resume page is styled to print cleanly as well.

  • HTML
  • CSS
  • No framework

Open source

I am starting to contribute to open source projects and write up what I learn. Links will appear here as the contributions land.

Replace this with your first merged pull request: project, what you changed, and a link.

Want the detail?

Happy to walk through any of these properly, including the architecture decisions and the ones I would make differently now.