Learn EDA sessions

[Amzani]

Why

As discussed with @fmvilas @KhudaDad414 @Souvikns @peter-rr, we would like to start knowledge sharing sessions around EDA (Event-Driven Architecture) topics. The main reasons are :

• EDA protocols LevelUp: Understanding the EDA protocols can be intimidating if we try in solo mode, doing this as a group will help us be more confident and challenge our knowledge
• Integrating with Event Brokers: Event brokers, such as Apache Kafka or RabbitMQ, are commonly used in event-driven systems. Understanding EDA equips AsyncAPI individual contributors with the knowledge and skills needed to integrate AsyncAPI with event brokers, enabling seamless communication and interoperability between different components (e.g some challenges are observed in projects like glee)
• Enhanced Collaboration: Connect with EDA community

What (Proposal)

• Meaning name: Learn EDA
• Duration: 1h
• When : First and last Monday every month at 10h UTC

How

Everyone is welcome to present a topic! You don't need to be a master in the subject matter. The goal is to foster a collaborative learning environment where individual contributors can explore topics they are interested in and share their newfound knowledge with the group. Here's how it works:

1. Choose a Topic: (by commenting in this PR) Select a topic that you find intriguing or want to learn more about (Websocket, Kafka, EDA architecture pattern...)
2. Learn it: (optional if you don't know the topic) Allocate some weeks to dive into the chosen topic. Utilize online resources, books, tutorials, and any other learning materials to gain a solid understanding of the subject. Take notes, experiment with practical examples, and explore different aspects of the topic.
3. Prepare the presentation: After some weeks of learning, prepare a presentation to share your knowledge with the group. Structure your presentation to include an introduction, key concepts, examples, and practical use cases. You can also include challenges or open questions to encourage discussion and engagement (With or without slides! a markdown file is fine as well - get inspiration from @derberg 🔥)
4. Plan it: (by commenting in this PR when you're ready)
5. Present it: during this session, present your topic to the group. Be open to questions, feedback, and discussions from other participants. This is an opportunity for everyone to learn from each other and explore different perspectives on the topic

Remember, the focus is on personal growth, learning, and sharing. You don't need to be an expert to present a topic. Embrace the opportunity to expand your knowledge, develop your presentation skills, and engage with the community. Together, we can create a vibrant learning environment where everyone can learn.

Some initial topics that might be interesting to cover:

• Introduction to Event-Driven Architecture: Basic principles, concepts
• EDA protocols (Websocket / Kafka...)
• Implementing EDA: Exploring messaging platforms like Apache Kafka, RabbitMQ...
• Event-Driven Design Patterns: Common patterns and best practices for designing event-driven systems.
• Event Sourcing and CQRS
• EDA with Microservices: How to design and implement event-driven microservices architecture.
• EDA in Cloud Environments: Applying EDA principles in cloud-native architectures, using services like AWS EventBridge, Azure Event Grid, or Google Cloud Pub/Sub.

Who is interested ?

[Amzani]

From @Souvikns

These are some of the suggestions for topics or things that I would love to learn

• Protocols that Glee supports or plans to support, and how they are implemented in Glee.
  • Kafka
  • AMQP
  • MQTT
  • Websocket
• Different tools from AsyncAPI like
  • Modelina
  • Generator
• Best practices or tips in EDA
• JSON Schema and how are we using it in AsyncAPI Spec.

[rukundob451]

Hey @Amzani, I would like to be a part. This is going to be a wonderful initiative surely.

[smoya]

As a "fun" fact, @boyney123, me, and few others started https://virtual-event-driven.vercel.app/ (previously reachable through virtualeda.io) with a very similar (if not the same) purpose. But we never had talk submissions, unfortunately. I must admit we didn't promote it as it deserved.

I'm really into making this happen.

[Amzani]

@smoya It's never late ;) we can push it again

[smoya]

I'm happy to present my talk "AsyncAPI v3: Unleashing the Power of Asynchronous APIs Design" if people is interested.

[fmvilas]

@smoya I'd love to see a small presentation from you explaining how to create a Kafka cluster on Kubernetes. Honestly, I'd love for these presentations to focus more on the community projects surrounding us than the projects we create.

[smoya]

🤖 If Fran wants to see this, let's Fran be happy then 🤖

Anyway, joking aside, would then this be more like a workshop rather than a presentation? There should be several blogposts about how to create a Kafka cluster in K8s for sure... maybe makes more sense if instead we do it all together (workshop) or at least me doing a demo.

Does that make sense?

[fmvilas]

Up to you, I guess. Thanks, dear bot 🤖

[ivangsa]

I would like to join.

[ivangsa]

It's not that I forgot, but I didn't have any time until now.

I would like to propose one talk for Monday 27th November to explore multiple availabe options for "Sending Messages Transactionaly with Transactional Outbox Pattern". I will focus on Java related technologies.

[ivangsa]

About Learn EDA I have now a big interest in "Modular Monoliths and Event-Driven Architectures"

I would like to do a deep dive into Spring Modulith to explore the following posibility:

• Develop functionality into separate modules
• Use AsyncAPI to describe Event-Driven interactions between modules, without a broker, just in memory spring messages
• The ability to move from memory-based to broker-based with (ideally) just configuration or dependencies...
• The ability to move a module to a different deployable with (ideally) just configuration

So, if any one is interested in exploring this with me, just say Hi.

I hope to have something to present at the begining of next year..