3 ms·

we use cloudflare for their dns so not a complete change of arch. (this kind of lockin is precisely why I've stayed away from faas) more importantly, its impor

we use cloudflare for their dns so not a complete change of arch. (this kind of lockin is precisely why I've stayed away from faas) more importantly, its important to send a message. We depend on these services for our livelihood. if I'm paying for a service, the least I'm owed is the ability to get in touch with a person to rectify the situation as soon as possible. Companies who want other companies relaying on their service need to provide that if they want to be taken seriously. EDIT: also, not to knock jgrahamc. appreciate that you're looking into this but one person on an email is not a scalable customer service solution for B2B. at the very minimum, there should be some sort of platform for filing the tickets, getting a timeframe on resolution as well as options to pay for faster turnaround.

kkielhofner 4y ago
If you’re using Cloudflare for DNS/registrar they have pass-through pricing. It’s a loss for them - you’re not paying for anything.
- cultofmetatron 4y ago
  Thats even more reason to switch to Route 53. I didn't choose cloudflare at the beginning but its clear its a bit of a liability here. To put it in perspective, we had to send out apology emails to very irate customers when our system went down for 10 minutes in December. edit: Route 53 not S3*
  - BasedInfra 4y ago
    You use Cloudflare for DNS but are moving over to S3 to replace Cloudflare? Do you not mean Route 53, AWS’s DNS product?
shireboy 4y ago
Totally agree they should have provided a warning. Any Saas (and really would apply to social media, web mail, etc) should clearly warn before taking drastic action if possible. But I don’t see how you’d have dns without vendor lockin. It’s not like moving dns to godaddy would be better. Route53 is nice, but aws is also a vendor lots of people are locked to Similar for ddos protection- you almost have to use somebody.

kkielhofner 4y ago

If you’re using Cloudflare for DNS/registrar they have pass-through pricing. It’s a loss for them - you’re not paying for anything.

cultofmetatron 4y ago
Thats even more reason to switch to Route 53. I didn't choose cloudflare at the beginning but its clear its a bit of a liability here. To put it in perspective, we had to send out apology emails to very irate customers when our system went down for 10 minutes in December. edit: Route 53 not S3*
- BasedInfra 4y ago
  You use Cloudflare for DNS but are moving over to S3 to replace Cloudflare? Do you not mean Route 53, AWS’s DNS product?

shireboy 4y ago

Totally agree they should have provided a warning. Any Saas (and really would apply to social media, web mail, etc) should clearly warn before taking drastic action if possible. But I don’t see how you’d have dns without vendor lockin. It’s not like moving dns to godaddy would be better. Route53 is nice, but aws is also a vendor lots of people are locked to Similar for ddos protection- you almost have to use somebody.