Problem
Relms builds a property management platform for the Australian real estate market. It covers leasing, bonds, inspections, maintenance requests, compliance notices, advertising, financials and tenancy documents. As the product and the team grew, the platform still shipped as a single application. Every area shared one release schedule, so a change in one place could hold up releases everywhere else, and handling more load meant scaling the whole platform rather than the one part that needed it.
Existing process
All business areas lived in one large codebase and were deployed together. Notifications had already been rebuilt once, as a separate cloud function service, and needed a better long-term home. The web front end was due for a rebuild, and new engineers lost time getting a working local environment set up.
What we built
We have worked as an extension of the Relms engineering team since March 2023, and the work is ongoing. We split the large application into separate services along its existing business boundaries, starting with accounts and communications, with the property area following. The original application keeps running during the transition, so nothing had to stop while the change happened.
- Notifications were rebuilt on Azure messaging, replacing the earlier function-based service.
- Tenancy agreements and condition reports are generated by their own service, so document work does not compete with everyday platform use.
- A new Blazor web application replaces the old front end, and it shares one generated API client with the internal admin tool.
- A shared local setup and release pipelines give each new service the same pattern, so engineers can get started with a single command.
Architecture / technology
Each service is a .NET 8 application using .NET Aspire for local orchestration and MassTransit for messaging. Services are containerised with Docker and run on Azure Container Apps, with Azure Service Bus carrying messages between them. The front end is a Blazor web application using both server and WebAssembly rendering, calling the backend through typed clients generated with Microsoft Kiota. Data sits in Azure SQL, secrets in Azure Key Vault, and releases go through multi-environment Azure DevOps pipelines with Application Insights monitoring.
Outcome
Relms can now release and scale accounts, communications and property features independently, without redeploying and retesting the whole platform each time. The web app and the admin tool can no longer drift apart, because both use the same generated client. Document generation runs away from the main platform, and new engineers start from one command across a codebase of more than 20 repositories. The migration is continuing one area at a time, with no big-bang cutover.