Is Superset extensible enough to click on the charts -- for example, click on part of the pie-chart and have it show the list that makes up the data for that part of the pie chart?
This is great. I am very curious about the architectural decisions you've taken here. Is there a blog post / article about them? 80 yrs of historical data -- are you storing that somewhere in PG and the APIs are just fetching it? If so, what indices have you set up to make APIs fetch faster etc. I just fetched 1960 to 2022 in about 12 secs.
This is great but doesn't work for applications that don't have the luxury of the internet. What are some decent map alternatives for air-gapped (no internet access) applications.
Honest question: why is SQLLite needed for local? Why would you not have PG at edge that replicates data with central PG? That way the SQL dialect problem you mentioned wouldn't exist.
We have multiple roles across the three disciplines. The company has grown 150% since last year. We offer meaningful equity, great work life balance (no on-call) + benefits, and hard problems to solve with wide impact.
Raft (https://goraft.tech/) | Sr. Engineers (Multiple Roles) | Full Time | Remote (US Based)
Raft partners with the DoD to work on three core things:
- Distributed Data Systems (Kafka, Flink, Airflow, Kubeflow)
- Platforms at Scale (K8s, Hardware in the loop, QEMU emulation, C++/Rust)
- Reactive App Dev (Scala, ReactJS, Python/Django)
We have multiple roles across three disciplines. The company has grown 150% since last year. We offer meaningful equity, great work life balance (no on-call) + benefits, and hard problems to solve with wide impact.