influxdb_iox VS neon

Watch out for the AGPL minio <https://github.com/metrico/iox-community/blob/155a14bb5e8e32...> the almost certainly AGPL grafana <https://github.com/grafana/grafana/blob/v10.1.1/LICENSE> and always eye anyone who uses :latest images with healthy suspicion

That said, influx_iox itself appears to be Apache 2 (and/or MIT?) https://github.com/influxdata/influxdb_iox/blob/main/LICENSE...

have you looked at https://github.com/influxdata/influxdb_iox ? that's where the development for the new version is done.

As I understand, InfluxDB 3 is just a re-branding of InfluxDB IOx. Then its' performance can be not very good comparing to Prometheus-like systems.

InfluxDB iox

Don't know how much is open or closed, but they were doing some development in the open: https://github.com/influxdata/influxdb_iox

Just want to say congratulations to the team!

2 years and 9,500+ commits is a hell of a feat.

https://github.com/influxdata/influxdb_iox

Already is: https://github.com/influxdata/influxdb_iox Just still a work in progress.

It looks like this crate is the workaround for that. But there's a PR on SQLX opened a couple days ago that will fix the issue.

You should check out polars, datafusion, influxdb iox and databend, all written in native Rust and powered by the Apache Arrow format. Polars in particular is pretty dam fast and has bindings for Python.

I want to use this as a chance to bring attention to a GitHub issue that I think would help reduce friction for Neon:

https://github.com/neondatabase/neon/issues/4989

If the Neon driver were to allow us to easily pass in a localhost connection, the development and test experience would be easier. Perhaps Neon could swap to something like this internally: https://github.com/porsager/postgres.

Having run a local dev environment connected to Neon and tests connected to Neon got in our way of adoption. We'd prefer to develop and run tests against a regular Postgres localhost database.

To the PMs of Neon, put yourself in the shoes of a new developer thinking of giving Neon a try. What changes will I have to make to my code and my development workflow?

Neon is an open source and cloud-native serverless database platform that focuses on simplicity and ease of use. It supports Postgres databases and offers built-in features like bottomless storage, autoscaling, and branching.

For MySQL, we've got PlanetScale, and for PostgreSQL, there's Neon.

8. https://neon.tech/As you might know not one tool fits all, I still have strong preferences for the following. It helps me get going faster and get things done right first time and helps in ease of maintenance.

Language: Typescript.

Migrated away when they removed the free tier, ended up using https://neon.tech/

Cool! At Neon[0], I work full time on our custom postgres proxy[1]. It's a very nice protocol to work with, although our usecase is quite a bit more complex compared to the ideas presented in the post.

Neon databases scale to zero, so the proxy needs to spin up databases on the fly. The proxy doesn't do that but it knows if the databases is running and asks our control plane to schedule it if it isn't. It's a fun service to maintain.

The biggest pain is error handling. Postgres is really bad for error messages and codes. The only available code we can use is usually protocol violation...

[0]: https://neon.tech/

Neon - PostgreSQL

For those looking for alternatives check out https://neon.tech/, https://turso.tech/ and https://developers.cloudflare.com/d1/.

Neon is an open-source serverless Postgres offering.