This message was deleted.
# generals
Slackbot
04/06/2023, 9:32 PMThis message was deleted.
f
Felix GV
04/06/2023, 9:33 PMWhat is the confusion about the current name? Can you elaborate?
s
Sushant Mane
04/06/2023, 9:33 PMThe
producerf
Felix GV
04/06/2023, 9:33 PMWhy is it confusing?
s
Sushant Mane
04/06/2023, 9:34 PMIMO this is just an extension of our
VeniceWriterf
Felix GV
04/06/2023, 9:35 PMVW is an internal detail, not intended for public consumption.
Felix GV
04/06/2023, 9:35 PMProducer conveys asynchrony, like a Kafka producer.
s
Sushant Mane
04/06/2023, 9:38 PMOk makes sense.
I tend to think of:
writes --> databases and produce to pubSubf
Felix GV
04/06/2023, 9:39 PMWell that's the thing: this class produces to the pub sub, not directly to the DB.
s
Sushant Mane
04/06/2023, 9:40 PMRight, but from user's perspective they are writing to a store not to a pub-sub topic. Topic is in a way transparent to the users...
f
Felix GV
04/06/2023, 9:41 PMWell we want to make sure they don't have the perspective that it's a strong consistency write to the DB, since it's not going to be that...
s
Sushant Mane
04/06/2023, 9:42 PMYeah there is that
f
Felix GV
04/06/2023, 9:45 PMIt is true that the RT topic is an internal detail and the user may not be aware of it. IDK if there is a better way to convey all of that.
Felix GV
04/06/2023, 9:57 PMEssentially, Venice is a deconstructed DB:
ā¢ The RT topic is the WAL.
ā¢ The server is the actual table.
ā¢ The version topics are commit logs.
The producer writes to the WAL. The consumer consumes from the commit log. The client reads from the table.
š
1
š 2
š 1
3 Views