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.
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.
More Cloud Architect portfolios
Ready to build your portfolio?
Follow the Cloud Architect roadmap — skills, projects, and timeline to get hired.