https://play.clickhouse.com/play?user=play
and
https://github.demo.trial.altinity.cloud:8443/play?user=demo (password demo)
Details matter.
8443 is the default port for secure HTTP traffic on ClickHouse and has been for many years. This particular endpoint uses that port so that applications using the Python clickhouse-driver (and many others) work as expected without surprises.
There is nothing wrong with copycats because we allow them. But nothing to be proud of from your side.
It's also working slower, has less number of datasets, and it is using an older version of ClickHouse. Better to show something original.
We've never said differently. I was one of the people who congratulated on you the dataset when you first introduced it and also authored an early article on your play UI, which is an excellent ClickHouse feature than every user should know about. [0,1]
> It's also working slower, has less number of datasets, and it is using an older version of ClickHouse. Better to show something original.
Altinity.Cloud can run any version of ClickHouse. It's currently on the latest 22.10.4 build. We upgrade it regularly. I see that as a feature rather than a drawback.
I honestly don't see it as competing with anyone. We put this endpoint up a couple years ago to give people a convenient endpoint to try out ClickHouse and to certify BI tools like Superset. If anything we should all be competing to ensure ClickHouse gets the recognition it deserves. It's an outstanding analytic database.
[0] https://news.ycombinator.com/item?id=25364000
[1] https://altinity.com/blog/connecting-to-altinity-cloud-with-...
https://github.demo.trial.altinity.cloud:8443/play?user=demo (Password=demo)
It also has tables with NYC cab data (trip data) and the US DOT airline ontime dataset. They are also fun datasets for putting ClickHouse through its paces.
Disclaimer. I work at Altinity.