Summary of "You Keep Using That Word • Sam Newman • GOTO 2023"

Main Ideas and Concepts

Boxes and Arrows in Architecture:
The speaker uses the metaphor of "boxes and arrows" to describe the components of system architecture, where boxes represent services and arrows indicate dependencies between these services. The focus is on understanding the relationships and dependencies in service-based architectures, particularly in microservices.
Communication Between Services:
The talk emphasizes the importance of communication between services and the distinctions between different types of communication: synchronous vs. asynchronous. The speaker argues that the terms "synchronous" and "asynchronous" can often lead to confusion due to varying definitions and interpretations.
Request-Response vs. Event-Driven Communication:
- Request-Response: This is a common interaction style where one service sends a request to another and waits for a response. The speaker prefers the term "request" over "command" to reflect the optional nature of the interaction.
- Event-Driven: In this model, services emit events and other services can react to these events without a direct request-response interaction, allowing for more decoupled communication.
Synchronous vs. Asynchronous Communication:
The speaker highlights the lack of clarity around what "asynchronous" means in practice, suggesting that it often leads to miscommunication. Asynchronous communication can be defined as interactions where the sender does not wait for the receiver to complete its work before continuing its own processes.
Temporal Coupling and Intermediaries:
The discussion includes the concept of temporal coupling, where the availability of one service affects the operation of another. Message brokers are introduced as intermediaries that can help manage this coupling, allowing services to communicate without needing to be directly connected at all times.
Clarifying Definitions:
The speaker emphasizes the importance of using clear and specific terminology when discussing architecture and communication patterns. The need for context in understanding terms like "asynchronous" is highlighted, suggesting that relying on shared meanings is crucial for effective communication.

Methodology/Instructions

Clarify Communication Needs: Before adopting terms like "asynchronous," clarify what that means in the context of your application and architecture.
Use Specific Language: Instead of using vague terms, describe the exact nature of interactions:
- Use "non-blocking calls" instead of "asynchronous."
- Specify the use of a particular message broker and explain why.
Assess System Requirements: Consider what the application needs in terms of speed, availability, and how to handle failures.
Encourage Stateless Processing: Design systems to be stateless wherever possible, which simplifies scaling and error handling.

Speakers/Sources Featured

Sam Newman: The primary speaker and author discussing architecture and communication in distributed systems.
Pat Helland: Cited for his insights on eventual consistency and the meaning of terms in computing.
Darren Hobs: Mentioned for his perspective on asynchronous communication.
Steve Smith: Contributed thoughts on TCP connections and non-blocking communication.
Benjamin Johnson: Provided definitions related to synchronous and asynchronous communication.
Grle Gramlee: Shared insights on temporal decoupling and service communication.

This summary encapsulates the main ideas, methodologies, and notable speakers from Sam Newman's talk at GOTO 2023, focusing on the nuances of communication in distributed systems.