Format

The Event-Driven model heavily relies on the QUALITY of events.

Good quality events are:

• explicitly defined via contracts
• have comments
• support evolution with backward and forward compatibility
• support code generation
• breaking changes are well thought

Good events are implemented using the right tools:

• use Avro/Thrift/Protobuf formats and never use JSON!
• use the right event broker (such as Pulsar)

Good events are designed to:

• contain all the info needed by consumers
• use separate streams for each event type
• use the right data types for their fields (don’t use string for numbers, use enums, etc.)
• don’t use type field and fields based on it
• be as small as possible
• consider requirements from consumers
• not just signals - they contain all info needed by consumers

These topics are disclosed in the Chapter 3 of the book we are currently studying:

In January 2022, I started the Communication Genius course from one of the best public speaking coaches - to be a bit less toxic and more efficient 🙂

Lesson 1 discovers:

• What is the purpose of communication?
• What are the two parts of success?
• Why should you clearly define and write down your real goal?
• How to consider your Audience?
• What is the Format and its elements: Time, Place, Dress Code and Genre and how to use them?
• How to choose the right Moment? Examples of good and bad moments?