Capabilities - Hybrid, containers, automation
Cloud and infrastructure architecture
The architecture, the migration path, and the team that can run it after.
What that means in practice
- Hybrid and multicloud architecture with a costed migration path
- Container platforms, orchestration and workload placement
- Infrastructure as code, configuration management and policy as code
- CI/CD and DevSecOps pipeline design
- Virtualization, edge and on-premises estates including air-gapped environments
- Capacity, resilience and disaster recovery design
- Depth
- Enterprise-scale hybrid programs, including regulated estates where the cloud target had to satisfy an auditor as well as an architect.
- Who I bring in
- Platform engineers, SRE teams, ecosystem delivery partners.
- Scoping this
- Ask for a current-state assessment before you ask for a migration plan.
Where I write about this
The newsletter follows what is changing here: one drawing, one decision worth revisiting, one tool used in anger, and what I am seeing across the network. Research worth reading gets cited when it changes a decision.
Adjacent
Rarely just one domain.
Most engagements touch three or four. These are the ones that usually come with it.
- R&D and special projects Feasibility, prototypes, hard problems
- RF, electromagnetics and analog Circuits, antennas, spectrum
- Semiconductor and programmable logic VLSI, ASIC, FPGA
- Embedded systems and device drivers Firmware, kernel, board bring-up
- Hardware manufacturing and supply ODM, DFM, certification
- Industrial automation and controls Robotics, SCADA, OT
- Software engineering Systems, automation, quality
- Security engineering Architecture, identity, testing
- Governance, risk and compliance Audit, frameworks, fractional CISO
- Water, power and energy systems Treatment, generation, infrastructure
- Technical leadership and advisory Robotics, capital projects, family offices