12,232 karma · joined October 5, 2008
gmail » teej.murphy@
current » Linear
prior » Downlink (YC W24), Chaturbate, Minted, Zynga, MinoMonsters
> no one that really wanted to maintain this
I feel strongly that the data organization needs to own this outright, and the only thing holding them back was the right tooling. This seems like the perfect tool to enable it. Very excited to give it a spin.
I originally test drove in Boston and placed my order there. I informed them I would take delivery on the west coast and they set that up for me. I later found out about the three systems when my car was weeks late for delivery. No one seemed to know where it was or where it was headed. Tesla's internal system said it was en route to Hayward, CA. Salesforce said it was headed to a different location that turned out doesn't do deliveries. The shipping company said the car was headed to New York. The car's GPS pinged it to a railroad track in Georgia.
My experience is an outlier, but it does indicate that these APIs might not always be correct.
- Common Table Expressions (CTEs). They will equip you to write clean, organized, and expressive SQL.
- CREATE TABLE AS SELECT. This command powers SQL-driven data transformation.
- Window functions, particularly SUM, LEAD, LAG, and ROW_NUMBER. These enable complex calculations without messy self-joins.
Learning those three will change your relationship with SQL and blow the door open of problems you can solve with the language.
https://www.citusdata.com/blog/2018/06/07/what-is-citus-good...
---
When we first started building Citus, we began on the OLAP side. As time has gone on Citus has evolved to have full transactional support, first when targeting a single shard, and now fully distributed across your Citus database cluster.
Today, we find most who use the Citus database do so for either:
(OLTP) Fully transactional database powering their system of record or system of engagement (often multi-tenant)
(HTAP) For providing real-time insights directly to internal or external users across large amounts of data.
“Our logs are stored as newline-delimited JSON objects.” No, it’s improperly escaped so it’s actually a JSON-like string of unknown character encoding.
“This is a postal code field.” Nope, it’s a user-generated string that occasionally converges on something approximating a postal code.
“This is the user’s IP address.” Well I clearly see localhost in here so unless folks are browsing the site from our servers, this is “sometimes” the user’s IP address.
This was the “killer feature” of the Google Analytics replacement I built for myself a few years back. I would grab referrers for social and scrape them to give a more useful report of the source of traffic.
Unfortunately this is challenging or impossible for many social platforms due to HTTPS everywhere, the prevalence of outbound link scrubbing, and app-driven embedded web views.
I still think it would be a killer feature to know who tweeted you out or which subreddit you are trending on but it’s just not feasible to do based on a website pixel alone.
API Gateway by itself is $3.50/million requests, which is 2-4x more expensive than Fastly at $0.75 - $1.60/million