Finally, InlfuxDB 3.0 (previous as InlfuxDB IOx) is in GA state (with InlfuxDB Cloud). InfluxDB 3.0 leverages Apache Arrow as its core data model and rewrite in Rust, which looks like would be a very promising high performance timeseries databse. And it adapts SQL as query language instead of its own flux anymore.

Wait, when would we have a production self-host version ???

Refs:

• Tweet status from @pauldix
• Introducing InfluxDB 3.0: Available Today in InfluxDB Cloud Dedicated
• Announcing InfluxDB IOx - The Future Core of InfluxDB Built with Rust and Arrow

What's a good news! DO NOT touch default Python installed by OS, it's always considered as a bad practice on the flip side.

Debian's python3.11 interpreter will soon (>= 3.11.2-3) declare the installation to be EXTERNALLY-MANAGED, instructing pip to disallow package installation outside virtualenvs.

Practically, this means that you can't use pip to install packages outside a virtualenv, on Debian's Python interpreter by default, any more.

Or you could use third python env managers like Pyenv, Conda or other similars.

Refs:

• PEP 668 – Marking Python base environments as "externally managed"
• Update NEWS to reflect the true PEP-668 rollout in cpython3

Tweet status from @leeerob

We built a playground to explore using @vercel Edge Functions with various database providers

• Vercel Edge Functions + Database Latency
• Regional execution for ultra-low latency rendering at the edge – Vercel
• Find your Edge Functions templates – Vercel

Here are some notable serverless databases for edge applications:

• PG style
  • Neon: Open-source Serverless Postgres. Serverless, Fault-Tolerant, Branchable Postgres.
  • xata: Xata is a scalable, type-safe database with branches and a search-engine built right in. Powered by proven technologies such as PostgreSQL and Elasticsearch.
• MySQL
  • PlanetScale: PlanetScale is the world’s most advanced serverless MySQL platform
• Firebase
  • Supabase: The Open Source Firebase Alternative
• SQLite
  • Turso: SQLite Developer Experience in an Edge Database
• Message Queue
  • Upstash: Serverless Data for Redis® and Kafka®
• MongoDB & DynamoDB
  • Tigris Data: The Serverless NoSQL Database and Search Platform
  • Fauna: Fauna is a distributed document-relational database delivered as a cloud API.
• Not classified
  • Convex: Convex is the backend application platform with everything you need to build your product.

A PR to introduce initial support of io_uring for libuv has been merged. A lot of downstream projects (nodejs, uvicorn, etc) will benefit from it.

Add io_uring support for several asynchronous file operations. io_uring is used when the kernel is new enough, otherwise libuv simply falls back to the thread pool.

Performance looks great; an 8x increase in throughput has been observed.

This work was sponsored by ISC, the Internet Systems Consortium.

• linux: introduce io_uring support #3952
• Tweet status from @axboe

Until now I just know there're DNS issues in Apline image, which is major caused by musl libc. Check Racy conntrack and DNS lookup timeouts

All right, I know musl libc is different to gnu libc, usually user shouldn't feel differences in app level, but this definitely an user-aware issue.

1. glibc could be configured to send those requests sequentially, with single-request and single-request-reopen options, but musl cannot.

2. musl's resolver previously did not support the "domain" and "search" keywords in resolv.conf. This feature was added in version 1.1.13, but its behavior differs slightly from glibc's

The good news is query DNS sequentially is not the only one solution for netfilter race problem (UDP query would be dropped accidentally).

Refs:

• Functional differences from glibc - Name Resolver/DNS
• Why does musl make my Rust code so slow?
• 如何解决 Kubernetes 的 DNS 延迟问题 (Chinese)
• 记一次 k3s 的 dns 问题调查解决过程 (Chinese)
• Using NodeLocal DNSCache in Kubernetes Clusters
• Wener Wiki - musl (Chinese)