To wersja testowa nowego serwisu infoShare Academy — wyświetlane treści i oferta nie są wiążące ani kompletne

Software Design

Event-Driven Architecture in Python

An intensive, one-day workshop introducing the world of Event-Driven Architecture (EDA) using Python.

Duration
8h · 1 day
Ask about the program → See all
Who it's for

Ideal for teams that…

1 Python developers with an intermediate level of proficiency
2 Software architects seeking to expand their knowledge of modern design patterns
3 IT specialists interested in scalable and reactive application design
Outcomes after the program

Solid backend and architecture — patterns proven in production.

✓

Understand the fundamental concepts of Event-Driven Architecture

✓

Learn practical mechanisms for implementing event-driven patterns in Python

✓

Design efficient and responsive systems using events

✓

Apply best practices in event-driven architecture design

Program

What we actually do

  • · Introduction to Event-Driven Architecture Characteristics and key assumptions of event-driven architecture Comparison of traditional architectural models with the event-driven approach
  • · Basic Concepts and Patterns Definition and types of events in software context Event publication and subscription mechanisms Designing an event-driven system
  • · Practical Tools and Libraries Introduction to event handling libraries in Python (asyncio, RxPY) Implementing a simple event queuing system Practical exercises in designing event-driven microservices
  • · Advanced Design Patterns Mediator pattern and its implementation Event Sourcing – storing application state through event sequences Designing reactive systems using Event-Driven Architecture
  • · Use Cases and Real-World Scenarios Case studies from various domains (e-commerce, financial systems, IoT) Group workshops – designing an event-driven architecture for a specific business problem Analyzing potential challenges and solutions
  • · Summary and Q&A
Every module is adapted to your stack and context. The above is a starting point — not a fixed agenda.
How we work

From brief to retro in 30 days.

01

Brief & diagnosis

A call with the team lead + a short survey for participants. We define goals, gap and context.

02

Program customization

We adapt modules, case studies and code examples to your stack. Approval in 5 days.

03

Workshop

Trainer-led sessions, hands-on, code review. Mentor available between sessions too.

04

Retro + report

Outcome report for the team and lead. 30 days of consulting included.

Inquiry

Send a brief. We'll reply within 1 day.

After a short brief we'll prepare a program and a quote. No obligations — it's just a starting point.

✓Quote within 48h of the brief
✓First session within 30 days
✓Pilot before the full decision
✓VAT invoice, payment in instalments possible

How we handle your data

We process your business data (name, work e-mail, phone number, company, job title) in order to handle your corporate training inquiry and prepare an offer. The data controller is infoShare Academy Sp. z o.o., Al. Grunwaldzka 472B, 80-309 Gdańsk. Providing the data is voluntary but necessary to receive a response. You have the right to access, rectify, erase or restrict the processing of your data and to object to it. Full information is available in our data processing notice.

Optional marketing consents

The controller of your personal data is infoShare Academy sp. z o.o. The rules for processing personal data are set out in the Privacy Policy and the Data Processing Notice.

Other programs for teams

See all →
Software Design

Application architecture

Solid backend and architecture — patterns proven in production.

16h · 2 days →
Software Design

DDD

Solid backend and architecture — patterns proven in production.

16h · 2 days →
Software Design

Design patterns in C#

Solid backend and architecture — patterns proven in production.

16h · 2 days →