Architecting a Scalable Notification Service
This post can serve as a reference document that highlights some of the best practices in architecting a Notification Service infrastructure.
Why a Notification Service?
I will be using “Notification Service” as an umbrella term to cover the different components that we will need to run a fully functioning notification service on production.
Notification services are widely used nowadays in any product. They are useful whether you’d like to be notified of a change in price (ideally a price drop) or the availability of a product that you are interested in, or whether you’d like to be notified if there’s a new job specification available for a job search criteria that you have specified.
With the advent of mobile apps, getting notified to take action through our mobile devices’ push notifications is convenient on top of receiving good old emails.
For simplicity, we will be focusing on the product price change use case.
