text
stringlengths
0
2.46k
[1199.62 --> 1206.58] good point are those things that when using neon are those things that are like pre-integrated for
[1206.58 --> 1213.22] you as a user of neon database or is it like click a box get pg vector how does it work with plugins and
[1213.22 --> 1218.98] yeah we just we yeah we provide those those extensions you just do create extension and you get it so you
[1218.98 --> 1225.14] just have full you have full postgres access and you're just doing your thing huh yep okay so geo
[1225.14 --> 1231.62] distributed postgres around the world let's talk about that okay can you do that no we don't do that
[1231.62 --> 1236.34] at the moment okay we've been thinking of that we have a lot of good ideas i know you do i remember
[1236.34 --> 1241.22] asking about that as well i'd love to hear from your from your mind what are some ideas around this
[1241.70 --> 1247.14] uh so what you could do uh first of all you can write run read only replicas in different regions
[1247.14 --> 1252.82] uh that's the kind of the first step easy step uh with neon we could also run the storage in
[1252.82 --> 1258.66] different regions and do the kind of the replication at the lower level okay uh we have no plans for
[1258.66 --> 1263.86] multi-master or multiple rider uh systems there are other projects trying to do that but that's
[1263.86 --> 1268.10] always a hard problem and it yeah it introduces a whole new set of problems so we're not going there
[1268.10 --> 1274.10] at the moment yeah you gotta kind of break the cap theorem to do that people are are claiming claiming
[1274.10 --> 1278.42] it's possible is there a real demand for that or is it just something that people like me like to
[1278.42 --> 1284.98] talk about and ask about i i don't know i haven't really seen very we don't hear a lot of people
[1284.98 --> 1290.02] requesting that let's put it that way okay uh people talk about it people you know people ask about it
[1290.02 --> 1294.50] but not in a serious way like i don't think we've lost any customers because we don't have it
[1296.10 --> 1301.22] given neon today what is the current architecture if you're not geo you know distributed what is the
[1301.22 --> 1305.86] architecture when you deploy neon what is the benefits of using it why do people choose neon for
[1306.50 --> 1309.54] you know you don't write the dish you write to distribute how does that actually play out what's
[1309.54 --> 1314.90] the architecture so the the core of the architecture is the separation of compute and storage and then
[1314.90 --> 1320.34] we have a control plan that kind of manages those postgres instances in vms and there's a proxy there's
[1320.34 --> 1327.30] some moving pieces but the so the big differentiator that you get with that architecture is uh it's serverless
[1327.30 --> 1331.62] so what we mean by that is that we actually shut down postgres if you're not using it so that's
[1331.62 --> 1336.02] really good if you're a developer and you you don't need to worry about you know forgetting to shut it
[1336.02 --> 1342.66] down uh in a nutshell the other thing that the storage system can do is the branching and it uh uh
[1343.30 --> 1348.18] it kind of replaces traditional backups and while archive so you can do point in time query you can
[1348.18 --> 1354.18] easily spin up a new postgres instance against an older point in time start running queries against that
[1354.18 --> 1358.18] uh stuff like that the branching is something that is kind of unique and we hear a lot of good
[1358.18 --> 1363.22] things about that people people like that if you're if you're a developer you want to create the branch
[1363.22 --> 1369.06] of your of your development database or even your production database uh and do your changes run your pr
[1369.06 --> 1375.22] against that uh and when you're done you can forget about it or you can you can refresh that right you
[1375.22 --> 1381.46] said storage system is that like a different term that sits above the database so neon is the storage
[1381.46 --> 1385.30] system and then there's the database like give me an idea what you mean when you say storage system
[1385.30 --> 1392.58] so we we wrote a completely new like server software that runs below postgres and that's it deals with
[1392.58 --> 1397.46] those eight kilobyte pages and it understands the postgres writer head log format the transaction log
[1397.46 --> 1402.74] and parses that so whenever postgres needs to read a page it goes and fetches the page from the storage
[1402.74 --> 1408.10] system instead and there's an there's an interface for that so that's different from just running a
[1408.10 --> 1413.78] postgres on a remote volume because it actually understands about the postgres uh disk format
[1413.78 --> 1419.06] and it can do this uh branching it can do the copy and write uh stuff underneath that that's
[1419.62 --> 1425.54] what else is exciting to you right now in the world of postgres or even beyond well i mentioned pg
[1425.54 --> 1429.86] vector already i think that's an that's an exciting thing people are doing a lot of exciting stuff with
[1429.86 --> 1438.02] that uh postgres world there's uh stuff happening with asynchronous io uh from colleagues
[1438.02 --> 1442.66] at microsoft they're doing doing work on that so i think that will improve the io speed and that's
[1442.66 --> 1446.50] that's really good for neon as well like the yeah because we've separated the storage that that
[1446.50 --> 1451.14] actually helps us a lot so i'm hoping to spend personally some time reviewing those patches to
[1451.14 --> 1466.02] to see them go in cool i love it yeah thanks for talking awesome thank you appreciate it thank you
[1468.02 --> 1482.02] so
[1488.50 --> 1495.62] so i'm here with ian withrow vp of product management at century so ian you've got a developer first
[1495.62 --> 1500.66] application monitoring platform it shows you what's slowed down to the line of code that's
[1500.66 --> 1506.90] very developer friendly and it's making performance monitoring actionable what are you all doing that's
[1506.90 --> 1513.46] new what's what's novel there traditionally in errors what's the strength of century is we've taken
[1514.10 --> 1519.14] not a stream of errors and said hey go look at this like all these error codes are flowing into it says
[1519.14 --> 1525.22] we actually look at them we try and fingerprint them and say hey we've actually grouped all these things
[1525.22 --> 1531.46] and then we give you everything you need within century to go and solve that error and close that
[1531.46 --> 1537.46] out and that's i think driven tons of value for our users and traditionally if you look at performance
[1537.46 --> 1542.98] it's not that thing it's you know looking at certain golden signals setting up lots of alerts maintaining
[1542.98 --> 1548.34] those alerts grooming those alerts and then detecting them and maybe you have a war room and you try and look
[1548.34 --> 1554.18] at traces or maybe you realize oh it's this engineering team that owns it maybe they'll look at logs whatever they have
[1554.18 --> 1562.10] available performance is very rotated on detection and then isolating to where the problem may exist
[1562.66 --> 1571.30] and root causing is often an exercise left to the user good performance products provide a lot of context and
[1571.30 --> 1582.18] details details that a an experienced uh engineer or or devops professional can can kind of parse and make sense of and try and get to a hypothesis of what went wrong
[1582.18 --> 1591.62] but it's not like that century error experience where it's like here's a stack trace here's all the tags oh we see it's like this particular set segment of code and
[1591.62 --> 1602.18] ian did the commit that changed that code and do you want to fire your issue and assign it to ian like it's not like that crisp kind of tight right that we have errors this is breadcrumbs
[1602.18 --> 1619.70] right and we said hey maybe there's no reason why we could do this for performance let's try okay so you took a swing you tried describe to me how that trial works if i'm if i go to my dashboard now and i enable apm on my application what are the steps
[1619.70 --> 1630.30] largely because we kind of encourage you to go and set up uh transaction information when you set up century you probably as a user probably don't need to do much but if you skip that step you do need to configure to send that data
[1630.30 --> 1653.02] uh in your sdk and what happens is we start now looking at that information and then when we see a what we call a performance issue we fingerprint that and we put that into your issues feed which is already where you're looking for error issues right it's not a separate inbox this is the same inb...
[1653.02 --> 1670.40] um and for newer users sometimes we detect hey you've probably never seen this before we can kind of we do things because we know we build for for math market that bring your attention to it but it's the same workflow you have for errors today so you don't have to learn something new uh to take a...
[1670.40 --> 1682.60] so you asked the experience so last fall we did the experiment the first one which we called uh m plus one and we didn't know how it was go honestly uh but uh people liked it like we we kind of know
[1682.60 --> 1712.58] people like it when they start tweeting and saying things about it and so um yeah it got traction very cool so if your team is looking for a developer first apm tool to use check out sentry and use the code change law when you sign up and you're gonna get the team plan for free for three months m...
[1712.60 --> 1742.30] are we started yet this is the show man all right we're here with robert abukalil hello hello his second appearance on the changelog apparently allegedly allegedly sorry that's a better word so apparently also works
[1742.30 --> 1750.14] according according to you and with some verifiable memory of mine we talked to you at oscon probably 2018
[1750.14 --> 1760.82] 2017 2017 maybe i would say 2019 yeah okay and we talked about web assembly we did was this in europe was it in europe
[1760.82 --> 1767.64] no no okay it was in portland well you were in it was in portland you were there i went to oscon london one time
[1767.64 --> 1775.46] 2018 when that was okay was web assembly a thing then yeah it was uh yeah it was a thing it must have
[1775.46 --> 1781.30] been as much as you were into it now okay this is sparking a memory okay isn't it yeah well backstory
[1781.30 --> 1787.00] for you adam is he walked by earlier and we both kind of locked eyes and i was like do i know you and he's
[1787.00 --> 1791.64] like do i know you or something and he's like yeah i think you had and i was like i have no memory of this
[1791.64 --> 1797.56] i'm like i know this guy so i have a memorable face jared and i went to an oscon together in austin i want
[1797.56 --> 1804.54] to say right probably 2017 portland in 2018 portland 2018 that's probably where we met and then we haven't
[1804.54 --> 1810.02] been there since because it stopped yeah so that's why i thought the only oscon we had been to was in
[1810.02 --> 1815.86] austin so in my memory until this moment have you now inserted one brand new oscon in my life which i
[1815.86 --> 1824.00] went to i definitely went to portland in 2019 in the summer for sure so yeah because i took my
[1824.00 --> 1830.24] daughter and my mom to meet with family and that was oscon so maybe it's 2019 anyways either way
[1830.24 --> 1833.86] neither here nor there history has been painted robert was there he's probably correct and we're
[1833.86 --> 1838.96] probably wrong he was in the web assembly he's in the bioinformatics yes i am you're still into both
[1838.96 --> 1845.58] of these things i surprisingly yes and i don't know what we talked about then specifically but one thing
[1845.58 --> 1851.76] that is interesting to me about web assembly is how much promise it has but how much how little
[1851.76 --> 1861.04] in my purview practical use it has beyond tinkers or people with very specific needs so just curious
[1861.04 --> 1866.38] your perspective on that yeah i think i generally agree with that i think people who think that web
[1866.38 --> 1872.00] assembly is going to be used everywhere are just wrong wrong okay it's just not what it's meant for
[1872.00 --> 1878.38] it's a very heavy duty tool like if you have needs for running compute intensive workloads in the
[1878.38 --> 1885.06] browser like figma and photoshop google earth all the or bioinformatics i should add all those are great
[1885.06 --> 1890.54] applications for web assembly because for the first time you can take code that's not written in javascript
[1890.54 --> 1897.38] and bring it to the browser but if you're building your typical web application that doesn't have any
[1897.38 --> 1905.08] sort of compute any sort of processing audio visual then you probably don't need it okay that's kind
[1905.08 --> 1910.28] of my view on it what about these people that are taking it server side there's a lot of talk about
[1910.28 --> 1917.10] that as well i mean do you do you dip into that area at all a little bit so there is a lot of excitement
[1917.10 --> 1926.04] about that i don't share that excitement okay because here's the thing when when you're running
[1926.04 --> 1932.60] web assembly in the browser it lets you do something that was previously impossible you just couldn't take