Events & Commands • Chris Richardson • YOW! 2018

Подписаться 1 млн

Просмотров 2,1 тыс.

50% 1

This presentation was recorded at YOW! 2018. #GOTOcon #YOW
yowcon.com
Chris Richardson - Creator of the Original CloudFoundry.com & Author of 'POJOs in Action' & 'Microservices Patterns'
RESOURCES
x.com/crichardson
/ pojos
github.com/cer
fosstodon.org/...
www.chrisrichar...
microservices.io
RECOMMENDED BOOKS
Chris Richardson • Microservices Patterns • amzn.to/3PVVvHj
Chris Richardson • POJOs in Action • amzn.to/44JGSLr
Sam Newman • Monolith to Microservices • amzn.to/2Nml96E
Sam Newman • Building Microservices • amzn.to/3dMPbOs
Ronnie Mitra & Irakli Nadareishvili • Microservices: Up and Running• amzn.to/3c4HmmL Mitra, Nadareishvili, McLarty & Amundsen • Microservice Architecture • amzn.to/3fVNAb0
/ gotocon
/ goto-
/ gotoconferences
#Events #Commands #Microservices #Monolith #MicroservicesArchitecture #SoftwareArchitecture #ChrisRichardson #YOWcon
Looking for a unique learning experience?
Attend the next GOTO conference near you! Get your ticket at gotopia.tech
Sign up for updates and specials at gotopia.tech/n...
SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.
www.youtube.co...

Опубликовано:

30 сен 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 4

@GOTO- 2 месяца назад

We are currently releasing older YOW! videos to serve as a valuable archive, preserving historical content. It is possible that a video is perceived as outdated. We believe it offers insightful glimpses into the past, enriching our understanding of history and development.

@jscancella 3 месяца назад

I don't understand from his talk why Kafka isn't an event store since it stores the messages forever if you set it that way

@Satook 3 месяца назад

Access patterns. it doesn’t support giving you efficient access for per-stream or per aggregate-type sequential reads and stream fetches at the same time. In many common ES scenarios you end up replaying all events even when you only want a few of them. This becomes a problem pretty quickly as it’s essentially a large read-amplification.

@jscancella 3 месяца назад

@@Satook sorry, that still doesn't make sense to me. Why would you continue to have a single stream? Just like in accounting you close them out every X timebox so you are only ever needing to read from the end of the last timebox (snapshot, savepoint, whatever you want to call it). You can also have aggregated streams that just provide the latest value of all the messages