Designing Events-First Microservices

InfoQ Dev Summit Boston, a two-day conference of actionable advice from senior software developers hosted by InfoQ, will take place on June 24-25, 2024 Boston, Massachusetts.

Deep-dive into 20+ talks from senior software developers over 2 days with parallel breakout sessions. Clarify your immediate dev priorities and get practical advice to make development decisions easier and less risky.

----------------------------------------------------------------------------------------------------------------

Jonas Bonér explores the nature of events, what it means to be event-driven, and how to unleash the power of events and commands by applying an events-first domain-driven design to microservices-based architectures.

#Microservices #EventDrivenArchitecture #Events #InfoQ #QCon #QConNewYork

[sidekickrida]

Thank you for… broadcasting this event ;)

[easycollabDotNet]

Really clear and concise talk. Thank you very much for the effort.

[rhazen]

This is a very nice talk, thank you for transmitting the experience!

[mikemyers]

Great talk, good explanations, good references. Well done!

[aammssaamm]

Managing events is a very powerful approach. Basically development converts into simple configuration.This is related to Actor model by Carl Hewitt.

[souravkabiraj]

25:14 how to get joined data in a CRUD microservice system? thanks in advance

[rrrbb]

there has to be an exception made for deletions: holding on to a request to delete a fact, and then perform the delete when we find the fact to be deleted; knowing the fact can't be recreated (because of unique ids). GDPR is a great example.

[mohamedfouad]

OK, whats the difference between event driven services and a multi agent system !?

[gigiduru]

There are databases like cockroachdb and faunadb, diatributed databases which offer serializable isolation level and can scale to 100k+ tps. I don't think eventual consistency is something you want to deal with unless you need to scale to 3 continents on the same database shard or somehing.

[MarcelToma]

Seems to me that the future of microservices will use a lot of blockchain concepts

[MarcusNielsen]

Can't that be eventually succeeds or fails instead of atomically? If I use google pub/sub and postgresql, can't I log that I'm inserting the event into the DB, and then when I'm done sending it over pub/sub, log that I'm done with the event?

[PiyushChauhan]

I already gave up after "You know part" because I don't know

[r]

This talk has some glaring errors in trying to strictly define things. For example, a command does not always have a single receiver. You can send a command to n receivers and that's actually extremely useful, for the same reasons he likes events so much.

[Jack-yxzh]

Good content but the stuttering is tough to take.

[alejandrojumilla]

Distribute for Availability not scalability if you are going to do this understanding this is basic

[sowenzhang]

generally, Jonas is a good speaker, but this one he didn't seem to be well prepared...
I believe he knows all of those stuff because I have seen him talking about those things before, but did he change a set of new slides the night before this talk?

[-two]

I think he was trying to say something useful/valuable - but I really struggled to sift through the waffle.. Points were laboured FAR too much for my liking.. Good try though :-)

[hotplugin]

How about an example project to go with the talk, all these buzz words are just marketing gimmicks.

[chessmaster]

Get put post delete are verbs. So we focus on nouns. Where did ver s come back again? Intent can only be insert update delete select. When events are produced there is no choice but consume event producer is obliged to produce and consumer is obliged yo consume if application has to work. Events are finally crud. What is crud less system. We need some code to look at. How event looks like, how message looks like how rdbms looked. How it looked after events. How much delay happened. How cars looks like how materialized view looks like. I would not present something without examples. This assumes that e eryone knows everything. Like taking to yourself not really for audience.

[einfacherkerl]

10:04 and and and try to understad the facts. i'll i'll i'll get the commands quite soon. but but but trying to find the co co cozal... between your your your components and the service. and and and and the service