Cloud architecture

Use the cloud to solve architectural problems, not create new ones.

Cloud platforms offer an enormous number of architectural choices. The challenge is choosing the right balance of scalability, resilience, security, operational effort, cost and development complexity.

Cloud architecture decisions

Assessment

Review cloud architecture decisions against system needs and operational reality.

AWS architecture

Design AWS solutions, migration approaches and cloud-native service boundaries.

Serverless

Evaluate Lambda, API Gateway and managed services where the workload fits.

Containers

Assess container-based architectures, deployment models and team responsibilities.

Identity & access

Define security, IAM and trust boundaries at the right level of detail.

Resilience

Reason about scaling, failure modes, dependencies and recovery approaches.

Observability

Make systems understandable in production through operational signals.

Technology evaluation

Choose services based on system characteristics instead of trends.

Trade-offs

Choosing between valid options

Architecture decisions rarely have one universally correct answer. Lambda or ECS depends on workload characteristics, execution model, scaling requirements, operational model, deployment needs, team capabilities and other constraints.

My approach is to make trade-offs explicit and choose technology based on the characteristics of the system.

AWS experience

Migration, serverless and architecture assessment

My AWS work has included application migration, serverless architecture, Lambda, API Gateway, CloudFormation, authentication, architecture assessment and modernization.

I also hold training/certification credentials in AWS Well-Architected and Developing on AWS.

Discuss Your Cloud Architecture