Sam Newman Portfolio
Independent consultant and author of "Building Microservices" and "Monolith to Microservices" (O'Reilly), advising organizations on decomposing systems into cloud-native, independently deployable services.
Location
Somewhere on planet Earth, most likely near a laptop.
Skills
What makes it work
A breakdown of the choices that make this portfolio stand out.
Books as the primary portfolio artifact, backed by consulting
Rather than a project gallery, the portfolio centers on three O'Reilly books that lay out one continuous, evolving argument — from building microservices, to migrating to them, to making distributed systems resilient.
A stated, narrow set of service areas
The site limits its consulting scope to three named things — microservices, cloud, continuous delivery — instead of listing a broad menu of technology services, making it clear what expertise is actually being sold.
Independent-consultant positioning distinct from a single employer
Presenting as an independent consultant rather than tied to one company's specific cloud product lets the architecture advice read as vendor-neutral, which matters for cross-cloud and migration advice specifically.
What Cloud Architects can take from this
Specific, actionable tips to apply to your own portfolio — no generic advice.
If you've written at length on a topic, let published books or long-form writing be the centerpiece of your portfolio instead of a list of short blog posts.
Name a narrow, specific set of services you offer rather than a broad list — three clear specialties are more credible than ten vague ones.
If your advice needs to be vendor-neutral, say so explicitly in how you position yourself — independence is a credential in cross-platform architecture work.
Case studies
Three O'Reilly books making one argument in stages: how to build microservices, how to migrate to them, and how to keep distributed systems running. Sam Newman also publishes the patterns behind them, such as Backends For Frontends, as standalone pages.
Building Microservices, 2nd Edition
A broad book on microservices across the whole delivery process, in three parts: Foundation, Implementation, People. It covers modeling service boundaries with information hiding, coupling and DDD, splitting a monolith, and communication styles. Inter-process communication now takes up three chapters.
Choosing service boundaries is the hardest microservices decision, and this book teaches it through coupling and cohesion, not tooling.
Every page of the 1st edition reviewed; the 2nd edition is longer
Three parts: Foundation, Implementation, People
Free first chapter via O'Reilly
Monolith To Microservices
A book on moving an existing monolith to microservices step by step while the business keeps running. It covers whether to migrate at all, how to prioritize, named migration patterns, and database decomposition, including the loss of referential and transactional integrity.
Most architecture work is migration, not greenfield. The book opens with 'When Might Microservices Be A Bad Idea?', which shows judgment rather than evangelism.
Chapter 2 includes 'When Might Microservices Be A Bad Idea?'
Named patterns: Strangler Fig, UI Composition, Branch by Abstraction
Deep coverage of splitting the database, not just the code
Building Resilient Distributed Systems
A book on making both software and teams more resilient. Part I covers SLOs and error budgets, timeouts, retries and idempotency, thundering herds, rate limiting, and a chapter on AI's effect on resilience. Later parts cover machine and data-center failure and the sociotechnical side.
Timeouts, retries and load shedding are what separate a system that fails gracefully from one that falls over. The book treats them as core design topics.
Chapters on timeouts, retries/idempotency, thundering herds, rate limiting
Dedicated chapter on resilience and AI
Second half focuses on the cultural and team side of resilience
Pattern: Backends For Frontends
A pattern write-up arguing for single-purpose edge services per user interface instead of one general-purpose API gateway. It covers how many BFFs to run, handling multiple downstream calls, reuse, autonomy, perimeter concerns and when to use the pattern.
Where to put API aggregation for web versus mobile clients is a recurring architecture decision. This write-up names the pattern and states when to use it and when not to.
Contrasts BFFs with a general-purpose API gateway
Sections on 'How Many?', reuse and autonomy
Part of a free patterns catalog on his site
More Cloud Architect portfolios
Ready to build your portfolio?
Follow the Cloud Architect roadmap — skills, projects, and timeline to get hired.