A team is designing a notification platform that will deliver alerts triggered by user activity on partner systems. Traffic is bursty, with most of each day quiet and occasional spikes lasting minutes. Notifications are not visible to the user immediately and a delay of up to one minute is acceptable. The team weighs three architectural choices: synchronous direct calls into a long-running service, an event-driven design with a message queue and a small worker pool, and an event-driven design with a message queue and serverless consumers. The most appropriate choice is:

Question

Accepted Answer

Event-driven with serverless consumers, since the bursty traffic with deep idle periods matches what serverless handles best and the platform absorbs spikes by spawning concurrent invocations.

Answer

Event-driven with a small long-running worker pool, since the workers can be sized for steady throughput and the queue absorbs the spikes that arrive between quiet periods.

Answer

Any of the three options performs equivalently for this workload, since the acceptable one-minute delay removes all meaningful differences between synchronous and asynchronous designs in this context.

Answer

Synchronous direct calls into a long-running service, since this design is the simplest to operate and avoids the queue infrastructure that the other two options would require.

Crowdly

A team is designing a notification platform that will deliver alerts triggered b...

Хочете миттєвий доступ до всіх перевірених відповідей на moodle.polytechnic.bh?