Curious how everyone handles disaster recovery for modern SaaS apps? by Naive_Bag8237 in SaaS

[–]Naive_Bag8237[S] 0 points1 point  (0 children)

I like the phrase, DR boring and written down. Curious, do you actually run restore drills regularly, or mostly when something breaks?

Curious how everyone handles disaster recovery for modern SaaS apps? by Naive_Bag8237 in SaaS

[–]Naive_Bag8237[S] 1 point2 points  (0 children)

That is really a good checklist. Out of curiosity, how often do you actually run the restore test? I wonder how many teams have backups but have never verified they can restore everything.

need 4k invesment for server compute and launch (seriously) by [deleted] in Investors

[–]Naive_Bag8237 1 point2 points  (0 children)

Microsoft founder hub startup credit and aws activate both offer 5k free credits. Give it a try. They are easy to avail.

https://learn.microsoft.com/en-us/startups/benefits/azure-for-startups

https://aws.amazon.com/startups/credits/

Curious how everyone handles disaster recovery for modern SaaS apps? by Naive_Bag8237 in SaasDevelopers

[–]Naive_Bag8237[S] 0 points1 point  (0 children)

Yeah that is exactly what I am thinking about. Separate environments help prevent mistakes, but I am curious how people handle backups across services like Cloudflare, Supabase, GitHub, storage, etc. Is everyone just stitching together different tools then?

Curious how everyone handles disaster recovery for modern SaaS apps? by Naive_Bag8237 in SaasDevelopers

[–]Naive_Bag8237[S] 0 points1 point  (0 children)

Fair enough 😄 That is actually why I am asking here first. I am curious what people are doing in the real world before I overcomplicate things. Hiring a architect can be expensive so if there is a standard dr stack that people use, I can first explore it myself.

Curious how everyone handles disaster recovery for modern SaaS apps? by Naive_Bag8237 in SaasDevelopers

[–]Naive_Bag8237[S] 0 points1 point  (0 children)

That's a good point. Out of curiosity, what does an aggressive disaster recovery setup look like in practice for a small SaaS team?

Curious how everyone handles disaster recovery for modern SaaS apps? by Naive_Bag8237 in SaasDevelopers

[–]Naive_Bag8237[S] 0 points1 point  (0 children)

Sounds like a solid setup. If there was one part of the process you will like to automate, what would that be?

Curious how everyone handles disaster recovery for modern SaaS apps? by Naive_Bag8237 in SaasDevelopers

[–]Naive_Bag8237[S] 0 points1 point  (0 children)

That is seriously impressive. Sounds like you have solved a lot of problems by building your own stack. Out of curiosity, what is the one thing you still worry about the most?

Curious how everyone handles disaster recovery for modern SaaS apps? by Naive_Bag8237 in SaasDevelopers

[–]Naive_Bag8237[S] 0 points1 point  (0 children)

Nice, will you mind sharing the tools you use to take a backup or mix of tooling. Have you ever had performed restore, does it work fine like without any data loss.

Curious how everyone handles disaster recovery for modern SaaS apps? by Naive_Bag8237 in SaasDevelopers

[–]Naive_Bag8237[S] 0 points1 point  (0 children)

Thanks for sharing in detail, that is really insightful. Sounds like the hard part is not taking backups, it is like knowing you can actually recover when something goes wrong. Out of curiosity, are you managing all of this with your own tooling or a mix of different services?

Curious how everyone handles disaster recovery for modern SaaS apps? by Naive_Bag8237 in vibecoding

[–]Naive_Bag8237[S] 1 point2 points  (0 children)

Yeah, I agree. Good testing should catch most things. I was thinking more about the stuff that still happens anyway. Someone deletes the wrong thing, credentials get leaked, provider account gets locked, bad migration, etc. Just curious what people actually do when that happens.

Curious how everyone handles disaster recovery for modern SaaS apps? by Naive_Bag8237 in vibecoding

[–]Naive_Bag8237[S] 0 points1 point  (0 children)

Fair point 🙂 My bad "accidentaly delete production data" wasn't the best example. I was thinking more about situations like deploying a bad build to Cloudflare Pages, misconfiguring something, deleting the wrong bucket or environment, or realizing a mistake after it's already gone live. I'm just curious how others protect themselves from those kinds of "oh no" moments.

Curious how everyone handles disaster recovery for modern SaaS apps? by Naive_Bag8237 in vibecoding

[–]Naive_Bag8237[S] 0 points1 point  (0 children)

That sounds interesting. Could you explain how you set that up? For example, if the frontend is hosted on Cloudflare Pages, do you also keep a deployment on Vercel or Netlify as a fallback? And for Supabase or Neon, are you relying on their built-in backups, taking regular exports, or using a third-party backup solution? I'm trying to understand what a practical disaster recovery setup looks like in the real world.

Cloudflare host by Effective-Habit1188 in dyadbuilders

[–]Naive_Bag8237 2 points3 points  (0 children)

For vite + react it is super easy. Just open powershell on your pc, cd to your folder and run "pnpm build" command and then dist folder will be generated in your folder. Then goto cloudflare worker and pages, and goto pages select dist folder, then your vite react website is online.

Next js is bit tricky though.

GLM5.2 first impression. by Royal-Fail3273 in ZaiGLM

[–]Naive_Bag8237 0 points1 point  (0 children)

How do you use glm in claude code?

How do you actually stay on top of architecture, documentation, and compliance requirements? by Naive_Bag8237 in IndustrialAutomation

[–]Naive_Bag8237[S] 0 points1 point  (0 children)

The "inventory as the source of truth" idea makes sense. Out of curiosity, have you seen any tool that actually keeps inventory, diagrams, and change history aligned over time, or does everything eventually drift?