nikita

5 ms·

1.
by nikita 28d ago
Today CDC, tomorrow an authoritative part of storage.
2.
by nikita 2mo ago
If you product is CDC based (peerdb) you don’t want storage to support this :) This architecture is better for OLTP because all maintenance operations are moved to storage AND it has all other benefits such as LTAP that emerge from having a
3.
by nikita 2mo ago
Conversion is async. The whole point is to never deal with CDC which is error prone and taxing Postgres with occupying a replication slot and burning memory and cpu in the OLTP system.
4.
by nikita 2mo ago
Recent data plus working set is always in Postgres page format. Historical data when pushed to s3 is in parquet. This happens async - not on the transaction hot path. So older data below certain LSN is on s3 in parquet available to all anal
5.
by nikita 2mo ago
Safekeepers keep a window of WAL in Postgres WAL format and doesn’t have an external API. It streams WAL to pageservers and Postgres read replicas
6.
by nikita 4mo ago
* Rate limiting on proxy in front of compute fleet * Large tenants are broken up into shards, reducing hotspots * Each shard is throttled to a fixed req/s rate * We do not run pageservers at their redline in terms of CPU load, so there
7.
by nikita 4mo ago
Generally the more throughput the system supports the better. In this case we were hitting limits (btw each operation is many queries of different sizes) and the customer observed higher latencies which is typical if the system can't s
8.
by nikita 4mo ago
Lakebase is referring to the fact that in addition to disaggregated storage s3 is authoritative storage for older data. Since data is on s3 (or lake) you can perform direct to s3 type operations like data loading, reading this data by engin
9.
by nikita 4mo ago
Lakebase is OLTP.
10.
by nikita 4mo ago
We provide you fully managed Postgres. Lots of our customers use it for lots of small instances of Postgres since using Lakebase is so lightweight. Small and large instances benefit from this performance optimization.
11.
by nikita 4mo ago
This applies to our storage implementation. In Lakebase architecture storage serves pages and it doesn't always have the most recent version of the page and therefore it reconstructs it on demand. In the past we relied on Postgres comp
12.
by nikita 4mo ago
This specific perf improvement is orthogonal to HA. However generally disaggregating storage makes HA simpler and allows for things like zero downtime patching: https://www.databricks.com/blog/zero-downtime-patching-lak
13.
by nikita 4mo ago
I'm a VP on Databricks and former CEO of Neon. Happy to answer performance related or any other questions here.
14.
by nikita 1y ago
replit
15.
A recap on May/June stability at Neon(neon.com)
55 points by nikita 1y ago|5 comments
16.
by nikita 1y ago
(Neon CEO) Not really. OrioleDB solve the vacuum problem with the introduction of the undo log. Neon gives you scale out storage which is in a way orthogonal to OrielDB. With some work you can run OrioleDB AND neon storage and get benefits
17.
by nikita 1y ago
One of the services that can replace the fauna service is DocumentDB Postgres plugin (+proxy that is not open sourced yet, but will be shortly). It's available on Azure, but I can also see other Postgres Providers will start picking th
18.
by nikita 2y ago
This is an exciting project. Few highlights: - Query processor is DuckDB - as long as it translates PG type system to DuckDB typesystem well - it will be very fast. - Data is stored on S3 in Parquet with Delta or Iceberg metadata. This is r
19.
by nikita 2y ago
The word is it's a serious effort on the part of Microsoft. It's missing a MongoDB wire protocol which they plan to opensource as well. In the meantime it's possible to use FerretDB for that. I think the biggest use case is b
20.
Microsoft open sources a document database built on Postgres(opensource.microsoft.com)
1 points by nikita 2y ago|0 comments
21.
by nikita 2y ago
Oh, that's coming very very soon! London and San Paolo. Def in Q1.
22.
by nikita 2y ago
(neon ceo). What region are you in?
23.
WeSQL. Separation of storage and compute for MySQL(wesql.io)
3 points by nikita 2y ago|1 comments
24.
by nikita 2y ago
I remember having a hard time solving this in my first year of college. This is really impressive. So I have this problem here: given that for positive integers m and n, 0 ≤ x[m + n] ≤ x[m] + x[n], I need to prove that the limit of x[n]&#x2
25.
New Sota Text to Image(huggingface.co)
1 points by nikita 2y ago|0 comments
26.
by nikita 2y ago
Neon CEO... This is possible from the cost perspective due to the architecture of Neon and the ability scale to 0. Happy to answer questions!
27.
by nikita 2y ago
(neon ceo). We have lots of examples of this. Here is one with Retool. https://neon.tech/blog/how-retool-uses-retool-and-the-neon-a...
28.
by nikita 2y ago
A number of features stood out to me in this release: 1. Chipping away more at vacuum. Fundamentally Postgres doesn't have undo log and therefore has to have vacuum. It's a trade-off of fast recovery vs well.. having to vacuum. Th
29.
by nikita 2y ago
At neon we only worry about hyperscalers particularly Amazon. But they already have Aurora so we just open source everything under Apache 2.0 Being open is extremely important to us to build trust and we had this since day 1. VCs are fine w
30.
by nikita 2y ago
CEO of Neon here. Happy to answer question about Postgres development.

More ›