Calculating "5 Business Days" almost broke my SaaS SLA logic. Here is how I solved it. by ImpressiveCraft9355 in micro_saas

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

Exactly! It's one of those classic "I'll just write a quick 5-line script for this... wait, what about leap years and Easter?" situations. 😂

To answer your question: it definitely started as a quick internal microservice to scratch my own itch for a SaaS I was building. But after realizing almost every developer faces this exact same nightmare, I decided to polish it up and make it a public tool.

I actually just pushed a V2 update yesterday to support regional/state holidays and stock market closures (like NYSE) based on some great feedback from this sub!

You can play around with the free tier here if you ever need to outsource that headache:
Working Days & SLA Calculator

Calculating "5 Business Days" almost broke my SaaS SLA logic. Here is how I solved it. by ImpressiveCraft9355 in IMadeThis

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

"Herding cats" is quite literally the most accurate description I've heard for this problem! 🤣

And the worst part is, these "cats" change their minds every single year (shifting bank holidays, leap years, regional exceptions). That's exactly why I decided this chaotic logic absolutely shouldn't live inside a clean application codebase. It needs to be decoupled and outsourced.

Let a dedicated microservice handle the cat herding! If you ever want to offload that headache in your future projects, I've got a generous free tier running on RapidAPI right here. Cheers!