1,122 karma · joined August 11, 2011
Previously, Co-Founder @ Meldium (YC W13)
[ my public key: https://keybase.io/borisjabes; my proof: https://keybase.io/borisjabes/sigs/D21xbbT3TY6UgNSNeN3bZQnY_bUYjC7f8pTTXLI2vFY ]
[YC Badge: 0x67E2Ac2DC95Da381E380ea04aA9A6D3eE3c5Bb7C]
[keyoxide proof] $argon2id$v=19$m=512,t=256,p=1$BemQB6Wu330NdfnvbyH+bA$rXga/SeCukjCBfM91zSntnxx3ocZbi0fLLeOXHre4Kc
We support all the major data warehouses (incl. straight Postgres), connect to a bunch of different applications, and don't store any of your customer data!
Bonus: we recently added native support for dbt :-)
So it’s not quite customer support and it’s not quite cold sales. There’s healthy debate about the scope of the team though!
Heroku Connect is pretty powerful but not only is it super expensive as you point out but also forces you into creating an extra layer in the stack by creating a Heroku Postgres DB. The secret advantage of Connect is that since it's owned by Salesforce it bypasses Salesforce API quotas but that's a whole other can of worms :-)
You can customize how data is mapped and how frequently it’s synced. You can also use SQL to build custom views on your data. Our goal is to help you build an effective customer data hub out of your data warehouse.
Would love to hear feedback from the HN community.
Are you seeding the DHT with your own machines right now? At web scale, wouldn't the number of machines participating in the storage network (as opposed to the blockchain) need to be huge?
"The actual implementation continually blows my mind. You're basically using a man-in-the-middle attack for good, if I don't betray my poor understanding of the concept. A less malignant analogy would be to liken it to the way telephone companies operated switchboards before individual telephone numbers connected people directly. You had to call the central and ask the operator (i.e. Meldium) to talk to your friend Frank McFakeperson in Ipsum, South Dakota (i.e. MailChimp) and the operator would patch you through to them seamlessly."