| My company recently started to invest more into analytics and we had to find a good solution on which backend/database we want to decide.
After some research we settled on ClickHouse and we couldn't be happier. - Super easy to setup
- Easy to backup
- Fast configuration (documentation could be better at some parts)
- Similar SQL dialect as our devs use in MySQL Only negative points I could find so far:
- No 'good' management GUI as e.g. phpMyAdmin, pgAdmin, Mysql Workbench
- Caching/Batching layers not directly implemented, but through external software As we are a fairly small company all other analytical databases would have cost us a large amount of money/time more. Friends of us recently hired a group of data engineers/analytics who also brought all their AWS knowledge and toolings with them, which basically brought them to the same outcome as us, while we only have 5% of their costs and all our devs are able to either ingest or query some data EDIT:
Does anyone have some recommendations on what GUIs I could give our PMs to work with ClickHouse instead of writing queries? All SaaS I found didn't support ClickHouse yet or would cost us a newborn.
Also what tools do your devs use when they work with ClickHouse data? |
I think once you reach that scale, systems that completely separate data and compute (like snowflake or trino+s3) are much less of a pain to run since even if you completely blow up your compute the data stays.
> Does anyone have some recommendations on what GUIs I could give our PMs to work with ClickHouse instead of writing queries? All SaaS I found didn't support ClickHouse yet or would cost us a newborn. Also what tools do your devs use when they work with ClickHouse data?
I think both Superset and Metabase were interesting choices - if you want to save money (at the expense of engineering time) you can self-host them.