Course Outline
Day 1: Foundations of Event-Driven Architecture in Go
- Introduction to EDA
- Defining Event-Driven Architecture
- Contrasting Monolithic, Microservices, and Event-Driven Systems
- Leveraging Go's concurrency model and lightweight goroutines for EDA
- Core Concepts & Benefits
- Achieving decoupling, scalability, and resilience in enterprise contexts
- Defining key roles: Events, Producers, Consumers, and Event Brokers
- Examining real-world case studies where Go drives high-performance event systems
- CAP Theorem & Trade-offs in EDA
- Reviewing Consistency, Availability, and Partition Tolerance
- Analyzing the impact of EDA on these fundamental properties
- Strategies for balancing consistency and availability in Go-based architectures
Day 2: Events, Messages, and Communication Patterns in Go
- Understanding Event Types
- Distinguishing between Domain Events and Integration Events
- Handling Synchronous vs. Asynchronous events in Go applications
- Messaging Patterns in Practice
- Implementing Publish-Subscribe (Pub/Sub) patterns in Go
- Designing and structuring event payloads using JSON, Protocol Buffers, or Avro
- Implementing Event Handling in Go
- Overview of widely used Go libraries and frameworks for messaging
- Code demonstrations: dispatching and processing events via idiomatic Go patterns
- Practical session: Developing a basic event-driven service in Go
Day 3: Messaging Systems & Event Brokers with Go
- Selecting and Integrating Event Brokers
- Overview of leading brokers: Apache Kafka, RabbitMQ, and NATS
- Comparing use cases and best practices for Go-centric systems
- Setting Up Messaging Infrastructure
- Using Docker Compose to provision Kafka, RabbitMQ, or NATS
- Configuration of topics, exchanges, queues, and channels
- Review of Go client libraries
- Hands-On Workshop
- Developing a sample Go microservice capable of producing and consuming events
- Integrating the service with the selected event broker
- Debugging and validating event flows
Day 4: Deploying, Monitoring, and Advanced Topics in Go EDA
- Deploying Go Event-Driven Applications on Kubernetes
- Containerizing Go applications for production environments
- Deploying Kafka (or alternative brokers) onto Kubernetes clusters
- Introduction to KEDA (Kubernetes Event-Driven Autoscaling) for managing event consumer scale
- Error Handling and Monitoring
- Strategies for managing event failures
- Implementing observability features within Go services
- Advanced Topics & Q&A
- Exploring Serverless Event-Driven Architectures using Go
- Event Choreography vs. Orchestration: Analyzing use cases and design implications
- Reviewing common pitfalls, lessons learned, and industry best practices
- Open Q&A session and interactive troubleshooting
Requirements
- Competency in Go (Golang), specifically with goroutines and channels
- Foundational knowledge of software architecture models, including monoliths and microservices
- Working familiarity with Docker and Docker Compose
- Basic comprehension of REST APIs and networking principles
- Practical experience with command-line utilities and Git
- Recommended: prior interaction with Kubernetes and messaging systems such as Kafka, RabbitMQ, or NATS
Target Audience
- Go developers focused on building scalable, event-driven applications
- Software engineers shifting from monolithic or REST-based architectures to asynchronous systems
- DevOps and cloud engineers engaged with containerized or distributed microservices
- Technical architects and system designers investigating EDA patterns using Go
Testimonials (7)
we write some code in GO and we learn some stuff regarding EDA like events, when and how.
Alin
Course - Event Driven Architecture Custom
It was an interactive course, no time to sleep :)). Also was nice to work in teams and then to debate according to each result.
Alina
Course - Event Driven Architecture Custom
I enjoyed most the discussions and the examples provided so we could reach by ourselves to the conclusions he wanted to share with us. I liked the pace, the english, the patience, that even if we did not came with the best answer he would not say it is wrong, but came with examples of what could be better.
Simona
Course - Event Driven Architecture Custom
The open discussions and going from understanding the problems/reasons (the `why`) to `EDA`.
Constantin
Course - Event Driven Architecture Custom
the approach of presenting things heavily based on interaction and examples
Virgil
Course - Event Driven Architecture Custom
The interactive nature of the course The self-discovery learning approach where you found answers yourselves The practical focus with real-life examples that made concepts more relatable
Roxana Sandu
Course - Event Driven Architecture Custom
Very interactive. The trainer was very knowledgeable and patient.