zlacker

>>tardis+(OP)
4 Billion requests per month involving 1 Petabyte of traffic doesn't seem like a "small SAAS", at least packet-wise. If its small revenue-wise, addressing that is a business concern as important as having your platform throttled for using the cheapo economy edition tier of whatever you've signed up for with Cloudflare. Did Cloudflare issue any formal communication with you warning about usage and how it violates contractual terms, or did they "ban" you out of nowhere?

>>Dowwie+Yc
I worked for a large bank, my internal backend would receive couple orders more requests from other internal apps and users and probably similar traffic.

It is very easy (relatively) to build a SaaS platform that serves this amount of traffic and this can be done by even a one determined individual or a small startup team.

I don't think it is useful to measure the size of the company in the amount of requests they are serving. Revenue/number of employees are much better measurements saying more about the type of things that are/can be happening. They may have relatively low margins per request and need to get to 4B to get by to pay for couple salaries?

>>twawaa+Rd
Are you doing RAM-aaS or something?

Must be alot of redundant data back and forth.

>>rightb+Tg
I've worked with several EMR (Electronic Medical Record) systems that communicate an absolute metric shit-ton of redundant data for no reason other than just because and bad programming habits. Banking and Healthcare thrive in redundant redundancy.