IMHO, antitrust fines/penalties should change from amount of money to some other type of penalty, like temporary market exclusion/block or something, otherwise companies like Google and others can simply use its cash (that's was also made due to the unfair advantage), pay the fine and move on to the next market dominance.
They will always have cash to pay, even if the fines are higher and higher. They kind of expect for this in their long term strategic planning.
Backblaze B2 is awesome and the future looks very promising. Their team is also very open to new ideas and projects.
We have few PB of data there and never had any problem.
I honestly don't see any reason for anyone to use AWS or Google Cloud for object storage, except for the outbound network transfer issue from these providers.
SlicingDice founder here. We built SlicingDice exactly for this kind of necessity, very fast user segmentation. Actually, we just developed it because we didn't find any other solution that could support our needs.
Very clear, thanks so much for the detailed explanation.
I'm still curious about how much it would cost for scenario where you have 1 billion user and 200 billion events for a year of data and keep adding 10 billion monthly (a very real DMP or Telco scenario) and you have to make a query like this one below on top of all this data (200 billion records). I'm wondering how many MapD servers/infrastructure I would need to have in order to get results under 100-ms.
Count UNIQUE Users that from "San Francisco" OR "New York" AND accessed the pages "/sports" OR "/news" more than 3 times in the past 12 months.
I was just wondering what kind of companies (except from financial sector) would be willing to spend hundreds of thousands to get their latency from hundreds of ms to dozens of ms. I'm saying that because if you have a very well-tuned Redshift cluster, you can easily get dozens of ms for your queries, spending thousands of dollars, not hundreds of thousands.
If anyone is interested to know more about our reasons for building SlicingDice or what is powering the service under the hood, these blog posts below are good starting points: