There is some good advice here but I do not really understand why the talk is named 'Reactive' systems? Its like fragments of multiple talks about distributed systems composed into one talk.
Yeah, I had the same thought. A lot of the properties (scalable, tolerant to failure, graceful error, responsiveness to users, loosely coupled) is built into the BEAM. some of it (flexible, easy to develop) is not.
Great talk
Good talk ! Thanks
Excellent talk
There is some good advice here but I do not really understand why the talk is named 'Reactive' systems? Its like fragments of multiple talks about distributed systems composed into one talk.
I think Erlang had this same idea back in the 80s
Yeah, I had the same thought. A lot of the properties (scalable, tolerant to failure, graceful error, responsiveness to users, loosely coupled) is built into the BEAM. some of it (flexible, easy to develop) is not.
😊😊😊me gustó GOTO :)
Isn't that just an Actor Model based systems? AKKA, Erlang/Elixir already doing it for years
the content is almost identical to Domain Driven Design