Which pattern can a web API use to notify its client of state changes as soon as they occur?
43 comments · newest first
IR
Iraida
11 months ago
Shared database triggers can be tricky, though.
JE
Jennifer
11 months ago
A is the best choice, no doubt about it!
RH
Rhea
12 months ago
Wait, is ETL really an option here? That seems off.
CA
Cathrine
12 months ago
I think B could work too, but not as efficient.
OZ
Ozell
1 year ago
Definitely A, webhooks are the way to go!
JO
Johanna
1 year ago
ETL data load doesn’t sound right for immediate notifications. I’m leaning towards A too, but I wish I could remember more details.
VI
Vilma
1 year ago
I practiced a question similar to this, and I feel like webhooks were definitely the focus. So, A seems likely.
MA
Mariann
1 year ago
I'm not entirely sure, but I remember something about shared database triggers being used for state changes in some scenarios.
VI
Vicki
1 year ago
I think the answer might be A, HTTP Webhook, because it’s designed for real-time notifications, right?
SA
Sarah
1 year ago
I'm a bit confused by the options. Can someone explain the differences between them?
GA
Gayla
1 year ago
I'm pretty confident the answer is A. Webhooks are a common pattern for real-time notifications in web APIs.
CH
Charlena
1 year ago
Option C, Schedule Event Publisher, sounds like it could work too. I'll need to review the differences between the choices.
JO
Josephine
1 year ago
Hmm, I'm not sure about this one. I'll have to think it through carefully.
HO
Hoa
1 year ago
I think the answer is A. HTTP Webhooks allow the client to subscribe to events and get notified as soon as they occur.
KR
Kristeen
1 year ago
Schedule Event Publisher? Sounds like a lot of work just to get some notifications. I'll pass.
JO
Josephine
1 year ago
Yeah, Schedule Event Publisher might be too complex for just getting notifications.
SO
Solange
1 year ago
HTTP Webhook is also a popular choice for immediate state change notifications.
TO
Tony
1 year ago
Shared database trigger would be a simpler option for real-time notifications.
RE
Rebecka
1 year ago
ETL data load? Really? I think I'd be better off just staring at a loading spinner all day.
HE
Heidy
2 years ago
Shared database trigger? Now that's an interesting idea. I wonder if it could work for my use case.
JO
Johnna
1 year ago
It's worth exploring shared database triggers for your specific use case.
HA
Haley
1 year ago
I think HTTP Webhook might be a more common choice for web APIs.
BR
Brittni
1 year ago
Shared database trigger could be a good option for real-time notifications.
JE
Jesusa
2 years ago
Wait, what's a webhook again? I'm going to have to Google that one.
ST
Stefania
1 year ago
D) ETL data load
JU
Junita
1 year ago
C) Schedule Event Publisher
KA
Kanisha
1 year ago
B) Shared database trigger
BA
Barney
2 years ago
A) HTTP Webhook
FR
Frank
2 years ago
I'm not sure about this one. Webhooks? Isn't that a little too fancy for my simple use case?
JA
Janna
1 year ago
Yeah, Webhooks are a simple and effective way to get instant updates from a web API.
JE
Jeniffer
1 year ago
I think HTTP Webhook is the best option for real-time notifications.
JA
Jade
1 year ago
D) ETL data load
CA
Casandra
1 year ago
C) Schedule Event Publisher
ME
Melvin
1 year ago
B) Shared database trigger
JA
Janey
1 year ago
A) HTTP Webhook
WI
Willodean
2 years ago
Hmm, webhooks seem like the obvious choice here. Real-time updates are what I need for my web app!
GI
Gilbert
1 year ago
D) ETL data load
TA
Tawna
2 years ago
C) Schedule Event Publisher
TR
Tracey
2 years ago
B) Shared database trigger
BE
Bernadine
2 years ago
A) HTTP Webhook
JA
Jaime
2 years ago
I'm not sure about the answer. Can you explain why HTTP Webhook is the correct choice?
GE
Geoffrey
2 years ago
I agree with Nana. Webhooks are commonly used for real-time notifications.
NA
Nana
2 years ago
I think the answer is A) HTTP Webhook.