15
points
menegattig
Joined 106 karma
- menegattig parentIt was a major outage, taking many Docs offline, but now it's back online.
- 1 point
- Totally agree.
- 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.
- Agree. I think Pinot (from Linkedin) and Druid would also provide a good solution.
- Paying $10 per 1 Million events streamed and $1 for each 100 Million properties scanned, Algolia would be dead.
- 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.
- 2 points
- Lucene (used by ElasticSearch) uses Bitmaps a lot and it is one of the main reasons for their low storage usage and search/query speed.
At my company we also strongly use Bitmaps on the analytics database engine we developed (S1Search).
- Very nice job.
Looks like we were trying to solve the same problem (user segmentation), in the same industry (DMP), at the same time (2013-2016). LOL.
I'm the founder of a DMP too.
https://blog.slicingdice.com/why-we-built-slicingdice-1beffc...
I will email you guys.
- 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.
https://blog.slicingdice.com/why-we-built-slicingdice-1beffc...
- 1 point
- Good content for creating time-series database engines that was just posted on other HN thread:
https://medium.com/slicingdice-com-blog/want-to-build-a-new-...
- The serverlees concept is also being applied to other types of services, like databases and data warehouses.
In this post below the company I work describes the reasons for a serverless data warehouse and the trends:
https://blog.slicingdice.com/why-a-serverless-data-warehouse...
(Disclosure: SlicingDice employee here)
- 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.
- Right, I agree with you.
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.
- At what point do you think starts making sense cost-wise to use MapD (or GPU in general) instead of Redshift or BigQuery?
- Price comparison between Amazon Redshift, Google BigQuery, ElasticSearch and SlicingDice using the same dataset:
https://blog.slicingdice.com/slicingdice-pricing-model-and-c...
- SlicingDice co-founder here.
There is a more in-depth overview about S1Search on this post below:
https://blog.slicingdice.com/slicingdice-uncovered-part-3-s1...
If anyone is interested to know more about our reasons for building S1Search or SlicingDice, this blog post below is a good one:
Why we built SlicingDice: https://blog.slicingdice.com/why-we-built-slicingdice-1beffc....
Happy to answer any questions about the service or infrastructure.
- If you are looking for a database-related blog, SlicingDice's is a good one:
This series of posts below describes in details how they built their database engine from scratch and the data warehouse service.
- https://blog.slicingdice.com/slicingdice-uncovered-part-1-in...
- https://blog.slicingdice.com/slicingdice-uncovered-part-2-s1...
- https://blog.slicingdice.com/slicingdice-uncovered-part-3-s1...
- https://blog.slicingdice.com/slicingdice-uncovered-part-4-in...
- Count on me too.
- SlicingDice co-founder here.
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:
Why we built SlicingDice https://blog.slicingdice.com/why-we-built-slicingdice-1beffc...
SlicingDice Uncovered - Part 1 https://blog.slicingdice.com/slicingdice-uncovered-part-1-in...
Happy to answer any questions about the service or infrastructure.
- 14 points
- Few month ago we developed and launched an AI-based AdBlocker (called AdFilter) and also had several problems with Google Chrome Web Store. Almost every week they had a "strange reason" to remove our extension from the Google Chrome Web Store.
We had more than 380,000 DAU (Daily Active Users) from 36 countries with all good feedbacks on Google Chrome Web Store, but even so, Google always tried to find a way to get us delisted and sometimes removed... they called it "an automated review process that is not performed by humans".
Every time this happened we need to send several messages to all available email address to get our extension approved and listed again in 24-48 hours. After facing this kind of situation more than 12 times, we simply gave up and remembered that it's not worth trying to build a business (or App) on top 3rd party company, like Google or FB.
- I had a similar situation on my startup, so here is my 2 cents.
My advice:
1) Have an easy but totally clear conversation with your co-founder, exposing your thoughts and opinions to him as you did here, don't be afraid to hurt him, but be respectful;
2) Ask him what he clearly expects the outcome of the company/partnership to be in the near future (12 months) and try to understand if that fits into your expectation; (Unfortunately, sometimes its comum to see co-founders thinking they should have less/lower "commitment" with the company, just because they own the smallest part of it)
3) Try to make some clear action plan out of this conversation and give a last try, but do that with a true open mind and good hart, forget the past and really try to to make it work with him.
3.1) If the conversation was good and you were able to create this clear action plan, but even so after few weeks your co-funder still behave the same way, then I think its time to move on;
4) If you really fell the result of this conversation was bad or the time was completely wasted, kindly start the process to remove him from your company; Don't make the mistake of simply ignoring him and let him stay, as this will possibly be a future cancer for your company (and you).
Important (IMHO): Before and after this conversation I suggest that you try your best to make some internal analysis of ourself too, sometimes the behavior of others are the just reflex or consequence of our own current or past actions/behaviors. No one is perfect or always right. Try to put yourself on his shoes and think with his head on why is he acting/behaving the way you consider to be bad/wrong.
Hope you solve this situation and manage to be really successful together.
- Well.. try to drive in São Paulo or Rio de Janeiro - Brazil.
- Our company (Simbiose) recently did a strong stress test with memSQL with billions of JSON rows, using complex JOIN queries and the results are simply AMAZING.