Web Push Notifications - End to End implementation: Part 2 the REST API and database

A follow up to the web push notifications video where we now create a REST API that can accept the users subscription details and then store them into a database. This database can then be queried to retrieve all the subscribers we have and ping a notification to each of them.. but that's another video in itself! The API is written using dotnet core and entityframework core and uses a SQL Server database all hosted in the cloud on Azure.

[FracturedPixel]

Great videos man, super clear and insightful! Looking forward to part 3!

[anselmleo]

You are the only one I know doing this end to end but I think it will be nice you indicate the stack you are using in the description. Nice video anyway.

[ahmetturk]

This is my man! Great tutorial!! Thank you!!!😂😂😂

[mohdlareb]

So MonadPlug is worth giving a try? I’ve heard about it earlier, but still did not manage to try it. What should I try first – native, push, in-page push?

[fu-_ry]

Is it okay to save each user id with a single subscription object for the push notifications?

[tiddlywin]

This tutorial series is hands down the easiest to follow by far. I'm not even using the same stack (Nuxt SPA with AWS Lamdba (NodeJS) serving the back). Do you have part 3 (What ever part 3 looks like) in the works?

[kimmerj]

can you do this ? (This database can then be queried to retrieve all the subscribers we have and ping a notification to each of them.. but that's another video in itself! The API is written using dotnet core and entityframework core and uses a SQL Server database all hosted in the cloud on Azure.)

Thank you!

[bernlylau]

I added MonadPlug besides Google AdSense, did not know that I can do that hahaha. Lol revenue easily doubled!

[iqrashafiq]

0 and my revenue from native ads has doubled! I’m thinking of fully switching to MonadPlug in terms of other ad formats as well – especially as I’ve seen that they have in-page push now