Nice presentations, thanks! I liked the idea of avoiding additional infra/overhead of Kafka and the like and relying on REST APIs. IMO if one doesn't like the pull approach, it's also possible to use server-sent events and use the interesting sources of data as event sources. Reactive programming can also help deal with back-pressure
It is really like interfaces in EJB 2.0 which you had to obey completelly, implement but you did not have any benefit. For me the Event is an object which tells me *what happened* and so it has type of event and maybe few attribute details. Other thing is Command which tells me *do something* and it contains data. That's it, easy, no need to use Spring API.
![[Full Episode] The Restaurant War Thailand ศึกพ่อค้าซ่าแม่ค้าแซ่บ Episode 3 | 6 ต.ค. 67](http://i.ytimg.com/vi/fTfIMFVjt_8/mqdefault.jpg)
![CAMPปลิ้น | EP.82[2/2] เมาท์มอยกับ 3 สาวเพื่อนซี้ ที่พร้อมขยี้พ่อหมีได้ทุกเมื่อ](http://i.ytimg.com/vi/Wwn7WnylNtQ/mqdefault.jpg)
Nice presentations, thanks! I liked the idea of avoiding additional infra/overhead of Kafka and the like and relying on REST APIs. IMO if one doesn't like the pull approach, it's also possible to use server-sent events and use the interesting sources of data as event sources. Reactive programming can also help deal with back-pressure
It is really like interfaces in EJB 2.0 which you had to obey completelly, implement but you did not have any benefit. For me the Event is an object which tells me *what happened* and so it has type of event and maybe few attribute details. Other thing is Command which tells me *do something* and it contains data. That's it, easy, no need to use Spring API.
Is there link to github repo?
github.com/olivergierke/sos This one?
That's it!