2,5 weeks into building the backend for my podcast app. I’m not working on it fulltime as I’m working on @Podhomefm for our awesome customers.

I now run two databases, a writable one and a read-only replica. This works sooo much better for performance.

I run my podping listener in one Function App (Linux, B2 size), and the feed puller in another Function App (Linux, B3 series), because ai found that running it all in one Function app didn’t fit memory-wise.

I’m monitoring the behavior to see if I can scale anything back and fix errors when I run into them.

One example is that a feed contained items with a duration of -1 seconds. I parse this into a C# TimeSpan, which works, but fails when I save it to the database. Just stuff like that.

This backend serves 2 purposes:
1️⃣ discovery: show users podcasts and episodes they might be interested in
2️⃣ notifications: notify users when a new episode is published for a podcast they are interested in

Next is more for discovery, before I start with the client app. I want to create an API that I can use to search for podcasts, episodes, people and topics. Ideally this works with my own data, and the Podcast Index API as augmentation (if I don’t have the results myself, so that users can always find a podcast)
BONUS: currently I save every (unique-ish) person that I find in a feed. This will be the basis for a Person API that I can also use for
@Podhomefm
to let podcasters search and select people to add to their show and episodes. When this works well, I’ll open this API up for open use.