menegattig

6 ms·

1.
Ask HN: How do you normally choose your database?
15 points by menegattig 8y ago|5 comments
2.
by menegattig 8y ago
It was a major outage, taking many Docs offline, but now it's back online.
3.
Readme.io is down and all its customer's docs too
1 points by menegattig 8y ago|1 comments
4.
by menegattig 8y ago
Totally agree.
5.
by menegattig 8y ago
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
6.
by menegattig 8y ago
Agree. I think Pinot (from Linkedin) and Druid would also provide a good solution.
7.
by menegattig 8y ago
Paying $10 per 1 Million events streamed and $1 for each 100 Million properties scanned, Algolia would be dead.
8.
by menegattig 8y ago
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 Googl
9.
CircleCI offline due GitHub API changes(status.circleci.com)
2 points by menegattig 8y ago|0 comments
10.
by menegattig 9y ago
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)
11.
by menegattig 9y ago
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-bu
12.
by menegattig 9y ago
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://b
13.
by menegattig 9y ago
Very similar to S1Search: https://blog.slicingdice.com/slicingdice-uncovered-part-2-s1... https://blog.slicingdice.com/slicingdice-uncovered-part-3-s1...
14.
Concepts, techniques and papers to build a time-series database(blog.slicingdice.com)
1 points by menegattig 9y ago|0 comments
15.
by menegattig 9y ago
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-... https://news.ycombinator.com/item?id=14246
16.
by menegattig 9y ago
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
17.
by menegattig 9y ago
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 rea
18.
by menegattig 9y ago
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 yo
19.
by menegattig 9y ago
At what point do you think starts making sense cost-wise to use MapD (or GPU in general) instead of Redshift or BigQuery?
20.
by menegattig 9y ago
Price comparison between Amazon Redshift, Google BigQuery, ElasticSearch and SlicingDice using the same dataset: https://blog.slicingdice.com/slicingdice-pricing-model-and-c...
21.
by menegattig 9y ago
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 bu
22.
by menegattig 9y ago
If you are looking for a database-related blog, SlicingDice's is a good one: https://blog.slicingdice.com/ This series of posts below describes in details how they built their database engine from scratch and the data
23.
by menegattig 9y ago
Count on me too.
24.
by menegattig 9y ago
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:&#
25.
Show HN: SlicingDice – Serverless Data Warehouse(blog.slicingdice.com)
14 points by menegattig 9y ago|2 comments
26.
by menegattig 10y ago
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 Chro
27.
by menegattig 11y ago
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, bu
28.
by menegattig 11y ago
Well.. try to drive in São Paulo or Rio de Janeiro - Brazil.
29.
by menegattig 11y ago
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.
30.
by menegattig 12y ago
I tried using Firefox 29.0.1 on a Mac OS 10.8.5 and didn't work. Just shows Calibrating and never starts processing.

More ›