Submissions from twitter.com/nikitabase

		We accidentally created the perfect DB for AI agents (twitter.com/nikitabase)
		4 points by davidgomes 4 months ago \| past \| 1 comment
		Postgres is missing an analytics engine (twitter.com/nikitabase)
		3 points by tosh 5 months ago \| past
		Postgres has low connection limits and goes towards multi-threaded architecture (twitter.com/nikitabase)
		13 points by nikita 7 months ago \| past \| 1 comment
		How can you make a stateful legacy system serverless? Postgres example (twitter.com/nikitabase)
		1 point by nikita on Nov 17, 2023 \| past
		Database Architecture Thread (twitter.com/nikitabase)
		1 point by nikita on Nov 12, 2023 \| past
		Use NVMe not EBS when building cloud native platforms (twitter.com/nikitabase)
		1 point by jamesblonde on Sept 9, 2023 \| past
		People should not use EBS when building cloud native infrastructure services (twitter.com/nikitabase)
		4 points by eatonphil on Sept 8, 2023 \| past
		Neon adds pgvector support for HNSW index (twitter.com/nikitabase)
		2 points by nikita on Aug 30, 2023 \| past
		“Formula for an infrastructure startup success” (twitter.com/nikitabase)
		1 point by eatonphil on June 13, 2023 \| past
		Things that will be possible in a database platform when we apply AI and LLMs (twitter.com/nikitabase)
		2 points by nikita on Sept 20, 2022 \| past
		Neon Branching Use Cases (twitter.com/nikitabase)
		1 point by nikita on Sept 13, 2022 \| past