Neon: A Serverless And Developer Friendly Postgres

• Because the storage is now a networked system, what new performance/latency challenges does that introduce? How have you addressed them in Neon? ... {ts:572} of your product Vis A what you can get off the shelf from Amazon and then we realized that servus was kind of a big deal and that's when we made a decision to delay our release and it delayed our release by at least six months and ship ... {ts:809} different plugins and some of the ways that you're orienting towards that developer experience by removing the operational concerns well I think there are two questions in one here one is how do you maintain compatibility with postgress in ... {ts:1045} hundreds of thousands of them all at the same time on on our platform so basically the answer how do you deal with the you know massive ecosystem of post is well through that architecture we don't break out compatibility because the engine itself is still posterous uh is just with {ts:1064} swapping out storage uh from under press and the API to storage is so small uh that it doesn't app compatibility so developers don't suffer but do do they Thrive that's another question so and what are the things that developers need to thrive well some of {ts:1085} the stuff is silly you know you go and uh launch an RDS instance it's not connected to the internet and if you run cloudflare workers it's a gigantic pain to connect your application to the database um you know certain things {ts:1102} don't support TCP connections so that's why we launched our servol as driver hosas doesn't do very well with lots of connections and therefore there are systems like poers or PG bouncer that allows you to scale number connections to postest so part of the value is just packaging all that and make it it stupid simple to consume never run out of con … {ts:1505} environment but I'm I'm sharing that staging environment with my whole team let's say my team is tens of people maybe hundreds of people they all need a stageing environment and they all changing schema because they're building the app now they conflicting on both their resources but then the a {ts:1522} centralized resource is just the state of that database so you can't have a but if you want to have a staging environment on a per developer and God forbid they also test in performance now you you have hundreds of copies of that not only hard to manage it's also inefficient from the cost standpoint now