zlacker

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+(OP)
Are you doing RAM-aaS or something?

Must be alot of redundant data back and forth.

>>rightb+23
I said nothing about the application and you already know everything about it.

Seems like I spent quarter of century in this business for naught.

>>rightb+23
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.

>>twawaa+4c
There is a huge waste of power on the internet with data going back and forth for no good reason.

Obviously I have no clue about your work.