Neon is a serverless Postgres platform that separates storage from compute, unlike traditional managed Postgres instances that co-locate both. This post explains Neon's object hierarchy: projects (containers for resources), branches (isolated copies of data using copy-on-write, similar to Git branches), and compute endpoints (the connection points to databases within branches that support autoscaling). Understanding these three objects is key to leveraging Neon's cloud-native workflows and developer productivity features.
1 Impression