Sam Newman
where else to find them
what they talk about
all 10 in the filters
where they keep going back
- NDC London7 editions2018–2025
- NDC Oslo5 editions2017–2023
- Craft Conference3 editions2021–2025
all 22 in the filters
on a stage with
- Adrian Mouatonce
- Chris Fordonce
- Fred Georgeonce
all 12 in the filters
who talks about the same things
- Eric Johnson25 talks
- Martin Thompson20 talks
- Hugh McKee26 talks
- David Schmitz9 talks
- Dylan Beattie81 talks
- Chris Riley15 talks
| title | conference | date |
|---|---|---|
| Keynote: You Keep Using That Word | MQ Summit 2025 | 2025-11-06 |
Claim: “asynchronous” is too vague for engineering decisions. Definitions collapse into three concrete concerns: non-blocking (futures and async/await)… | ||
| Models For Resilience | Apidays India 2025 | 2025-10-08 |
Explains resilience as measurable system performance and maps three practical models: Woods’s four capabilities (robustness, rebound, graceful extensibility… | ||
| The Flawed Logic of Universal API Governance in Large Enterprises | Apidays India 2025 | 2025-10-08 |
Argues that a one-size-fits-all API policy fails because different APIs have different cost of change and use cases, so governance must be tiered rather than… | ||
| [ Keynote preview ] Resiliency in Distributed Systems: Beyond Just Two Copies Behind a Load Balancer | Apidays India 2025 | 2025-10-08 |
Keynote preview argues that resilient distributed systems require more than two identical service instances behind a load balancer; it grounds that claim in… | ||
| Cloud, Containers & Security | GOTO Copenhagen 2025 | 2025-09-29 |
Argues container signing is now practical with cosign with GitHub OIDC, recommends removing long‑lived tokens, and flags SBOMs as often incomplete; claims a… | ||
| SW Design, Architecture & Clarity at Scale | GOTO Copenhagen 2025 | 2025-09-29 |
Panel argues that lightweight Decision Records (short or long templates, draft status for collaboration) plus automation and placement where teams already work… | ||
| Definition Of Insanity | Craft Conference 2025 | 2025-05-29 |
Argues retries are often correct for ephemeral failures but only if made safe: use timeouts, limits, jitter/backoff and idempotency. Cites a real outage where… | ||
| The Definition Of Insanity | NDC London 2025 | 2025-01-27 |
Argues that timeouts, retries, idempotency are the real levers for resilient distributed systems and gives concrete fixes: tune histograms-first timeouts… | ||
| Is Fun Fundamental? | CPH DevFest 2024 | 2024-08-26 |
Argues that paying more can reduce performance on cognitive tasks (MIT studies and Indian replication show higher rewards hurt anything but mechanical work)… | ||
| You Keep Using That Word | GOTO Amsterdam 2024 | 2024-06-10 |
Argument: the word asynchronous is too vague and causes real mistakes. Evidence: people mean different things — non-blocking (futures, reactive extensions… | ||
| You Keep Using That Word: Asynchronous And Interprocess Comms | NDC London 2024 | 2024-01-29 |
Argues that “asynchronous” is too vague and should be replaced by concrete terms and patterns, claiming no consistent definition exists. Distinguishes… | ||
| You Keep Using That Word | Software Architecture fwdays'23 | 2023-09-19 |
Explains why the word “asynchronous” is useless without context and gives precise distinctions: non-blocking vs blocking (futures, await and parallel calls)… | ||
| You Keep Using That Word: Asynchronous And Interprocess Comms (Remote) | Copenhagen Developers Festival 2023 | 2023-08-28 |
Argues that "asynchronous" is ambiguous and unusable, replacing it with concrete choices: request–response vs event-driven interactions, client-side… | ||
| You Keep Using That Word: Asynchronous And Interprocess Comms | NDC Oslo 2023 | 2023-05-22 |
Argues that “asynchronous” is ambiguous and instead distinguishes request–response vs event-driven interactions, shows request–response can be implemented with… | ||
| You Keep Using That Word | Craft Conference 2023 | 2023-05-18 |
Argues that “asynchronous” is overloaded and unusable without context, contrasting request–response vs event‑driven semantics, showing request–response can be… | ||
| You Keep Using That Word: Asynchronous And Interprocess Comms | NDC London 2023 | 2023-01-23 |
Claim: the word "asynchronous" is meaningless without context because people use it to mean different things — non-blocking/await code using futures or… | ||
| Hiding The Lead | Build Stuff 2021 | 2021-11-17 |
Argues that independent deployability depends on strict information hiding and shows concrete failure modes: shared databases create common coupling and… | ||
| Hiding The Lead | Craft Conference 2021 | 2021-06-02 |
Argues that information hiding is the essential practice to achieve independent deployability, advocating minimal APIs, explicit schemas and CI checks (JSON… | ||
| Hiding The Lead | NDC London 2021 | 2021-01-25 |
Argues that independent deployability hinges on maintaining backwards compatibility and practicing strict information hiding: keep internal data and… | ||
| Hiding The Lead: Coupling, Cohesion, and Microservices-Style | Build Stuff 2020 | 2020-11-11 |
Argues that microservices only deliver independent deployability if interfaces are stable and internal details are hidden, citing David Parnas (1971) and… | ||
| Where We’re Going, We Don’t Need Servers! | GOTOpia Europe 2020 | 2020-09-15 |
Public cloud doesn’t mean universal adoption — about 70% of IT spend remains on premise, so choices matter. Serverless is broader than functions: S3 and SQS… | ||
| Hiding The Lead | NDC Oslo 2020 | 2020-06-08 |
Argues that microservice success depends on independent deployability and that old structured‑programming ideas — information hiding, cohesion and several… | ||
| It's A Trap! | NDC DevOps 2020 | 2020-03-11 |
Argues that private clouds mostly underdeliver: IDC shows 70% of infrastructure spend stays on‑premise, DORA finds high performers are 24x more likely to use… | ||
| Microservices and Serverless | NDC DevOps 2020 | 2020-03-11 |
Argues that serverless raises developer productivity but has real limits: AWS Lambda and similar platforms use containers under the hood, enforce short… | ||
| Q&A - Monolith to Microservices | GOTO Oslo 2020 | 2020-03-03 |
Advocates require a clear, pressing problem before splitting a monolith, not fashion; many teams start with one to three services and scale the dial up, while… | ||
| Rip It Up And Start Again? | NDC London 2020 | 2020-01-27 |
Argues that microservices only deliver if organization and ownership change: a ticketing case shows 60 services → one story touches 6 services creating a… | ||
| Monolith Decomposition Patterns | NDC Oslo 2019 | 2019-06-17 |
Practical patterns to break a monolith into services: put a proxy (nginx or similar) in front to strangler fig route endpoints and measure added latency… | ||
| What Is This Cloud Native Thing Anyway? | NDC Copenhagen 2019 | 2019-03-27 |
Frames cloud native as a set of practical abstractions rather than a buzzword: container packaged workloads (Docker-style images, with Lambda running… | ||
| Insecure Transit - Microservice Security | NDC Porto 2019 | 2019-02-26 |
Organizations still fail basic hygiene: 81% of breaches link to weak or stolen passwords and ~44% follow known unpatched vulnerabilities (Equifax exploited an… | ||
| Insecure Transit - Microservice Security | NDC London 2019 | 2019-01-30 |
Microservice security focuses on concrete fixes: use Vault or cloud KMS plus consul template to rotate time-limited credentials and avoid checked‑in API keys… | ||
| Insecure Transit - Microservice | GOTO Berlin 2018 | 2018-10-31 |
Argues that microservices can improve security if teams patch regularly and handle secrets properly, citing the Equifax breach (143 million records) and the… | ||
| Insecure Transit - Microservice Security | NDC Oslo 2018 | 2018-06-11 |
Microservice security prioritizes practical fixes: Verizon data shows ~80% of breaches trace to weak passwords, so mandate password managers and check "have I… | ||
| What is this cloud native thing anyway? | NDC London 2018 | 2018-01-15 |
Fast, specific definition: cloud native means applications that are container-packaged, dynamically managed and designed for platform-driven scaling and… | ||
| Microservices: An unexpected Journey | JavaDay Ukraine 2017 | 2017-11-04 |
Defines microservices as independently deployable services modeled around the business domain and argues independent deployability is the key goal. Traces… | ||
| AppSec and Microservices | JavaDay Ukraine 2017 | 2017-11-04 |
Microservice architectures trade a single perimeter for many networked boundaries, so adopt HTTPS everywhere (use Let's Encrypt ACME automation) and consider… | ||
| Confusion In The Land Of The Serverless | JavaDay Ukraine 2017 | 2017-11-04 |
Argues serverless means developers stop managing servers, not that servers vanish, and shows concrete tradeoffs: AWS Lambda (functions) and DynamoDB (BaaS)… | ||
| Security And Microservices | NDC Sydney 2017 | 2017-08-14 |
Microservices increase attack surface but also enable tighter per-service controls; key claims: HTTPS everywhere via Let's Encrypt (ACME) and client-side… | ||
| Confusion In The Land Of The Serverless | NDC Sydney 2017 | 2017-08-14 |
Defines serverless as a platform-level abstraction (not zero servers), contrasts functions-as-a-service like AWS Lambda (60s limits, JVM pre-warming) with… | ||
| Confusion In The Land Of The Serverless | NDC Oslo 2017 | 2017-06-14 |
Argues serverless is essentially a higher‑level platform as a service with five practical criteria (no host management, autoscale, precise billing, non‑host… | ||
| Feature Branches And Toggles In A Post-GitHub World | NDC Oslo 2017 | 2017-06-14 |
Long-lived feature branches cause large merge pain: an 18‑month rollout with ~60 developers created r3→r4 merges that take days to compile and introduce… | ||
| AppSec & Microservices | GOTO Copenhagen 2016 | 2016-10-03 |
Live Internet attacks run constantly and indiscriminately; treat prevention, detection, response and recovery as distinct responsibilities. Use HTTPS… | ||
| Deploying and Scaling Microservices | NDC Sydney 2016 | 2016-08-01 |
Argues services must be independently deployable and use one artifact for all environments, showing concrete artifact options: tarballs (fragile), OS packages… | ||
| Deploying And Scaling Microservices | GOTO Chicago 2016 | 2016-05-23 |
Argues that independent deployability and one artifact for all environments are the rules, and shows tradeoffs between Docker Swarm, Mesos+Marathon and… | ||
| Microservice Panel | GOTO Chicago 2016 | 2016-05-23 |
Conference panel argues containers and automated ops enable microservices but warn they move complexity into contracts, tracing and ops. Typical sizing… | ||
| From Macro To Micro | GOTO Aarhus 2013 | 2013-09-30 |
Explains how to split a monolith by mapping bounded contexts to services, using package visualization tools like Structure101 and DB tools like schema spy… | ||
| Journeys with Maps, Riemann, http.async.client, Canon fodder | EuroClojure 2012 | 2012-05-17 |
Opinionated migration notes on idioms and state handling with concrete takeaways: avoid heavyweight docstrings and hiding code, keep mutable globals to ns user… | ||
| nothing matches | ||