Видео

36:10 Colin, you may have hit the jackpot. Checkout @thatdot Quine product. Entities, relations and state(late arrival also) , ingestion with back pressure , events in motion( standing query) more than a group by . May be pairing with nats would do it

I think it's my 5th time coming back to it.

I have a few project ideas for Erlang, looking forward to implementing them

My take is just on his example of services relying on each other to complete a workflow (order + credit service). The thing he's missing is to use a saga pattern. And if they did their DDD well they could have realise some of them could have been in the same bounded context. eventing in microservice should be a broadcast and forget. Once we have the notion of state 1 > state 2 > state 3, you need another strategy to manage that.

I know the reactor-netty-incubator-quic but There is an example for RSocket Quic? Is Quic implemented into the Rsocket?

ρгό𝔪σŞｍ

great and thanks. where we can get the code?

That was f awesome talk!

This talk didn't age well after structured concurrency. Loom is going to kill reactive programming. Amen.

Bekaar

Great video. Realy seems that the combination between Loom + Reactive Frameworks will be very good.

He looks like he's been taken hostage.

This is a creative, entertaining talk: thank you. I enjoyed it very much.

Coolest Erlang introduction! Thank you, Fred.

What I don’t understand about event sourcing, is how do you maintain that current state for millions of different entities ? Are you basically committing it to database by consuming the ‘added’ command? Or is it held in memory and has to be recalculated every time he restarts his server by reading the whole stream? When would you replay the whole stream if it’s committed to a database?

so correct me if im wrong: good event source implementation includes both an EVENT and a snapshot of STATE so if required we can query and replay historical events up the point of failure ?

Great stuff Josh!! Thanks

Great video!

11:00 Good and interesting explanation of the lunar module failure ruclips.net/video/B1J2RMorJXM/видео.html

I've never heard stateful vs stateless described in this way, which is basically just caching vs not caching. More commonly stateless refers to the state being carried around on the requests/responses, so that there's no need to retrieve state on an arbitrary insuran instance, unlike stateful where the instance must either hold state or retrieve it from a central location.

I expected a talk about actors and modern uses of them, instead I got something else? If you want, go re-watch this talk, there are more buzz-words in than I could count. Every slide is an assertion, with disconnected results of that assertion and absolutely no facts, code, or explanation. Even the Q&A section was a mess: "Professor, how do we deal with X and Y when Z exists? Carl: well we have Y and X so Z isn't a problem". Every answer he gave was just a re-phrase of the question, then he acted like he had answered the question! This talk was a markov chain of buzzwords. The Q&A section was the same markov with a different random seed.

1:52 distributed transactions is a different game 1:59 resource manager 3:04 in practice, life is more challenging than that 3:16 configuration is hard 4:33 reason: CAP theorem 4:58 important paper: life beyond distributed transactions 5:43 CQRS/ES to the rescure 7:37 only Durability in ACID is valid

Guys that was a great talk!!! I hope we will see you again together on this topic.

i am the 69th liker

Thank you very much for the clarufucation about the difference between Message and Event.

0:00 Introduction 2:59 Sample use case 11:19 CompletableFuture 13:42 Project Reactor 19:05 Project Loom 30:10 Loom + Reactive approach 34:01 Questions

This really helps in understanding reactive programming better!

What just happened?

Interesting about the problem of clustering in 17:23 Erlang has a global registry where you can find the correct process across the cluster. Pretty similar

OK, not just forgiving but enjoying and encouraging diversity of accents but... C'mon man! SKEDJeweler is "schedule... er"? Anyway, awesome presentation all kidding aside.

GREAT !!!!!

Great Presentation! Thank you

Go DDoS yourself.

Where is the repo ?

Awesome!

Thnx Rob for this nice compressed and information-rich presentation.

Does he not look like Jesse Pinkman from Breaking bad???

Such a great tribute to Dmitry

very useful detailed presentation for akka actors and akka streams. if you can please keep in touch for future online meetings with you to understand more about the system. furqan.cloud.dev@gmail.com

Could you please share GitHub URL for the project?

Nats is fantastic! Thank you Derek, Waldemar and all who made it possible.

Can't you just make an sql-view for the search service to query the reservations without the need for kafka?

What a great talk!

I want to work on this project. It is hard and what we need for energy transformation.

You both are amazing!! Lovely presentation and really amazing speech by both of you guys!!

I love this tech.

not a scam

A great introduction into Akka Streams from the trenches! One question, though: if data loss is to be avoided at all costs, then why rely on the assumption that processing of in-flight messages will succeed? An Akka Streams process could be abruptly terminated by a multitude of external factors, most trivially hardware failure. Since your're consuming from Kafka, why not use explicit offset confirmation like Alpakka Kafka supports, and only confirm the Kafka offset after the HTTP message was successfully sent? That way, unconfirmed in-flight messages would be refetched from Kafka and reprocessed. Of course, that would only work if the external endpoints were idempotent, but that's a reasonable assumption. Even if they weren't, there would be other ways to work around that.

it seems to rain with computer illiterates (imbeciles) in this forum. they all speak nice, but have no clue what so ever. unsubscribing!

Excellent presentation. I like the concept of xxxOn() methods.