Course Outline
Day 1: Foundations of Event-Driven Architecture in Go
- Introduction to EDA
- Defining Event-Driven Architecture
- Comparison of Monolithic, Microservices, and Event-Driven Systems
- The role of Go’s concurrency model and lightweight goroutines in enabling EDA
- Core Concepts & Benefits
- Achieving decoupling, scalability, and resilience in enterprise environments
- Defining Events, Producers, Consumers, and Event Brokers
- Real-world examples and case studies highlighting Go’s role in high-performance event systems
- CAP Theorem & Trade-offs in EDA
- Overview of Consistency, Availability, and Partition Tolerance
- The impact of EDA on these system properties
- Strategies for balancing consistency and availability in Go-based systems
Day 2: Events, Messages, and Communication Patterns in Go
- Understanding Event Types
- Distinguishing between Domain Events and Integration Events
- Managing synchronous versus 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 popular Go libraries and frameworks for messaging
- Code examples demonstrating the dispatching and processing of events using idiomatic Go patterns
- Hands-on session: Constructing 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-based implementations
- Setting Up Messaging Infrastructure
- Configuring Docker Compose for Kafka, RabbitMQ, or NATS
- Defining topics, exchanges, queues, and channels
- Review of Go client libraries
- Hands-On Workshop
- Developing a sample Go microservice that produces and consumes events
- Integrating the service with the selected event broker
- Debugging and testing event flows
Day 4: Deploying, Monitoring, and Advanced Topics in Go EDA
- Deploying Go Event-Driven Applications on Kubernetes
- Containerizing Go applications for production use
- Deploying Kafka (or alternative brokers) on Kubernetes clusters
- Introduction to KEDA (Kubernetes Event-Driven Autoscaling) for scaling event consumers
- Error Handling and Monitoring
- Strategies for handling event failures
- Implementing observability features in Go services
- Advanced Topics & Q&A
- Exploring Serverless Event-Driven Architectures with Go
- Comparing Event Choreography versus Orchestration: Use cases and design considerations
- Common pitfalls, lessons learned, and industry best practices
- Open Q&A session and interactive troubleshooting
Requirements
- Proficiency in Go (Golang), with a solid understanding of goroutines and channels.
- Fundamental knowledge of software architecture models, including monoliths and microservices.
- Familiarity with Docker and Docker Compose.
- Basic understanding of REST APIs and networking principles.
- Experience utilizing command-line tools and Git.
- Optional but recommended: Prior exposure to Kubernetes and messaging systems such as Kafka, RabbitMQ, or NATS.
Target Audience
- Go developers aiming to build scalable, event-driven applications.
- Software engineers shifting from monolithic or REST-based architectures to asynchronous systems.
- DevOps and cloud engineers working with containerized or distributed microservices.
- Technical architects and system designers exploring EDA patterns in 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.