AWS · HA/DR · Architecture · Platform Design

Cloud Database Architect
NZ & ANZ

Architecture support for teams designing, modernising or stabilising business-critical database platforms across AWS, Oracle and PostgreSQL. The focus is practical: reliable architecture, clear trade-offs, migration readiness and operational runbooks that teams can actually use.

Available immediately for contract & partner subcontracting · Auckland / Remote ANZ

Send the database problem →View case studies →

NZ-based senior specialistAuckland presence, ANZ remote delivery.

Oracle + PostgreSQL depthOCM background with AWS database focus.

Production-first deliveryAssessment, change control, rollback and runbooks.

Partner friendlyContracting, subcontracting and advisory support.

When to call me

Design review

A database architecture decision carries production risk

You need a second pair of senior eyes before committing to topology, migration path, HA/DR, capacity or managed-service assumptions.

Architecture review
Risk and trade-offs
Decision support

Modernisation

Legacy and cloud systems need to meet safely

Oracle, PostgreSQL and AWS choices need to be made together, not in isolated teams.

Oracle/PostgreSQL bridge
AWS database options
Migration roadmap

Operations

The design must survive real incidents

Architecture is not complete until failover, backups, monitoring, runbooks and support ownership are clear.

HA/DR validation
Operational model
Runbook design

Architecture areas I cover

AWS databases

RDS, Aurora and managed database patterns

Aurora PostgreSQL, RDS, DMS, RDS Proxy, backup/restore, monitoring, cost and platform governance.

AWS database design
Cost-aware options
Operational resilience

Enterprise databases

Oracle and PostgreSQL depth

Oracle RAC/Data Guard/GoldenGate/Exadata background plus PostgreSQL/Aurora design and performance considerations.

Source platform depth
Target-state design
Performance implications

Delivery governance

Make the plan buildable

Scope, sequencing, validation, rollout, rollback and stakeholder communication to reduce delivery surprises.

Roadmap
Risk register
Implementation support

Typical deliverables

Architecture outputs

Target-state architecture
Risk-ranked recommendations
HA/DR and backup posture review
Capacity and cost considerations

Delivery support

Migration or modernisation roadmap
Change sequence and rollback view
Validation and monitoring checklist
Stakeholder-ready summary

Handover

Runbook outline
Operational responsibility map
Knowledge transfer
Next-step implementation options

Engagement model

Good fit for architecture review, migration strategy, partner bid support, or short-term contract ownership of database design and delivery planning.

The architecture principle

Design for operation, not diagrams

A database architecture is only useful if teams can monitor it, fail it over, recover it, tune it and explain it during pressure.

Make trade-offs visible

Cost, availability, performance, migration effort and team skill all compete. Good architecture names the trade-offs instead of hiding them.

Connect strategy to delivery

The output should become a buildable roadmap with dependencies, risks, validation checkpoints and decisions that project teams can actually execute.