Podcasts about cdns

$24 billion of free cash flow in a single quarter is no small feat. If Nvidia can keep that pace, it may actually be trading at a reasonable price. (00:21) Tim Beyers and Mary Long discuss: - Market relief about the latest in Trump's trade saga. - A rose and a thorn from Nvidia's latest report. - Another trade-related announcement that affects the semiconductor supply chain. Companies discussed: NVDA, CDNS, SNPS, SIEGY Host: Mary Long Guest: Tim Beyers Engineer: Dan Boyd Advertisements are sponsored content and provided for informational purposes only. The Motley Fool and its affiliates (collectively, "TMF") do not endorse, recommend, or verify the accuracy or completeness of the statements made within advertisements. TMF is not involved in the offer, sale, or solicitation of any securities advertised herein and makes no representations regarding the suitability, or risks associated with any investment opportunity presented. Investors should conduct their own due diligence and consult with legal, tax, and financial advisors before making any investment decisions. TMF assumes no responsibility for any losses or damages arising from this advertisement. Learn more about your ad choices. Visit megaphone.fm/adchoices

The race to quantum supremacy is on. While this future will not come tomorrow, big tech companies are building to the technology's “ChatGPT moment.” Motley Fool Senior Analyst, Asit Sharma ,joins Mary Long to discuss: - The complex problems that quantum computers could solve. - How healthcare and logistics companies benefit from ultra-fast processing. - The small players and hyperscalers building the future of quantum. Companies discussed: GOOG, GOOGL, MSFT, IBM, QBTS, AMZN, RGTI, CDNS, SNPS, IONQ Motley Fool One members can access Asit's full report, “Decoding Quantum” here: https://www.fool.com/premium/4627/coverage/2025/03/19/decoding-quantum-insights-for-investors Host: Mary Long Guest: Asit Sharma Producer: Ricky Mulvey Engineer: Rick Engdahl Learn more about your ad choices. Visit megaphone.fm/adchoices

Ashley Peacock, the author of Serverless Apps on Cloudflare, speaks with host Jeremy Jung about content delivery networks (CDNs). Along the way, they examine dependency injection with bindings, local development, serverless, cold starts, the V8 runtime, AWS Lambda vs Cloudflare workers, WebAssembly limitations, and core services such as R2, D1, KV, and Pages. Ashley suggests why most users use an external database and discusses eventually consistent data stores, S3-to-R2 migration strategies, queues and workflows, inter-service communication, durable objects, and describes some example projects. Brought to you by IEEE Computer Society and IEEE Software magazine.

Q&A224: Can tracker blocking and other privacy techniques make you stand out more? Has Wayland fixed any of X's security shortcomings? Why don't people talk about the risks of CDNs more? Is there any way to know what's going on in the RF around us? Join our next Q&A on Patreon: https://www.patreon.com/collection/415684?view=expanded or XMR Chat: https://xmrchat.com/surveillancepodWelcome to the Surveillance Report Q&A - featuring Techlore & The New Oil answering your questions about privacy and security.❤️ Support us on Patreon: https://www.patreon.com/surveillancepod

Let's explore ways to create a more sustainable podcasting workflow, reduce waste, and inspire listeners to take eco-friendly action. As Earth Day approaches, it's a perfect time for podcasters to reflect on their environmental impact and take actionable steps toward sustainability. While podcasting is largely a digital medium, it still consumes energy, data, and resources—and increasingly, AI tools like ChatGPT and other platforms also play a role in your workflow, using significant computing power. By making small yet meaningful changes, podcasters can contribute to a greener industry while maintaining high-quality content. Today's Hosts: Mike Dell, MacKenzie Bennett, and Todd Cochrane We're diving into sustainable podcasting—simple steps you can take to reduce waste, conserve energy, and make your show a little greener! 1. Optimize Your Podcasting Setup for Energy Efficiency The equipment you use for recording, editing, and publishing your podcast can have a significant environmental footprint. Consider these changes: ✅ Use energy-efficient devices – Choose ENERGY STAR-rated computers, LED lights, and low-power audio interfaces. ✅ Opt for rechargeable batteries – Instead of disposable batteries for wireless mics or audio gear, go rechargeable. ✅ Turn off and unplug equipment when not in use – Many electronics consume power even when turned off. ✅ Switch to renewable energy sources – If possible, power your studio with solar energy or choose a green energy plan.

Brandon Liu is an open source developer and creator of the Protomaps basemap project. We talk about how static maps help developers build sites that last, the PMTiles file format, the role of OpenStreetMap, and his experience funding and running an open source project full time. Protomaps Protomaps PMTiles (File format used by Protomaps) Self-hosted slippy maps, for novices (like me) Why Deploy Protomaps on a CDN User examples Flickr Pinball Map Toilet Map Related projects OpenStreetMap (Dataset protomaps is based on) Mapzen (Former company that released details on what to display based on zoom levels) Mapbox GL JS (Mapbox developed source available map rendering library) MapLibre GL JS (Open source fork of Mapbox GL JS) Other links HTTP range requests (MDN) Hilbert curve Transcript You can help correct transcripts on GitHub. Intro [00:00:00] Jeremy: I'm talking to Brandon Liu. He's the creator of Protomaps, which is a way to easily create and host your own maps. Let's get into it. [00:00:09] Brandon: Hey, so thanks for having me on the podcast. So I'm Brandon. I work on an open source project called Protomaps. What it really is, is if you're a front end developer and you ever wanted to put maps on a website or on a mobile app, then Protomaps is sort of an open source solution for doing that that I hope is something that's way easier to use than, um, a lot of other open source projects. Why not just use Google Maps? [00:00:36] Jeremy: A lot of people are gonna be familiar with Google Maps. Why should they worry about whether something's open source? Why shouldn't they just go and use the Google maps API? [00:00:47] Brandon: So Google Maps is like an awesome thing it's an awesome product. Probably one of the best tech products ever right? And just to have a map that tells you what restaurants are open and something that I use like all the time especially like when you're traveling it has all that data. And the most amazing part is that it's free for consumers but it's not necessarily free for developers. Like if you wanted to embed that map onto your website or app, that usually has an API cost which still has a free tier and is affordable. But one motivation, one basic reason to use open source is if you have some project that doesn't really fit into that pricing model. You know like where you have to pay the cost of Google Maps, you have a side project, a nonprofit, that's one reason. But there's lots of other reasons related to flexibility or customization where you might want to use open source instead. Protomaps examples [00:01:49] Jeremy: Can you give some examples where people have used Protomaps and where that made sense for them? [00:01:56] Brandon: I follow a lot of the use cases and I also don't know about a lot of them because I don't have an API where I can track a hundred percent of the users. Some of them use the hosted version, but I would say most of them probably use it on their own infrastructure. One of the cool projects I've been seeing is called Toilet Map. And what toilet map is if you're in the UK and you want find a public restroom then it maps out, sort of crowdsourced all of the public restrooms. And that's important for like a lot of people if they have health issues, they need to find that information. And just a lot of different projects in the same vein. There's another one called Pinball Map which is sort of a hobby project to find all the pinball machines in the world. And they wanted to have a customized map that fit in with their theme of pinball. So these sorts of really cool indie projects are the ones I'm most excited about. Basemaps vs Overlays [00:02:57] Jeremy: And if we talk about, like the pinball map as an example, there's this concept of a basemap and then there's the things that you lay on top of it. What is a basemap and then is the pinball locations is that part of it or is that something separate? [00:03:12] Brandon: It's usually something separate. The example I usually use is if you go to a real estate site, like Zillow, you'll open up the map of Seattle and it has a bunch of pins showing all the houses, and then it has some information beneath it. That information beneath it is like labels telling, this neighborhood is Capitol Hill, or there is a park here. But all that information is common to a lot of use cases and it's not specific to real estate. So I think usually that's the distinction people use in the industry between like a base map versus your overlay. The overlay is like the data for your product or your company while the base map is something you could get from Google or from Protomaps or from Apple or from Mapbox that kind of thing. PMTiles for hosting the basemap and overlays [00:03:58] Jeremy: And so Protomaps in particular is responsible for the base map, and that information includes things like the streets and the locations of landmarks and things like that. Where is all that information coming from? [00:04:12] Brandon: So the base map information comes from a project called OpenStreetMap. And I would also, point out that for Protomaps as sort of an ecosystem. You can also put your overlay data into a format called PMTiles, which is sort of the core of what Protomaps is. So it can really do both. It can transform your data into the PMTiles format which you can host and you can also host the base map. So you kind of have both of those sides of the product in one solution. [00:04:43] Jeremy: And so when you say you have both are you saying that the PMTiles file can have, the base map in one file and then you would have the data you're laying on top in another file? Or what are you describing there? [00:04:57] Brandon: That's usually how I recommend to do it. Oftentimes there'll be sort of like, a really big basemap 'cause it has all of that data about like where the rivers are. Or while, if you want to put your map of toilets or park benches or pickleball courts on top, that's another file. But those are all just like assets you can move around like JSON or CSV files. Statically Hosted [00:05:19] Jeremy: And I think one of the things you mentioned was that your goal was to make Protomaps or the, the use of these PMTiles files easy to use. What does that look like for, for a developer? I wanna host a map. What do I actually need to, to put on my servers? [00:05:38] Brandon: So my usual pitch is that basically if you know how to use S3 or cloud storage, that you know how to deploy a map. And that, I think is the main sort of differentiation from most open source projects. Like a lot of them, they call themselves like, like some sort of self-hosted solution. But I've actually avoided using the term self-hosted because I think in most cases that implies a lot of complexity. Like you have to log into a Linux server or you have to use Kubernetes or some sort of Docker thing. What I really want to emphasize is the idea that, for Protomaps, it's self-hosted in the same way like CSS is self-hosted. So you don't really need a service from Amazon to host the JSON files or CSV files. It's really just a static file. [00:06:32] Jeremy: When you say static file that means you could use any static web host to host your HTML file, your JavaScript that actually renders the map. And then you have your PMTiles files, and you're not running a process or anything, you're just putting your files on a static file host. [00:06:50] Brandon: Right. So I think if you're a developer, you can also argue like a static file server is a server. It's you know, it's the cloud, it's just someone else's computer. It's really just nginx under the hood. But I think static storage is sort of special. If you look at things like static site generators, like Jekyll or Hugo, they're really popular because they're a commodity or like the storage is a commodity. And you can take your blog, make it a Jekyll blog, hosted on S3. One day, Amazon's like, we're charging three times as much so you can move it to a different cloud provider. And that's all vendor neutral. So I think that's really the special thing about static storage as a primitive on the web. Why running servers is a problem for resilience [00:07:36] Jeremy: Was there a prior experience you had? Like you've worked with maps for a very long time. Were there particular difficulties you had where you said I just gotta have something that can be statically hosted? [00:07:50] Brandon: That's sort of exactly why I got into this. I've been working sort of in and around the map space for over a decade, and Protomaps is really like me trying to solve the same problem I've had over and over again in the past, just like once and forever right? Because like once this problem is solved, like I don't need to deal with it again in the future. So I've worked at a couple of different companies before, mostly as a contractor, for like a humanitarian nonprofit for a design company doing things like, web applications to visualize climate change. Or for even like museums, like digital signage for museums. And oftentimes they had some sort of data visualization component, but always sort of the challenge of how to like, store and also distribute like that data was something that there wasn't really great open source solutions. So just for map data, that's really what motivated that design for Protomaps. [00:08:55] Jeremy: And in those, those projects in the past, were those things where you had to run your own server, run your own database, things like that? [00:09:04] Brandon: Yeah. And oftentimes we did, we would spin up an EC2 instance, for maybe one client and then we would have to host this server serving map data forever. Maybe the client goes away, or I guess it's good for business if you can sign some sort of like long-term support for that client saying, Hey, you know, like we're done with a project, but you can pay us to maintain the EC2 server for the next 10 years. And that's attractive. but it's also sort of a pain, because usually what happens is if people are given the choice, like a developer between like either I can manage the server on EC2 or on Rackspace or Hetzner or whatever, or I can go pay a SaaS to do it. In most cases, businesses will choose to pay the SaaS. So that's really like what creates a sort of lock-in is this preference for like, so I have this choice between like running the server or paying the SaaS. Like businesses will almost always go and pay the SaaS. [00:10:05] Jeremy: Yeah. And in this case, you either find some kind of free hosting or low-cost hosting just to host your files and you upload the files and then you're good from there. You don't need to maintain anything. [00:10:18] Brandon: Exactly, and that's really the ideal use case. so I have some users these, climate science consulting agencies, and then they might have like a one-off project where they have to generate the data once, but instead of having to maintain this server for the lifetime of that project, they just have a file on S3 and like, who cares? If that costs a couple dollars a month to run, that's fine, but it's not like S3 is gonna be deprecated, like it's gonna be on an insecure version of Ubuntu or something. So that's really the ideal, set of constraints for using Protomaps. [00:10:58] Jeremy: Yeah. Something this also makes me think about is, is like the resilience of sites like remaining online, because I, interviewed, Kyle Drake, he runs Neocities, which is like a modern version of GeoCities. And if I remember correctly, he was mentioning how a lot of old websites from that time, if they were running a server backend, like they were running PHP or something like that, if you were to try to go to those sites, now they're like pretty much all dead because there needed to be someone dedicated to running a Linux server, making sure things were patched and so on and so forth. But for static sites, like the ones that used to be hosted on GeoCities, you can go to the internet archive or other websites and they were just files, right? You can bring 'em right back up, and if anybody just puts 'em on a web server, then you're good. They're still alive. Case study of news room preferring static hosting [00:11:53] Brandon: Yeah, exactly. One place that's kind of surprising but makes sense where this comes up, is for newspapers actually. Some of the users using Protomaps are the Washington Post. And the reason they use it, is not necessarily because they don't want to pay for a SaaS like Google, but because if they make an interactive story, they have to guarantee that it still works in a couple of years. And that's like a policy decision from like the editorial board, which is like, so you can't write an article if people can't view it in five years. But if your like interactive data story is reliant on a third party, API and that third party API becomes deprecated, or it changes the pricing or it, you know, it gets acquired, then your journalism story is not gonna work anymore. So I have seen really good uptake among local news rooms and even big ones to use things like Protomaps just because it makes sense for the requirements. Working on Protomaps as an open source project for five years [00:12:49] Jeremy: How long have you been working on Protomaps and the parts that it's made up of such as PMTiles? [00:12:58] Brandon: I've been working on it for about five years, maybe a little more than that. It's sort of my pandemic era project. But the PMTiles part, which is really the heart of it only came in about halfway. Why not make a SaaS? [00:13:13] Brandon: So honestly, like when I first started it, I thought it was gonna be another SaaS and then I looked at it and looked at what the environment was around it. And I'm like, uh, so I don't really think I wanna do that. [00:13:24] Jeremy: When, when you say you looked at the environment around it what do you mean? Why did you decide not to make it a SaaS? [00:13:31] Brandon: Because there already is a lot of SaaS out there. And I think the opportunity of making something that is unique in terms of those use cases, like I mentioned like newsrooms, was clear. Like it was clear that there was some other solution, that could be built that would fit these needs better while if it was a SaaS, there are plenty of those out there. And I don't necessarily think that they're well differentiated. A lot of them all use OpenStreetMap data. And it seems like they mainly compete on price. It's like who can build the best three column pricing model. And then once you do that, you need to build like billing and metrics and authentication and like those problems don't really interest me. So I think, although I acknowledge sort of the indie hacker ethos now is to build a SaaS product with a monthly subscription, that's something I very much chose not to do, even though it is for sure like the best way to build a business. [00:14:29] Jeremy: Yeah, I mean, I think a lot of people can appreciate that perspective because it's, it's almost like we have SaaS overload, right? Where you have so many little bills for your project where you're like, another $5 a month, another $10 a month, or if you're a business, right? Those, you add a bunch of zeros and at some point it's just how many of these are we gonna stack on here? [00:14:53] Brandon: Yeah. And honestly. So I really think like as programmers, we're not really like great at choosing how to spend money like a $10 SaaS. That's like nothing. You know? So I can go to Starbucks and I can buy a pumpkin spice latte, and that's like $10 basically now, right? And it's like I'm able to make that consumer choice in like an instant just to spend money on that. But then if you're like, oh, like spend $10 on a SaaS that somebody put a lot of work into, then you're like, oh, that's too expensive. I could just do it myself. So I'm someone that also subscribes to a lot of SaaS products. and I think for a lot of things it's a great fit. Many open source SaaS projects are not easy to self host [00:15:37] Brandon: But there's always this tension between an open source project that you might be able to run yourself and a SaaS. And I think a lot of projects are at different parts of the spectrum. But for Protomaps, it's very much like I'm trying to move maps to being it is something that is so easy to run yourself that anyone can do it. [00:16:00] Jeremy: Yeah, and I think you can really see it with, there's a few SaaS projects that are successful and they're open source, but then you go to look at the self-hosting instructions and it's either really difficult to find and you find it, and then the instructions maybe don't work, or it's really complicated. So I think doing the opposite with Protomaps. As a user, I'm sure we're all appreciative, but I wonder in terms of trying to make money, if that's difficult. [00:16:30] Brandon: No, for sure. It is not like a good way to make money because I think like the ideal situation for an open source project that is open that wants to make money is the product itself is fundamentally complicated to where people are scared to run it themselves. Like a good example I can think of is like Supabase. Supabase is sort of like a platform as a service based on Postgres. And if you wanted to run it yourself, well you need to run Postgres and you need to handle backups and authentication and logging, and that stuff all needs to work and be production ready. So I think a lot of people, like they don't trust themselves to run database backups correctly. 'cause if you get it wrong once, then you're kind of screwed. So I think that fundamental aspect of the product, like a database is something that is very, very ripe for being a SaaS while still being open source because it's fundamentally hard to run. Another one I can think of is like tailscale, which is, like a VPN that works end to end. That's something where, you know, it has this networking complexity where a lot of developers don't wanna deal with that. So they'd happily pay, for tailscale as a service. There is a lot of products or open source projects that eventually end up just changing to becoming like a hosted service. Businesses going from open source to closed or restricted licenses [00:17:58] Brandon: But then in that situation why would they keep it open source, right? Like, if it's easy to run yourself well, doesn't that sort of cannibalize their business model? And I think that's really the tension overall in these open source companies. So you saw it happen to things like Elasticsearch to things like Terraform where they eventually change the license to one that makes it difficult for other companies to compete with them. [00:18:23] Jeremy: Yeah, I mean there's been a number of cases like that. I mean, specifically within the mapping community, one I can think of was Mapbox's. They have Mapbox gl. Which was a JavaScript client to visualize maps and they moved from, I forget which license they picked, but they moved to a much more restrictive license. I wonder what your thoughts are on something that releases as open source, but then becomes something maybe a little more muddy. [00:18:55] Brandon: Yeah, I think it totally makes sense because if you look at their business and their funding, it seems like for Mapbox, I haven't used it in a while, but my understanding is like a lot of their business now is car companies and doing in dash navigation. And that is probably way better of a business than trying to serve like people making maps of toilets. And I think sort of the beauty of it is that, so Mapbox, the story is they had a JavaScript renderer called Mapbox GL JS. And they changed that to a source available license a couple years ago. And there's a fork of it that I'm sort of involved in called MapLibre GL. But I think the cool part is Mapbox paid employees for years, probably millions of dollars in total to work on this thing and just gave it away for free. Right? So everyone can benefit from that work they did. It's not like that code went away, like once they changed the license. Well, the old version has been forked. It's going its own way now. It's quite different than the new version of Mapbox, but I think it's extremely generous that they're able to pay people for years, you know, like a competitive salary and just give that away. [00:20:10] Jeremy: Yeah, so we should maybe look at it as, it was a gift while it was open source, and they've given it to the community and they're on continuing on their own path, but at least the community running Map Libre, they can run with it, right? It's not like it just disappeared. [00:20:29] Brandon: Yeah, exactly. And that is something that I use for Protomaps quite extensively. Like it's the primary way of showing maps on the web and I've been trying to like work on some enhancements to it to have like better internationalization for if you are in like South Asia like not show languages correctly. So I think it is being taken in a new direction. And I think like sort of the combination of Protomaps and MapLibre, it addresses a lot of use cases, like I mentioned earlier with like these like hobby projects, indie projects that are almost certainly not interesting to someone like Mapbox or Google as a business. But I'm happy to support as a small business myself. Financially supporting open source work (GitHub sponsors, closed source, contracts) [00:21:12] Jeremy: In my previous interview with Tom, one of the main things he mentioned was that creating a mapping business is incredibly difficult, and he said he probably wouldn't do it again. So in your case, you're building Protomaps, which you've admitted is easy to self-host. So there's not a whole lot of incentive for people to pay you. How is that working out for you? How are you supporting yourself? [00:21:40] Brandon: There's a couple of strategies that I've tried and oftentimes failed at. Just to go down the list, so I do have GitHub sponsors so I do have a hosted version of Protomaps you can use if you don't want to bother copying a big file around. But the way I do the billing for that is through GitHub sponsors. If you wanted to use this thing I provide, then just be a sponsor. And that definitely pays for itself, like the cost of running it. And that's great. GitHub sponsors is so easy to set up. It just removes you having to deal with Stripe or something. 'cause a lot of people, their credit card information is already in GitHub. GitHub sponsors I think is awesome if you want to like cover costs for a project. But I think very few people are able to make that work. A thing that's like a salary job level. It's sort of like Twitch streaming, you know, there's a handful of people that are full-time streamers and then you look down the list on Twitch and it's like a lot of people that have like 10 viewers. But some of the other things I've tried, I actually started out, publishing the base map as a closed source thing, where I would sell sort of like a data package instead of being a SaaS, I'd be like, here's a one-time download, of the premium data and you can buy it. And quite a few people bought it I just priced it at like $500 for this thing. And I thought that was an interesting experiment. The main reason it's interesting is because the people that it attracts to you in terms of like, they're curious about your products, are all people willing to pay money. While if you start out everything being open source, then the people that are gonna be try to do it are only the people that want to get something for free. So what I discovered is actually like once you transition that thing from closed source to open source, a lot of the people that used to pay you money will still keep paying you money because like, it wasn't necessarily that that closed source thing was why they wanted to pay. They just valued that thought you've put into it your expertise, for example. So I think that is one thing, that I tried at the beginning was just start out, closed source proprietary, then make it open source. That's interesting to people. Like if you release something as open source, if you go the other way, like people are really mad if you start out with something open source and then later on you're like, oh, it's some other license. Then people are like that's so rotten. But I think doing it the other way, I think is quite valuable in terms of being able to find an audience. [00:24:29] Jeremy: And when you said it was closed source and paid to open source, do you still sell those map exports? [00:24:39] Brandon: I don't right now. It's something that I might do in the future, you know, like have small customizations of the data that are available, uh, for a fee. still like the core OpenStreetMap based map that's like a hundred gigs you can just download. And that'll always just be like a free download just because that's already out there. All the source code to build it is open source. So even if I said, oh, you have to pay for it, then someone else can just do it right? So there's no real reason like to make that like some sort of like paywall thing. But I think like overall if the project is gonna survive in the long term it's important that I'd ideally like to be able to like grow like a team like have a small group of people that can dedicate the time to growing the project in the long term. But I'm still like trying to figure that out right now. [00:25:34] Jeremy: And when you mentioned that when you went from closed to open and people were still paying you, you don't sell a product anymore. What were they paying for? [00:25:45] Brandon: So I have some contracts with companies basically, like if they need a feature or they need a customization in this way then I am very open to those. And I sort of set it up to make it clear from the beginning that this is not just a free thing on GitHub, this is something that you could pay for if you need help with it, if you need support, if you wanted it. I'm also a little cagey about the word support because I think like it sounds a little bit too wishy-washy. Pretty much like if you need access to the developers of an open source project, I think that's something that businesses are willing to pay for. And I think like making that clear to potential users is a challenge. But I think that is one way that you might be able to make like a living out of open source. [00:26:35] Jeremy: And I think you said you'd been working on it for about five years. Has that mostly been full time? [00:26:42] Brandon: It's been on and off. it's sort of my pandemic era project. But I've spent a lot of time, most of my time working on the open source project at this point. So I have done some things that were more just like I'm doing a customization or like a private deployment for some client. But that's been a minority of the time. Yeah. [00:27:03] Jeremy: It's still impressive to have an open source project that is easy to self-host and yet is still able to support you working on it full time. I think a lot of people might make the assumption that there's nothing to sell if something is, is easy to use. But this sort of sounds like a counterpoint to that. [00:27:25] Brandon: I think I'd like it to be. So when you come back to the point of like, it being easy to self-host. Well, so again, like I think about it as like a primitive of the web. Like for example, if you wanted to start a business today as like hosted CSS files, you know, like where you upload your CSS and then you get developers to pay you a monthly subscription for how many times they fetched a CSS file. Well, I think most developers would be like, that's stupid because it's just an open specification, you just upload a static file. And really my goal is to make Protomaps the same way where it's obvious that there's not really some sort of lock-in or some sort of secret sauce in the server that does this thing. How PMTiles works and building a primitive of the web [00:28:16] Brandon: If you look at video for example, like a lot of the tech for how Protomaps and PMTiles works is based on parts of the HTTP spec that were made for video. And 20 years ago, if you wanted to host a video on the web, you had to have like a real player license or flash. So you had to go license some server software from real media or from macromedia so you could stream video to a browser plugin. But now in HTML you can just embed a video file. And no one's like, oh well I need to go pay for my video serving license. I mean, there is such a thing, like YouTube doesn't really use that for DRM reasons, but people just have the assumption that video is like a primitive on the web. So if we're able to make maps sort of that same way like a primitive on the web then there isn't really some obvious business or licensing model behind how that works. Just because it's a thing and it helps a lot of people do their jobs and people are happy using it. So why bother? [00:29:26] Jeremy: You mentioned that it a tech that was used for streaming video. What tech specifically is it? [00:29:34] Brandon: So it is byte range serving. So when you open a video file on the web, So let's say it's like a 100 megabyte video. You don't have to download the entire video before it starts playing. It streams parts out of the file based on like what frames... I mean, it's based on the frames in the video. So it can start streaming immediately because it's organized in a way to where the first few frames are at the beginning. And what PMTiles really is, is it's just like a video but in space instead of time. So it's organized in a way where these zoomed out views are at the beginning and the most zoomed in views are at the end. So when you're like panning or zooming in the map all you're really doing is fetching byte ranges out of that file the same way as a video. But it's organized in, this tiled way on a space filling curve. IIt's a little bit complicated how it works internally and I think it's kind of cool but that's sort of an like an implementation detail. [00:30:35] Jeremy: And to the person deploying it, it just looks like a single file. [00:30:40] Brandon: Exactly in the same way like an mp3 audio file is or like a JSON file is. [00:30:47] Jeremy: So with a video, I can sort of see how as someone seeks through the video, they start at the beginning and then they go to the middle if they wanna see the middle. For a map, as somebody scrolls around the map, are you seeking all over the file or is the way it's structured have a little less chaos? [00:31:09] Brandon: It's structured. And that's kind of the main technical challenge behind building PMTiles is you have to be sort of clever so you're not spraying the reads everywhere. So it uses something called a hilbert curve, which is a mathematical concept of a space filling curve. Where it's one continuous curve that essentially lets you break 2D space into 1D space. So if you've seen some maps of IP space, it uses this crazy looking curve that hits all the points in one continuous line. And that's the same concept behind PMTiles is if you're looking at one part of the world, you're sort of guaranteed that all of those parts you're looking at are quite close to each other and the data you have to transfer is quite minimal, compared to if you just had it at random. [00:32:02] Jeremy: How big do the files get? If I have a PMTiles of the entire world, what kind of size am I looking at? [00:32:10] Brandon: Right now, the default one I distribute is 128 gigabytes, so it's quite sizable, although you can slice parts out of it remotely. So if you just wanted. if you just wanted California or just wanted LA or just wanted only a couple of zoom levels, like from zero to 10 instead of zero to 15, there is a command line tool that's also called PMTiles that lets you do that. Issues with CDNs and range queries [00:32:35] Jeremy: And when you're working with files of this size, I mean, let's say I am working with a CDN in front of my application. I'm not typically accustomed to hosting something that's that large and something that's where you're seeking all over the file. is that, ever an issue or is that something that's just taken care of by the browser and, and taken care of by, by the hosts? [00:32:58] Brandon: That is an issue actually, so a lot of CDNs don't deal with it correctly. And my recommendation is there is a kind of proxy server or like a serverless proxy thing that I wrote. That runs on like cloudflare workers or on Docker that lets you proxy those range requests into a normal URL and then that is like a hundred percent CDN compatible. So I would say like a lot of the big commercial installations of this thing, they use that because it makes more practical sense. It's also faster. But the idea is that this solution sort of scales up and scales down. If you wanted to host just your city in like a 10 megabyte file, well you can just put that into GitHub pages and you don't have to worry about it. If you want to have a global map for your website that serves a ton of traffic then you probably want a little bit more sophisticated of a solution. It still does not require you to run a Linux server, but it might require (you) to use like Lambda or Lambda in conjunction with like a CDN. [00:34:09] Jeremy: Yeah. And that sort of ties into what you were saying at the beginning where if you can host on something like CloudFlare Workers or Lambda, there's less time you have to spend keeping these things running. [00:34:26] Brandon: Yeah, exactly. and I think also the Lambda or CloudFlare workers solution is not perfect. It's not as perfect as S3 or as just static files, but in my experience, it still is better at building something that lasts on the time span of years than being like I have a server that is on this Ubuntu version and in four years there's all these like security patches that are not being applied. So it's still sort of serverless, although not totally vendor neutral like S3. Customizing the map [00:35:03] Jeremy: We've mostly been talking about how you host the map itself, but for someone who's not familiar with these kind of tools, how would they be customizing the map? [00:35:15] Brandon: For customizing the map there is front end style customization and there's also data customization. So for the front end if you wanted to change the water from the shade of blue to another shade of blue there is a TypeScript API where you can customize it almost like a text editor color scheme. So if you're able to name a bunch of colors, well you can customize the map in that way you can change the fonts. And that's all done using MapLibre GL using a TypeScript API on top of that for customizing the data. So all the pipeline to generate this data from OpenStreetMap is open source. There is a Java program using a library called PlanetTiler which is awesome, which is this super fast multi-core way of building map tiles. And right now there isn't really great hooks to customize what data goes into that. But that's something that I do wanna work on. And finally, because the data comes from OpenStreetMap if you notice data that's missing or you wanted to correct data in OSM then you can go into osm.org. You can get involved in contributing the data to OSM and the Protomaps build is daily. So if you make a change, then within 24 hours you should see the new base map. Have that change. And of course for OSM your improvements would go into every OSM based project that is ingesting that data. So it's not a protomap specific thing. It's like this big shared data source, almost like Wikipedia. OpenStreetMap is a dataset and not a map [00:37:01] Jeremy: I think you were involved with OpenStreetMap to some extent. Can you speak a little bit to that for people who aren't familiar, what OpenStreetMap is? [00:37:11] Brandon: Right. So I've been using OSM as sort of like a tools developer for over a decade now. And one of the number one questions I get from developers about what is Protomaps is why wouldn't I just use OpenStreetMap? What's the distinction between Protomaps and OpenStreetMap? And it's sort of like this funny thing because even though OSM has map in the name it's not really a map in that you can't... In that it's mostly a data set and not a map. It does have a map that you can see that you can pan around to when you go to the website but the way that thing they show you on the website is built is not really that easily reproducible. It involves a lot of c++ software you have to run. But OpenStreetMap itself, the heart of it is almost like a big XML file that has all the data in the map and global. And it has tagged features for example. So you can go in and edit that. It has a web front end to change the data. It does not directly translate into making a map actually. Protomaps decides what shows at each zoom level [00:38:24] Brandon: So a lot of the pipeline, that Java program I mentioned for building this basemap for protomaps is doing things like you have to choose what data you show when you zoom out. You can't show all the data. For example when you're zoomed out and you're looking at all of a state like Colorado you don't see all the Chipotle when you're zoomed all the way out. That'd be weird, right? So you have to make some sort of decision in logic that says this data only shows up at this zoom level. And that's really what is the challenge in optimizing the size of that for the Protomaps map project. [00:39:03] Jeremy: Oh, so those decisions of what to show at different Zoom levels those are decisions made by you when you're creating the PMTiles file with Protomaps. [00:39:14] Brandon: Exactly. It's part of the base maps build pipeline. and those are honestly very subjective decisions. Who really decides when you're zoomed out should this hospital show up or should this museum show up nowadays in Google, I think it shows you ads. Like if someone pays for their car repair shop to show up when you're zoomed out like that that gets surfaced. But because there is no advertising auction in Protomaps that doesn't happen obviously. So we have to sort of make some reasonable choice. A lot of that right now in Protomaps actually comes from another open source project called Mapzen. So Mapzen was a company that went outta business a couple years ago. They did a lot of this work in designing which data shows up at which Zoom level and open sourced it. And then when they shut down, they transferred that code into the Linux Foundation. So it's this totally open source project, that like, again, sort of like Mapbox gl has this awesome legacy in that this company funded it for years for smart people to work on it and now it's just like a free thing you can use. So the logic in Protomaps is really based on mapzen. [00:40:33] Jeremy: And so the visualization of all this... I think I understand what you mean when people say oh, why not use OpenStreetMaps because it's not really clear it's hard to tell is this the tool that's visualizing the data? Is it the data itself? So in the case of using Protomaps, it sounds like Protomaps itself has all of the data from OpenStreetMap and then it has made all the decisions for you in terms of what to show at different Zoom levels and what things to have on the map at all. And then finally, you have to have a separate, UI layer and in this case, it sounds like the one that you recommend is the Map Libre library. [00:41:18] Brandon: Yeah, that's exactly right. For Protomaps, it has a portion or a subset of OSM data. It doesn't have all of it just because there's too much, like there's data in there. people have mapped out different bushes and I don't include that in Protomaps if you wanted to go in and edit like the Java code to add that you can. But really what Protomaps is positioned at is sort of a solution for developers that want to use OSM data to make a map on their app or their website. because OpenStreetMap itself is mostly a data set, it does not really go all the way to having an end-to-end solution. Financials and the idea of a project being complete [00:41:59] Jeremy: So I think it's great that somebody who wants to make a map, they have these tools available, whether it's from what was originally built by Mapbox, what's built by Open StreetMap now, the work you're doing with Protomaps. But I wonder one of the things that I talked about with Tom was he was saying he was trying to build this mapping business and based on the financials of what was coming in he was stressed, right? He was struggling a bit. And I wonder for you, you've been working on this open source project for five years. Do you have similar stressors or do you feel like I could keep going how things are now and I feel comfortable? [00:42:46] Brandon: So I wouldn't say I'm a hundred percent in one bucket or the other. I'm still seeing it play out. One thing, that I really respect in a lot of open source projects, which I'm not saying I'm gonna do for Protomaps is the idea that a project is like finished. I think that is amazing. If a software project can just be done it's sort of like a painting or a novel once you write, finish the last page, have it seen by the editor. I send it off to the press is you're done with a book. And I think one of the pains of software is so few of us can actually do that. And I don't know obviously people will say oh the map is never finished. That's more true of OSM, but I think like for Protomaps. One thing I'm thinking about is how to limit the scope to something that's quite narrow to where we could be feature complete on the core things in the near term timeframe. That means that it does not address a lot of things that people want. Like search, like if you go to Google Maps and you search for a restaurant, you will get some hits. that's like a geocoding issue. And I've already decided that's totally outta scope for Protomaps. So, in terms of trying to think about the future of this, I'm mostly looking for ways to cut scope if possible. There are some things like better tooling around being able to work with PMTiles that are on the roadmap. but for me, I am still enjoying working on the project. It's definitely growing. So I can see on NPM downloads I can see the growth curve of people using it and that's really cool. So I like hearing about when people are using it for cool projects. So it seems to still be going okay for now. [00:44:44] Jeremy: Yeah, that's an interesting perspective about how you were talking about projects being done. Because I think when people look at GitHub projects and they go like, oh, the last commit was X months ago. They go oh well this is dead right? But maybe that's the wrong framing. Maybe you can get a project to a point where it's like, oh, it's because it doesn't need to be updated. [00:45:07] Brandon: Exactly, yeah. Like I used to do a lot of c++ programming and the best part is when you see some LAPACK matrix math library from like 1995 that still works perfectly in c++ and you're like, this is awesome. This is the one I have to use. But if you're like trying to use some like React component library and it hasn't been updated in like a year, you're like, oh, that's a problem. So again, I think there's some middle ground between those that I'm trying to find. I do like for Protomaps, it's quite dependency light in terms of the number of hard dependencies I have in software. but I do still feel like there is a lot of work to be done in terms of project scope that needs to have stuff added. You mostly only hear about problems instead of people's wins [00:45:54] Jeremy: Having run it for this long. Do you have any thoughts on running an open source project in general? On dealing with issues or managing what to work on things like that? [00:46:07] Brandon: Yeah. So I have a lot. I think one thing people point out a lot is that especially because I don't have a direct relationship with a lot of the people using it a lot of times I don't even know that they're using it. Someone sent me a message saying hey, have you seen flickr.com, like the photo site? And I'm like, no. And I went to flickr.com/map and it has Protomaps for it. And I'm like, I had no idea. But that's cool, if they're able to use Protomaps for this giant photo sharing site that's awesome. But that also means I don't really hear about when people use it successfully because you just don't know, I guess they, NPM installed it and it works perfectly and you never hear about it. You only hear about people's negative experiences. You only hear about people that come and open GitHub issues saying this is totally broken, and why doesn't this thing exist? And I'm like, well, it's because there's an infinite amount of things that I want to do, but I have a finite amount of time and I just haven't gone into that yet. And that's honestly a lot of the things and people are like when is this thing gonna be done? So that's, that's honestly part of why I don't have a public roadmap because I want to avoid that sort of bickering about it. I would say that's one of my biggest frustrations with running an open source project is how it's self-selected to only hear the negative experiences with it. Be careful what PRs you accept [00:47:32] Brandon: 'cause you don't hear about those times where it works. I'd say another thing is it's changed my perspective on contributing to open source because I think when I was younger or before I had become a maintainer I would open a pull request on a project unprompted that has a hundred lines and I'd be like, Hey, just merge this thing. But I didn't realize when I was younger well if I just merge it and I disappear, then the maintainer is stuck with what I did forever. You know if I add some feature then that person that maintains the project has to do that indefinitely. And I think that's very asymmetrical and it's changed my perspective a lot on accepting open source contributions. I wanna have it be open to anyone to contribute. But there is some amount of back and forth where it's almost like the default answer for should I accept a PR is no by default because you're the one maintaining it. And do you understand the shape of that solution completely to where you're going to support it for years because the person that's contributing it is not bound to those same obligations that you are. And I think that's also one of the things where I have a lot of trepidation around open source is I used to think of it as a lot more bazaar-like in terms of anyone can just throw their thing in. But then that creates a lot of problems for the people who are expected out of social obligation to continue this thing indefinitely. [00:49:23] Jeremy: Yeah, I can totally see why that causes burnout with a lot of open source maintainers, because you probably to some extent maybe even feel some guilt right? You're like, well, somebody took the time to make this. But then like you said you have to spend a lot of time trying to figure out is this something I wanna maintain long term? And one wrong move and it's like, well, it's in here now. [00:49:53] Brandon: Exactly. To me, I think that is a very common failure mode for open source projects is they're too liberal in the things they accept. And that's a lot of why I was talking about how that choice of what features show up on the map was inherited from the MapZen projects. If I didn't have that then somebody could come in and say hey, you know, I want to show power lines on the map. And they open a PR for power lines and now everybody who's using Protomaps when they're like zoomed out they see power lines are like I didn't want that. So I think that's part of why a lot of open source projects eventually evolve into a plugin system is because there is this demand as the project grows for more and more features. But there is a limit in the maintainers. It's like the demand for features is exponential while the maintainer amount of time and effort is linear. Plugin systems might reduce need for PRs [00:50:56] Brandon: So maybe the solution to smash that exponential down to quadratic maybe is to add a plugin system. But I think that is one of the biggest tensions that only became obvious to me after working on this for a couple of years. [00:51:14] Jeremy: Is that something you're considering doing now? [00:51:18] Brandon: Is the plugin system? Yeah. I think for the data customization, I eventually wanted to have some sort of programmatic API to where you could declare a config file that says I want ski routes. It totally makes sense. The power lines example is maybe a little bit obscure but for example like a skiing app and you want to be able to show ski slopes when you're zoomed out well you're not gonna be able to get that from Mapbox or from Google because they have a one size fits all map that's not specialized to skiing or to golfing or to outdoors. But if you like, in theory, you could do this with Protomaps if you changed the Java code to show data at different zoom levels. And that is to me what makes the most sense for a plugin system and also makes the most product sense because it enables a lot of things you cannot do with the one size fits all map. [00:52:20] Jeremy: It might also increase the complexity of the implementation though, right? [00:52:25] Brandon: Yeah, exactly. So that's like. That's really where a lot of the terrifying thoughts come in, which is like once you create this like config file surface area, well what does that look like? Is that JSON? Is that TOML, is that some weird like everything eventually evolves into some scripting language right? Where you have logic inside of your templates and I honestly do not really know what that looks like right now. That feels like something in the medium term roadmap. [00:52:58] Jeremy: Yeah and then in terms of bug reports or issues, now it's not just your code it's this exponential combination of whatever people put into these config files. [00:53:09] Brandon: Exactly. Yeah. so again, like I really respect the projects that have done this well or that have done plugins well. I'm trying to think of some, I think obsidian has plugins, for example. And that seems to be one of the few solutions to try and satisfy the infinite desire for features with the limited amount of maintainer time. Time split between code vs triage vs talking to users [00:53:36] Jeremy: How would you say your time is split between working on the code versus issue and PR triage? [00:53:43] Brandon: Oh, it varies really. I think working on the code is like a minority of it. I think something that I actually enjoy is talking to people, talking to users, getting feedback on it. I go to quite a few conferences to talk to developers or people that are interested and figure out how to refine the message, how to make it clearer to people, like what this is for. And I would say maybe a plurality of my time is spent dealing with non-technical things that are neither code or GitHub issues. One thing I've been trying to do recently is talk to people that are not really in the mapping space. For example, people that work for newspapers like a lot of them are front end developers and if you ask them to run a Linux server they're like I have no idea. But that really is like one of the best target audiences for Protomaps. So I'd say a lot of the reality of running an open source project is a lot like a business is it has all the same challenges as a business in terms of you have to figure out what is the thing you're offering. You have to deal with people using it. You have to deal with feedback, you have to deal with managing emails and stuff. I don't think the payoff is anywhere near running a business or a startup that's backed by VC money is but it's definitely not the case that if you just want to code, you should start an open source project because I think a lot of the work for an opensource project has nothing to do with just writing the code. It is in my opinion as someone having done a VC backed business before, it is a lot more similar to running, a tech company than just putting some code on GitHub. Running a startup vs open source project [00:55:43] Jeremy: Well, since you've done both at a high level what did you like about running the company versus maintaining the open source project? [00:55:52] Brandon: So I have done some venture capital accelerator programs before and I think there is an element of hype and energy that you get from that that is self perpetuating. Your co-founder is gungho on like, yeah, we're gonna do this thing. And your investors are like, you guys are geniuses. You guys are gonna make a killing doing this thing. And the way it's framed is sort of obvious to everyone that it's like there's a much more traditional set of motivations behind that, that people understand while it's definitely not the case for running an open source project. Sometimes you just wake up and you're like what the hell is this thing for, it is this thing you spend a lot of time on. You don't even know who's using it. The people that use it and make a bunch of money off of it they know nothing about it. And you know, it's just like cool. And then you only hear from people that are complaining about it. And I think like that's honestly discouraging compared to the more clear energy and clearer motivation and vision behind how most people think about a company. But what I like about the open source project is just the lack of those constraints you know? Where you have a mandate that you need to have this many customers that are paying by this amount of time. There's that sort of pressure on delivering a business result instead of just making something that you're proud of that's simple to use and has like an elegant design. I think that's really a difference in motivation as well. Having control [00:57:50] Jeremy: Do you feel like you have more control? Like you mentioned how you've decided I'm not gonna make a public roadmap. I'm the sole developer. I get to decide what goes in. What doesn't. Do you feel like you have more control in your current position than you did running the startup? [00:58:10] Brandon: Definitely for sure. Like that agency is what I value the most. It is possible to go too far. Like, so I'm very wary of the BDFL title, which I think is how a lot of open source projects succeed. But I think there is some element of for a project to succeed there has to be somebody that makes those decisions. Sometimes those decisions will be wrong and then hopefully they can be rectified. But I think going back to what I was talking about with scope, I think the overall vision and the scope of the project is something that I am very opinionated about in that it should do these things. It shouldn't do these things. It should be easy to use for this audience. Is it gonna be appealing to this other audience? I don't know. And I think that is really one of the most important parts of that leadership role, is having the power to decide we're doing this, we're not doing this. I would hope other developers would be able to get on board if they're able to make good use of the project, if they use it for their company, if they use it for their business, if they just think the project is cool. So there are other contributors at this point and I want to get more involved. But I think being able to make those decisions to what I believe is going to be the best project is something that is very special about open source, that isn't necessarily true about running like a SaaS business. [00:59:50] Jeremy: I think that's a good spot to end it on, so if people want to learn more about Protomaps or they wanna see what you're up to, where should they head? [01:00:00] Brandon: So you can go to Protomaps.com, GitHub, or you can find me or Protomaps on bluesky or Mastodon. [01:00:09] Jeremy: All right, Brandon, thank you so much for chatting today. [01:00:12] Brandon: Great. Thank you very much.

In this week's episode of Market Mondays, we dive into the global economic storm brewing as Trump's proposed tariffs spark fears of a full-blown trade war. We unpack how these moves are shaking markets—from auto stocks taking a hit in Europe to Goldman Sachs raising the likelihood of a U.S. recession. Gold is hitting all-time highs, and we break down what that says about investor sentiment. Plus, we discuss which car brands, if any, might be worth a look right now, and whether major companies could start adding Bitcoin to their balance sheets as an economic hedge.We also take a deep look into the AI boom: who's set to benefit next in the ecosystem, and which companies are quietly leveraging NVIDIA's AI stack for future dominance. We review Dennis Fish's 2024 stock picks and play a high-stakes game of portfolio building from a curated list of major players like Netflix, HubSpot, Palo Alto, and Alibaba. To close out, we offer financial advice specifically for married couples looking to build together in uncertain economic times. Tap in!#MarketMondays #Gold #TrumpTariffs #AIStocks #Bitcoin #Recession #Investing #StockMarket #Finance #MarriedMoney #FinancialFreedom #EarnYourLeisure #NVDA #TradeWarTimestamps:12:10 – Biggest lesson learned this week15:55 – Gold hits all-time high21:38 – Trump's incoming tariff plans & market impact40:00 – Who will benefit next in the AI ecosystem?48:00 – Which company benefits most from NVDA's AI stack?52:30 – Dennis Fish's 2024 picks (CDNS, KLA, MELI) — Do we love them?57:00 – Building a portfolio from this stock list: INTU, ASTL, BKNG, HUBS, NFLX, PANW, PWR, BABA, CYBR1:08:30 – Trump tariffs shake Europe: Are any car stocks worth investing in?1:26:00 – Goldman Sachs raises recession odds to 35%: Trade war fallout1:31:00 – Will major companies start adding Bitcoin to hedge against downturns?1:34:10 – How uncertain are we as Q2 kicks off?1:48:00 – Financial advice for married couplesOur Sponsors:* Check out NerdWallet: https://www.nerdwallet.comSupport this podcast at — https://redcircle.com/marketmondays/donationsAdvertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacy

En este episodio, exploramos los eventos más relevantes que están afectando los mercados y sectores estratégicos: Mercados en tensión por aranceles y datos de inflación: Wall Street opera mixto mientras los inversionistas esperan el PPI de febrero. Canadá y la UE responden con tarifas del 25% sobre bienes estadounidenses, intensificando la guerra comercial. Intel nombra a Lip-Bu Tan como CEO: El ex líder de $CDNS asumirá la dirección de $INTC tras la salida de Pat Gelsinger. Analizamos cómo este cambio podría transformar la estrategia de la compañía en IA y semiconductores. D-Wave Quantum declara supremacía cuántica: $QBTS anuncia que su computadora cuántica ha superado a supercomputadoras en simulaciones, impulsando el sector cuántico. Discutimos el impacto para empresas como $QUBT, $IONQ y $GOOGL. Oro en alza por guerra comercial: El metal precioso sigue subiendo mientras los aranceles de Trump y la inflación generan temores de recesión. Evaluamos cómo este entorno podría influir en las decisiones de la Fed y en los mercados de refugio. Acompáñanos para entender cómo estos eventos están moldeando los mercados, la tecnología y la política monetaria. ¡Un episodio lleno de análisis estratégico!

President Trump rolls back AI regulations and throws TikTok a lifeline. Attackers pose as Ukraine's CERT-UA tech support. A critical vulnerability is found in the Brave browser. Sophos observes hacking groups abusing Microsoft 365 services and exploiting default Microsoft Teams settings. Researchers uncover critical flaws in tunneling protocols. A breach exposes personal information of thousands of students and educators. Oracle patches 320 security vulnerabilities. Kaspersky reveals over a dozen vulnerabilities in a Mercedes-Benz infotainment system. Tim Starks from CyberScoop discusses executive orders on cybersecurity and the future of CISA. We preview coming episodes of Threat Vector.  Honesty isn't always the best policy.  Remember to leave us a 5-star rating and review in your favorite podcast app. Miss an episode? Sign-up for our daily intelligence roundup, Daily Briefing, and you'll never miss a beat. And be sure to follow CyberWire Daily on LinkedIn. Threat Vector Segment On our Threat Vector podcast preview today:  IoT devices are everywhere, with billions deployed globally in industries like healthcare, manufacturing, and critical infrastructure. But this explosion of connectivity brings unprecedented security challenges. Host David Moulton speaks with Dr. May Wang, CTO of IoT Security at Palo Alto Networks, about how AI is transforming IoT security. Stay tuned for the full conversation this Thursday.  CyberWire Guest Our guest is Tim Starks from CyberScoop discussing executive orders on cybersecurity and the future of CISA. You can read Tim's article on the recent Biden EO here.   Selected Reading Trump revokes Biden executive order on addressing AI risks (Reuters) TikTok is back up in the US after Trump says he will extend deadline (Bleeping Computer) Hackers impersonate Ukraine's CERT to trick people into allowing computer access (The Record)  Brave Browser Vulnerability Let Malicious Website Mimic as Legitimate One (Cyber Security News)  Ransomware Groups Abuse Microsoft Services for Initial Access (SecurityWeek) Tunneling Flaws Put VPNs, CDNs and Routers at Risk Globally (Hackread) Students, Educators Impacted by PowerSchool Data Breach (SecurityWeek) Oracle To Address 320 Vulnerabilities in January Patch Update (Infosecurity Magazine) Details Disclosed for Mercedes-Benz Infotainment Vulnerabilities (SecurityWeek) Washington Man Admits to Role in Multiple Cybercrime, Fraud Schemes (SecurityWeek) Share your feedback. We want to ensure that you are getting the most out of the podcast. Please take a few minutes to share your thoughts with us by completing our brief listener survey as we continually work to improve the show.  Want to hear your company in the show? You too can reach the most influential leaders and operators in the industry. Here's our media kit. Contact us at cyberwire@n2k.com to request more info. The CyberWire is a production of N2K Networks, your source for strategic workforce intelligence. © N2K Networks, Inc. Learn more about your ad choices. Visit megaphone.fm/adchoices

Brad Mitchell of Mojohost is this week's guest on Adult Site Broker Talk in part two of a two-part interview. Brad is a veteran of the adult industry. He is the founder of MojoHost. MojoHost was founded in 1999. Since its inception, they have been an adult-friendly web host. They offer Cloud computing, Cloud Storage, Virtual Private Servers, Dedicated Servers, CDNs, Domains, and Technical Support Services. With over 2,000 customers across its multiple hosting brands, MojoHost is the trusted home for more than 50,000 websites. Its global staff of more than 50 employees service them via its numerous data centers in the United States and Europe. MojoHost prides itself on delivering world-class support and has won many awards from every major industry awards show. Adult Site Broker is the most experienced company to broker adult sites. They've sold and helped people buy more xxx sites than any other broker. Adult Site Broker is the leading company to sell porn sites and buy porn sites. They help their clients work out equitable deals. Check out their brand-new website at www.adultsitebroker.com, the leading destination to broker porn sites. Adult Site Broker also has an affiliate program, ASB Cash, at https://asbcash.com, where you can earn 20% by referring people to buy adult sites and sell adult sites to Adult Site Broker, the porn website broker. For more information, please visit us at www.adultsitebroker.com to help you broker adult sites. Listen to Brad Mitchell of Mojohost on Adult Site Broker Talk, starting today at www.adultsitebrokertalk.com

Brad Mitchell of Mojohost is this week's guest on Adult Site Broker Talk in part one of a two-part interview. Brad is a veteran of the adult industry. He is the founder of MojoHost. MojoHost was founded in 1999. Since its inception, they have been an adult-friendly web host. They offer Cloud computing, Cloud Storage, Virtual Private Servers, Dedicated Servers, CDNs, Domains, and Technical Support Services. With over 2,000 customers across its multiple hosting brands, MojoHost is the trusted home for more than 50,000 websites. Its global staff of more than 50 employees service them via its numerous data centers in the United States and Europe. MojoHost prides itself on delivering world-class support and has won many awards from every major industry awards show. Adult Site Broker is the most experienced company to broker adult sites. They've sold and helped people buy more xxx sites than any other broker. Adult Site Broker is the leading company to sell porn sites and buy porn sites. They help their clients work out equitable deals. Check out their brand-new website at www.adultsitebroker.com, the leading destination to broker porn sites. Adult Site Broker also has an affiliate program, ASB Cash, at https://asbcash.com, where you can earn 20% by referring people to buy adult sites and sell adult sites to Adult Site Broker, the porn website broker. For more information, please visit us at www.adultsitebroker.com to help you broker adult sites. Listen to Brad Mitchell of Mojohost on Adult Site Broker Talk, starting today at www.adultsitebrokertalk.com

In the first episode in our customer interview series, Joe DePalo, Vice President and Chief Platform Officer at Netskope, joins Avi Freedman and Jezzibell Gilmore of Kentik to explore how content delivery networks (CDNs) enable the seamless, high-performance internet we take for granted. We demystify some of the “magic” of the internet, and highlight the critical role of edge connectivity in reducing latency, optimizing delivery, and ensuring great user experiences. We also explore the challenges of maintaining a performant internet as we end 2024: What are the evolving network performance and security demands? And why does making them work well remain a tough problem?

In this episode of Environment Variables, Anne Currie welcomes Carlos Pignataro, a leading expert in sustainable network architecture, to explore how networks can balance energy efficiency with performance and resilience. Carlos shares insights from his career at Cisco and beyond, including strategies for reducing emissions through dynamic software principles, energy-aware networking, and leveraging technologies like IoT and Content Delivery Networks (CDNs). They discuss practical applications, the alignment of green practices with business interests, and the role of multidisciplinary collaboration in driving innovation. Tune in for actionable advice and forward-thinking perspectives on making networks greener while enhancing their capabilities.

In this episode, join us as we chat with Kevin Bratch, a Canadian real estate expert diving into opportunities south of the border. Discover his journey into U.S. real estate, his innovative software for Canadian investors, and tips on fix-and-flip strategies.   ================================== Want to grow your real estate investing business and portfolio?  You're in the right place. Welcome to the Property Profits Real Estate Podcast

Ralph Burns and John Moran are giving you an exclusive sneak peek into Tier 11's Data Suite, designed to solve the long-standing issues of attribution and data integrity in digital marketing. They explore how this tool leverages edge servers and CDNs to clean up and optimize data, offering marketers better visibility and accuracy for decision-making. They point out the pitfalls of traditional tracking methods, share insights on ad spend optimization, and discuss the implications for small and mid-sized businesses navigating a complex ad ecosystem. Their conversation is laced with examples that explain the impact of precise data in scaling businesses effectively.Chapters00:00:00 - Welcome to the Party: Ralph's Big Data Reveal00:01:00 - Oh, Privacy, You're Killing Me: The Data Crisis Unpacked00:01:36 - The Secret Sauce: Tier 11's Data Suite (You're Welcome)00:02:29 - John's Here, Let's Get Serious (Kind of)00:05:15 - Attribution: The World's Most Annoying Puzzle00:08:14 - The Edge, the Warehouse, and the Interface Walk Into a Bar00:13:14 - War Stories: Real Clients, Real Wins, Real Chaos00:18:19 - Tech Nerd Alert: The Edge Servers Explained00:21:05 - Tag, You're It: The CDN That Knows Everything00:25:45 - Lost in Data Limbo? Here's How to Get Out00:28:12 - First-Party Data: The Cleanest Dirty Laundry You'll Ever Own00:30:35 - Performance Max Is Lying to You (But It's Okay)00:32:20 - Smarter Decisions Start Here: Data You Can Actually Trust00:34:22 - Autopsy Time: How Campaigns Succeed (or Crash)00:35:38 - Performance Max vs. Reality: Spoiler Alert, It's Complicated00:36:20 - ROAS Dreams and Brand Nightmares00:37:43 - Cold Traffic, Warm Wallets: Campaign Tips That Work00:38:38 - Brave New World: Non-Brand Search Campaigns for Beginners00:43:54 - Feeder Strategy Gold: Insights You Didn't Know You Needed00:45:24 - Q&A: Your Burning Questions, Our Smug Answers00:54:30 - Black Friday: Scaling Without Losing Your Mind01:00:05 - That's a Wrap: See ya!LINKS AND RESOURCES:Tier 11 JobsPerpetual Traffic on YouTubeTiereleven.comMarketing Performance Indicators™ ChecklistSchedule a Tier 11 Discovery CallAdCritter for AgenciesAgency Freedom Live - December 2024Mongoose MediaPerpetual Traffic SurveyPerpetual Traffic WebsiteFollow Perpetual Traffic on TwitterConnect with Lauren on Instagram and Connect with Ralph on LinkedInThanks so much for joining us this week. Want...

Omar Ramadan, CEO and co-founder of BlockCast, discusses the challenges of content delivery in the current internet landscape, particularly the monopolistic control over media distribution and the resulting internet capacity crunch. He explains how BlockCast aims to decentralize content delivery using blockchain technology, allowing individuals and organizations to participate in a more efficient and equitable media distribution system. The discussion also covers the marketplace dynamics for CDNs, the product roadmap for BlockCast, and Omar's vision for the future of internet broadcasting. Why you should listen Blockcast is a cutting-edge content delivery network (CDN) that utilizes multicast technology to revolutionize internet content distribution. Unlike traditional centralized CDNs, Blockcast operates through a decentralized caching architecture. This approach aggregates capacity from a global network of nodes, enabling content providers, such as streaming platforms and gaming companies, to deliver high-quality experiences more efficiently. By leveraging this decentralized framework, Blockcast reduces delivery costs and extends its reach to even the most remote areas. At the core of Blockcast's offering is its Multicast Adaptive HTTP Proxy technology. This enables one-to-many content delivery, optimizing bandwidth usage and alleviating network congestion. Blockcast is creating a Capacity Marketplace where content providers can purchase delivery capacity from a diverse range of network operators, including ISPs, over-the-air broadcasters (ATSC, 5G, DVB, and satellite), and individual users hosting caching nodes. This system not only maximizes resource utilization but also opens up new revenue streams for participants. Blockcast's decentralized caching nodes play a vital role in enhancing content delivery speed and reliability. Individuals and organizations are incentivized to host these nodes through Web3 token rewards, encouraging widespread participation and bolstering the network's robustness. The benefits of this setup extend across various stakeholders. Content providers can cut delivery expenses while maintaining high-quality service and expanding into underserved regions. The multicast capabilities further allow for the efficient delivery of high-resolution content like 4K streaming without additional cost burdens. Broadcasters, including ATSC 3.0 television stations, cellular carriers, and satellite operators, can capitalize on their existing infrastructure by contributing data channel capacity to Blockcast. This not only helps them generate new revenue streams but also allows them to participate actively in the evolving digital content ecosystem. Similarly, CDNs and ISPs gain an opportunity to extend their capacity and reach, especially in geographies where deploying traditional infrastructure may not be economically feasible. In April 2024, Blockcast joined the Advanced Television Systems Committee (ATSC) to support the development of ATSC 3.0 technologies. This collaboration underscores Blockcast's dedication to mitigating network congestion and inefficiencies tied to unicast content delivery. By integrating over-the-air digital technologies, Blockcast is positioned at the forefront of content distribution innovation. Blockcast's decentralized approach addresses key challenges in the content delivery space, including high costs, network congestion, and infrastructure limitations. Its scalable solution is well-suited for the increasing demands of today's digital content consumers, providing an efficient, cost-effective alternative to traditional CDNs. Supporting links Stabull Finance Blockcast Andy on Twitter  Brave New Coin on Twitter Brave New Coin If you enjoyed the show please subscribe to the Crypto Conversation and give us a 5-star rating and a positive review in whatever podcast app you are using.

Check out the New Bond account with an initial APY of 6.9%, only at https://public.com/csi Arm Holding (ARM) and Qualcomm (QCOM) are in the midst of a legal battle over Qualcomm's use of Arm licenses for design of the Snapdragon X Elite laptop chips. Meanwhile, software design leader Cadence Design Systems' (CDNS) stated that they are expanding their relationship with Arm. What does all this mean? Is Qualcomm in trouble? Is Arm being silly? And who ultimately wins from an investment perspective? Chip Stock Investor breaks down where these three companies fit within the semiconductor supply chain. Blog Post: https://chipstockinvestor.com/qualcomm-vs-apple-will-history-be-changed-as-two-new-chips-target-the-laptop-market-giants/ Join us on Discord with Semiconductor Insider: https://ko-fi.com/chipstockinvestor

Cadence Design Systems (CDNS) takes off after a 3Q earnings beat. George Tsilis breaks down this company's exposure to the semiconductor industry, saying CDNS could be a good barometer for any potential weakness in that group. ======== Schwab Network ======== Empowering every investor and trader, every market day. Subscribe to the Market Minute newsletter - https://schwabnetwork.com/subscribe Download the iOS app - https://apps.apple.com/us/app/schwab-network/id1460719185 Download the Amazon Fire Tv App - https://www.amazon.com/TD-Ameritrade-Network/dp/B07KRD76C7 Watch on Sling - https://watch.sling.com/1/asset/191928615bd8d47686f94682aefaa007/watch Watch on Vizio - https://www.vizio.com/en/watchfreeplus-explore Watch on DistroTV - https://www.distro.tv/live/schwab-network/ Follow us on X – https://twitter.com/schwabnetwork Follow us on Facebook – https://www.facebook.com/schwabnetwork Follow us on LinkedIn - https://www.linkedin.com/company/schwab-network/ About Schwab Network - https://schwabnetwork.com/about

Sam and Ryan talk about how frameworks and infrastructure evolve with each other, using Next.js as a representative example. They discuss how hosting providers like Heroku have always imposed certain constraints on apps, what features those constraints enable hosting providers to support, how burdensome those constraints are across different frameworks, and how frameworks that add infra-specific APIs can best communicate the costs of those APIs and benefits they enable.Timestamps:0:00 - Intro3:03 - Heroku and the Twelve-Factor App7:39 - GitHub Pages and static sites13:57 - Serverless and JAMstack17:30 - Vercel and CDNs, self-hosting, and Next.js19:00 - How framework APIs can nudge an app towards a particular hosting solution23:09 - What constraints does Next.js impose on your app (e.g. middleware doesn't run node), and what benefits do those constraints give you?36:13 - How Next.js APIs are motivated by wanting to tease apart static and dynamic code, in an attempt to support the needs of any web app with a single stack40:33 - What is the relationship between frameworks and infra?47:37 - How can frameworks that add infra-specific APIs best communicate the costs of those APIs and the benefits they enable?Links:The Twelve-Factor App

Connor had the pleasure of sitting down with Omar Ramadan, a former big tech entrepreneur who transitioned into the world of crypto and DePIN. They delved into the concept of Content Delivery Networks (CDNs) and how they play a crucial role in enhancing user experience by caching website data closer to users geographically. Omar shared his background, including his involvement in projects like Magma and OpenCellular, which aimed to provide connectivity to remote communities. They discussed the limitations of traditional CDNs, particularly in live streaming scenarios where multiple users access the same content. Omar highlighted the inefficiencies of unicast-based CDNs and introduced the idea of multicast CDNs, which can significantly reduce bandwidth usage by allowing multiple users to share the same stream. The conversation also touched on the challenges faced by streaming giants in deploying CDN infrastructure in high-demand areas, as well as the potential of decentralized infrastructure and blockchain technology to incentivize individuals to run their own CDN nodes. Omar explained how DePIN's could help overcome the cold start problem and facilitate a more efficient and cost-effective CDN model. Overall, this episode provided valuable insights into the future of content delivery, the role of decentralization, and the exciting possibilities that lie ahead in the intersection of technology and crypto. 00:00 - Introduction 00:38 - Omar's Transition from Big Tech to Crypto 02:54 - Understanding CDNs: A User's Perspective 03:32 - How CDNs Work: Caching and Latency 05:01 - Challenges for Remote Areas and Streaming Giants 06:25 - The Role of Locality in CDN Performance 08:24 - CDNs and the Future of the Metaverse 10:19 - Multicast CDNs: A New Paradigm 10:41 - Incentives and Blockchain in CDN Infrastructure 12:30 - Conclusion  Disclaimer: The hosts and the firms they represent may hold stakes in the companies mentioned in this podcast. None of this is financial advice.

Dein Code ist nichts wert, bevor er nicht in Produktion ist!Viele Software-Entwickler*innen haben sich bereits in der Situation gefunden, wo wir immer und immer wieder über den eigenen Source Code iterieren, um diesen noch schöner zu machen. Soviel Spaß dies auch macht … ist das schönste Gefühl jedoch, wenn jemand meinen Source Code wirklich nutzt. Und das geht nur, wenn wir diesen auch deployen.Oder etwas direkter gesagt: Dein Source Code ist solange nichts wert, bis dieser nicht in Produktion ist und vom Kunden genutzt werden kann. Klingt hart, ist aber Fakt. Deswegen geht's in dieser Podcast Episode um das Thema Deployment.Wir sprechen über Anti-Patterns wie manuelle Deployments, Big-Bang Deployments und Deployment Monolithen. Wir schauen uns an welche Herausforderungen wir bereits in unserer beruflichen Laufbahn bei Deployments gesehen haben, wie zB Caching, CDNs, Deployment unter Hochlast oder das Einspielen von Datenbankänderungen und geben mal eine Tour durch verschiedene Deployment-Arten, mit u.a. Canary Deployments, der Blue-Green-Stratgie, Feature Flags oder Shadow Deployments bzw. Dark Launches.Final bringen wir die Frage auf den Tisch, wann du das letzte mal deinen Rollback getestet hast.Bonus: Wie macht man eine Podcast-Episode über Deployment ohne Continuous Delivery und Continuous Deployment (CD) zu erwähnen?Das schnelle Feedback zur Episode:

“How do we help others, especially those that don't have a good opportunity? But, you know, they don't have life on a silver platter. So how do we make silver platters for people?” “You never wanna go to the president and talk about yourself. You wanna go to the president and you wanna talk about the team and what the team did…” “A coach talks to you, a mentor talks with you, and a sponsor talks about you.” Chapters: 00:00  Innovation and Inclusivity: A Journey with Yvette Kanouff 03:00  The Impact of AI and Endless Possibilities in Technology 08:54  The Power of Genuine Connections and Generosity 25:26  The Art of Leadership and Management 32:18  Navigating Mentorship and Self-Advocacy 41:09  Embracing Authentic Leadership Episode Summary: Yvette Kanouff, an Emmy award-winning technology pioneer and partner at JC2 Ventures, shares insights on technology, innovation, inclusivity, and generosity. She discusses her background, the impact of AI, the importance of networking, and the concept of return on generosity. Yvette emphasizes the value of genuine connections, the power of innovation, and the role of generosity in creating opportunities for others. The conversation covers a range of topics related to leadership, management, mentorship, and self-advocacy. It emphasizes the importance of results and followership in promotions, the value of team-first leadership, and the significance of being true to oneself. It also delves into the role of coaching, mentoring, and sponsorship, as well as the art of having difficult conversations with honesty and kindness. R.O.G. Takeaway Tips: Yvette Kanouff's journey from Germany to the US and her passion for innovation and inclusivity. The impact of AI on technology and the endless possibilities for innovation and improvement. The importance of genuine connections, generosity, and networking in creating opportunities for others. The concept of return on generosity and the value of empathetic and generous leadership in the workplace. Results and followership are key factors in promotions. Team-first leadership and focusing on the success of the team are essential for effective management. Being true to oneself and embracing one's unique leadership style is crucial for success. The roles of coaching, mentoring, and sponsorship are valuable in personal and professional development. Having difficult conversations with honesty and kindness is an important skill in leadership and management. Guest Bio: Yvette Kanouff is an Emmy award winning technology pioneer and Partner at JC2 Ventures, a venture firm founded by Cisco Chairman Emeritus and Silicon Valley legend, John Chambers. Yvette headed the $7B service provider business at Cisco Systems, the worldwide leader in IT, networking, and cybersecurity solutions. She has held CTO and President roles at various companies and has focused on leading technology innovation and invention. Yvette has pioneered technologies instrumental in creating video streaming, app stores, MPEG standards, encoding standards, CDNs, and the DVD. Yvette has received numerous industry awards including a 2020 Lifetime Achievement Emmy for her contributions to television engineering and technology, the National Cable and Television Association's Vanguard Award for Leadership in Science and Technology, being named an Industry Pioneer, an Emmy for her work in Video on Demand with SeaChange, being named an Industry Wonder Woman, Top Techie, and Woman in Technology; she has been named one of the 11 most influential women in the Television industry, and has consistently been ranked as one of the top 100 industry executives. Yvette began her career in digital signal processing and has a bachelor's and master's degree in mathematics from UCF. Yvette is a 2011 recipient of the UCF Distinguished Alumni Award and supports UCF students through the Yvette Kanouff Industrial Mathematics Scholarship, in addition to supporting the University and College of Sciences, where she serves on the Dean's Advisory Board. Yvette holds several patents and is on various corporate and industry boards. She is a long-standing leader in industry organizations, foundations, and standards bodies, and she has chaired several industry award boards including the Cable Pioneers and IEEE Ibuka medal award committee. Resources: Cisco's Yvette Kanouff: Massive Transformation for Service Providers Yvette Kanouff Shares Insights on Video on Demand Where to find R.O.G. Podcast: R.O.G on YouTube R.O.G on Apple Podcasts R.O.G on Spotify How diverse is your network?  N.D.I. Network Diversity Index What is your Generosity Style?  Generosity Quiz Credits: Yvette Kanouff, Sheep Jam Productions, Host Shannon Cassidy, Bridge Between, Inc. Coming Next: Please join us next week, Episode 196, with special guest Daisy Auger-Dominguez.

Ben Rains explores where the stock market stands and dives into why the selloff offers long-term investors great opportunities to buy best-in-class tech stocks and artificial intelligence (AI) firms at big discounts. The episode looks specifically at Cadence Design Systems, Inc. (CDNS) and Vertiv Holdings Co (VRT) to see why the stocks might be worth buying down at least 20% as they find support near key moving averages.  (0:30) - Stock Market Update: Should You Buy The Dip? (4:30) - Is Now A Good Time To Buy Cadence Design Systems Stock? (8:45) - Should You Be Investing In Vertiv After The Recent Tech Sell-off? Podcast@Zacks.com

In this episode, James Quick, seasoned JavaScript developer, speaker, and teacher, chats about full stack web development. From single-page applications and static site generators to the latest in server components and hybrid rendering, he covers the evolution of modern web development practices and gives personal insights on navigating these new technologies. Links https://www.jamesqquick.com https://www.youtube.com/c/jamesqquick https://www.tiktok.com/@jamesqquick https://www.learnbuildteach.com https://x.com/jamesqquick We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Let us know by sending an email to our producer, Emily, at emily.kochanekketner@logrocket.com (mailto:emily.kochanekketner@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understand where your users are struggling by trying it for free at [LogRocket.com]. Try LogRocket for free today.(https://logrocket.com/signup/?pdr) Special Guest: James Q. Quick.

David Flanagan, founder of Rawdoke Academy, discusses why WebAssembly (WASM) could be the future of serverless technology and explores the evolution, benefits, and potential of WASM in transforming server-side applications across various environments. Links https://davidflanagan.com https://github.com/davidflanagan https://twitter.com/__DavidFlanagan https://www.linkedin.com/in/rawkode https://rawkode.academy https://youtube.com/@RawkodeAcademy https://www.hopp.bio/rawkode We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Let us know by sending an email to our producer, Emily, at emily.kochanekketner@logrocket.com (mailto:emily.kochanekketner@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understand where your users are struggling by trying it for free at [LogRocket.com]. Try LogRocket for free today.(https://logrocket.com/signup/?pdr) Special Guest: David Flanagan.

Instant analysis of Cadence Design Systems ($CDNS) Q2 earnings, as we hear from CEO Anirudh Devgan. More than “beat” or “miss” –the Drill Down Earnings with Futurum Group chief market strategist Cory Johnson has the business stories behind stocks on the move.    https://x.com/corytv #Cadence Design Systems #Earnings @Cadence Design Systems $CDNS #Technology #Software #CloudComputing #Chips #AI #ArtificialIntelligence #Semiconductors #Stocks #Trading #Business @DrillDownPod Learn more about your ad choices. Visit megaphone.fm/adchoices

 In today's episode, they dive deep into web performance optimization and the strategies employed by our expert panel to achieve it. Join Dan, Steve, Charles, and guest Vinicius Dallacqua as they explore robust techniques like code splitting, lazy loading, and server-side solutions to enhance website performance.In this episode, you'll hear Vinicius discuss his experiences with different benchmarking frameworks and innovative optimization strategies, including how he improved performance for the Prometheus client for Node. They delve into the importance of performance metrics, data analysis, and real user monitoring (RUM) tools. They underscore the need for precise measurements before and after optimizations and share insights on overcoming the challenges posed by third-party integrations.Hear about practical tools like Partytown and Lighthouse, and how companies like NEXX Insurance have achieved significant performance gains. The conversation also touches on the critical balance between backend performance, CDNs, and frontend optimizations, alongside recommendations for engaging management to prioritize performance enhancements.Plus, for a bit of fun, our episode includes some light-hearted "Dad jokes of the week" and book recommendations around TypeScript and AI. SocialsLinkedIn: Vinicius Dallacqua PicksCharles - Take 5 | Board GameDan - Total TypeScriptSteve - Warp: Your terminal, reimaginedVinicius - Watch Sweet Tooth | Netflix Official SiteBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Leger poll: Most Canadians expect Justin Trudeau to try to hang on to the PM title/job until the federal election likely next year. What's the breakdown though? Guest: Andrew Enns. Snr VP Leger Marketing, Central Canada Learn more about your ad choices. Visit megaphone.fm/adchoices

Global News IPSOS poll: Poilievre Top Choice for Best PM in Canada. 68% of Canadians believe Justin Trudeau should step down, including 33% of Liberal voters. Only 25% of Canadians say the Liberals have done a good job.   Bad news continues for Trudeau/Liberals and does this drag down further Jagmeet Singh and NDP?  Trudeau just this week told CBC "Canadians are not in a decision mode right now." Let's find out. Guest: Darrell Bricker. CEO. IPSOS Public Affairs. Learn more about your ad choices. Visit megaphone.fm/adchoices

Today's podcast: As parliament adjourns for 3 months, four issues for Conservative Party of Canada house leader to address:   MPs are up and out of there (parliament) for a voted on 3-month vacation. Conservatives voted against this while Liberals, NDP & BQ voted for the long absence from parliament.  By-election next Tuesday in long held by Liberals Toronto riding of St. Paul. Full court press by Justin Trudeau and LPC MPs. A loss for Liberals would be a very disturbing situation for the party. Federal Minister of Finance Chrystia Freeland's dire warnings about the dark future for Canada and divide among wealthy and poor if Liberals capital gains tax increase not accepted. Trudeau government declares IRGC a terrorist organization.  Global News poll of Canadians by IPSOS shows 68% want Justin Trudeau to resign as prime minister. Guest: Andrew Scheer. CPC MP, Saskatchewan. CPC House leader and former party leader. "Let's Go Oilers."  Edmonton Oilers are "dragging" the Panthers back to Florida for game 7 of the Stanley Cup final. Oilers have decidedly outscored and outplayed the Panthers in games 4, 5 and 6. What is the outlook in Edmonton. Guest: Reid Wilkins. Host of Inside Sports and The Edmonton Oilers hockey broadcasts on 630 CHED. Global News IPSOS poll: Poilievre Top Choice for Best PM in Canada. 68% of Canadians believe Justin Trudeau should step down, including 33% of Liberal voters. Only 25% of Canadians say the Liberals have done a good job.   Bad news continues for Trudeau/Liberals and does this drag down further Jagmeet Singh and NDP?  Trudeau just this week told CBC "Canadians are not in a decision mode right now." Let's find out. Guest: Darrell Bricker. CEO. IPSOS Public Affairs. British Columbia and Alberta are taking steps to either limit or end smartphone use in classrooms beginning in September. B.C. Is leaving the implementation to individual school districts and Alberta appears poised to follow that formula.  In Saskatchewan, the Prairie South School District (Moose Jaw) leaves the policy concerning presence and use of mobile phones in the classroom to individual schools. Ontario has announced all phones must be silent and turned off during the school day for K-6. Grade 7 and up students may use their phones during recess and lunch, but during class periods they must be turned off. Guest: Professor Louis Philippe Beland. Carleton University. Conducted research on the issue and found low-achieving students most benefit from classroom smartphone bans.  --------------------------------------------- Host/Content Producer – Roy Green Technical/Podcast Producer – Tom Craig If you enjoyed the podcast, tell a friend! For more of the Roy Green Show, subscribe to the podcast! https://globalnews.ca/roygreen/ Learn more about your ad choices. Visit megaphone.fm/adchoices

Story 1 - Man pleads guilty to stabbing at UW but not to terror or hate crimes charges. Story 2 - Spike in Canadians fleeing Canada to the United States Story 3 - At the fifth anniversary of the Inquiry into Murdered and Missing Indigenous Women and Girls, Canada has made nearly no progress on the 231 calls to action. Story 4 - Neo-Nazi leader in Greece wil not get an early prison release. Story 5 - Nigeria's unions are on unlimited general strike demanding a hike in the country's minimum wage. Get bonus content on Patreon Hosted on Acast. See acast.com/privacy for more information.

Today's podcast: We speak with two mothers of Jewish children in Ottawa. One mother's 5 year-old child on his school bus heard the words "all Jews raise your hands." Shades of 1933?  Another Jewish child in Ottawa was told to go and kill herself and her mother is terrified when her daughter wears the Star of David in public.   Guests: Anna. Grew up in the Soviet Union and came to Canada because this is a "beautiful and peaceful country." Now her daughter has been told to go and kill herself. And: Dr. Tejaswinhi Srinivas. Psychologist who wrote op ed in the Ottawa Citizen. Dr. Srinivas is Indo-American and not usually thought of as Jewish. What she hears in conversation is chilling. Citizen.https://ottawacitizen.com/opinion/srinivas-antisemitism-is-becoming-normalized-in-canada-we-must-not-allow-this Ontario premier Doug Ford has been attacked for his remarks on Thursday in the presence of Justin Trudeau and Toronto Mayor Olivia Chow when the premier said he's "had it up to here" with attacks on Ontario's Jewish community and urged anyone coming to Ontario to live not do so if they are bringing hatred and vitriol with them. A gratuitous attack on immigrants by Ford, or an elected politician speaking his mind and perhaps echoing what many have been thinking? What do Canadians want from their elected officials? Doug Ford bluntness or statements such as the one made by prime minister Justin Trudeau who following the arson attack on the Shara Tzedeck synagogue in Vancouver offered only "a synagogue was attacked last night in Vancouver in another disgusting act of antisemitism. We cannot let this hate or these acts of violence stand. This is not the Canada we want to be."   What do Canadians want from their politicians as response to Jew-hatred and acts of terrorism such as shooting at Jewish schools and arson at synagogues? Guest: Darrell Bricker. CEO. IPSOS Public Affairs. Following up on the statement by premier Ford. The premier doubled down yesterday on his Thursday statement and we speak with Toronto Sun featured columnist Joe Warmington who has reported extensively on Ford and his Thursday statement. Guest: Joe Warmington.  Public inquiry into foreign election interference. PM Trudeau responds to Commissioner Justice Marie-Josee Hogue's complaint the Liberal government guilty of redacting, as well as refusing to turn over significant numbers of documents to the Inquiry. Guest: Duff Conacher. Co-founder Democracy Watch.   --------------------------------------------- Host/Content Producer – Roy Green Technical/Podcast Producer – Tom Craig If you enjoyed the podcast, tell a friend! For more of the Roy Green Show, subscribe to the podcast! https://globalnews.ca/roygreen/ Learn more about your ad choices. Visit megaphone.fm/adchoices

Today's podcast: Just released Dalhousie Agri-foods laboratory study shows almost 60% of Canadians regularly eat food beyond its 'best before' date, with 23% doing so regularly. Among Millenials 41% believe they have become ill after eating potentially unsafe food products in the past year. And Canada's food sector falling behind that of the U.S. in wholesale and industrial prices. Might Canadian companies pull the plug and exit Canada for the United States?  Guest: Professor Sylvain Charlebois. Director Dalhousie University Agri-Foods laboratory.   Jew-hatred continues to roil across Canada.  Guests: Melissa Lantsman. CPC Deputy leader and Jewish Toronto MP who had a bitter exchange with PM Trudeau during Question Period when Trudeau responded to a challenge by Lantsman by accusing Conservative MPs of "standing with people who wave swastikas."  And:  David Sachs. Jewish Federation of Ottawa. After leaving a Muslim-Jewish interfaith event on parliament hill, Sachs was identified as Jewish by pro-Palestinian demonstrators and was swarmed, requiring a police escort to leave the area. Sachs is engaged in combatting antisemitism by the Jewish Federation of Ottawa.   Global News: "B.C. to ban drug use in all public places in major overhaul of decriminalization." Premier David Eby on Friday made a formal request to Health Canada for changes to its exemption under the Controlled Drugs and Substances Act as the 3 year experiment with decriminalization falters. Guest: Dr. Brian Conway. Medical director and infectious diseases specialist at the Vancouver Infectious Diseaes Centre. East-side of Vancouver.   A report released on Friday by Statscan shows 8.7 million Canadians, or 22.9 per cent of the national population reported some level of food insecurity in 2022. An increase of almost 1.8 million people from the previous year.  Guest: Professor Valerie Tarasuk. Lead investigator of the University of Toronto's household food insecurity research program PROOF. --------------------------------------------- Host/Content Producer – Roy Green Technical/Podcast Producer – Tom Craig If you enjoyed the podcast, tell a friend! For more of the Roy Green Show, subscribe to the podcast! https://globalnews.ca/roygreen/ Learn more about your ad choices. Visit megaphone.fm/adchoices

A report released on Friday by Statscan shows 8.7 million Canadians, or 22.9 per cent of the national population reported some level of food insecurity in 2022. An increase of almost 1.8 million people from the previous year.  Guest: Professor Valerie Tarasuk. Lead investigator of the University of Toronto's household food insecurity research program PROOF. Learn more about your ad choices. Visit megaphone.fm/adchoices

Just released Dalhousie Agri-foods laboratory study shows almost 60% of Canadians regularly eat food beyond its 'best before' date, with 23% doing so regularly. Among Millenials 41% believe they have become ill after eating potentially unsafe food products in the past year. And Canada's food sector falling behind that of the U.S. in wholesale and industrial prices. Might Canadian companies pull the plug and exit Canada for the United States?  Guest: Professor Sylvain Charlebois. Director Dalhousie University Agri-Foods laboratory. Learn more about your ad choices. Visit megaphone.fm/adchoices

National poll: What Canadians want from the federal government in this month's budget. Global News story. Guest: Sean Simpson. Vice president. IPSOS Public Affairs. Conducted poll for Global News Learn more about your ad choices. Visit megaphone.fm/adchoices

Thisis our 14th Kaizen episode! Gerhard put some CDNs to the test, we've taken our next step with Postgres on Neon & Jerod pushed 55 commits (but 0 PRs)!

Thisis our 14th Kaizen episode! Gerhard put some CDNs to the test, we've taken our next step with Postgres on Neon & Jerod pushed 55 commits (but 0 PRs)!

Send us a Text Message.Embark on a journey with me, Benny Kitchell, as we chart the course through the complex waters of system design, zeroing in on the pivotal role of scalability. Imagine the chaos of a concert ticket site crashing just as sales go live; it's a scenario I've lived through, and one that illustrates the high stakes of scaling. Within this episode, we dissect the anatomy of scalability, providing essential insights into how understanding both the product and user behavior is crucial for ensuring a system can handle fluctuating demands. As a veteran of the tech trenches, I share war stories and lessons learned, revealing how misguided scaling can be just as disastrous as stagnation, and how financial implications like ballooning AWS fees can catch you off guard if you're not prepared.Then, we shift gears and plunge into the 'War on Latency', where I illuminate the strategic deployment of caching and CDNs as our primary weapons. Not only do we unravel the technical threads of these systems, but we also tune in to the melodies of Aimless Orbiter, punctuating our discussion with an auditory experience that transcends the typical tech talk. From the intricacies of the CAP theorem to the harmonious balance proposed by its successor, the PACELC theorem, you'll come away from this session armed with the knowledge that's as practical as it is profound. Prepare to be enlightened by the symbiosis of robust system design discourse and the soul-stirring tunes that underscore our technological odyssey.Support the Show.Dedicated to the memory of Crystal Rose.Email me at LearnSystemDesignPod@gmail.comJoin the free Discord Consider supporting us on PatreonSpecial thanks to Aimless Orbiter for the wonderful music.Please consider giving us a rating on ITunes or wherever you listen to new episodes.

Chip Stock Investors Nick and Kasey discuss Cadence Design Systems (CDNS) in today's video, the #2 player in the electronic design automation (EDA) oligopoly behind Synopsys (SNPS) and ahead of Siemens EDA (formerly Mentor Graphics). They talk about Cadence's impressive performance in 2023, which has steadily propelled the “top AI stock” to new heights. Cadence Design Systems has had a successful organic developer of new tech, and its collaborations (such as with Nvidia), and its impact on AI and accelerated computing systems, has put it in position for excellent growth prospects going forward. Its hardware division is also a good indicator of the overall semiconductor market, acting as a proxy for more good times to come. Watch this video to learn more about Cadence Design Systems, and how Chip Stock Investor is handling this investment in their own portfolio. Chapters 00:00 Introduction and Overview of Cadence Design Systems 01:54 Review of Cadence Design Systems' Recent Performance 04:41 Understanding Cadence's Business Model and Growth Strategy 09:00 The Role of AI in Cadence Design Systems' Future 13:45 Analyzing Cadence's Valuation and Future Prospects

Breaking earnings from Cadence Design Systems (CDNS), with a look at the business story behind these earnings. And we hear first hand from Anirudh Devgan, PhD as to why the COVID pandemic recovery is STILL a specter over Cadence results.  https://linktr.ee/drilldownpod The Drill Down Earnings with Futurum Group chief market strategist Cory Johnson offers a quick look at the important takeaways from technology company earnings. More than “beat” or “miss” – it's the business stories behind stocks on the move.  The Drill Down Earnings is a production of Six Five Media and Futurum Group, a leading global technology advisory, media and research firm. Six Five Media's platform spans across multiple OTT and VOD channels that have surpassed 9 million views and over 421 million digital and social media impressions. Learn more about your ad choices. Visit megaphone.fm/adchoices

Cadence Design Systems's Q4 2023 earnings call, unedited

S&P Futures are slightly higher this morning with the S&P's holding above the 5000 level. Markets are relatively quiet this morning with no major news catalyst occurring overnight. Markets are looking ahead to tomorrows CPI report which is expected to display further signs of disinflation. On the earnings front, this afternoon we have earnings results due out from ANET, CDNS, WM, LSCC, CAR & MEDP. In Europe, stocks are slightly higher with positive action in the retail sector. Oil prices are falling this morning down more than 1%.

It's our annual Thanksgiving special! We've got a look back at the year that's been, some things we've gotten right, some things we haven't, some tips for toys this holiday season and some things we're thankful for. (00:21) Bill Mann and Jason Moser discuss: - Why it doesn't feel like the market is up 18% YTD and their slices of humble pie this Thanksgiving. - The reasons they're thankful for Cadence Design Systems, CRISPR, and our podcast listeners around the globe. - The no-go topics at this year's dinner table – crypto and weight-loss drugs. (19:11) James Zahn, Editor in Chief at The Toy Book, shares the toys and brands to watch this holiday season. (32:48) Jason and Bill break down two stocks on their radar: Samsara and Domino's. Catch a picture of the new Domino's delivery oven bike here. Stocks discussed: CDNS, CRSP, IOT, DPZ Host: Dylan Lewis Guests: Bill Mann, Jason Moser, James Zahn, Mr. Gobbler Engineers: Dan Boyd, Rick Engdahl Learn more about your ad choices. Visit megaphone.fm/adchoices

In this episode of the Thoughtful Entrepreneur, your host Josh Elledge speaks to the President of Uniform, Darren Guarnaccia.Darren pointed out that many companies had to adapt quickly to stay connected with their customers in a digital world. However, he also acknowledged that there is still room for improvement. Companies are exploring new technologies and innovations to enhance their digital presence and customer experience.Darren shared how Uniform is revolutionizing how teams collaborate to create compelling digital experiences. Uniform is more than just a platform; it's a tool that allows digital teams to blend content, data, and technology seamlessly. The goal is to overcome common challenges such as inefficient communication, waiting for developers, and general frustration. One of the unique aspects of Uniform is its "composable" nature. Darren likened it to Lego bricks, where users can assemble and reassemble different components to create a customized solution that meets their needs. This modularity allows for flexibility and adaptability, enabling users to easily plug in and remove other elements to test and learn what works best.Key Points from the Episode:Importance of collaboration and building customer experiences onlineImpact of COVID-19 on remote work and digital customer experiencesChallenges faced by teams without a collaborative platform like UniformUniform as a visual workspace for blending content, data, and technologyIntegration with existing tools and benefits for clients in various industriesConcept of "composable" and its application in Uniform's platformMaking the platform easy to use, navigate, and connect data and content sourcesFocus on enhancing collaboration and streamlining processesAbout Darren Guarnaccia:Darren Guarnaccia is the President of Uniform, a pioneering Digital Experience Composition Platform (DXCP) empowering developers and marketers to manage their digital experience stack. With a wealth of experience, he combines top-tier product marketing and management techniques to navigate business hurdles, distinguish products, and catalyze remarkable expansion. In his role, Darren takes charge of crucial aspects, including marketing, product strategy, and enablement at Uniform. His leadership steers the development of innovative solutions, fostering seamless collaboration between technical and creative teams. Under Darren's guidance, Uniform continues to push the boundaries of digital experience management, offering a comprehensive platform that streamlines control over the intricacies of crafting and delivering exceptional digital experiences.About Uniform:Uniform DXCP empowers contemporary enterprises to construct swift and adaptable digital experience platforms. By establishing a uniform visual layer for content coordination across all channels, Uniform empowers business users, including marketing and e-commerce teams, to swiftly construct and experiment with ideas sans developer assistance. This proficiency is facilitated by pre-built integrations that eliminate the necessity for custom code when connecting content sources like legacy DXPs, customer data platforms, and headless services. Consequently, projects are expedited with reduced costs, all while preserving long-term adaptability for innovation. Uniform further enhances high-performance digital experiences by directly dispatching content to the forefront of modern CDNs, even accommodating personalized content delivery. Through these capabilities, Uniform DXCP stands as a catalyst for streamlined, cost-effective, and agile digital

Matthew Prince, Co-founder & CEO at Cloudflare, joins Corey on Screaming in the Cloud to discuss how and why Cloudflare is working to solve some of the Internet's biggest problems. Matthew reveals some of his biggest issues with cloud providers, including the tendency to charge more for egress than ingress and the fact that the various clouds don't compete on a feature vs. feature basis. Corey and Matthew also discuss how Cloudflare is working to change those issues so the Internet is a better and more secure place. Matthew also discusses how transparency has been key to winning trust in the community and among Cloudflare's customers, and how he hopes the Internet and cloud providers will evolve over time.About MatthewMatthew Prince is co-founder and CEO of Cloudflare. Cloudflare's mission is to help build a better Internet. Today the company runs one of the world's largest networks, which spans more than 200 cities in over 100 countries. Matthew is a World Economic Forum Technology Pioneer, a member of the Council on Foreign Relations, winner of the 2011 Tech Fellow Award, and serves on the Board of Advisors for the Center for Information Technology and Privacy Law. Matthew holds an MBA from Harvard Business School where he was a George F. Baker Scholar and awarded the Dubilier Prize for Entrepreneurship. He is a member of the Illinois Bar, and earned his J.D. from the University of Chicago and B.A. in English Literature and Computer Science from Trinity College. He's also the co-creator of Project Honey Pot, the largest community of webmasters tracking online fraud and abuse.Links Referenced: Cloudflare: https://www.cloudflare.com/ Twitter: https://twitter.com/eastdakota TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. One of the things we talk about here, an awful lot is cloud providers. There sure are a lot of them, and there's the usual suspects that you would tend to expect with to come up, and there are companies that work within their ecosystem. And then there are the enigmas.Today, I'm talking to returning guest Matthew Prince, Cloudflare CEO and co-founder, who… well first, welcome back, Matthew. I appreciate your taking the time to come and suffer the slings and arrows a second time.Matthew: Corey, thanks for having me.Corey: What I'm trying to do at the moment is figure out where Cloudflare lives in the context of the broad ecosystem because you folks have released an awful lot. You had this vaporware-style announcement of R2, which was an S3 competitor, that then turned out to be real. And oh, it's always interesting, when vapor congeals into something that actually exists. Cloudflare Workers have been around for a while and I find that they become more capable every time I turn around. You have Cloudflare Tunnel which, to my understanding, is effectively a VPN without the VPN overhead. And it feels that you are coming at building a cloud provider almost from the other side than the traditional cloud provider path. Is it accurate? Am I missing something obvious? How do you see yourselves?Matthew: Hey, you know, I think that, you know, you can often tell a lot about a company by what they measure and what they measure themselves by. And so, if you're at a traditional, you know, hyperscale public cloud, an AWS or a Microsoft Azure or a Google Cloud, the key KPI that they focus on is how much of a customer's data are they hoarding, effectively? They're all hoarding clouds, fundamentally. Whereas at Cloudflare, we focus on something of it's very different, which is, how effectively are we moving a customer's data from one place to another? And so, while the traditional hyperscale public clouds are all focused on keeping your data and making sure that they have as much of it, what we're really focused on is how do we make sure your data is wherever you need it to be and how do we connect all of the various things together?So, I think it's exactly right, where we start with a network and are kind of building more functions on top of that network, whereas other companies start really with a database—the traditional hyperscale public clouds—and the network is sort of an afterthought on top of it, just you know, a cost center on what they're delivering. And I think that describes a lot of the difference between us and everyone else. And so oftentimes, we work very much in conjunction with. A lot of our customers use hyperscale public clouds and Cloudflare, but increasingly, there are certain applications, there's certain data that just makes sense to live inside the network itself, and in those cases, customers are using things like R2, they're using our Workers platform in order to be able to build applications that will be available everywhere around the world and incredibly performant. And I think that is fundamentally the difference. We're all about moving data between places, making sure it's available everywhere, whereas the traditional hyperscale public clouds are all about hoarding that data in one place.Corey: I want to clarify that when you say hoard, I think of this, from my position as a cloud economist, as effectively in an economic story where hoarding the data, they get to charge you for hosting it, they get to charge you serious prices for egress. I've had people mishear that before in a variety of ways, usually distilled down to, “Oh, and their data mining all of their customers' data.” And I want to make sure that that's not the direction that you intend the term to be used. If it is, then great, we can talk about that, too. I just want to make sure that I don't get letters because God forbid we get letters for things that we say in the public.Matthew: No, I mean, I had an aunt who was a hoarder and she collected every piece of everything and stored it somewhere in her tiny little apartment in the panhandle of Florida. I don't think she looked at any of it and for the most part, I don't think that AWS or Google or Microsoft are really using your data in any way that's nefarious, but they're definitely not going to make it easy for you to get it out of those places; they're going to make it very, very expensive. And again, what they're measuring is how much of a customer's data are they holding onto whereas at Cloudflare we're measuring how much can we enable you to move your data around and connected wherever you need it. And again, I think that that kind of gets to the fundamental difference between how we think of the world and how I think the hyperscale public clouds thing of the world. And it also gets to where are the places where it makes sense to use Cloudflare, and where are the places that it makes sense to use an AWS or Google Cloud or Microsoft Azure.Corey: So, I have to ask, and this gets into the origin story trope a bit, but what radicalized you? For me, it was the realization one day that I could download two terabytes of data from S3 once, and it would cost significantly more than having Amazon.com ship me a two-terabyte hard drive from their store.Matthew: I think that—so Cloudflare started with the basic idea that the internet's not as good as it should be. If we all knew what the internet was going to be used for and what we're all going to depend on it for, we would have made very different decisions in how it was designed. And we would have made sure that security was built in from day one, we would have—you know, the internet is very reliable and available, but there are now airplanes that can't land if the internet goes offline, they are shopping transactions shut down if the internet goes offline. And so, I don't think we understood—we made it available to some extent, but not nearly to the level that we all now depend on it. And it wasn't as fast or as efficient as it possibly could be. It's still very dependent on the geography of where data is located.And so, Cloudflare started out by saying, “Can we fix that? Can we go back and effectively patch the internet and make it what it should have been when we set down the original protocols in the '60s, '70s, and '80s?” But can we go back and say, can we build a new, sort of, overlay on the internet that solves those problems: make it more secure, make it more reliable, make it faster and more efficient? And so, I think that that's where we started, and as a result of, again, starting from that place, it just made fundamental sense that our job was, how do you move data from one place to another and do it in all of those ways? And so, where I think that, again, the hyperscale public clouds measure themselves by how much of a customer's data are they hoarding; we measure ourselves by how easy are we making it to securely, reliably, and efficiently move any piece of data from one place to another.And so, I guess, that is radical compared to some of the business models of the traditional cloud providers, but it just seems like what the internet should be. And that's our North Star and that's what just continues to drive us and I think is a big reason why more and more customers continue to rely on Cloudflare.Corey: The thing that irks me potentially the most in the entire broad strokes of cloud is how the actions of the existing hyperscalers have reflected mostly what's going on in the larger world. Moore's law has been going on for something like 100 years now. And compute continues to get faster all the time. Storage continues to cost less year over year in a variety of ways. But they have, on some level, tricked an entire generation of businesses into believing that network bandwidth is this precious, very finite thing, and of course, it's going to be ridiculously expensive. You know, unless you're taking it inbound, in which case, oh, by all means back the truck around. It'll be great.So, I've talked to founders—or prospective founders—who had ideas but were firmly convinced that there was no economical way to build it. Because oh, if I were to start doing real-time video stuff, well, great, let's do the numbers on this. And hey, that'll be $50,000 a minute, if I read the pricing page correctly, it's like, well, you could get some discounts if you ask nicely, but it doesn't occur to them that they could wind up asking for a 98% discount on these things. Everything is measured in a per gigabyte dimension and that just becomes one of those things where people are starting to think about and meter something that—from my days in data centers where you care about the size of the pipe and not what's passing through it—to be the wrong way of thinking about things.Matthew: A little of this is that everybody is colored by their experience of dealing with their ISP at home. And in the United States, in a lot of the world, ISPs are built on the old cable infrastructure. And if you think about the cable infrastructure, when it was originally laid down, it was all one-directional. So, you know, if you were turning on cable in your house in a pre-internet world, data fl—Corey: Oh, you'd watch a show and your feedback was yelling at the TV, and that's okay. They would drop those packets.Matthew: And there was a tiny, tiny, tiny bit of data that would go back the other direction, but cable was one-directional. And so, it actually took an enormous amount of engineering to make cable bi-directional. And that's the reason why if you're using a traditional cable company as your ISP, typically you will have a large amount of download capacity, you'll have, you know, a 100 megabits of down capacity, but you might only have a 10th of that—so maybe ten megabits—of upload capacity. That is an artifact of the cable system. That is not just the natural way that the internet works.And the way that it is different, that wholesale bandwidth works, is that when you sign up for wholesale bandwidth—again, as you phrase it, you're not buying this many bytes that flows over the line; you're buying, effectively, a pipe. You know, the late Senator Ted Stevens said that the internet is just a series of tubes and got mocked mercilessly, but the internet is just a series of tubes. And when Cloudflare or AWS or Google or Microsoft buys one of those tubes, what they pay for is the diameter of the tube, the amount that can fit through it. And the nature of this is you don't just get one tube, you get two. One that is down and one that is up. And they're the same size.And so, if you've got a terabit of traffic coming down and zero going up, that costs exactly the same as a terabit going up and zero going down, which costs exactly the same as a terabit going down and a terabit going up. It is different than your home, you know, cable internet connection. And that's the thing that I think a lot of people don't understand. And so, as you pointed out, but the great tragedy of the cloud is that for nothing other than business reasons, these hyperscale public cloud companies don't charge you anything to accept data—even though that is actually the more expensive of the two operations for that because writes are more expensive than reads—but the inherent fact that they were able to suck the data in means that they have the capacity, at no additional cost, to be able to send that data back out. And so, I think that, you know, the good news is that you're starting to see some providers—so Cloudflare, we've never charged for egress because, again, we think that over time, bandwidth prices go to zero because it just makes sense; it makes sense for ISPs, it makes sense for connectiv—to be connected to us.And that's something that we can do, but even in the cases of the cloud providers where maybe they're all in one place and somebody has to pay to backhaul the traffic around the world, maybe there's some cost, but you're starting to see some pressure from some of the more forward-leaning providers. So Oracle, I think has done a good job of leaning in and showing how egress fees are just out of control. But it's crazy that in some cases, you have a 4,000x markup on AWS bandwidth fees. And that's assuming that they're paying the same rates as what we would get at Cloudflare, you know, even though we are a much smaller company than they are, and they should be able to get even better prices.Corey: Yes, if there's one thing Amazon is known for, it as being bad at negotiating. Yeah, sure it is. I'm sure that they're just a terrific joy to be a vendor to.Matthew: Yeah, and I think that fundamentally what the price of bandwidth is, is tied very closely to what the cost of a port on a router costs. And what we've seen over the course of the last ten years is that cost has just gone enormously down where the capacity of that port has gone way up and the just physical cost, the depreciated cost that port has gone down. And yet, when you look at Amazon, you just haven't seen a decrease in the cost of bandwidth that they're passing on to customers. And so, again, I think that this is one of the places where you're starting to see regulators pay attention, we've seen efforts in the EU to say whatever you charge to take data out is the same as what you should charge it to put data in. We're seeing the FTC start to look at this, and we're seeing customers that are saying that this is a purely anti-competitive action.And, you know, I think what would be the best and healthiest thing for the cloud by far is if we made it easy to move between various cloud providers. Because right now the choice is, do I use AWS or Google or Microsoft, whereas what I think any company out there really wants to be able to do is they want to be able to say, “I want to use this feature at AWS because they're really good at that and I want to use this other feature at Google because they're really good at that, and I want to us this other feature at Microsoft, and I want to mix and match between those various things.” And I think that if you actually got cloud providers to start competing on features as opposed to competing on their overall platform, we'd actually have a much richer and more robust cloud environment, where you'd see a significantly improved amount of what's going on, as opposed to what we have now, which is AWS being mediocre at everything.Corey: I think that there's also a story where for me, the egress is annoying, but so is the cross-region and so is the cross-AZ, which in many cases costs exactly the same. And that frustrates me from the perspective of, yes, if you have two data centers ten miles apart, there is some startup costs to you in running fiber between them, however you want to wind up with that working, but it's a sunk cost. But at the end of that, though, when you wind up continuing to charge on a per gigabyte basis to customers on that, you're making them decide on a very explicit trade-off of, do I care more about cost or do I care more about reliability? And it's always going to be an investment decision between those two things, but when you make the reasonable approach of well, okay, an availability zone rarely goes down, and then it does, you get castigated by everyone for, “Oh it even says in their best practice documents to go ahead and build it this way.” It's funny how a lot of the best practice documents wind up suggesting things that accrue primarily to a cloud provider's benefit. But that's the way of the world I suppose.I just know, there's a lot of customer frustration on it and in my client environments, it doesn't seem to be very acute until we tear apart a bill and look at where they're spending money, and on what, at which point, the dawning realization, you can watch it happen, where they suddenly realize exactly where their money is going—because it's relatively impenetrable without that—and then they get angry. And I feel like if people don't know what they're being charged for, on some level, you've messed up.Matthew: Yeah. So, there's cost to running a network, but there's no reason other than limiting competition why you would charge more to take data out than you would put data in. And that's a puzzle. The cross-region thing, you know, I think where we're seeing a lot of that is actually oftentimes, when you've got new technologies that come out and they need to take advantage of some scarce resource. And so, AI—and all the AI companies are a classic example of this—right now, if you're trying to build a model, an AI model, you are hunting the world for available GPUs at a reasonable price because there's an enormous scarcity of them.And so, you need to move from AWS East to AWS West, to AWS, you know, Singapore, to AWS in Luxembourg and bounce around to find wherever there's GPU availability. And then that is crossed against the fact that these training datasets are huge. You know, I mean, they're just massive, massive, massive amounts of data. And so, what that is doing is you're having these AI companies that are really seeing this get hit in the face, where they literally can't get the capacity they need because of the fact that whatever cloud provider in whatever region they've selected to store their data isn't able to have that capacity. And so, they're getting hit not only by sort of a double whammy of, “I need to move my data to wherever there's capacity. And if I don't do that, then I have to pay some premium, an ever-escalating price for the underlying GPUs.” And God forbid, you have to move from AWS to Google to chase that.And so, we're seeing a lot of companies that are saying, “This doesn't make any sense. We have this enormous training set. If we just put it with Cloudflare, this is data that makes sense to live in the network, fundamentally.” And not everything does. Like, we're not the right place to store your long-term transaction logs that you're only going to look at if you get sued. There are much better places, much more effective places do it.But in those cases where you've got to read data frequently, you've got to read it from different places around the world, and you will need to decrease what those costs of each one of those reads are, what we're seeing is just an enormous amount of demand for that. And I think these AI startups are really just a very clear example of what company after company after company needs, and why R2 has had—which is our zero egress cost S3 competitor—why that is just seeing such explosive growth from a broad set of customers.Corey: Because I enjoy pushing the bounds of how ridiculous I can be on the internet, I wound up grabbing a copy of the model, the Llama 2 model that Meta just released earlier this week as we're recording this. And it was great. It took a little while to download here. I have gigabit internet, so okay, it took some time. But then I wound up with something like 330 gigs of models. Great, awesome.Except for the fact that I do the math on that and just for me as one person to download that, had they been paying the listed price on the AWS website, they would have spent a bit over $30, just for me as one random user to download the model, once. If you can express that into the idea of this is a model that is absolutely perfect for whatever use case, but we want to have it run with some great GPUs available at another cloud provider. Let's move the model over there, ignoring the data it's operating on as well, it becomes completely untenable. It really strikes me as an anti-competitiveness issue.Matthew: Yeah. I think that's it. That's right. And that's just the model. To build that model, you would have literally millions of times more data that was feeding it. And so, the training sets for that model would be many, many, many, many, many, many orders of magnitude larger in terms of what's there. And so, I think the AI space is really illustrating where you have this scarce resource that you need to chase around the world, you have these enormous datasets, it's illustrating how these egress fees are actually holding back the ability for innovation to happen.And again, they are absolutely—there is no valid reason why you would charge more for egress than you do for ingress other than limiting competition. And I think the good news, again, is that's something that's gotten regulators' attention, that's something that's gotten customers' attention, and over time, I think we all benefit. And I think actually, AWS and Google and Microsoft actually become better if we start to have more competition on a feature-by-feature basis as opposed to on an overall platform. The choice shouldn't be, “I use AWS.” And any big company, like, nobody is all-in only on one cloud provider. Everyone is multi-cloud, whether they want to be or not because people end up buying another company or some skunkworks team goes off and uses some other function.So, you are across multiple different clouds, whether you want to be or not. But the ideal, and when I talk to customers, they want is, they want to say, “Well, you know that stuff that they're doing over at Microsoft with AI, that sounds really interesting. I want to use that, but I really like the maturity and robustness of some of the EC2 API, so I want to use that at AWS. And Google is still, you know, the best in the world at doing search and indexing and everything, so I want to use that as well, in order to build my application.” And the applications of the future will inherently stitch together different features from different cloud providers, different startups.And at Cloudflare, what we see is our, sort of, purpose for being is how do we make that stitching as easy as possible, as cost-effective as possible, and make it just make sense so that you have one consistent security layer? And again, we're not about hording the data; we're about connecting all of those things together. And again, you know, from the last time we talked to now, I'm actually much more optimistic that you're going to see, kind of, this revolution where egress prices go down, you get competition on feature-by-features, and that's just going to make every cloud provider better over the long-term.Corey: This episode is sponsored in part by Panoptica.  Panoptica simplifies container deployment, monitoring, and security, protecting the entire application stack from build to runtime. Scalable across clusters and multi-cloud environments, Panoptica secures containers, serverless APIs, and Kubernetes with a unified view, reducing operational complexity and promoting collaboration by integrating with commonly used developer, SRE, and SecOps tools. Panoptica ensures compliance with regulatory mandates and CIS benchmarks for best practice conformity. Privacy teams can monitor API traffic and identify sensitive data, while identifying open-source components vulnerable to attacks that require patching. Proactively addressing security issues with Panoptica allows businesses to focus on mitigating critical risks and protecting their interests. Learn more about Panoptica today at panoptica.app.Corey: I don't know that I would trust you folks to the long-term storage of critical data or the store of record on that. You don't have the track record on that as a company the way that you do for being the network interchange that makes everything just work together. There are areas where I'm thrilled to explore and see how it works, but it takes time, at least from the sensible infrastructure perspective of trusting people with track records on these things. And you clearly have the network track record on these things to make this stick. It almost—it seems unfair to you folks, but I view you as Cloudflare is a CDN, that also dabbles in a few other things here in there, though, increasingly, it seems it's CDN and security company are becoming synonymous.Matthew: It's interesting. I remember—and this really is going back to the origin story, but when we were starting Cloudflare, you know, what we saw was that, you know, we watched as software—starting with companies like Salesforce—transition from something that you bought in the box to something that you bought as a service [into 00:23:25] the cloud. We watched as, sort of, storage and compute transition from something that you bought from Dell or HP to something that you rented as a service. And so the fundamental problem that Cloudflare started out with was if the software and the storage and compute are going to move, inherently the security and the networking is going to move as well because it has to be as a service as well, there's no way you can buy a you know, Cisco firewall and stick it in front of your cloud service. You have to be in the cloud as well.So, we actually started very much as a security company. And the objection that everybody had to us as we would sort of go out and describe what we were planning on doing was, “You know, that sounds great, but you're going to slow everything down.” And so, we became just obsessed with latency. And Michelle, my co-founder, and I were business students and we had an advisor, a guy named Tom [Eisenmann 00:24:26] in business school. And I remember going in and that was his objection as well and so we did all this work to figure it out.And obviously, you know, I'd say computer science, and anytime that you have a problem around latency or speed caching is an obvious part of the solution to that. And so, we went in and we said, “Here's how we're going to do it: [unintelligible 00:24:47] all this protocol optimization stuff, and here's how we're going to distribute it around the world and get close to where users are. And we're going to use caching in the places where we can do caching.” And Tom said, “Oh, you're building a CDN.” And I remember looking at him and then I'm looking at Michelle. And Michelle is Canadian, and so I was like, “I don't know that I'm building a Canadian, but I guess. I don't know.”And then, you know, we walked out in the hall and Michelle looked at me and she's like, “We have to go figure out what the CDN thing is.” And we had no idea what a CDN was. And even when we learned about it, we were like, that business doesn't make any sense. Like because again, the CDNs were the first ones to really charge for bandwidth. And so today, we have effectively built, you know, a giant CDN and are the fastest in the world and do all those things.But we've always given it away basically for free because fundamentally, what we're trying to do is all that other stuff. And so, we actually started with security. Security is—you know, my—I've been working in security now for over 25 years and that's where my background comes from, and if you go back and look at what the original plan was, it was how do we provide that security as a service? And yeah, you need to have caching because caching makes sense. What I think is the difference is that in order to do that, in order to be able to build that, we had to build a set of developer tools for our own team to allow them to build things as quickly as possible.And, you know, if you look at Cloudflare, I think one of the things we're known for is just the rapid, rapid, rapid pace of innovation. And so, over time, customers would ask us, “How do you innovate so fast? How do you build things fast?” And part of the answer to that, there are lots of ways that we've been able to do that, but part of the answer to that is we built a developer platform for our own team, which was just incredibly flexible, allowed you to scale to almost any level, took care of a lot of that traditional SRE functions just behind the scenes without you having to think about it, and it allowed our team to be really fast. And our customers are like, “Wow, I want that too.”And so, customer after customer after customer after customer was asking and saying, you know, “We have those same problems. You know, if we're a big e-commerce player, we need to be able to build something that can scale up incredibly quickly, and we don't have to think about spinning up VMs or containers or whatever, we don't have to think about that. You know, our customers are around the world. We don't want to have to pick a region for where we're going to deploy code.” And so, where we built Cloudflare Workers for ourself first, customers really pushed us to make it available to them as well.And that's the way that almost any good developer platform starts out. That's how AWS started. That's how, you know, the Microsoft developer platform, and so the Apple developer platform, the Salesforce developer platform, they all start out as internal tools, and then someone says, “Can you expose this to us as well?” And that's where, you know, I think that we have built this. And again, it's very opinionated, it is right for certain applications, it's never going to be the right place to run SAP HANA, but the company that builds the tool [crosstalk 00:27:58]—Corey: I'm not convinced there is a right place to run SAP HANA, but that's probably unfair of me.Matthew: Yeah, but there is a startup out there, I guarantee you, that's building whatever the replacement for SAP HANA is. And I think it's a better than even bet that Cloudflare Workers is part of their stack because it solves a lot of those fundamental challenges. And that's been great because it is now allowing customer after customer after customer, big and large startups and multinationals, to do things that you just can't do with traditional legacy hyperscale public cloud. And so, I think we're sort of the next generation of building that. And again, I don't think we set out to build a developer platform for third parties, but we needed to build it for ourselves and that's how we built such an effective tool that now so many companies are relying on.Corey: As a Cloudflare customer myself, I think that one of the things that makes you folks standalone—it's why I included security as well as CDN is one of the things I trust you folks with—has been—Matthew: I still think CDN is Canadian. You will never see us use that term. It's like, Gartner was like, “You have to submit something for the CDN-like ser—” and we ended up, like, being absolute top-right in it. But it's a space that is inherently going to zero because again, if bandwidth is free, I'm not sure what—this is what the internet—how the internet should work. So yeah, anyway.Corey: I agree wholeheartedly. But what I've always enjoyed, and this is probably going to make me sound meaner than I intend it to, it has been your outages. Because when computers inherently at some point break, which is what they do, you personally and you as a company have both taken a tone that I don't want to say gleeful, but it's sort of the next closest thing to it regarding the postmortem that winds up getting published, the explanation of what caused it, the transparency is unheard of at companies that are your scale, where usually they want to talk about these things as little as possible. Whereas you've turned these into things that are educational to those of us who don't have the same scale to worry about but can take things from that are helpful. And that transparency just counts for so much when we're talking about things as critical as security.Matthew: I would definitely not describe it as gleeful. It is incredibly painful. And we, you know, we know we let customers down anytime we have an issue. But we tend not to make the same mistake twice. And the only way that we really can reliably do that is by being just as transparent as possible about exactly what happened.And we hope that others can learn from the mistakes that we made. And so, we own the mistakes we made and we talk about them and we're transparent, both internally but also externally when there's a problem. And it's really amazing to just see how much, you know, we've improved over time. So, it's actually interesting that, you know, if you look across—and we measure, we test and measure all the big hyperscale public clouds, what their availability and reliability is and measure ourselves against it, and across the board, second half of 2021 and into the first half of 2022 was the worst for every cloud provider in terms of reliability. And the question is why?And the answer is, Covid. I mean, the answer to most things over the last three years is in one way, directly or indirectly, Covid. But what happened over that period of time was that in April of 2020, internet traffic and traffic to our service and everyone who's like us doubled over the course of a two-week period. And there are not many utilities that you can imagine that if their usage doubles, that you wouldn't have a problem. Imagine the sewer system all of a sudden has twice as much sewage, or the electrical grid as twice as much demand, or the freeways have twice as many cars. Like, things break down.And especially the European internet came incredibly close to just completely failing at that time. And we all saw where our bottlenecks were. And what's interesting is actually the availability wasn't so bad in 2020 because people were—they understood the absolute critical importance that while we're in the middle of a pandemic, we had to make sure the internet worked. And so, we—there were a lot of sleepless nights, there's a—and not just at with us, but with every provider that's out there. We were all doing Herculean tasks in order to make sure that things came online.By the time we got to the sort of the second half of 2021, what everybody did, Cloudflare included, was we looked at it, and we said, “Okay, here were where the bottlenecks were. Here were the problems. What can we do to rearchitect our systems to do that?” And one of the things that we saw was that we effectively treated large data centers as one big block, and if you had certain pieces of equipment that failed in a way, that you would take that entire data center down and then that could have cascading effects across traffic as it shifted around across our network. And so, we did the work to say, “Let's take that one big data center and divide it effectively into multiple independent units, where you make sure that they're all on different power suppliers, you make sure they're all in different [crosstalk 00:32:52]”—Corey: [crosstalk 00:32:51] harder than it sounds. When you have redundant things, very often, the thing that takes you down the most is the heartbeat that determines whether something next to it is up or not. It gets a false reading and suddenly, they're basically trying to clobber each other to death. So, this is a lot harder than it sounds like.Matthew: Yeah, and it was—but what's interesting is, like, we took it all that into account, but the act of fixing things, you break things. And that was not just true at Cloudflare. If you look across Google and Microsoft and Amazon, everybody, their worst availability was second half of 2021 or into 2022. But it both internally and externally, we talked about the mistakes we made, we talked about the challenges we had, we talked about—and today, we're significantly more resilient and more reliable because of that. And so, transparency is built into Cloudflare from the beginning.The earliest story of this, I remember, there was a 15-year-old kid living in Long Beach, California who bought my social security number off of a Russian website that had hacked a bank that I'd once used to get a mortgage. He then use that to redirect my cell phone voicemail to a voicemail box he controlled. He then used that to get into my personal email. He then used that to find a zero-day vulnerability in Google's corporate email where he could privilege-escalate from my personal email into Google's corporate email, which is the provider that we use for our email service. And then he used that as an administrator on our email at the time—this is back in the early days of Cloudflare—to get into another administration account that he then used to redirect one of Cloud Source customers to a website that he controlled.And thankfully, it wasn't, you know, the FBI or the Central Bank of Brazil, which were all Cloudflare customers. Instead, it was 4chan because he was a 15-year-old hacker kid. And we fix it pretty quickly and nobody knew who Cloudflare was at the time. And so potential—Corey: The potential damage that could have been caused at that point with that level of access to things, like, that is such a ridiculous way to use it.Matthew: And—yeah [laugh]—my temptation—because it was embarrassing. He took a bunch of stuff from my personal email and he put it up on a website, which just to add insult to injury, was actually using Cloudflare as well. And I wanted to sweep it under the rug. And our team was like, “That's not the right thing to do. We're fundamentally a security company and we need to talk about when we make mistakes on security.” And so, we wrote a huge postmortem on, “Here's all the stupid things that we did that caused this hack to happen.” And by the way, it wasn't just us. It was AT&T, it was Google. I mean, there are a lot of people that ended up being involved.Corey: It builds trust with that stuff. It's painful in the short term, but I believe with the benefit of hindsight, it was clearly the right call.Matthew: And it was—and I remember, you know, pushing ‘publish' on the blog post and thinking, “This is going to be the end of the company.” And quite the opposite happened, which was all of a sudden, we saw just an incredible amount of people who signed up the next day saying, “If you're going to be that transparent about something that was incredibly embarrassing when you didn't have to be, then that's the sort of thing that actually makes me trust that you're going to be transparent the future.” And I think learning that lesson early on, has been just an incredibly valuable lesson for us and made us the company that we are today.Corey: A question that I have for you about the idea of there being no reason to charge in one direction but not the other. There's something that I'm not sure that I understand on this. If I run a website, to use your numbers of a terabit out—because it's a web server—and effectively nothing in—because it's a webserver; other than the request, nothing really is going to come in—that ingress bandwidth becomes effectively unused and also free. So, if I have another use case where I'm paying for it anyway, if I'm primarily caring about an outward direction, sure, you can send things in for free. Now, there's a lot of nuance that goes into that. But I'm curious as to what the—is their fundamental misunderstanding in that analysis of the bandwidth market?Matthew: No. And I think that's exactly, exactly right. And it's actually interesting. At Cloudflare, our infrastructure team—which is the one that manages our connections to the outside world, manages the hardware we have—meets on a quarterly basis with our product team. It's called the Hot and Cold Meeting.And what they do is they go over our infrastructure, and they say, “Okay, where are we hot? Where do we have not enough capacity?” If you think of any given server, an easy way to think of a server is that it has, sort of, four resources that are available to it. This is, kind of, vast simplification, but one is the connectivity to the outside world, both transit in and out. The second is the—Corey: Otherwise it's just a complicated space heater.Matthew: Yeah [laugh]. The other is the CPU. The other is the longer-term storage. We use only SSDs, but sort of, you know, hard drives or SSD storage. And then the fourth is the short-term storage, or RAM that's in that server.And so, at any given moment, there are going to be places where we are running hot, where we have a sort of capacity level that we're targeting and we're over that capacity level, but we're also going to be running cold in some of those areas. And so, the infrastructure team and the product team get together and the product team has requests on, you know, “Here's some more places we would be great to have more infrastructure.” And we're really good at deploying that when we need to, but the infrastructure team then also says, “Here are the places where we're cold, where we have excess capacity.” And that turns into products at Cloudflare. So, for instance, you know, the reason that we got into the zero-trust space was very much because we had all this excess capacity.We have 100 times the capacity of something like Zscaler across our network, and we can add that—that is primar—where most of our older products are all about outward traffic, the zero-trust products are all about inward traffic. And the reason that we can do everything that Zscaler does, but for, you know, a much, much, much more affordable prices, we going to basically just layer that on the network that already exists. The reason we don't charge for the bandwidth behind DDoS attacks is DDoS attacks are always about inbound traffic and we have just a ton of excess capacity around that inbound traffic. And so, that unused capacity is a resource that we can then turn into products, and very much that conversation between our product team and our infrastructure team drives how we think about building new products. And we're always trying to say how can we get as much utilization out of every single piece of equipment that we run everywhere in the world.The way we build our network, we don't have custom machines or different networks for every products. We build all of our machines—they come in generations. So, we're on, I think, generation 14 of servers where we spec a server and it has, again, a certain amount of each of those four [bits 00:39:22] of capacity. But we can then deploy that server all around the world, and we're buying many, many, many of them at any given time so we can get the best cost on that. But our product team is very much in constant communication with our infrastructure team and saying, “What more can we do with the capacity that we have?” And then we pass that on to our customers by adding additional features that work across our network and then doing it in a way that's incredibly cost-effective.Corey: I really want to thank you for taking the time to, basically once again, suffer slings and arrows about networking, security, cloud, economics, and so much more. If people want to learn more, where's the best place for them to find you?Matthew: You know, used to be an easy question to answer because it was just, you know, go on Twitter and find me but now we have all these new mediums. So, I'm @eastdakota on Twitter. I'm eastdakota.com on Bluesky. I'm @real_eastdakota on Threads. And so, you know, one way or another, if you search for eastdakota, you'll come across me somewhere out there in the ether.Corey: And we will, of course, put links to that in the show notes. Thank you so much for your time. I appreciate it.Matthew: It's great to talk to you, Corey.Corey: Matthew Prince, CEO and co-founder of Cloudflare. I'm Cloud Economist Corey Quinn and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice along with an angry, insulting comment that I will of course not charge you inbound data rates on.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.

Watch on YouTube About the show Sponsored by us! Support our work through: Our courses at Talk Python Training Test & Code Podcast Patreon Supporters Connect with the hosts Michael: @mkennedy@fosstodon.org Brian: @brianokken@fosstodon.org Show: @pythonbytes@fosstodon.org Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Tuesdays at 11am PT. Older video versions available there too. Main topic: AMA questions from the audience. Use the transcript search to find timestamps if you want to locate a particular one. Extras Michael: Deputy CPython Developer in Residence position accepting applications. My Make Your Python Web App Fly Around the World with CDNs talk at PWC 2023 is online. “Joke”: Ode to Python recommended by FelixTheCat

Immersive technology is more than goggles. Jason Moser and Matt Frankel discuss:  - Apple's bet on spatial computing - A major interface problem for headset adoption - Meta's VR subscription service - Less obvious companies that could benefit from a boom in immersive tech Companies discussed: AAPL, META, GOOG, GOOGL, MSFT, ATVI, CDNS, AMT, AXON Host: Jason Moser Guest: Matt Frankel Producer: Ricky Mulvey Engineer: Rick Engdahl

If you clean out your closet once in a while, consider doing the same with your investment portfolio. (0:21) Ron Gross and Jason Moser discuss: - Stocks investors should consider trimming like hedges - 2 stocks to throw out altogether - Stocks that spark joy (a la Marie Kondo) - Investments poised for a comeback - Why Visa, Mastercard, and Berkshire-Hathaway are good stocks for a rainy day - Actual cleaning tips! (19:11) Motley Fool senior analyst Bill Mann talks with Howard Marks, co-founder of Oaktree Capital Management, about China's effect on inflation in the U.S. and the winners and losers in a world of higher interest rates. To get your copy of our free report "Top Stocks For Rising Interest Rates" just go to fool.com/interest. Stocks discussed: FIVE, DG, DLTR, OLLI, ZG, UA, COST, CDNS, XBI, PYPL, SQ, BRK, V, MA Host: Chris Hill Guests: Jason Moser, Ron Gross, Bill Mann, Howard Marks Producer: Ricky Mulvey Engineer: Dan Boyd