Estospaces case study

00 Overview

A property platform for India and the UK: my role, the system, the decisions behind it and the evidence.

I am Co-founder and Technical Lead (May 2025 to now). The production environment passed 72 of 72 smoke checks after each of 11 releases (launch-readiness, October 2026). The platform has not launched publicly, and production is offline as of November 2026; the screens on this page are captures from the dev environment with test data.

01 Role

My role

  • I decided

    The architecture: seven Go services on Cloud Run with a database each, a shared Go library, a React web app and a Flutter Android app, with the infrastructure defined in Terraform. Also the written rules (RULES.md) that every change goes through.

  • Teammates built

    The first service scaffolds in February 2026, the first auth pass in core-service, the first Flutter scaffold and the estospaces.co.uk landing site.

  • AI agents typed

    Most of the remaining code, as Claude Code and Codex sessions that I specified and reviewed. Most commits come from the bot account the agents commit as.

  • I led

    A team of 6 to 8: engineering interns, QA, design and marketing. I interviewed 50+ letting agencies to shape the product.

02 Architecture

The system

The web app talks to seven Go services on Cloud Run. Each service owns its PostgreSQL database. Services never query another service's database: they refer to each other's records by ID and call each other over HTTP with service tokens.

estospaces-web

  • SubdomainRouterRole and domain routing
  • Auth/session contextAccess + refresh lifecycle
  • User workspaceSearch, saved homes, Fast Track, docs, messages
  • Manager workspaceDashboard, properties, leads, Fast Track, verification
  • Admin workspaceUsers, verifications, tickets, platform ops
  • Frontend service modulesfetch/axios adapters

The router sends each request to the auth context and to one of the three workspaces. The workspaces call the backend through the frontend service modules; calls to payment-service were hidden at this phase.

Cloud Run backend services

  • core-serviceAuth, users, properties, leads, verification
  • booking-serviceApplications, viewings, contracts, Fast Track
  • search-serviceSearch logs, saved searches, discovery
  • media-serviceUploads, signed URLs, document media
  • messaging-serviceChat, support tickets, conversations
  • notification-serviceNotification records and delivery
  • payment-servicePayments and invoices, hidden in the UI at that phase

All seven services use Cloud SQL PostgreSQL, and media-service also uses the Cloud Storage bucket. Secret Manager supplies the web app and the services, and the services write to Cloud Logging and Monitoring.

Data and platform

  • Cloud SQL PostgreSQL
  • Cloud Storage media bucket
  • Secret Manager
  • Cloud Logging + Monitoring
Redrawn from the component diagram in the July 2026 architecture document. The payment UI was still hidden at that point. Original diagram.

03 Decisions

Decisions and trade-offs

The reasons come from the "Known design decisions" table and the goals of the July 2026 architecture document; the cold-start figure comes from the October 2026 launch-readiness report.

04 Worked example

Worked example: Fast Track

A seeker asks for the nearest agent. core-service ranks eligible managers by area and availability and notifies them. A manager shares a shortlist, the seeker picks a home, and booking-service opens a Fast Track case, created idempotently. The case then moves through six stages: selected, documents, viewing, decision, agreement and handover. The first three screens follow one synthetic request (Chennai, 600094) through the QA pass of 6 to 8 October 2026 on the dev environment; the fourth is an earlier test case from the same pass.

    1. User to app.estospaces.comRequest nearest property agent
    2. app.estospaces.com to core-servicePOST /api/v1/leads/broker-request
    Estospaces home seeker dashboard: the Ask us to help form set to Rent, with Request nearest property agent ticked and Chennai as the preferred location
    The seeker asks for the nearest agent.
    1. core-serviceRank eligible managers by area and availability
    2. core-service to notification-serviceNotify matching managers
    Estospaces home seeker dashboard after the request: nearby property agents being ranked in waves for it
    core-service ranks the eligible managers by area and notifies them in waves.
    1. notification-service to Manager dashboardLive request appears in response tracker
    2. Manager dashboard to core-serviceAccept request and share properties
    3. core-service to app.estospaces.comReturn shared shortlist to user
    Estospaces manager dashboard, live response tracker: a pending request with its countdown beside a responded request that waits for a property shortlist
    The manager's live tracker: the same request, Chennai 600094, is accepted and now waits for a shortlist.
    1. User to app.estospaces.comSelect property from shortlist
    2. app.estospaces.com to core-serviceLink broker request selection
    3. app.estospaces.com to booking-servicePOST /api/v1/fast-track
    4. booking-serviceCreate idempotent Fast Track case
    5. booking-service to app.estospaces.comFast Track case created
    6. app.estospaces.com to UserOpen Fast Track workspace
    7. booking-service to Manager dashboardCase visible in manager Fast Track 24h
    Estospaces Fast Track workspace as the home seeker sees it: a case at Share your documents, step 2 of 6, with two required documents
    A Fast Track workspace as the seeker sees it, here an earlier test case at the documents step.

Steps from the sequence diagram in the architecture document. Original diagram

Status changes use a compare-and-set update, so two concurrent decisions cannot both land. The excerpt below is that guard. A PostgreSQL race test runs a manager's rejection and a sale closure at the same moment and checks that each application is closed exactly once.

	// Compare-and-set on the status read above so two concurrent decisions cannot both land (MB-0496).
	result := s.db.WithContext(ctx).Model(&Application{}).Where("id = ? AND status = ?", app.ID, app.Status).Updates(updates)
	if result.Error != nil {
		return nil, result.Error
	}
	if result.RowsAffected == 0 {
		return nil, ErrApplicationStatusChanged
	}
booking-service, internal/bookings/service.go, lines 1525 to 1532 on main at f707fdd (23 October 2026), verbatim. The race test is TestPostgresDecisionRejectionRacesCompetingSaleClosure in fasttrack_postgres_integration_test.go.
Illustration of the guard, not a test run: two decisions read the same status, the first update lands, and the second finds no row with that status and returns ErrApplicationStatusChanged.

05 Evidence

Claim, mechanism, evidence

See every repository