Hybrid and multi-cloud architecture across AWS and Microsoft Azure: migration strategy, workload placement, tenancy and landing zone design, and the segmentation tying cloud workloads back to the enterprise estate.
Hosting models were evaluated against recovery objectives and the cost of meeting them rather than against a platform preference.
Subtopics
- Cloud MigrationA $42M move off mainframe onto Oracle ERP in AWS, with isolated environments and controlled promotion between them.
Applied in
- Career Reference Record — Design, Build and Publishing PlatformA cross-linked reference work built as a derived graph: edges declared once, every index, backlink and chart generated from them, published static with per-document access control.
- Client Architecture Portfolio88 numbered engagements across two years, twenty-plus live at any moment, across healthcare, manufacturing, financial services and the public sector — the inverse of nineteen years inside one estate, and a different problem.
- Commercial Site Rebuild and Live Domain MigrationTwenty pages moved off a hosted page builder onto a static build, and a live domain repointed to a new host without touching any of the six records carrying its mail.
- ISP Cutover, Public IP Renumbering and WAN ModernizationAn estate moved to a new provider and a new public address space, then modernized for remote and hosted working without dropping the applications the business ran on.
- Oracle ERP Program — RFP to Cloud Go-LiveTwelve years from the 2011 request for proposal to a 2020 cloud go-live — the cost model that had to exist first, and a cutover instrumented so neither side could blame the other.
- Solid Waste Systems ModernizationLegacy route, fleet and scalehouse systems replaced and integrated to cloud, sequenced around an operation with no slow season.
Career
See also
Also searched as
- landing zone
- hybrid cloud
- multicloud
- workload placement
- cloud strategy