using your database as a queue? good or bad idea?
Published 1 year ago • 17K plays • Length 9:31Download video MP4
Download video MP3
Similar videos
-
1:00
using your database as a queue? good or bad idea? #shorts
-
11:43
you want to use kafka? or do you really need a queue?
-
11:39
message ordering in pub/sub or queue
-
13:51
shared database between services? maybe!
-
16:58
aider and claude 3.5: develop a full-stack app without writing any code!
-
42:51
adam hendel: blazingly fast message queue on postgres with rust (pgconf.eu 2023)
-
11:25
don't fail publishing events! event driven architecture consistency
-
13:15
masstransit bus stop - database as a queue?
-
15:38
what is a message queue?
-
9:59
what is a message queue and where is it used?
-
10:18
architecture decision records (adr) as a log that answers "why?"
-
7:44
just store utc? handling time zones & daylight saving
-
9:43
was that message processed? asynchronous request-response pattern
-
6:46
don't use websockets (until you try this…)
-
30:45
creating a queue management database in microsoft access
-
10:57
where should you use grpc? and where not to use it!
-
9:00
alternative to the outbox pattern? not so fast.
-
8:14
5 tips for building resilient architecture
-
9:10
rpc vs messaging: when to use which?
-
8:53
avoiding a queue backlog disaster with backpressure & flow control
-
6:39
unbelievable!! can postgresql replace your messaging queue?!