Podcasts about faunadb

这次关于基础软件的硬核直播，干货实在是太多了！如果你对基础软件、开发者工具、开源这些话题感兴趣，一定不能错过。国内开源独角兽 PingCAP, Coinbase 数据平台负责人，刚创业的Google Tensorflow 大牛，一起来聊聊全球视角下的基础软件创业的经验和坑，用户视角的选型逻辑，更有未来的技术展望。 小提示：本次内容需要对database 等领域有一定技术背景知识。 Hello World, who is OnBoard?! 过去3年，国内外的基础软件、开源和开发者工具领域都涌现出前所未有的热潮。作为这个领域的投资人，Monica 看到，这些企业在走向国际竞技场的过程中，真切感受到了中美市场从用户需求、技术生态、人才组织、创业环境等等方面的异同。这中间要经历的挑战、思考、与调整，非常需要来自中美的多方经验来一起碰撞、讨论、提升。 这次三位重磅嘉宾，正是代表了三个非常重要的视角。有中国和美国本土的创业公司，更有美国科技企业infra负责人，都是资深大牛。不同的视角，同样的犀利。有市场和生态的现实，又有未来展望。这次讨论有些长，全程无尿点又不好分开。不过，只要你对打造全球一流的基础软件公司这个话题感兴趣，相信这次的内容绝对不会让你失望。 大家 Enjoy! 几位嘉宾所在的公司 三位嘉宾的具体介绍，可以参见这一篇文章。 Dongxu/Ed Huang，PingCAP co-founder & CTO, TiDB, TiKV 作者 Leo Liang: Coinbase 数据平台负责人，前 Cruise ML 平台负责人 Mingsheng Hong: Bluesky co-founder & CEO，前 Google Tensorflow Runtime 机器学习负责人 我们聊了什么 02:03 开场 & 几位嘉宾自我介绍 & fun fact: 最近看到有意思的开源项目 (Vercel, AnyScale) 11:46 PingCAP 的出海体会 14:16 Dongxu 对美国市场的观察：Developer will be the king， 开发者体验越来越重要 16:20Dongxu 对美国市场的观察：cloud native 已经是事实标准 18:28 Dongxu 对美国市场的观察：storytelling 太重要 & supabase 的例子 24:36 Leo: 开发者想要听怎样的故事 27:23 Mingsheng: 什么是一个开发者体验好的产品 30:12 Leo: 硅谷科技公司如何做技术选型：opensource, composable, componentize 42:11 Dongxu: 中国基础软件公司走向海外的节奏与重要性 47:01 Mingsheng: 创业公司如何选择早期用户 52:10 讨论：销售模式应该选择PLG （自下而上产品驱动增长）vs 传统大客户销售 55:59 讨论：不同阶段如何选择不同用户？中美用户购买决策有何差异？ 63:10 Dongxu: 全球化的社区运营有什么挑战？运营与产品之间的关系？ 68:14 Leo, Mingsheng 推荐了解的开源项目：Anyscale/Ray, Tensorflow 73:58 Dongxu：开源项目如何考虑商业化的节点与方式？ 79:26 重点讨论：美国Digital Native Business (DNB) 的公司如何做开源产品的购买决策，中美有什么异同，为什么 91:16 划重点：为什么客户关注的是 ROI>易用性>性能>功能，但是公司宣传的时候往往反过来 92:07 Mingsheng: 什么是下一代的云计算成本优化 96:45 讨论：展望未来，哪些让你们感兴趣的创新机会？文件传输格式分离，serverless, ML in infra 101:27 Q&A: 存储领域的挑战和新机会？ 113:36 Q&A: 企业用户如何考虑基础软件产品ROI Reference/提到的公司 Neon: serverless Postgres Vercel: serverless frontend stack for web developers, started from hosting node.js Upstash: serverless data for Redis and Kafka Supabase: opensource Firebase alternative Toolchain: ergonomic open source developer workflow system FaunaDB: serverless Anyscale: company behind Ray, an open-source Python framework for running distributed computing Tensorflow: Dbt: opensource data transformation tool for ELT 提到的文章 Dongxu 登顶Hackernews 的文章：Some notes on DynamoDB 2022 paper Leo 关于Serverless 的文章 欢迎关注M小姐的微信公众号，了解更多中美连线对话！ M小姐研习录 (ID: MissMStudy) 大家的点赞、评论、转发是对我们最好的鼓励！希望你分享给对这个话题感兴趣的朋友哦~ 如果你有希望我们聊的话题，希望我们邀请的访谈嘉宾，都欢迎在留言中告诉我们，我们会认真看每个评论的！

In this episode Brian and Raymond discuss the Jamstack, what it is, how did it start and what are their favorite tools for the job.If you liked the topic, you can use the promo code pod20minjs22 to get a 35% discount when you buy their book, "The Jamstack Book".Show links:Check out Raymond's preferred stack:Eleventy (e11y): https://www.11ty.dev/Netlify: https://www.netlify.com/FaunaDB: https://fauna.com/Algolia: https://www.algolia.com/And check out Brian's recommended stack:Hugo: https://gohugo.io/NextJS: https://nextjs.org/SvelteKit: https://kit.svelte.dev/ & check our episode with Mark Volkmann on this topicAstro: https://astro.build/Sanity:  https://www.sanity.io/Contentful:  https://www.contentful.com/Get in touch with our guests:Brian: @remotesynthRaymond: @raymondcamdenReview Us!Don't forget to leave a review of the episode or the entire podcast on Podchasers!Meet our host, OpenReplay:OpenReplay is an open-source session replay suite, built for developers and self-hosted for full control over your customer data. If you're looking for a way to understand how your users interact with your application, check out OpenReplay.

In this episode we talk about all the different database options we've considered for our projects. This includes, mongoDB, sqlite, postgreSQL, redis, faunaDB, firebase, supabase, as well as ORMs like prisma and do-it-alls like notion.

Learn more: https://fauna.com/features Fauna is the creator of FaunaDB — a disruptive, global serverless database that makes modern applications possible with rich clients and serverless backends. The founders of the company come from global tech giants like Twitter. In this episode of Let’s Talk, I sat down with Evan Weaver, Co-Founder and CTO of Fauna, to learn more about FaunaDB and what unique problem it's trying to solve.

Evan Weaver of Fauna discusses the Fauna distributed database. Host Felienne spoke with him about its design and properties, as well as the FQL query language, and the different models it supports: document-based as well as relational.

About Rebecca MarshburnRebecca's interested in the things that interest people—What's important to them? Why? And when did they first discover it to be so? She's also interested in sharing stories, elevating others' experiences, exploring the intersection of physical environments and human behavior, and crafting the perfect pun for every situation. Today, Rebecca is the Head of Content & Community at Common Room. Prior to Common Room, she led the AWS Serverless Heroes program, where she met the singular Jeremy Daly, and guided content and product experiences for fashion magazines, online blogs, AR/VR companies, education companies, and a little travel outfit called Airbnb.Twitter: @beccaodelayLinkedIn: Rebecca MarshburnCompany: www.commonroom.ioPersonal work (all proceeds go to the charity of the buyer's choice): www.letterstomyexlovers.comWatch this episode on YouTube: https://youtu.be/VVEtxgh6GKI This episode sponsored by CBT Nuggets and Lumigo.Transcript:Rebecca: What a day today is! It's not every day you turn 100 times old, and on this day we celebrate Serverless Chats 100th episode with the most special of guests. The gentleman whose voice you usually hear on this end of the microphone, doing the asking, but today he's going to be doing the telling, the one and only, Jeremy Daly, and me. I'm Rebecca Marshburn, and your guest host for Serverless Chats 100th episode, because it's quite difficult to interview yourself. Hey Jeremy!Jeremy: Hey Rebecca, thank you very much for doing this.Rebecca: Oh my gosh. I am super excited to be here, couldn't be more honored. I'll give your listeners, our listeners, today, the special day, a little bit of background about us. Jeremy and I met through the AWS Serverless Heroes program, where I used to be a coordinator for quite some time. We support each other in content, conferences, product requests, road mapping, community-building, and most importantly, I think we've supported each other in spirit, and now I'm the head of content and community at Common Room, and Jeremy's leading Serverless Cloud at Serverless, Inc., so it's even sweeter that we're back together to celebrate this Serverless Chats milestone with you all, the most important, important, important, important part of the podcast equation, the serverless community. So without further ado, let's begin.Jeremy: All right, hit me up with whatever questions you have. I'm here to answer anything.Rebecca: Jeremy, I'm going to ask you a few heavy hitters, so I hope you're ready.Jeremy: I'm ready to go.Rebecca: And the first one's going to ask you to step way, way, way, way, way back into your time machine, so if you've got the proper attire on, let's do it. If we're going to step into that time machine, let's peel the layers, before serverless, before containers, before cloud even, what is the origin story of Jeremy Daly, the man who usually asks the questions.Jeremy: That's tough. I don't think time machines go back that far, but it's funny, when I was in high school, I was involved with music, and plays, and all kinds of things like that. I was a very creative person. I loved creating things, that was one of the biggest sort of things, and whether it was music or whatever and I did a lot of work with video actually, back in the day. I was always volunteering at the local public access station. And when I graduated from high school, I had no idea what I wanted to do. I had used computers at the computer lab at the high school. I mean, this is going back a ways, so it wasn't everyone had their own computer in their house, but I went to college and then, my first, my freshman year in college, I ended up, there's a suite-mate that I had who showed me a website that he built on the university servers.And I saw that and I was immediately like, "Whoa, how do you do that"? Right, just this idea of creating something new and being able to build that out was super exciting to me, so I spent the next couple of weeks figuring out how to do HTML, and this was before, this was like when JavaScript was super, super early and we're talking like 1997, and everything was super early. I was using this, I eventually moved away from using FrontPage and started using this thing called HotDog. It was a software for HTML coding, but I started doing that, and I started building websites, and then after a while, I started figuring out what things like CGI-bins were, and how you could write Perl scripts, and how you could make interactions happen, and how you could capture FormData and serve up different things, and it was a lot of copying and pasting.My major at the time, I think was psychology, because it was like a default thing that I could do. But then I moved into computer science. I did computer science for about a year, and I felt that that was a little bit too narrow for what I was hoping to sort of do. I was starting to become more entrepreneurial. I had started selling websites to people. I had gone to a couple of local businesses and started building websites, so I actually expanded that and ended up doing sort of a major that straddled computer science and management, like business administration. So I ended up graduating with a degree in e-commerce and internet marketing, which is sort of very early, like before any of this stuff seemed to even exist. And then from there, I started a web development company, worked on that for 12 years, and then I ended up selling that off. Did a startup, failed the startup. Then from that startup, went to another startup, worked there for a couple of years, went to another startup, did a lot of consulting in between there, somewhere along the way I found serverless and AWS Cloud, and then now it's sort of led me to advocacy for building things with serverless and now I'm building sort of the, I think what I've been dreaming about building for the last several years in what I'm doing now at Serverless, Inc.Rebecca: Wow. All right. So this love story started in the 90s.Jeremy: The 90s, right.Rebecca: That's an incredible, era and welcome to 2021.Jeremy: Right. It's been a journey.Rebecca: Yeah, truly, that's literally a new millennium. So in a broad way of saying it, you've seen it all. You've started from the very HotDog of the world, to today, which is an incredible name, I'm going to have to look them up later. So then you said serverless came along somewhere in there, but let's go to the middle of your story here, so before Serverless Chats, before its predecessor, which is your weekly Off-by-none newsletter, and before, this is my favorite one, debates around, what the suffix "less" means when appended to server. When did you first hear about Serverless in that moment, or perhaps you don't remember the exact minute, but I do really want to know what struck you about it? What stood out about serverless rather than any of the other types of technologies that you could have been struck by and been having a podcast around?Jeremy: Right. And I think I gave you maybe too much of a surface level of what I've seen, because I talked mostly about software, but if we go back, I mean, hardware was one of those things where hardware, and installing software, and running servers, and doing networking, and all those sort of things, those were part of my early career as well. When I was running my web development company, we started by hosting on some hosting service somewhere, and then we ended up getting a dedicated server, and then we outgrew that, and then we ended up saying, "Well maybe we'll bring stuff in-house". So we did on-prem for quite some time, where we had our own servers in the T1 line, and then we moved to another building that had a T3 line, and if anybody doesn't know what that is, you probably don't need to anymore.But those are the things that we were doing, and then eventually we moved into a co-location facility where we rented space, and we rented electricity, and we rented all the utilities, the bandwidth, and so forth, but we had Blade servers and I was running VMware, and we were doing all this kind of stuff to manage the infrastructure, and then writing software on top of that, so it was a lot of work. I know I posted something on Twitter a few weeks ago, about how, when I was, when we were young, we used to have to carry a server on our back, uphill, both ways, to the data center, in the snow, with no shoes, and that's kind of how it felt, that you were doing a lot of these things.And then 2008, 2009, as I was kind of wrapping up my web development company, we were just in the process of actually saying it's too expensive at the colo. I think we were paying probably between like $5,000 and $7,000 a month between the ... we had leases on some of the servers, you're paying for electricity, you're paying for all these other things, and we were running a fair amount of services in there, so it seemed justifiable. We were making money on it, that wasn't the problem, but it just was a very expensive fixed cost for us, and when the cloud started coming along and I started actually building out the startup that I was working on, we were building all of that in the cloud, and as I was learning more about the cloud and how that works, I'm like, I should just move all this stuff that's in the co-location facility, move that over to the cloud and see what happens.And it took a couple of weeks to get that set up, and now, again, this is early, this is before ELB, this is before RDS, this is before, I mean, this was very, very early cloud. I mean, I think there was S3 and EC2. I think those were the two services that were available, with a few other things. I don't even think there were VPCs yet. But anyways, I moved everything over, took a couple of weeks to get that over, and essentially our bill to host all of our clients' sites and projects went from $5,000 to $7,000 a month, to $750 a month or something like that, and it's funny because had I done that earlier, I may not have sold off my web development company because it could have been much more profitable, so it was just an interesting move there.So we got into the cloud fairly early and started sort of leveraging that, and it was great to see all these things get added and all these specialty services, like RDS, and just taking the responsibility because I literally was installing Microsoft SQL server on an EC2 instance, which is not something that you want to do, you want to use RDS. It's just a much better way to do it, but anyways, so I was working for another startup, this was like startup number 17 or whatever it was I was working for, and we had this incident where we were using ... we had a pretty good setup. I mean, everything was on EC2 instances, but we were using DynamoDB to do some caching layers for certain things. We were using a sharded database, MySQL database, for product information, and so forth.So the system was pretty resilient, it was pretty, it handled all of the load testing we did and things like that, but then we actually got featured on Good Morning America, and they mentioned our app, it was the Power to Mobile app, and so we get mentioned on Good Morning America. I think it was Good Morning America. The Today Show? Good Morning America, I think it was. One of those morning shows, anyways, we got about 10,000 sign-ups in less than a minute, which was amazing, or it was just this huge spike in traffic, which was great. The problem was, is we had this really weak point in our system where we had to basically get a lock on the database in order to get an incremental-ID, and so essentially what happened is the database choked, and then as soon as the database choked, just to create user accounts, other users couldn't sign in and there was all kinds of problems, so we basically lost out on all of this capability.So I spent some time doing a lot of research and trying to figure out how do you scale that? How do you scale something that fast? How do you have that resilience in there? And there's all kinds of ways that we could have done it with traditional hardware, it's not like it wasn't possible to do with a slightly better strategy, but as I was digging around in AWS, I'm looking around at some different things, and we were, I was always in the console cause we were using Dynamo and some of those things, and I came across this thing that said "Lambda," with a little new thing next to it. I'm like, what the heck is this?So I click on that and I start reading about it, and I'm like, this is amazing. We don't have to spin up a server, we don't have to use Chef, or Puppet, or anything like that to spin up these machines. We can basically just say, when X happens, do Y, and it enlightened me, and this was early 2015, so this would have been right after Lambda went GA. Had never heard of Lambda as part of the preview, I mean, I wasn't sort of in that the re:Invent, I don't know, what would you call that? Vortex, maybe, is a good way to describe the event.Rebecca: Vortex sounds about right. That's about how it feels by the end.Jeremy: Right, exactly. So I wasn't really in that, I wasn't in that group yet, I wasn't part of that community, so I hadn't heard about it, and so as I started playing around with it, I immediately saw the value there, because, for me, as someone who again had managed servers, and it had built out really complex networking too. I think some of the things you don't think about when you move to an on-prem where you're managing your stuff, even what the cloud manages for you. I mean, we had firewalls, and we had to do all the firewall rules ourselves, right. I mean, I know you still have to do security groups and things like that in AWS, but just the level of complexity is a lot lower when you're in the cloud, and of course there's so many great services and systems that help you do that now.But just the idea of saying, "wait a minute, so if I have something happen, like a user signup, for example, and I don't have to worry about provisioning all the servers that I need in order to handle that," and again, it wasn't so much the server aspect of it as it was the database aspect of it, but one of the things that was sort of interesting about the idea of Serverless 2 was this asynchronous nature of it, this idea of being more event-driven, and that things don't have to happen immediately necessarily. So that just struck me as something where it seemed like it would reduce a lot, and again, this term has been overused, but the undifferentiated heavy-lifting, we use that term over and over again, but there is not a better term for that, right?Because there were just so many things that you have to do as a developer, as an ops person, somebody who is trying to straddle teams, or just a PM, or whatever you are, so many things that you have to do in order to get an application running, first of all, and then even more you have to do in order to keep it up and running, and then even more, if you start thinking about distributing it, or scaling it, or getting any of those things, disaster recovery. I mean, there's a million things you have to think about, and I saw serverless immediately as this opportunity to say, "Wait a minute, this could reduce a lot of that complexity and manage all of that for you," and then again, literally let you focus on the things that actually matter for your business.Rebecca: Okay. As someone who worked, how should I say this, in metatech, or the technology of technology in the serverless space, when you say that you were starting to build that without ELB even, or RDS, my level of anxiety is like, I really feel like I'm watching a slow horror film. I'm like, "No, no, no, no, no, you didn't, you didn't, you didn't have to do that, did you"?Jeremy: We did.Rebecca: So I applaud you for making it to the end of the film and still being with us.Jeremy: Well, the other thing ...Rebecca: Only one protagonist does that.Jeremy: Well, the other thing that's interesting too, about Serverless, and where it was in 2015, Lambda goes GA, this will give you some anxiety, there was no API gateway. So there was no way to actually trigger a Lambda function from a web request, right. There was no VPC access in Lambda functions, which meant you couldn't connect to a database. The only thing you do is connect via HDP, so you could connect to DynamoDB or things like that, but you could not connect directly to RDS, for example. So if you go back and you look at the timeline of when these things were released, I mean, if just from 2015, I mean, you literally feel like a caveman thinking about what you could do back then again, it's banging two sticks together versus where we are now, and the capabilities that are available to us.Rebecca: Yeah, you're sort of in Plato's cave, right, and you're looking up and you're like, "It's quite dark in here," and Lambda's up there, outside, sowing seeds, being like, "Come on out, it's dark in there". All right, so I imagine you discovering Lambda through the console is not a sentence you hear every day or general console discovery of a new product that will then sort of change the way that you build, and so I'm guessing maybe one of the reasons why you started your Off-by-none newsletter or Serverless Chats, right, is to be like, "How do I help tell others about this without them needing to discover it through the console"? But I'm curious what your why is. Why first the Off-by-none newsletter, which is one of my favorite things to receive every week, thank you for continuing to write such great content, and then why Serverless Chats? Why are we here today? Why are we at number 100? Which I'm so excited about every time I say it.Jeremy: And it's kind of crazy to think about all the people I've gotten a chance to talk to, but so, I think if you go back, I started writing blog posts maybe in 2015, so I haven't been doing it that long, and I certainly wasn't prolific. I wasn't consistent writing a blog post every week or every, two a week, like some people do now, which is kind of crazy. I don't know how that, I mean, it's hard enough writing the newsletter every week, never mind writing original content, but I started writing about Serverless. I think it wasn't until the beginning of 2018, maybe the end of 2017, and there was already a lot of great content out there. I mean, Ben Kehoe was very early into this and a lot of his stuff I read very early.I mean, there's just so many people that were very early in the space, I mean, Paul Johnson, I mean, just so many people, right, and I started reading what they were writing and I was like, "Oh, I've got some ideas too, I've been experimenting with some things, I feel like I've gotten to a point where what I could share could be potentially useful". So I started writing blog posts, and I think one of the earlier blog posts I wrote was, I want to say 2017, maybe it was 2018, early 2018, but was a post about serverless security, and what was great about that post was that actually got me connected with Ory Segal, who had started PureSec, and he and I became friends and that was the other great thing too, is just becoming part of this community was amazing.So many awesome people that I've met, but so I saw all this stuff people were writing and these things people were doing, and I got to maybe August of 2018, and I said to myself, I'm like, "Okay, I don't know if people are interested in what I'm writing". I wasn't writing a lot, but I was writing a little bit, but I wasn't sure people were overly interested in what I was writing, and again, that idea of the imposter syndrome, certainly everything was very early, so I felt a little bit more comfortable. I always felt like, well, maybe nobody knows what they're talking about here, so if I throw something into the fold it won't be too, too bad, but certainly, I was reading other things by other people that I was interested in, and I thought to myself, I'm like, "Okay, if I'm interested in this stuff, other people have to be interested in this stuff," but it wasn't easy to find, right.I mean, there was sort of a serverless Twitter, if you want to use that terminology, where a lot of people tweet about it and so forth, obviously it's gotten very noisy now because of people slapped that term on way too many things, but I don't want to have that discussion, but so I'm reading all this great stuff and I'm like, "I really want to share it," and I'm like, "Well, I guess the best way to do that would just be a newsletter."I had an email list for my own personal site that I had had a couple of hundred people on, and I'm like, "Well, let me just turn it into this thing, and I'll share these stories, and maybe people will find them interesting," and I know this is going to sound a little bit corny, but I have two teenage daughters, so I'm allowed to be sort of this dad-jokey type. I remember when I started writing the first version of this newsletter and I said to myself, I'm like, "I don't want this to be a newsletter." I was toying around with this idea of calling it an un-newsletter. I didn't want it to just be another list of links that you click on, and I know that's interesting to some people, but I felt like there was an opportunity to opine on it, to look at the individual links, and maybe even tell a story as part of all of the links that were shared that week, and I thought that that would be more interesting than just getting a list of links.And I'm sure you've seen over the last 140 issues, or however many we're at now, that there's been changes in the way that we formatted it, and we've tried new things, and things like that, but ultimately, and this goes back to the corny thing, I mean, one of the first things that I wanted to do was, I wanted to basically thank people for writing this stuff. I wanted to basically say, "Look, this is not just about you writing some content". This is big, this is important, and I appreciate it. I appreciate you for writing that content, and I wanted to make it more of a celebration really of the community and the people that were early contributors to that space, and that's one of the reasons why I did the Serverless Star thing.I thought, if somebody writes a really good article some week, and it's just, it really hits me, or somebody else says, "Hey, this person wrote a great article," or whatever. I wanted to sort of celebrate that person and call them out because that's one of the things too is writing blog posts or posting things on social media without a good following, or without the dopamine hit of people liking it, or re-tweeting it, and things like that, it can be a pretty lonely place. I mean, I know I feel that way sometimes when you put something out there, and you think it's important, or you think people might want to see it, and just not enough people see it.It's even worse, I mean, 240 characters, or whatever it is to write a tweet is one thing, or 280 characters, but if you're spending time putting together a tutorial or you put together a really good thought piece, or story, or use case, or something where you feel like this is worth sharing, because it could inspire somebody else, or it could help somebody else, could get them past a bump, it could make them think about something a different way, or get them over a hump, or whatever. I mean, that's just the kind of thing where I think people need that encouragement, and I think people deserve that encouragement for the work that they're doing, and that's what I wanted to do with Off-by-none, is make sure that I got that out there, and to just try to amplify those voices the best that I could. The other thing where it's sort of progressed, and I guess maybe I'm getting ahead of myself, but the other place where it's progressed and I thought was really interesting, was, finding people ...There's the heavy hitters in the serverless space, right? The ones we all know, and you can name them all, and they are great, and they produce amazing content, and they do amazing things, but they have pretty good engines to get their content out, right? I mean, some people who write for the AWS blog, they're on the AWS blog, right, so they're doing pretty well in terms of getting their things out there, right, and they've got pretty good engines.There's some good dev advocates too, that just have good Twitter followings and things like that. Then there's that guy who writes the story. I don't know, he's in India or he's in Poland or something like that. He writes this really good tutorial on how to do this odd edge-case for serverless. And you go and you look at their Medium and they've got two followers on Medium, five followers on Twitter or something like that. And that to me, just seems unfair, right? I mean, they've written a really good piece and it's worth sharing right? And it needs to get out there. I don't have a huge audience. I know that. I mean I've got a good following on Twitter. I feel like a lot of my Twitter followers, we can have good conversations, which is what you want on Twitter.The newsletter has continued to grow. We've got a good listener base for this show here. So, I don't have a huge audience, but if I can share that audience with other people and get other people to the forefront, then that's important to me. And I love finding those people and those ideas that other people might not see because they're not looking for them. So, if I can be part of that and help share that, that to me, it's not only a responsibility, it's just it's incredibly rewarding. So ...Rebecca: Yeah, I have to ... I mean, it is your 100th episode, so hopefully I can give you some kudos, but if celebrating others' work is one of your main tenets, you nail it every time. So ...Jeremy: I appreciate that.Rebecca: Just wanted you to know that. So, that's sort of the Genesis of course, of both of these, right?Jeremy: Right.Rebecca: That underpins the foundational how to share both works or how to share others' work through different channels. I'm wondering how it transformed, there's this newsletter and then of course it also has this other component, which is Serverless Chats. And that moment when you were like, "All right, this newsletter, this narrative that I'm telling behind serverless, highlighting all of these different authors from all these different global spaces, I'm going to start ... You know what else I want to do? I don't have enough to do, I'm going to start a podcast." How did we get here?Jeremy: Well, so the funny thing is now that I think about it, I think it just goes back to this tenet of fairness, this idea where I was fortunate, and I was able to go down to New York City and go to Serverless Days New York in late 2018. I was able to ... Tom McLaughlin actually got me connected with a bunch of great people in Boston. I live just outside of Boston. We got connected with a bunch of great people. And we started the Serverless Days Boston for 2019. And we were on that committee. I started traveling and I was going to conferences and I was meeting people. I went to re:Invent in 2018, which I know a lot of people just don't have the opportunity to do. And the interesting thing was, is that I was pulling aside brilliant people either in the hallway at a conference or more likely for a very long, deep discussion that we would have about something at a pub in Northern Ireland or something like that, right?I mean, these were opportunities that I was getting that I was privileged enough to get. And I'm like, these are amazing conversations. Just things that, for me, I know changed the way I think. And one of the biggest things that I try to do is evolve my thinking. What I thought a year ago is probably not what I think now. Maybe call it flip-flopping, whatever you want to call it. But I think that evolving your thinking is the most progressive thing that you can do and starting to understand as you gain new perspectives. And I was talking to people that I never would have talked to if I was just sitting here in my home office or at the time, I mean, I was at another office, but still, I wasn't getting that context. I wasn't getting that experience. And I wasn't getting those stories that literally changed my mind and made me think about things differently.And so, here I was in this privileged position, being able to talk to these amazing people and in some cases funny, because they're celebrities in their own right, right? I mean, these are the people where other people think of them and it's almost like they're a celebrity. And these people, I think they deserve fame. Don't get me wrong. But like as someone who has been on that side of it as well, it's ... I don't know, it's weird. It's weird to have fans in a sense. I love, again, you can be my friend, you don't have to be my fan. But that's how I felt about ...Rebecca: I'm a fan of my friends.Jeremy: So, a fan and my friend. So, having talked to these other people and having these really deep conversations on serverless and go beyond serverless to me. Actually I had quite a few conversations with some people that have nothing to do with serverless. Actually, Peter Sbarski and I, every time we get together, we only talk about the value of going to college for some reason. I don't know why. It has usually nothing to do with serverless. So, I'm having these great conversations with these people and I'm like, "Wow, I wish I could share these. I wish other people could have this experience," because I can tell you right now, there's people who can't travel, especially a lot of people outside of the United States. They ... it's hard to travel to the United States sometimes.So, these conversations are going on and I thought to myself, I'm like, "Wouldn't it be great if we could just have these conversations and let other people hear them, hopefully without bar glasses clinking in the background. And so I said, "You know what? Let's just try it. Let's see what happens. I'll do a couple of episodes. If it works, it works. If it doesn't, it doesn't. If people are interested, they're interested." But that was the genesis of that, I mean, it just goes back to this idea where I felt a little selfish having conversations and not being able to share them with other people.Rebecca: It's the very Jeremy Daly tenet slogan, right? You got to share it. You got to share it ...Jeremy: Got to share it, right?Rebecca: The more he shares it, it celebrates it. I love that. I think you do ... Yeah, you do a great job giving a megaphone so that more people can hear. So, in case you need a reminder, actually, I'll ask you, I know what the answer is to this, but do you know the answer? What was your very first episode of Serverless Chats? What was the name, and how long did it last?Jeremy: What was the name?Rebecca: Oh yeah. Oh yeah.Jeremy: Oh, well I know ... Oh, I remember now. Well, I know it was Alex DeBrie. I absolutely know that it was Alex DeBrie because ...Rebecca: Correct on that.Jeremy: If nobody, if you do not know Alex DeBrie, not only is he an AWS data hero, as well as the author of The DynamoDB Book, but he's also like the most likable person on the planet too. It is really hard if you've ever met Alex, that you wouldn't remember him. Alex and I started communicating, again, we met through the serverless space. I think actually he was working at Serverless Inc. at the time when we first met. And I think I met him in person, finally met him in person at re:Invent 2018. But he and I have collaborated on a number of things and so forth. So, let me think what the name of it was. "Serverless Purity Versus Practicality" or something like that. Is that close?Rebecca: That's exactly what it was.Jeremy: Oh, all right. I nailed it. Nailed it. Yes!Rebecca: Wow. Well, it's a great title. And I think ...Jeremy: Don't ask me what episode number 27 was though, because no way I could tell you that.Rebecca: And just for fun, it was 34 minutes long and you released it on June 17th, 2019. So, you've come a long way in a year and a half. That's some kind of wildness. So it makes sense, like, "THE," capital, all caps, bold, italic, author for databases, Alex DeBrie. Makes sense why you selected him as your guest. I'm wondering if you remember any of the ... What do you remember most about that episode? What was it like planning it? What was the reception of it? Anything funny happened recording it or releasing it?Jeremy: Yeah, well, I mean, so the funny thing is that I was incredibly nervous. I still am, actually a lot of guests that I have, I'm still incredibly nervous when I'm about to do the actual interview. And I think it's partially because I want to do justice to the content that they're presenting and to their expertise. And I feel like there's a responsibility to them, but I also feel like the guests that I've had on, some of them are just so smart, and the things they say, just I'm in awe of some of the things that come out of these people's mouths. And I'm like, "This is amazing and people need to hear this." And so, I feel like we've had really good episodes and we've had some okay episodes, but I feel like I want to try to keep that level up so that they owe that to my listener to make sure that there is high quality episode that, high quality information that they're going to get out of that.But going back to the planning of the initial episodes, so I actually had six episodes recorded before I even released the first one. And the reason why I did that was because I said, "All right, there's no way that I can record an episode and then wait a week and then record another episode and wait a week." And I thought batching them would be a good idea. And so, very early on, I had Alex and I had Nitzan Shapira and I had Ran Ribenzaft and I had Marcia Villalba and I had Erik Peterson from Cloud Zero. And so, I had a whole bunch of these episodes and I reached out to I think, eight or nine people. And I said, "I'm doing this thing, would you be interested in it?" Whatever, and we did planning sessions, still a thing that I do today, it's still part of the process.So, whenever I have a guest on, if you are listening to an episode and you're like, "Wow, how did they just like keep the thing going ..." It's not scripted. I don't want people to think it's scripted, but it is, we do review the outline and we go through some talking points to make sure that again, the high-quality episode and that the guest says all the things that the guest wants to say. A lot of it is spontaneous, right? I mean, the language is spontaneous, but we do, we do try to plan these episodes ahead of time so that we make sure that again, we get the content out and we talk about all the things we want to talk about. But with Alex, it was funny.He was actually the first of the six episodes that I recorded, though. And I wasn't sure who I was going to do first, but I hadn't quite picked it yet, but I recorded with Alex first. And it was an easy, easy conversation. And the reason why it was an easy conversation was because we had talked a number of times, right? It was that in a pub, talking or whatever, and having that friendly chat. So, that was a pretty easy conversation. And I remember the first several conversations I had, I knew Nitzan very well. I knew Ran very well. I knew Erik very well. Erik helped plan Serverless Days Boston with me. And I had known Marcia very well. Marcia actually had interviewed me when we were in Vegas for re:Invent 2018.So, those were very comfortable conversations. And so, it actually was a lot easier to do, which probably gave me a false sense of security. I was like, "Wow, this was ... These came out pretty well." The conversations worked pretty well. And also it was super easy because I was just doing audio. And once you add the video component into it, it gets a little bit more complex. But yeah, I mean, I don't know if there's anything funny that happened during it, other than the fact that I mean, I was incredibly nervous when we recorded those, because I just didn't know what to expect. If anybody wants to know, "Hey, how do you just jump right into podcasting?" I didn't. I actually was planning on how can I record my voice? How can I get comfortable behind a microphone? And so, one of the things that I did was I started creating audio versions of my blog posts and posting them on SoundCloud.So, I did that for a couple of ... I'm sorry, a couple of blog posts that I did. And that just helped make me feel a bit more comfortable about being able to record and getting a little bit more comfortable, even though I still can't stand the sound of my own voice, but hopefully that doesn't bother other people.Rebecca: That is an amazing ... I think we so often talk about ideas around you know where you want to go and you have this vision and that's your goal. And it's a constant reminder to be like, "How do I make incremental steps to actually get to that goal?" And I love that as a life hack, like, "Hey, start with something you already know that you wrote and feel comfortable in and say it out loud and say it out loud again and say it out loud again." And you may never love your voice, but you will at least feel comfortable saying things out loud on a podcast.Jeremy: Right, right, right. I'm still working on the, "Ums" and, "Ahs." I still do that. And I don't edit those out. That's another thing too, actually, that one of the things I do want people to know about this podcast is these are authentic conversations, right? I am probably like ... I feel like I'm, I mean, the most authentic person that I know. I just want authenticity. I want that out of the guests. The idea of putting together an outline is just so that we can put together a high quality episode, but everything is authentic. And that's what I want out of people. I just want that authenticity, and one of the things that I felt kept that, was leaving in, "Ums" and, "Ahs," you know what I mean? It's just, it's one of those things where I know a lot of podcasts will edit those out and it sounds really polished and finished.Again, I mean, I figured if we can get the clinking glasses out from the background of a bar and just at least have the conversation that that's what I'm trying to achieve. And we do very little editing. We do cut things out here and there, especially if somebody makes a mistake or they want to start something over again, we will cut that out because we want, again, high quality episodes. But yeah, but authenticity is deeply important to me.Rebecca: Yeah, I think it probably certainly helps that neither of us are robots because robots wouldn't say, "Um" so many times. As I say, "Uh." So, let's talk about, Alex DeBrie was your first guest, but there's been a hundred episodes, right? So, from, I might say the best guest, as a hundredth episode guests, which is our very own Jeremy Daly, but let's go back to ...Jeremy: I appreciate that.Rebecca: Your guests, one to 99. And I mean, you've chatted with some of the most thoughtful, talented, Serverless builders and architects in the industry, and across coincident spaces like ML and Voice Technology, Chaos Engineering, databases. So, you started with Alex DeBrie and databases, and then I'm going to list off some names here, but there's so many more, right? But there's the Gunnar Grosches, and the Alexandria Abbasses, and Ajay Nair, and Angela Timofte, James Beswick, Chris Munns, Forrest Brazeal, Aleksandar Simovic, and Slobodan Stojanovic. Like there are just so many more. And I'm wondering if across those hundred conversations, or 99 plus your own today, if you had to distill those into two or three lessons, what have you learned that sticks with you? If there are emerging patterns or themes across these very divergent and convergent thinkers in the serverless space?Jeremy: Oh, that's a tough question.Rebecca: You're welcome.Jeremy: So, yeah, put me on the spot here. So, yeah, I mean, I think one of the things that I've, I've seen, no matter what it's been, whether it's ML or it's Chaos Engineering, or it's any of those other observability and things like that. I think the common thing that threads all of it is trying to solve problems and make people's lives easier. That every one of those solutions is like, and we always talk about abstractions and, and higher-level abstractions, and we no longer have to write ones and zeros on punch cards or whatever. We can write languages that either compile or interpret it or whatever. And then the cloud comes along and there's things we don't have to do anymore, that just get taken care of for us.And you keep building these higher level of abstractions. And I think that's a lot of what ... You've got this underlying concept of letting somebody else handle things for you. And then you've got this whole group of people that are coming at it from a number of different angles and saying, "Well, how will that apply to my use case?" And I think a lot of those, a lot of those things are very, very specific. I think things like the voice technology where it's like the fact that serverless powers voice technology is only interesting in the fact as to say that, the voice technology is probably the more interesting part, the fact that serverless powers it is just the fact that it's a really simple vehicle to do that. And basically removes this whole idea of saying I'm building voice technology, or I'm building a voice app, why do I need to worry about setting up servers and all this kind of stuff?It just takes that away. It takes that out of the equation. And I think that's the perfect idea of saying, "How can you take your use case, fit serverless in there and apply it in a way that gets rid of all that extra overhead that you shouldn't have to worry about." And the same thing is true of machine learning. And I mean, and SageMaker, and things like that. Yeah, you're still running instances of it, or you still have to do some of these things, but now there's like SageMaker endpoints and some other things that are happening. So, it's moving in that direction as well. But then you have those really high level services like NLU API from IBM, which is the Watson Natural Language Processing.You've got AP recognition, you've got the vision API, you've got sentiment analysis through all these different things. So, you've got a lot of different services that are very specific to machine learning and solving a discrete problem there. But then basically relying on serverless or at least presenting it in a way that's serverless, where you don't have to worry about it, right? You don't have to run all of these Jupiter notebooks and things like that, to do machine learning for a lot of cases. This is one of the things I talk about with Alexandra Abbas, was that these higher level APIs are just taking a lot of that responsibility or a lot of that heavy lifting off of your plate and allowing you to really come down and focus on the things that you're doing.So, going back to that, I do think that serverless, that the common theme that I see is that this idea of worrying about servers and worrying about patching things and worrying about networking, all that stuff. For so many people now, that's just not even a concern. They didn't even think about it. And that's amazing to think of, compute ... Or data, or networking as a utility that is now just available to us, right? And I mean, again, going back to my roots, taking it for granted is something that I think a lot of people do, but I think that's also maybe a good thing, right? Just don't think about it. I mean, there are people who, they're still going to be engineers and people who are sitting in the data center somewhere and racking servers and doing it, that's going to be forever, right?But for the things that you're trying to build, that's unimportant to you. That is the furthest from your concern. You want to focus on the problem that you're trying to solve. And so I think that, that's a lot of what I've seen from talking to people is that they are literally trying to figure out, "Okay, how do I take what I'm doing, my use case, my problem, how do I take that to the next level, by being able to spend my cycles thinking about that as opposed to how I'm going to serve it up to people?"Rebecca: Yeah, I think it's the mantra, right, of simplify, simplify, simplify, or maybe even to credit Bruce Lee, be like water. You're like, "How do I be like water in this instance?" Well, it's not to be setting up servers, it's to be doing what I like to be doing. So, you've interviewed these incredible folks. Is there anyone left on your list? I'm sure there ... I mean, I know that you have a large list. Is there a few key folks where you're like, "If this is the moment I'm going to ask them, I'm going to say on the hundredth episode, 'Dear so-and-so, I would love to interview you for Serverless Chats.'" Who are you asking?Jeremy: So, this is something that, again, we have a stretch list of guests that we attempt to reach out to every once in a while just to say, "Hey, if we get them, we get them." But so, I have a long list of people that I would absolutely love to talk to. I think number one on my list is certainly Werner Vogels. I mean, I would love to talk to Dr. Vogels about a number of things, and maybe even beyond serverless, I'm just really interested. More so from a curiosity standpoint of like, "Just how do you keep that in your head?" That vision of where it's going. And I'd love to drill down more into the vision because I do feel like there's a marketing aspect of it, that's pushing on him of like, "Here's what we have to focus on because of market adoption and so forth. And even though the technology, you want to move into a certain way," I'd be really interesting to talk to him about that.And I'd love to talk to him more too about developer experience and so forth, because one of the things that I love about AWS is that it gives you so many primitives, but at the same time, the thing I hate about AWS is it gives you so many primitives. So, you have to think about 800 services, I know it's not that many, but like, what is it? 200 services, something like that, that all need to kind of connect together. And I love that there's that diversity in those capabilities, it's just from a developer standpoint, it's really hard to choose which ones you're supposed to use, especially when several services overlap. So, I'm just curious. I mean, I'd love to talk to him about that and see what the vision is in terms of, is that the idea, just to be a salad bar, to be the Golden Corral of cloud services, I guess, right?Where you can choose whatever you want and probably take too much and then not use a lot of it. But I don't know if that's part of the strategy, but I think there's some interesting questions, could dig in there. Another person from AWS that I actually want to talk to, and I haven't reached out to her yet just because, I don't know, I just haven't reached out to her yet, but is Brigid Johnson. She is like an IAM expert. And I saw her speak at re:Inforce 2019, it must have been 2019 in Boston. And it was like she was speaking a different language, but she knew IAM so well, and I am not a fan of IAM. I mean, I'm a fan of it in the sense that it's necessary and it's great, but I can't wrap my head around so many different things about it. It's such a ...It's an ongoing learning process and when it comes to things like being able to use tags to elevate permissions. Just crazy things like that. Anyways, I would love to have a conversation with her because I'd really like to dig down into sort of, what is the essence of IAM? What are the things that you really have to think about with least permission? Especially applying it to serverless services and so forth. And maybe have her help me figure out how to do some of the cross role IAM things that I'm trying to do. Certainly would love to speak to Jeff Barr. I did meet Jeff briefly. We talked for a minute, but I would love to chat with him.I think he sets a shining example of what a developer advocate is. Just the way that ... First of all, he's probably the only person alive who knows every service at AWS and has actually tried it because he writes all those blog posts about it. So that would just be great to pick his brain on that stuff. Also, Adrian Cockcroft would be another great person to talk to. Just this idea of what he's done with microservices and thinking about the role, his role with Netflix and some of those other things and how all that kind of came together, I think would be a really interesting conversation. I know I've seen this in so many of his presentations where he's talked about the objections, what were the objections of Lambda and how have you solved those objections? And here's the things that we've done.And again, the methodology of that would be really interesting to know. There's a couple of other people too. Oh, Sam Newman who wrote Building Microservices, that was my Bible for quite some time. I had it on my iPad and had a whole bunch of bookmarks and things like that. And if anybody wants to know, one of my most popular posts that I've ever written was the ... I think it was ... What is it? 16, 17 architectural patterns for serverless or serverless microservice patterns on AWS. Can't even remember the name of my own posts. But that post was very, very popular. And that even was ... I know Matt Coulter who did the CDK. He's done the whole CDK ... What the heck was that? The CDKpatterns.com. That was one of the things where he said that that was instrumental for him in seeing those patterns and being able to use those patterns and so forth.If anybody wants to know, a lot of those patterns and those ideas and those ... The sort of the confidence that I had with presenting those patterns, a lot of that came from Sam Newman's work in his Building Microservices book. So again, credit where credit is due. And I think that that would be a really fascinating conversation. And then Simon Wardley, I would love to talk to. I'd actually love to ... I actually talked to ... I met Lin Clark in Vegas as well. She was instrumental with the WebAssembly stuff, and I'd love to talk to her. Merritt Baer. There's just so many people. I'm probably just naming too many people now. But there are a lot of people that I would love to have a chat with and just pick their brain.And also, one of the things that I've been thinking about a lot on the show as well, is the term "serverless." Good or bad for some people. Some of the conversations we have go outside of serverless a little bit, right? There's sort of peripheral to it. I think that a lot of things are peripheral to serverless now. And there are a lot of conversations to be had. People who were building with serverless. Actually real-world examples.One of the things I love hearing was Yan Cui's "Real World Serverless" podcast where he actually talks to people who are building serverless things and building them in their organizations. That is super interesting to me. And I would actually love to have some of those conversations here as well. So if anyone's listening and you have a really interesting story to tell about serverless or something peripheral to serverless please reach out and send me a message and I'd be happy to talk to you.Rebecca: Well, good news is, it sounds like A, we have at least ... You've got at least another a hundred episodes planned out already.Jeremy: Most likely. Yeah.Rebecca: And B, what a testament to Sam Newman. That's pretty great when your work is referred to as the Bible by someone. As far as in terms of a tome, a treasure trove of perhaps learnings or parables or teachings. I ... And wow, what a list of other folks, especially AWS power ... Actually, not AWS powerhouses. Powerhouses who happened to work at AWS. And I think have paved the way for a ton of ways of thinking and even communicating. Right? So I think Jeff Barr, as far as setting the bar, raising the bar if you will. For how to teach others and not be so high-level, or high-level enough where you can follow along with him, right? Not so high-level where it feels like you can't achieve what he's showing other people how to do.Jeremy: Right. And I just want to comment on the Jeff Barr thing. Yeah.Rebecca: Of course.Jeremy: Because again, I actually ... That's my point. That's one of the reasons why I love what he does and he's so perfect for that position because he's relatable and he presents things in a way that isn't like, "Oh, well, yeah, of course, this is how you do this." I mean, it's not that way. It's always presented in a way to make it accessible. And even for services that I'm not interested in, that I know that I probably will never use, I generally will read Jeff's post because I feel it gives me a good overview, right?Rebecca: Right.Jeremy: It just gives me a good overview to understand whether or not that service is even worth looking at. And that's certainly something I don't get from reading the documentation.Rebecca: Right. He's inviting you to come with him and understanding this, which is so neat. So I think ... I bet we should ... I know that we can find all these twitter handles for these folks and put them in the show notes. And I'm especially ... I'm just going to say here that Werner Vogels's twitter handle is @Werner. So maybe for your hundredth, all the listeners, everyone listening to this, we can say, "Hey, @Werner, I heard that you're the number one guest that Jeremy Daly would like to interview." And I think if we get enough folks saying that to @Werner ... Did I say that @Werner, just @Werner?Jeremy: I think you did.Rebecca: Anyone if you can hear it.Jeremy: Now listen, he did retweet my serverless musical that I did. So ...Rebecca: That's right.Jeremy: I'm sort of on his radar maybe.Rebecca: Yeah. And honestly, he loves serverless, especially with the number of customers and the types of customers and ... that are doing incredible things with it. So I think we've got a chance, Jeremy. I really do. That's what I'm trying to say.Jeremy: That's good to know. You're welcome anytime. He's welcome anytime.Rebecca: Do we say that @Werner, you are welcome anytime. Right. So let's go back to the genesis, not necessarily the genesis of the concept, right? But the genesis of the technology that spurred all of these other technologies, which is AWS Lambda. And so what ... I don't think we'd be having these conversations, right, if AWS Lambda was not released in late 2014, and then when GA I believe in 2015.Jeremy: Right.Rebecca: And so subsequently the serverless paradigm was thrust into the spotlight. And that seems like eons ago, but also three minutes ago.Jeremy: Right.Rebecca: And so I'm wondering ... Let's talk about its evolution a bit and a bit of how if you've been following it for this long and building it for this long, you've covered topics from serverless CI/CD pipelines, observability. We already talked about how it's impacted voice technologies or how it's made it easy. You can build voice technology without having to care about what that technology is running on.Jeremy: Right.Rebecca: You've even talked about things like the future and climate change and how it relates to serverless. So some of those sort of related conversations that you were just talking about wanting to have or having had with previous guests. So as a host who thinks about these topics every day, I'm wondering if there's a topic that serverless hasn't touched yet or one that you hope it will soon. Those types of themes, those threads that you want to pull in the next 100 episodes.Jeremy: That's another tough question. Wow. You got good questions.Rebecca: That's what I said. Heavy hitters. I told you I'd be bringing it.Jeremy: All right. Well, I appreciate that. So that's actually a really good question. I think the evolution of serverless has seen its ups and downs. I think one of the nice things is you look at something like serverless that was so constrained when it first started. And it still has constraints, which are good. But it ... Those constraints get lifted. We just talked about Adrian's talks about how it's like, "Well, I can't do this, or I can't do that." And then like, "Okay, we'll add some feature that you can do that and you can do that." And I think that for the most part, and I won't call it anything specific, but I think for the most part that the evolution of serverless and the evolution of Lambda and what it can do has been thoughtful. And by that I mean that it was sort of like, how do we evolve this into a way that doesn't create too much complexity and still sort of holds true to the serverless ethos of sort of being fairly easy or just writing code.And then, but still evolve it to open up these other use cases and edge cases. And I think that for the most part, that it has held true to that, that it has been mostly, I guess, a smooth ride. There are several examples though, where it didn't. And I said I wasn't going to call anything out, but I'm going to call this out. I think RDS proxy wasn't great. I think it works really well, but I don't think that's the solution to the problem. And it's a band-aid. And it works really well, and congrats to the engineers who did it. I think there's a story about how two different teams were trying to build it at the same time actually. But either way, I look at that and I say, "That's a good solution to the problem, but it's not the solution to the problem."And so I think serverless has stumbled in a number of ways to do that. I also feel EFS integration is super helpful, but I'm not sure that's the ultimate goal to share ... The best way to share state. But regardless, there are a whole bunch of things that we still need to do with serverless. And a whole bunch of things that we still need to add and we need to build, and we need to figure out better ways to do maybe. But I think in terms of something that doesn't get talked about a lot, is the developer experience of serverless. And that is, again I'm not trying to pitch anything here. But that's literally what I'm trying to work on right now in my current role, is just that that developer experience of serverless, even though there was this thoughtful approach to adding things, to try to check those things off the list, to say that it can't do this, so we're going to make it be able to do that by adding X, Y, and Z.As amazing as that has been, that has added layers and layers of complexity. And I'll go back way, way back to 1997 in my dorm room. CGI-bins, if people are not familiar with those, essentially just running on a Linux server, it was a way that it would essentially run a Perl script or other types of scripts. And it was essentially like you're running PHP or you're running Node, or you're running Ruby or whatever it was. So it would run a programming language for you, run a script and then serve that information back. And of course, you had to actually know ins and outs, inputs and outputs. It was more complex than it is now.But anyways, the point is that back then though, once you had the script written. All you had to do is ... There's a thing called FTP, which I'm sure some people don't even know what that is anymore. File transfer protocol, where you would basically say, take this file from my local machine and put it on this server, which is a remote machine. And you would do that. And the second you did that, magically it was updated and you had this thing happening. And I remember there were a lot of jokes way back in the early, probably 2017, 2018, that serverless was like the new CGI-bin or something like that. But more as a criticism of it, right? Or it's just CGI-bins reborn, whatever. And I actually liked that comparison. I felt, you know what? I remember the days where I just wrote code and I just put it to some other server where somebody was dealing with it, and I didn't even have to think about that stuff.We're a long way from that now. But that's how serverless felt to me, one of the first times that I started interacting with it. And I felt there was something there, that was something special about it. And I also felt the constraints of serverless, especially the idea of not having state. People rely on things because they're there. But when you don't have something and you're forced to think differently and to make a change or find a way to work around it. Sometimes workarounds, turn into best practices. And that's one of the things that I saw with serverless. Where people were figuring out pretty quickly, how to build applications without state. And then I think the problem is that you had a lot of people who came along, who were maybe big customers of AWS. I don't know.I'm not going to say that you might be influenced by large customers. I know lots of places are. That said, "We need this." And maybe your ... The will gets bent, right. Because you just... you can only fight gravity for so long. And so those are the kinds of things where I feel some of the stuff has been patchwork and those patchwork things haven't ruined serverless. It's still amazing. It's still awesome what you can do within the course. We're still really just focusing on fast here, with everything else that's built. With all the APIs and so forth and everything else that's serverless in the full-service ecosystem. There's still a lot of amazing things there. But I do feel we've become so complex with building serverless applications, that you can't ... the Hello World is super easy, but if you're trying to build an actual application, it's a whole new mindset.You've got to learn a whole bunch of new things. And not only that, but you have to learn the cloud. You have to learn all the details of the cloud, right? You need to know all these different things. You need to know cloud formation or serverless framework or SAM or something like that, in order to get the stuff into the cloud. You need to understand the infrastructure that you're working with. You may not need to manage it, but you still have to understand it. You need to know what its limitations are. You need to know how it connects. You need to know what the failover states are like.There's so many things that you need to know. And to me, that's a burden. And that's adding new types of undifferentiated heavy-lifting that shouldn't be there. And that's the conversation that I would like to have continuing to move forward is, how do you go back to a developer experience where you're saying you're taking away all this stuff. And again, to call out Werner again, he constantly says serverless is about writing code, but ask anybody who builds serverless applications. You're doing a lot more than writing code right now. And I would love to see us bring the conversation back to how do we get back there?Rebecca: Yeah. I think it kind of goes back to ... You and I have talked about this notion of an ode to simplicity. And it's sort of what you want to write into your ode, right? If we're going to have an ode to simplicity, how do we make sure that we keep the simplicity inside of the ode?Jeremy: Right.Rebecca:So I've got ... I don't know if you've seen these.Jeremy: I don't know.Rebecca: But before I get to some wrap-up questions more from the brainwaves of Jeremy Daly, I don't want to forget to call out some long-time listener questions. And they wrote in a via Twitter and they wanted to perhaps pick your brain on a few things.Jeremy: Okay.Rebecca: So I don't know if you're ready for this.Jeremy: A-M-A. A-M-A.Rebecca: I don't know if you've seen these. Yeah, these are going to put you in the ...Jeremy: A-M-A-M. Wait, A-M-A-A? Asked me almost anything? No, go ahead. Ask me anything.Rebecca: A-M-A-A. A-M-J. No. Anyway, we got it. Ask Jeremy almost anything.Jeremy: There you go.Rebecca: So there's just three to tackle for today's episode that I'm going to lob at you. One is from Ken Collins. "What will it take to get you back to a relational database of Lambda?"Jeremy: Ooh, I'm going to tell you right now. And without a doubt, Aurora Serverless v2. I played around with that right after re:Invent 2000. What was it? 20. Yeah. Just came out, right? I'm trying to remember what year it is at this point.Rebecca: Yes. Indeed.Jeremy: When that just ... Right when that came out. And I had spent a lot of time with Aurora Serverless v1, I guess if you want to call it that. I spent a lot of time with it. I used it on a couple of different projects. I had a lot of really good success with it. I had the same pains as everybody else did when it came to scaling and just the slowness of the scaling and then ... And some of the step-downs and some of those things. There were certainly problems with it. But v2 just the early, early preview version of v2 was ... It was just a marvel of engineering. And the way that it worked was just ... It was absolutely fascinating.And I know it's getting ready or it's getting close, I think, to being GA. And when that becomes GA, I think I will have a new outlook on whether or not I can fit RDS into my applications. I will say though. Okay. I will say, I don't think that transactional applications should be using relational databases though. One of the things that was sort of a nice thing about moving to serverless, speak

On todays guest-free rant we'll discuss Prisma JS, Typescript ORM's/query builders, AWS Cognito, and why you should build everything yourself instead of trusting other peoples code. Postgres, NPM, FaunaDB and other Javascript topics also continue to exist. Questions? Comments? Find out more on our site podcast.unrulysoftware.com (https://podcast.unrulysoftware.com). You can join our discord (https://discord.gg/NGP2nWtFJb) to chat about tech anytime directly with the hosts.

You can find Keston on Linkedin or by email at keston@squirb.com.Check out Squirb at www.squirb.com and FaunaDB at fauna.com.For more stories about real-world use of serverless technologies, please follow us on Twitter as @RealWorldSls and subscribe to this podcast.To learn how to build production-ready serverless applications, check out my upcoming workshops.Opening theme song:Cheery Monday by Kevin MacLeodLink: https://incompetech.filmmusic.io/song/3495-cheery-mondayLicense: http://creativecommons.org/licenses/by/4.0

This week, Chris and Martin chat to Evan Weaver, CTO and co-founder at Fauna. The company has developed a database as a service, available simply through a globally available API. Fauna calls the platform “client serverless”. How can a database be made globally available and still guarantee performance, resiliency and most important, data consistency? Of […] The post #182 – FaunaDB – Client Serverless Computing appeared first on Storage Unpacked Podcast.

Evan Weaver (Co-Founder/CTO @Fauna) talks about FaunaDB, and enabling serverless, NoOps databases as new applications architectures emerge around APIs, Jamstack and other distributed systems. SHOW: 474SHOW SPONSOR LINKS:Learn more about Fauna: https://www.fauna.com/serverlessTry FaunaDB for Free: https://dashboard.fauna.com/accounts/registerCloudAcademy -Build hands-on technical skills. Get measurable results. Get 50% of the monthly price of CloudAcademy by using code CLOUDCASTDatadog Security Monitoring Homepage - Modern Monitoring and AnalyticsTry Datadog yourself by starting a free, 14-day trial today. Listeners of this podcast will also receive a free Datadog T-shirt.CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotwPodCTL Podcast is Back (Enterprise Kubernetes) - http://podctl.comSHOW NOTES:Fauna HomepageThe 4th generation application model (client-serverless)Supported Languages/ Frameworks: https://docs.fauna.com/fauna/current/drivers/Topic 1 - Welcome to the show. You’ve been at the forefront of really interesting tech in the past. Can you tell us a little bit about your background?Topic 2 - Over the last few months, we’ve been digging into newer distributed architecture elements (Jamstack, GraphQL, Serverless, etc.). But we haven’t dug into the role of data in these architectures. Help us understand this 4th generation architecture, or client-serverless, and the role of data.Topic 3 - Data is still stored somewhere, but its usage is now made up of a bunch of data coming together in various contexts. How does Fauna fit into this new world when clients and APIs play as much of a role as “the database”?Topic 4 - As you talk to people that come from a SQL / Relational-DB background, how does the discussion go in terms of how things change and some of the common bottlenecks/problems that Fauna can solve for them? Topic 5 - Databases have traditionally been difficult to scale, protect, maintain, etc. How does you enable the data layer or API access to now follow a NoOps model? Topic 6 - Where are the best places for people to engage to learn more about how to not only use the Jamstack architecture, but apply the principles around Fauna for Data/API management? FEEDBACK?Email: show at thecloudcast dot netTwitter: @thecloudcastnet

Hear Fauna’s Senior Product Manager, Lewis King, give a brief overview of Jamstack, FaunaDB and Fauna’s ecosystem.

Quick show notes Our Guest: Tamas Piros What he'd like for you to see: JAMstack.training His JAMstack Jams: "There's an API for that!" Formspree | Auth0 | Snipcart | Cloudinary His Musical Jam: Reggaeton in general, but J. Balvin specifically | And tis the season for some traditional Christmas Music :D Other Technology Mentioned 11ty Our sponsor this week: [https://takeshape.io/thatsmyjamstack]TakeShape.io Transcript Bryan Robinson 0:02 Hello, everyone, welcome to another episode of that's my jam into the podcast where we ask the burning question, what is your jam in the JAMstack. I'm your host, Bryan Robinson. And in today's episode, we're talking to a Cloudinary developer evangelist and awesome technical trainer, who just started jamstack.training Tamas Piros. Bryan Robinson 0:21 Today's episode is sponsored by TakeShape, a content platform made specifically for the JAMstack. Stick around after the episode to hear more or head over to takeshape.io/thatsmyjamstack for more information. Bryan Robinson 0:34 Hey, Tamas, thanks for being on the podcast today. Tamas Piros 0:37 Thank you very much for having me. Bryan Robinson 0:38 So if you don't mind, give us a little little overview of who you are, what you do for work, what you do for fun, that kind of thing. Tamas Piros 0:45 Sure. So I work as a developer evangelist for a company called Cloudinary thata does sort of cloud based media management -- media being images, videos. So been with them for Over a year, and before that I've worked at various other companies that can NoSQL company as a technical instructor. Tamas Piros 1:06 And as you know, as part of the role, I basically go and travel the world pretty much I attend conferences, I do talks and workshops at meetups and in various other places. And I also own a training company, which is called fullstack.training, where I basically try to deliver training courses about various pieces of web technologies. So that's what I do professionally. Tamas Piros 1:31 On the personal side of things, I always point out that I am a water polo player, which is a very tough sport for those of you who actually know it. And I like to say that as a coach, as a water polo coach, I have a gold and a bronze medal from some international tournaments. And as a player, I also have a third position in a tournament so I have a cup. So these are my little personal achievements Bryan Robinson 2:00 You're potentially the the best athlete we've had on the show so far. So that's, that's cool. I don't know water polo sounds incredibly difficult to me. Tamas Piros 2:10 It is it is. But you know, if you if you train and if you dedicate some time to it, then then it can be a little fun. Bryan Robinson 2:17 Very cool. So you're, you're working at Cloudinary. So obviously, professionally, you're doing quite a bit of JAMstack stuff, anything outside of work that you're working on JAMstack wise, or is it all just kind of that, that work environment? Tamas Piros 2:30 It's mostly the work environment. The other thing that I work on is I have you know, my own personal site, which is a site about me about what I do is like a one page thing. So I build that using 11ty, which is one of the static site generators and I'm hosting it on Netlify. The only thing that I do really, I also have, you know, my company's website and I have a blog on there, which one day if time permits and when you know, the wind blows from the right direction. I will also sort of transform into JAMstack site. But you know, I don't know what's going to happen. Bryan Robinson 3:08 Sure. So you've got you've got the full stack training company, but you're also doing some JAMstack stuff with that too, right?Unknown Speaker 3:14 Yes. So I basically, registered jamstack.training as a domain. And I have a site available up there, which is basically just using teachable, which is a very good service that I like. So they basically allow you to create your online sort of video portal, where you can upload your videos manage your courses, users can register so everything is happening out from the box. Tamas Piros 3:42 So on that site, I basically have two free courses available at the moment. One is an introduction to JAMstack, which is it's really a non technical thing. There's, you know, there's no discussions about code. I just wanted to create this course so that anyone even coming from a non technical basis can kind of understand what the JAMstack is. The second course that I have there is how to create the blog using 11ty and some other services. And then at the moment, I am recording another one, which is create an e commerce store using Gatsby and Snipcart. I actually tweeted about that today. It's it's a Christmas store with all his Christmas ornaments and stuff. So it's basically pressuring myself to finish it before Christmas, Tamas Piros 4:30 Yeah, otherwise, it's not going to work. So yeah, I have that side. I tried to, you know, use that to educate people about the JAMstack. And as I said, all the courses there are for free. So it's, I'm trying to, you know, produce as many courses as I can for free and put them out there. Bryan Robinson 4:47 Very cool. And have you so you've only got a couple courses there so far, but how does it feel doing the JAMstack side of things in terms of education versus that full stack side. Tamas Piros 4:59 So with the fullstack side I was the courses that I had weren't always necessary about, you know, always full stack was sometimes just NodeJS, but I have to say it does help in a stance that in a very relatively short video course I can talk about like how to create an entire ecommerce site that involves, you know, how to develop it, how to sort of deploy it, how to enhance it by adding, you know, just, you know, snipcart, I mean, the whole experience of making this happen is is wonderful, right? Tamas Piros 5:39 Whereas before, I had a course where I was talking about, you know, angular and node and express and full stack JavaScript and this and that, and that's like a very long course to put everything together. And I didn't even talk about how to deploy that, right, because I thought, you know, let's not focus on that. Let's focus on the actual code, whereas now, I can very easily just talk about how to deploy stuff Bryan Robinson 6:03 It lets you give like that full application feeling to all the all your courses at that point. Tamas Piros 6:08 Exactly. Right. So in about 30 or 40 videos, you know, we start from nothing, and we end up having an app that works and is deployed, which is, I think, pretty amazing Bryan Robinson 6:17 I agree. That is kind of one of my favorite things on the JAMstack. Bryan Robinson 6:21 So let's talk about technologies. You've mentioned the 11ty, A little bit, Obviously, you're working at Cloudinary, what are kind of your jams in the JAMstack. What are your favorite technologies, philosophies, methodologies? Tamas Piros 6:32 Sure. So I really like the the letter A in the JAMstack. You know, the API bit, because, and I just did a talk recently, and I made the joke that you know, how about 10 years ago, we used to say, oh, there's an app for that, you know, just about, you know, Apple's iPhone app store, you could do whatever you wanted. Tamas Piros 6:51 And I think now, it's safe to say that there's an API for that, right. So it doesn't matter what you want to do, or how complex that thing is. I'm pretty sure that an API out there that is available for you. So, you know a few examples that I've used. And these are my favorite ones as well like Formspree. Like, the bane of my life was contact forms because I had to have a server it had to have some, you know, mail service up and running. And then you had to have something that processes the form and sends it and it's like, oh my god, And then with Formspree just have the form elements. You have the action attribute, and you literally say formspree.io/emailaddress, and you're up and running. I mean, how simple Tamas Piros 7:36 Other things like, Auth0 for authentication, traditionally speaking was always very difficult, right? With their API's. It's, it's really simple. Or the recent recording that I'm doing for the e commerce stuff, right. So as I said, I'm using Snipcart. I'm also using Cloudinary to display product images, right. Tamas Piros 7:58 So the combination of these two API's means that with Snipcart, I can just have an entire checkout flow, including you know, shipping, shipping details, payments, and everything embedded in my application in just like three or four lines of code, and that's pretty much it, everything works. And then they have their own dashboard where they have the stats, how many sales do this and then I'm also displaying products using Cloudinary which is, you know, displaying images and you know, videos on your website is traditionally speaking kind of challenging because you can go wrong with that. Tamas Piros 8:32 And so here's an example what I'm doing in this app. I have this sort of like a jumper on a lady that is like a Christmasy jumper that I'm you know, selling in this wonderful ecommerce store. And Cloudinary has a feature to replace the color with another color. So as opposed to me generating you know, five or six different images from the same product to say what was yellow should now be red, and it should not be green should not be blue, and then just display those like, and that's it, you know, they can achieve whatever I want, using the API's. Tamas Piros 9:06 And I can let all these companies to deal with, you know, scaling and security. And you know, because what happens when my ecommerce store becomes very popular, right? I don't need to worry about, oh, how I'm going to handle the increased load of the checkout flow, because Snipcart is responsible for that service. And I'm sure they're going to take care of that, right. So this is what I really enjoy and loving the JAMstack. So that's why I like to point out there, you know, I'm all for ace. And I'm sure there's an API for everything that I ever wanted to do on the web. Bryan Robinson 9:39 Definitely. And I actually really enjoyed the idea of the the Christmas shop, especially in terms of that scalability, because the Christmas shop may not do a lot of traffic from January to October, but it's going to ramp up real hard in November and so you have to be prepared for it, which would have been hard if you manage your own server. Tamas Piros 9:55 Exactly. And now everything is pretty much transparent to you. You don't you know, see You don't need to worry about it. That's that's pretty much it. Bryan Robinson 10:03 And I absolutely love the the "there's an API for that". I'm, I'm definitely going to be gonna be tweeting about that as for sure. Alright, so so I guess Tell me a little bit about how you're kind of advocating and cloud Neri and what sorts of technologies you're using. Obviously, we talked about, like the color change, but like, what other kind of big things are you kind of talking about in your professional life in the jam stack. Tamas Piros 10:28 So there's a first of all, because of, you know, me having this gem center training website, I tried to sort of explore all the static site generators, all the all the headless CMS is all the components, and all the tools that I could use under the JAMstack. I just like to explore these right and that's part of the role as a developer evangelist as well, so that you know, I'm kind of well versed in all of these different pieces of technology. Tamas Piros 11:00 So at Cloudinary, really, you know, be focused on media images and videos and how you store them, how you optimize them, how you sort of transform them. So we have, you know, API's for not only just managing these media assets, but also as I said, you know, to transform them into any way you want. We recently added lots of AI features. So you know, don't forget, this is all on our site. So all you need to do is modify the URL or make the right API or SDK call, and we do the job for you. Tamas Piros 11:33 So we have things like, you know, object recognition for about 20 or 30 items, so you can send an image to us and then we can find it, you know microwave on it. You can find the banana on it and then we can actually crop the image for you so that you know the banana or the microwave oven is going to be in the center of the image. And, you know, again, what do I need to do here? Nothing, upload the image, change something in The URL and I get the result that I wanted. Bryan Robinson 12:03 There you go. Yeah. And that's actually one of the one of the challenges I even had, managing an actual proprietary CMS was image cropping. And like dealing with all that, and figuring out where to crop the image, we put that on the user on our CMS users, and it never ended quite well. Tamas Piros 12:20 Yeah, I mean, you know, you can do that automatically with any of these AI features, or you could, you know, just manually, you know, say with height, crop, and then you know, you're good to go. It's, I do enjoy, you know, that side of things. It's really, really easy. And then, you know, there's the delivery side of things. So we also use a global CDN, which means that, you know, once you do a transformation, it gets pushed out to the CDN, it's always going to be returned to the closest requesting user. And also, if the same transformation is requested, we don't do it again. Right. So it's just going to be cached in the CDN. Tamas Piros 12:54 So it's the second time when you call the same image is even going to be faster and We do have automatic formatting features, which is basically says, if you're looking at this image from Chrome, we serve it as a WebP, if you look at it from a safari, we serve it as a JPEG right? And that's, again, completely transparent to you. Because otherwise, if you wouldn't have that feature, even have this sort of management tool available for you, you would theoretically if you want a website that performs well, you would have to create a JPEG file, a web p file, and you know, have the logic in place so that the right file is served to the right browser. Bryan Robinson 13:32 The whole CDN thing is, it's over my head, definitely. But it's very interesting to be that we have all these API's. They're doing CDN as well. So you've got Cloudinary on a CDN, FaunaDB has this kind of distributed database thing that we're fine with hosting on the CDN. And then putting all that logic at the CDN level just makes so much sense. But I could never set that up like that could never be me. So it's so nice to offload that to our various API's. Tamas Piros 13:55 And, you know, that's also one of the core ideas of the JAMstack i think is you know, Everything should be on an edge server. So there's really, you know, no more excuses for not creating websites that that perform well. Bryan Robinson 14:07 Exactly as quick as possible all over the world. Cool. So let's let's get to what you're actually jamming on right now in terms of music. What's your musical taste? What's your favorite song or musician? What were you? Were you listening to? Tamas Piros 14:20 So what I listened to in general, I have a weird set of music to listen to. It's really anything from metal music to reggaeton, reggaeton being my big favorite, right? So artists like J. Balvin, maluma, the Anki, these type of artists, and I love the music so much that I actually learned Spanish so that I can actually understand what they are singing about. And actually, I'm going to say this out loud now, so this isn't a recording. One of the challenges that I have for myself for the next year is to deliver a talk in Spanish. So I've been working on that, it's I'm getting there, I think but you know, 2020 is the year when it's going to happen. But yeah, so the big favorite that I have is really, you know, J Balvin. Anything from from J Balvin who is a Colombian reggaeton singer. I just love his songs. And I have to admit that, you know, we spoke about Christmas, it's Christmas time. I'm all for Christmas music. You know, it's Bring Crosby and Cliff, Richard and all of these. I'm going to start to play them very soon. Bryan Robinson 15:30 You know, I was at a cafe this past weekend, and they were playing Christmas music and I said, it's not Thanksgiving. So for us, right. It's not in the States. Not Thanksgiving yet. I feel like it's got to be December before we can listen to Christmas music. Yeah, Tamas Piros 15:43 it's Look, it's 10 more days, and I can, you know, have you told Bryan Robinson 15:49 I mean, I'm not gonna judge you could listen to it in July and I'd be I'd be happy for you listen to Christmas music done. Tamas Piros 15:54 I like Christmas. And, you know, I think Christmas music should be in December. It's cold maybe there's snow. It has a certain, you know, feeling for it. And I like that. Bryan Robinson 16:04 So last thing, anything you want to promote that you're doing right now, what do you want to kind of share with the jam stack world, Tamas Piros 16:10 I would just, you know, like people to check out jumps at the training, if you know anyone feels like they are for recording their own sort of video course, I'm more than happy to host that as well or help them, you know, ideate and help them to record stuff. Or if they just have an idea and say, Oh, I would love to see, you know, XYZ in the JAMstack. And I'm more than happy to at least try to somehow record that or accommodate those requests. But yeah, just, you know, as I said, it's all free. So I hope people will, will find value in what I'm doing there. Bryan Robinson 16:46 Excellent. Well, I appreciate you taking the time to talk with us today. Tamas Piros 16:49 Thank you very much for having me. Bryan Robinson 16:50 I want to take a second thing this week sponsor TakeShape. TakeShape they're offering a content platform and that's really the best description. They have handy CM,S a static site generator and simple GraphQL API that's all ready for your use in the JAMstack. Bryan Robinson 17:07 And they may have all that power but they also work within your current workflow. I'm currently converting one of my sites over to us to TakeShape CMS. But because I can bring my own static site generator, I don't have to rewrite a lot of that code. Just change where the data comes from, and BAM, instant upgrade my CMS. Bryan Robinson 17:22 They also have new features coming out all the time, like their new Mesh product that allows for you to mix and match data from multiple sources into one neat GraphQL interface. If that sounds interesting. Be sure to go to takeshape.io/thatsmyjamstack to find out more. Bryan Robinson 17:39 And of course, as always, I do want to thank you, our listeners You are the reason I do this. Be sure to like heart, favorite, subscribe, whatever you do, and your podcast app of choice to let me know that you want more and more and more episodes of the That's My JAMstack podcast. We'll see you next week and keep doing amazing things on the web.Transcribed by https://otter.aiIntro/outtro music by bensound.comSupport That's my JAMstack by donating to their Tip Jar: https://tips.pinecast.com/jar/thats-my-jamstack

So this is the discord link if you want to see this project (MentorCV) development updates live and interact with my community based around it: https://discord.gg/RBxDa7ZSome of my repos I mentioned:https://github.com/QuantumInformation/solar-popuphttps://github.com/quantuminformation/vanilla-typescript My Svelte stuff on youtube:

Gatsby raises a series A which raises questions about open source business models and selecting open source libraries for your projects. We then explore Chris' consulting background and how to go about doing what you want to do (and maybe get paid for it)The Complete Guide to FaunaDB

Quick show notes Our Guest: Andrew Sprouse What he'd like for you to see: TakeShape's new Mesh service His JAMstack Jams: Netlify | Gatsby | And of course TakeShape His musical Jam: The timeless Metal of Iron Maiden and the Thai-inspired acousitc stylings of Khruangbin Other Tech mentioned Webhook CMS FaunaDB Amazon AWS Imgix Cloudinary Transcript Bryan Robinson 0:00 Hello everyone! Welcome to another episode of the That’s my JAM stack podcast where we profile amazing people working in this new methodology. In this podcast, we dare to ask the age-old question “What’s your jam in the JAMstack?!” I’m your host Bryan Robinson and today I’m joined by Andrew Sprouse. Andrew is a cofounder and CTO of the amazing JAMstack company TakeShape. Bryan Robinson 0:59 So, Andrew, thanks for coming on the show today. Can you give our listeners a little background, who you are what you do for work and for fun? Andrew Sprouse 1:05 Yeah, great. Thanks for having me, by the way. Um, so I'm Andrew. I'm the CTO and co founder of a company called TakeShape. And take shape builds tools for JAMstack developers. And outside of TakeShape. I like to cook I like to ride my bike. And I like to code. So Bryan Robinson 1:27 very nice. So that not not just coding, but also cooking and bike riding. What kind of stuff do you cook? Andrew Sprouse 1:32 Oh, I'm, I'm very passionate about barbecuing. So any type of you know, charcoal fires, smoking. I have like a wood pizza attachment for my grill. So it's that's like a fun project on the weekends. Bryan Robinson 1:49 Very nice. I'm from Memphis. So I take barbecue very seriously, we might not want to get into strong opinions on that too much. Andrew Sprouse 1:55 yeah, I think you would win on that one. Bryan Robinson 1:59 So obviously, now you're a CTO of a JAMstack company. But what was kind of your entry point into the JAMstack world? Andrew Sprouse 2:06 Yeah. So my introduction to sort of static sites and JAMstack goes back to 2010, when we first started using AWS at work, and at the time, I was working with my co founder, Mark, but at Newsweek magazine on the web team there. And so we found out that you could just put HTML files on s3, and then you could host them, basically with zero effort. And it was super fast. And so that was like, wow, if we could really do you know, the whole website this way, that would be amazing. Andrew Sprouse 2:48 So fast forward, like a few months, Mark left to pursue his own creative agency. And one of the first sites that he did was just some HTML, JavaScript and CSS on on s3. And it was the first proof where it was like it was this site for a charity called the Dobbs stories. And it was this first proof that, you know, you could build a full featured website, just with static files. And so that sort of influenced the way that we started to build from that, then on. Bryan Robinson 3:24 Okay, so So when you were at Newsweek were y'all using anything other than just hosting the static files on s3, were you going bigger? Or was it still like you had your content management system for the news? And Andrew Sprouse 3:33 yeah, so unfortunately, back then, we were using enterprise CMS called, it was called Day CQ5. Now, it's called Adobe, AN so since everything couldn't be static, we would spend a lot of time caching, like doing really robust caching. And so that was kind of like, the website, in effect was static. But it was just being served from a cache as opposed to proactively pushing it out to, you know, s3 or Netlify or something. So we we didn't have the tools back then to be able to make the whole site static. So we had to use this traditional CMS. Bryan Robinson 4:17 I actually worked in a news organization for about six years. And even like the side projects we did, we're still like database driven WordPress driven kind of stuff. And then we had our big content management system stack. Did y'all do any side projects like that on on static? Or were you like hosting in some other way? Andrew Sprouse 4:34 Yeah, so the discovery was for was for, you know, a side project was like, you could do a micro site with static hosting, but you can do the full blown media experience. Bryan Robinson 4:48 Gotcha. And so so there's that breakaway agency proof of concept. And then what was the big explosion point for you at that point? What what kind of tipped the scale into the giant, like static sites that you were doing? And then what was the JAMstack tipping point? Andrew Sprouse 5:04 So the tipping point really came along, when we found out that, you know, this is really clicking for the agency. So actually, fast forward a couple years, I joined Mark at the creative agency to help him with technology. And so we're working together. And we're realizing that every project that we do with static goes so smoothly. And you know, it's an amazing end result for the client. And so we start to push all of our clients to go static. And that just got easier and easier when there was more tools. And we had a really favorite tool called Webhook CMS. And it was sort of like a CMS and static site generator sort of built into one. And it was like that, for us was like, Whoa, if you combine this concept of Headless CMS plus static site generator, you get this amazing end result, it's easy to set up. And, you know, the the performance is great, and you don't get any calls, you know, late at night that the site's down or have any maintenance issues. Bryan Robinson 6:25 Nice. So so the JAMstack philosophy is professional, you've just been doing them for what sounds like like four or five years now as like your main go to what about personally or doing anything personally with the JAMstack and your side, like coding projects? Andrew Sprouse 6:38 Well, I'd love to have more side projects right now. But my, my main project is kind of my everything right now. So working on TakeShape. And actually building tools for the JAMstack on the JAMstack. Is is what I spend all my time doing nowadays. Bryan Robinson 7:02 So talk a little bit about that like building the JAMstack with the JAMstack. How does that work? How does that work? Andrew Sprouse 7:08 So TakeShape started out as a headless CMS. And from the very beginning, we wrote the API first. And so being in a jam, Sac State of Mind, we're like, well, how can we do this with no servers. So we built the back end all on AWS lambda using API gateway. So that was that was sort of the first step. And then we realized that our client app could simply be a static, single page react app that we host on s3. So it's actually using JAMstack techniques to build a CMS that's supremely useful for people who are building on the JAMstack. Andrew Sprouse 7:55 And we also incorporated just like our Webhook inspiration, we built a static site generator directly into the CMS so you could have the entire experience in one product. Bryan Robinson 8:09 I see that more and more in like JAMstack companies right now. I mean, Netlify is packing in like four or five different services. Obviously, AWS has a whole bunch of stuff built into it. And then I see you've also got the Mesh product, which is building an API's together, how's that been going? Andrew Sprouse 8:25 So the mesh has been an adventure. It's a problem that we've solved on our own many times, you know, for specific point to point things. But it's been an amazing adventure to try to figure out a way to generalize it and make it easier for everybody. So everybody can benefit from our experience, and frankly, our pain with integrating API's. Andrew Sprouse 8:51 So being able to use that mesh product in conjunction with our CMS product is just a, you know, it's the natural extension. So you have this idea of headless CMS with a custom data model. But then what our customers came to us for said, This CMS is great, but I have all these other things that I need to incorporate into my project. How do I do that? And what the best technique? And well, you know, as soon as we, our answer was, well, you have to launch a Netlify function and write all this custom code, and here's a sample project and then get repo that shows, you know, the sample people, you know, the eyes would roll back and, you know, glaze over. And they would sort of stop listening at that point, because they wanted it to be a plugin, or some sort of out of the box solution. So we realized there was a need for something like take shape mesh. Bryan Robinson 9:53 Definitely, yeah, when I was a, I actually have a little website, that's a repository of various products. And it's like, my client wants x, and there's so many things that clients want, and some of them make sense. some of them are a little bit weird, but, uh, but in the end that that is one of the impediments to getting JAMstack in agencies, at least when I worked in an agency that was one of the one of the problems? Andrew Sprouse 10:14 Yeah, absolutely. It's, it's like, the tools can be amazing, the end product can be amazing. But if you can't package it in a way that the client understands, you have a really hard time selling, you know, them on it. And that's something that traditionally WordPress, and traditional products have done really well, where it's like, oh, well, you need this feature. Well, there's just some random plugin, some guy wrote that, that kind of does that. And maybe it will, will work. But at a marketing level, that's amazing. Because like, oh, WordPress has infinite features. Andrew Sprouse 10:54 And then as the developer, you're saddled with some guys, you know, plugin that he wrote for one project, and you're kind of like, well, now I have a lot of work to do. And so the amazing part of the JAMstack is that each company that creates a JAMstack service sort of focuses on the thing that they're best at so Netlify, you know, is the gold standard for static site hosting, and you have, you know, image services like Imgix and Cloudinary and analytics and, and, you know, e commerce services, and so everybody gets to specialize. But then it also is like, well, now how do I bring it all together? And, and that is then thrust onto the developer. And what we found is that, you know, the developer has plenty of work to do, of actually making your product. So let's, let's give them a shortcut. And they're still using these best in class service is, but we're making them easier to combine. Bryan Robinson 12:03 I really like that concept of Mesh. Is it out of beta. Like, I remember a couple like a month ago, I tried to get in, but there was in beta, so I skipped it. Andrew Sprouse 12:11 Yeah, we we currently have a beta waitlist going on. So I would encourage you to sign up, and we can sort of like move you up to the top of the list. And, yeah, so so we're currently, we're currently building out all the features, and it's super early. So, you know, we're getting great feedback from our initial users so far. And, you know, we're really excited we can't wait to, to, you know, release this to a wider audience. And actually, in October, we're going to be at the JAMstack_conf inSan Francisco, and going to be presenting, you know, like 10 minutes, overview of the Mesh and, and sort of, hopefully, we can open it up wider at that point. Bryan Robinson 13:05 Very cool. Are you gonna go out and be like, Matt Billman and like, deploy on stage? Or maybe, maybe keep it in beta until week after? Andrew Sprouse 13:13 I don't know. I mean, that's a pretty brave guy. He's an and much smarter than I am. So, you know, he can get away with that. Mine might be a little bit more canned. Bryan Robinson 13:27 Alright, so obviously TakeShape is one of your jams in the JAMstack, but what are some others? What are some of your other favorite tools and products and things that you really enjoy using? Andrew Sprouse 13:37 You know, it's sort of like the JAMstack, it's hard to have favorites, because there's so many different functionalities. So I've already mentioned Netlify, you know, they're sort of the leader in this space, and they do, every product that they come out with is, is really, really great. You know, we use their static hosting extensively. And, you know, if you like react, I think Gatsby JS is great. You know, it provides a great way for you to build out a site and then sort of like, add in those single page features that you would want. Bryan Robinson 14:16 And talk about plugin ecosystem, they've got quite the plugin ecosystem already. Andrew Sprouse 14:20 Yeah, it's pretty amazing the amount of work that community has done, you know, and the couldn't have nicer founders, you know, those guys have have been really nice to us. And, you know, I always talk about Gatsby. And one other service that has sort of come onto my radar that I've only started to play around with is one called FaunaDB. And they've created this sort of globally distributed database that is ACID compliant, which is amazing for something that's that distributed. And so I just started, I just signed up the other day, and I've been playing around with it. So I have to plug them to Bryan Robinson 15:05 I think you might have signed up at roughly the same time I signed up. I'm working on my first like, demo in FaunaDB. I just started that like earlier this week. Andrew Sprouse 15:14 yeah, it looks really cool. Bryan Robinson 15:16 And real fast you through the term ACID compliant out there. I personally don't know what that is. So I'm going to assume that least a few listeners won't know what that means. But what is acid compliance? Andrew Sprouse 15:26 So it's sort of a, you know, a standard in database land of how can it's it's about consistency. So if if I write to the database, and then I asked the database back for an answer, am I going to get a consistent answer? Because in some databases, if you had, say, multiple servers, which you do not now that's abstracted from us, but if you have multiple servers and multiple locations, I might send my the update of the title of my blog post to that it would go to like three or four different servers. And then if I asked the cluster for what's the title, I might not if I if I asked for it at the exact same time, I might not get the the the old one versus the new one. And ACID is basically the guarantee that you would get back that consistent answer nice. I across all the machines, Bryan Robinson 16:22 I cannot even begin to fathom the solution there. But yeah, that is an important thing. Definitely. Andrew Sprouse 16:28 Yeah, I mean, that that's the amazing part, you know, of the ecosystem is you can have the guys at FaunaDB, who are worrying about that deeply technical problem, and they can sort of bottle their expertise, and just offer it to everybody. Which is really cool. Bryan Robinson 16:47 And so what's going to keep you in the JAMstack world, other than literally building a product on the JAMstack for the JAMstack, like what, what makes you love it deep down? Obviously, you're pretty passionate about? Andrew Sprouse 17:01 Yeah, I think, well, there's there's multiple ways I can answer this. But I think that the thing that I think of is if I've met a lot of great people working with the these technologies, and you know, it's the first development community that I've been in, that's been really like kind and, you know, friendly to beginners, and everybody's all about, you know, how can I? How can I boost, you know, your productivity or make your business better. And I feel like that sort of that spirit of giving everybody else a shortcut. And you know, you know, earlier in my career, I'd work with engineers who it was like, we gotta roll our own, we got to do everything custom, you know, we can't trust other people to to make good stuff, it has to be inside. And that sort of like limits your ability to be really productive. And so I think that JAMstack is on the right track, regardless of technology that that's the attitude towards building nowadays, Bryan Robinson 18:07 Bringing the best expertise from all over the internet. Bryan Robinson 18:11 Alright, so in terms of like, actual jamming, what's what's your musical jam right now? Andrew Sprouse 18:17 Oh, man. So last month, I went to an Iron Maiden concert. So I've been jamming out to some, you know, to some metal while doing coding, but I enjoy all types of music. There's a really eclectic band called Khruangbin. They're sort of Thai inspired. It's acoustic music, but it's really cool. I can't even not confident that I would be able to spell it on the air right now. Bryan Robinson 18:50 We'll put it in the show notes. though right. Andrew Sprouse 18:53 Yeah, for sure. That's all Also, if you want something a little bit more low key to code to I would say just that. Bryan Robinson 19:01 And I think I can guess what your answer to this is going to be. But is there anything that you would like to promote on on the podcast today? Andrew Sprouse 19:07 Yeah, sure. I mean, first of all, I want to thank you for, for letting me on. And this is a really great opportunity to talk to you and to your audience. But yeah, TakeShape, we're, we're, we're working really hard to get good products out for everybody, and especially the mesh. And, you know, we want everybody's feedback on it once the beta goes out. Andrew Sprouse 19:34 But please, you know, keep in touch sign up for the Mesh go to TakeShape.io and there's a place to sign up. And you can watch you know, the video that's there and, and sort of do that we'd love to hear from people there. You know, what they want out of the JAMstack? And, you know, how can we do better and and and build tools that people want to use? Bryan Robinson 19:59 Very cool. Definitely a noble aspiration: build tools that people actually want to not just have to use? Yeah, we hope so. All right, well, I really appreciate you coming on the show. And and I hope that you keep making some amazing stuff to TakeShape. Andrew Sprouse 20:12 Great. Great. Thank you so much.Transcribed by https://otter.aiIntro/outtro music by bensound.com

Sponsors Sentry– use the code “devchat” for $100 credit  Panel Charles Max Wood AJ O’Neal Joe Eames Aimee Knight With Special Guest: Evan Weaver Episode Summary Evan Weaver is the CEO and cofounder of FaunaDB, a serverless database and a great way to get started with GraphQL. Evan talks about what went into building the FaunaDB and his background with Twitter. FaunaDB arose from trying to fix Twitter’s scalability issues, and the panel discusses scalability issues encountered in both large and small companies. They talk about the difference between transient and persistent data. They discuss how to develop locally when using a serverless database and the importance of knowing why you’re using something. Evan talks about how developing locally works with FaunaDB. He addresses concerns that people might have about using FaunaDB since it is not backed by a tech giant. Evan talks about some of the services FaunaDB offers and talks about the flexibility of its tools. He talks about how to get started with FaunaDB and what the authentication is like. Finally, Evan talks about some well known companies that are using FaunaDB and what they are doing with it.  Links FaunaDB GraphQL Netlify AWS Lambda Apollo.io SQL Jamstack  Akkeris Graphile Follow DevChat on Facebook and Twitter Picks Charles Max Wood: Captain Sonar Canny JSJ Reccomendations Aimee Knight: Falling in Reverse Joe Eames: Battlestations Evan Weaver Forza Motorsport Follow Evan on Twitter and Github @evan

Sponsors Sentry– use the code “devchat” for $100 credit  Panel Charles Max Wood AJ O’Neal Joe Eames Aimee Knight With Special Guest: Evan Weaver Episode Summary Evan Weaver is the CEO and cofounder of FaunaDB, a serverless database and a great way to get started with GraphQL. Evan talks about what went into building the FaunaDB and his background with Twitter. FaunaDB arose from trying to fix Twitter’s scalability issues, and the panel discusses scalability issues encountered in both large and small companies. They talk about the difference between transient and persistent data. They discuss how to develop locally when using a serverless database and the importance of knowing why you’re using something. Evan talks about how developing locally works with FaunaDB. He addresses concerns that people might have about using FaunaDB since it is not backed by a tech giant. Evan talks about some of the services FaunaDB offers and talks about the flexibility of its tools. He talks about how to get started with FaunaDB and what the authentication is like. Finally, Evan talks about some well known companies that are using FaunaDB and what they are doing with it.  Links FaunaDB GraphQL Netlify AWS Lambda Apollo.io SQL Jamstack  Akkeris Graphile Follow DevChat on Facebook and Twitter Picks Charles Max Wood: Captain Sonar Canny JSJ Reccomendations Aimee Knight: Falling in Reverse Joe Eames: Battlestations Evan Weaver Forza Motorsport Follow Evan on Twitter and Github @evan

Sponsors Sentry– use the code “devchat” for $100 credit  Panel Charles Max Wood AJ O’Neal Joe Eames Aimee Knight With Special Guest: Evan Weaver Episode Summary Evan Weaver is the CEO and cofounder of FaunaDB, a serverless database and a great way to get started with GraphQL. Evan talks about what went into building the FaunaDB and his background with Twitter. FaunaDB arose from trying to fix Twitter’s scalability issues, and the panel discusses scalability issues encountered in both large and small companies. They talk about the difference between transient and persistent data. They discuss how to develop locally when using a serverless database and the importance of knowing why you’re using something. Evan talks about how developing locally works with FaunaDB. He addresses concerns that people might have about using FaunaDB since it is not backed by a tech giant. Evan talks about some of the services FaunaDB offers and talks about the flexibility of its tools. He talks about how to get started with FaunaDB and what the authentication is like. Finally, Evan talks about some well known companies that are using FaunaDB and what they are doing with it.  Links FaunaDB GraphQL Netlify AWS Lambda Apollo.io SQL Jamstack  Akkeris Graphile Follow DevChat on Facebook and Twitter Picks Charles Max Wood: Captain Sonar Canny JSJ Reccomendations Aimee Knight: Falling in Reverse Joe Eames: Battlestations Evan Weaver Forza Motorsport Follow Evan on Twitter and Github @evan

One of the biggest challenges for any business trying to grow and reach customers globally is how to scale their data storage. FaunaDB is a cloud native database built by the engineers behind Twitter's infrastructure and designed to serve the needs of modern systems. Evan Weaver is the co-founder and CEO of Fauna and in this episode he explains the unique capabilities of Fauna, compares the consensus and transaction algorithm to that used in other NewSQL systems, and describes the ways that it allows for new application design patterns. One of the unique aspects of Fauna that is worth drawing attention to is the first class support for temporality that simplifies querying of historical states of the data. It is definitely worth a good look for anyone building a platform that needs a simple to manage data layer that will scale with your business.

Upcoming events: A Conversation with Haseeb Qureshi at Cloudflare on April 3, 2019 FindCollabs Hackathon at App Academy on April 6, 2019 Twitter’s early engineers faced scalability problems that caused infrastructure failures on a regular basis. The infamous “fail whale” could happen as a result of problems in the application servers, the network, or the The post FaunaDB with Evan Weaver appeared first on Software Engineering Daily.

Sponsors Sentry– use the code “devchat” for $100 credit TripleByte offers a $1000 signing bonus CacheFly Episode Summary In this episode of React Round Up, Justin Bennett speaks with co-founder of Couchbase, Chris Anderson. Chris has been working with NoSQL databases for approximately a decade, and is currently working on FaunaDB, doing development outreach, while writing codes to connect with the different eco systems: Serverless, JAMStacks and React Native. He is also a blogger on a platform he calls ‘Serverless’ and enjoys decoding web applications and converting them to mobile. Chris elaborates on the particulars and functions of JAMstacks, FaunaDB, React Native, Expo, Firebase and Netlify along with their databases. He tells of his journey with FaunaDB and explains what led to its introduction. He also gives a detailed explanation on Serverless functions, Multi-cloud deployment and extends advice to apprentices in the similar field. Links https://serverless.com/author/chrisanderson/ https://twitter.com/jchris https://github.com/jchris https://fauna.com/ Serverless Netlify React Native Firebase https://www.facebook.com/React-Round-Up https://twitter.com/reactroundup Picks Chris Anderson: React Native Starter Kit Netlify Fauna Todo Justin Bennett: Refactoring UI Build Your Own Mint

Sponsors Sentry– use the code “devchat” for $100 credit TripleByte offers a $1000 signing bonus CacheFly Episode Summary In this episode of React Round Up, Justin Bennett speaks with co-founder of Couchbase, Chris Anderson. Chris has been working with NoSQL databases for approximately a decade, and is currently working on FaunaDB, doing development outreach, while writing codes to connect with the different eco systems: Serverless, JAMStacks and React Native. He is also a blogger on a platform he calls ‘Serverless’ and enjoys decoding web applications and converting them to mobile. Chris elaborates on the particulars and functions of JAMstacks, FaunaDB, React Native, Expo, Firebase and Netlify along with their databases. He tells of his journey with FaunaDB and explains what led to its introduction. He also gives a detailed explanation on Serverless functions, Multi-cloud deployment and extends advice to apprentices in the similar field. Links https://serverless.com/author/chrisanderson/ https://twitter.com/jchris https://github.com/jchris https://fauna.com/ Serverless Netlify React Native Firebase https://www.facebook.com/React-Round-Up https://twitter.com/reactroundup Picks Chris Anderson: React Native Starter Kit Netlify Fauna Todo Justin Bennett: Refactoring UI Build Your Own Mint

Chris Anderson joins for a discussion about topics like RAFT and ACID in FaunaDb. Some notes from the show supplied by Chris: FaunaDb Secret Lives of Data: Raft Chris Anderson on Twitter  

David Wells & Chris Coyier talk about how you can build an app hosted on Netlify statically but still have a backend database to power it. We use the classic TODO app example where the database is powered by FaunaDB and we talk to that database via serverless functions (i.e. Node.js JavaScript functions running on AWS Lambda via Netlify’s extremely easy and powerful integration). Put the JavaScript files in a /functions folder and they’ll be deployed and runnable!… Read article “#165: Building Your Backend with Serverless Functions”

Charity Majors, founder & CEO of Honeycomb joins us to discuss exploratory learning through rich data, as well as news about Blue Origin, FaunaDB, Resin.io Credits Opening Music: Another beek beep beer please (http://freemusicarchive.org/music/Rolemusic/gigs_n_contest/rolemusic_-_gigs_n_contest_-_03_Another_beek_beep_beer_please) by Rolemusic (http://freemusicarchive.org/music/Rolemusic/) Special Guest: Charity Majors.