Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

Incredible that these kinds of services were hosted like this.

I guess they never came out of MVP, which could warrant using serverless, but in the end it makes 0 sense to use some slow solution like this for the service they are offering.

Why didnt they go with a self hosted backend right away?

Its funny how nowadays most devs are too scared to roll their own and just go with the cloud offerings that cost them tech debt and actual money down the road.



We did initially but thought cloud flare was a better solution for scalability and latency.

We believed their docs/marketing without doing extensive benchmarks, which is on us.

The appeal was also to use the same typescript stack across everything, which was nice to work with


Where did their marketing or documentation say this service is perfect for low latency APIs?


I doubt they literally said “perfect for low latency APIs” but their messaging is definitely trying to convince you that they’re fast globally, just look at the workers.ckoudflare.com page




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: