
https://nitter.gq/t.co/Z5Y47aTfQv UX Design @Databricks & @neondatabase, prev @Microsoft, @VMware
Europe
Joined February 2009
- Tweets33.6K
- Following866
- Followers1.7K
- Likes5.4K
Lachezar Petkov retweeted
Postgres 19 reached GA today, and it's already available on Neon.
To try it, pick PG 19 when creating a project or ask your agent to do it
Lachezar Petkov retweeted
LTAP isn't just a better CDC pipeline. It eliminates the need for one.
In Lakebase Postgres, the lake is the database's storage, not a replica.
We're debunking four common misconceptions about how LTAP actually works:
โ ๐๐'๐ ๐ท๐๐๐ ๐ฟ๐ฒ๐ฝ๐น๐ถ๐ฐ๐ฎ๐๐ถ๐ผ๐ป. LTAP maintains one logical table, not two databases that need to stay in sync.
โ ๐ข๐ป๐ฒ ๐ฐ๐ผ๐ฝ๐ ๐บ๐ฒ๐ฎ๐ป๐ ๐๐น๐ผ๐๐ฒ๐ฟ ๐พ๐๐ฒ๐ฟ๐ถ๐ฒ๐. Postgres uses heap pages for fast lookups, while analytics scans Parquet.
โ ๐๐ป๐ฎ๐น๐๐๐ถ๐ฐ๐ ๐บ๐๐๐ ๐ฏ๐ฒ ๐๐๐ฎ๐น๐ฒ. Queries see consistent snapshots, including recent commits not yet materialized in the lake.
โ ๐๐ผ๐ด๐ถ๐ฐ๐ฎ๐น ๐ฟ๐ฒ๐ฝ๐น๐ถ๐ฐ๐ฎ๐๐ถ๐ผ๐ป ๐ถ๐ ๐ฒ๐ป๐ผ๐๐ด๐ต. CDC requires a separate pipeline to process changes and maintain a second copy. LTAP doesn't.
Read the deep dive: databricks.com/blog/dispelliโฆ

ALT A flowchart titled "Dispelling LTAP myths" with four components. First is "Postgres" labeled "Common cache," followed by "Pageservers" labeled "n-copies," then "Object storage" labeled "Data (+1 copy)" which is highlighted in red, and finally "Lakehouse" labeled "Analytics." Arrows connect these components sequentially from left to right.
Lachezar Petkov retweeted
Big shifts happening in the AI landscape. These stats are crazy, and they come from our Unity Gateway, one of the largest router of proprietary/open source tokens (quadrillions of tokens per quarter). It's a cross-section of over 10,000 large enterprises using our gateway. Check these stats:
โ We've seen open source models go from single digit percentage 6 months ago to now over 30% of the tokens!
โ 6 months ago most enterprises had 1 model provider, today 75% have 2+ and 50% have 3+ model providers.
Read @pwendell's thread ๐
Lachezar Petkov retweeted
You can build agents with a full backend on @neondatabase and still own every piece of your stack. All our primitives are built on standard interfaces and fully composable. We donโt force infra you donโt want
The @ideavo_ai agent creates a Neon project for every app through the API, and users can claim that database into their own Neon account whenever theyโre ready
Lachezar Petkov retweeted
There are two unclimbable mountains in database world: 1 Combined transactional/analytical processing 2 true multi-master scale out
We are making significant progress on both in Lakebase
Lachezar Petkov retweeted
Postgres is a streaming database.
neon.com/docs/realtime/overvโฆ
postgres might seem like a strange choice for a streaming database.
if you compare postgres directly to something like kafka, in terms of pure write throughput, you're going to do about 2x worse, because you pay the penalty of the WAL on postgres. on my local SSD, optimized 64kb inserts are about 300 MB/s on Postgres, and about 600 MB/s on Kafka (with ack waits).
but maximizing disk throughput is very unlikely to be your biggest problem. your biggest problem is infra component bloat. it's the number 1 problem we try to avoid with the open source version of Hatchet. the only strict dependency should be Postgres, and we're going to do everything we can to optimize the shit out of it until we can't optimize it anymore.
so we built durable streams on Postgres, so users don't need to add any additional infra components to their self-hosted Hatchet stack to benefit from durable streams.
Lachezar Petkov retweeted
Hats off to @neondatabase - Iโm subscribed to a lot of DB newsletters, and theyโre always reaching out with changes to their product.
The product has gotten visibly better too over the past 12 months.
Lachezar Petkov retweeted
Dogfood everything
We shipped a new search experience for the Neon docs, built entirely on Neon primitives.
Neon docs search now uses our Lakebase Search extensions, is served by a Neon Function, and uses Neon AI Gateway for embeddings and reranking!
Read more here: neon.com/blog/neon-docs-searโฆ
Lachezar Petkov retweeted
The Databricks Lakebase team is at PostgreSQL Conference Europe 2026 in Valencia from 20โ23 October. Check out our speakersโ session schedules, and stop by booth 7 to meet the team! ๐
What bothers me about the Metal community is how folks tend to live in the past.
Like Metallica still gets questions about Jason (left the band 25 y ago), Cliff (passed 40 y ago), Mustaine (left 43 y ago)
Or Tarja gets asked about Nightwish which she left 21 years ago, etc.
1
100
Lachezar Petkov retweeted
Presenting Livebase, a demo app showing how to build collaborative human <> agent systems on a @neondatabase + @mastra stack.
Lachezar Petkov retweeted
Lakebase architecture has many benefits. One of which is making every dba operation instant.
This shift such operations left from dba to a developer and all the way to an agent.
Restoring a 100 TB database with Lakebase Postgres takes seconds.
How?
A branch-based restore is a metadata operation. It creates a branch at a point in time, referencing immutable history that already lives in decoupled storage. No copying data, no replaying WAL. Recovery is near-instant regardless of database size, and simple enough for agents to use in branching and undo workflows.
databricks.com/blog/lakebaseโฆ
Lachezar Petkov retweeted
Can a single database architecture satisfy both vibe-coded and large scale enterprise apps?
The same approach makes small database ultra cheap to run and branch can also make a large one faster and easier to operate. We call this architecture Lakebase.
Lachezar Petkov retweeted
Neon now has realtime, built by the team behind Electric. Turn any SQL query into a live query, joins and aggregates included. All inside Postgres, and ready for agents.
Itโs in public beta and available in all Neon plans. Give it a try and tell us what you think!
Lachezar Petkov retweeted
Major update to the Free Plan: you now get 0ฬถ.ฬถ5ฬถ ฬถGฬถBฬถ 1 GB of Postgres storage per project, 100 projects still included.
This is made possible by efficiencies of scale as we grow. We're creating new projects at a rate of more than one per second!
Go build.
Lachezar Petkov retweeted
The Neon backend is GA. A complete set of primitives for apps and agents built around the database, with open standards, no lock-in, and branching-first by design.
Starting with: Lakebase Postgres, Object Storage, Functions, Managed Better Auth, and AI Gateway. More to come.
I met this 19-year-old @slipknot fan and realized I've been listening to Slipknot for a few years longer than she's been alive. ๐ด
6
316
Lachezar Petkov retweeted
My co-founder @rxin personally wrote this really good paper that explains the main idea behind postgres Lakebase as well as LTAP. It almost serves as a primer on how transactional databases are built and how Lakebase and LTAP work. Maybe more importantly, what are the tradeoffs, and what are you giving up by adopting this new approach. Highly recommended reading:
databricks.com/blog/lakebaseโฆ

















