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 optimal EDA performance
- Core Concepts & Benefits
- Achieving decoupling, scalability, and resilience in enterprise-grade systems
- 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 distributed system 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
- Synchronous versus Asynchronous events within 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 within Go
- Implementing Event Handling in Go
- Overview of leading Go libraries and frameworks for messaging
- Code demonstrations: dispatching and processing events using idiomatic Go patterns
- Practical session: Constructing a basic event-driven service in Go
Day 3: Messaging Systems & Event Brokers with Go
- Selecting and Integrating Event Brokers
- Surveying popular brokers: Apache Kafka, RabbitMQ, and NATS
- Comparing use cases and identifying best practices for Go-based systems
- Setting Up Messaging Infrastructure
- Configuring Kafka, RabbitMQ, or NATS using Docker Compose
- Managing 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) on Kubernetes clusters
- Introduction to KEDA (Kubernetes Event-Driven Autoscaling) for dynamic consumer scaling
- Error Handling and Monitoring
- Addressing event failures through robust strategies
- Implementing observability features within Go services
- Advanced Topics & Q&A
- Investigating Serverless Event-Driven Architectures with Go
- Event Choreography versus Orchestration: Use cases and design implications
- Identifying common pitfalls, lessons learned, and industry best practices
- Open Q&A session and collaborative troubleshooting
Requirements
- Strong command of Go (Golang), with specific experience in utilizing goroutines and channels
- Foundational knowledge of software architectural models, including monolithic and microservices structures
- Working familiarity with Docker and Docker Compose
- Basic understanding of REST APIs and core networking principles
- Practical experience with command-line interfaces and Git version control
- Recommended but not mandatory: prior exposure to Kubernetes and messaging platforms such as Kafka, RabbitMQ, or NATS
Target Audience
- Go developers focused on building scalable, event-driven applications
- Software engineers transitioning from monolithic or synchronous REST-based architectures to asynchronous systems
- DevOps and cloud professionals working with containerized or distributed microservices
- Technical architects and system designers investigating EDA patterns through 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.