apache kafka - Data in Event Driven Microservices Architecture -


i'm trying build event driven microservices architecture, understand it's recommended build services without db, , instead use event store technique based on event driven microservices architecture.

my question is, if services small , totally independent each other, including not have dedicated db each service, should event store act 1 single unit \ "service" holds other services events'?

if yes, 1 of event store components message bus (like apache kafka), in order services consume , publish events, mean event store domain virtual? (because whole components including kafka doesn't being packaged single unit).

i not recommend building app has persist data without permanent store. though possible store event queue forever not random data access. imagine app needs access user information stored in middle of queue. since dont have event id you'll have reprocess queue in order find information slow.

the event queue useful decouple service dependencies not permanent data storage. typically you'll want process queue service dependent consumers transform , move data format , storage useful service.

also see this answer


Comments

Popular posts from this blog

c# - Update a combobox from a presenter (MVP) -

How to understand 2 main() functions after using uftrace to profile the C++ program? -

How to put a lock and transaction on table using spring 4 or above using jdbcTemplate and annotations like @Transactional? -