I'd like to discuss about the deployment of notifications, into any particular sector, how any tool/ product may have 20-30 notification flows, across features like authentication, newsletters, security, and generic business logic.
Managing these in inferior configuration files or python classes/ functions, leads to scalability issues, high coupling and poor overall development experience. Additionally the requirements to setup Kafka ( or some kind of queue ) + small micro-service to send out notifications, for scalability purposes, can be cumbersome and over-engineering to some extent.
Novu, a open source notification platform, abstracts away complex topics, making it easy to push notifications via multiple providers, easily change providers, setup custom features, all while keeping it pocket friendly and extensible. The existence of Novu, allows startups and enterprises, to ship notifications in a way that would otherwise take weeks or even months to get fully rolling, Novu and it's amazing community of developers makes this possible in a matter or days and even hours.
I'd like to introduce people to Novu, how it works, deployment processes, writing notification workflows, and getting it integrated into your infrastructure, also all-in-all Novu makes use of things like Docker and React Email projects, which I'll also touch on for a few minutes. My experience in Novu comes from building notifications from 0-100 in two early stage startups, where speed and convenience was paramount.
A improved understanding of how notifications work, what requirements are needed for stable, production ready notifications systems and how Novu meets those needs.
Often times, new-age engineers undermine notifications, keep it for the last minute and while there is nothing wrong with that, understanding the complexity and the engineering behind it, is essential to building any product, and Novu - The Open Source Notification platform is ideal for the same.