Podcasts about pub sub

Guy Royse, dev advocate at Redis, discusses going beyond the cache with Redis and Node.js. He explores its capabilities as a memory-first database, session management, and even fun use cases like the Bigfoot Tracker API. He also shares insights on Redis OM for object mapping and its future in the JavaScript ecosystem. Links http://guyroyse.com http://github.com/guyroyse https://www.twitch.tv/guyroyse https://www.youtube.com/channel/UCNt5SDc6LosO41E77jr59cQ https://x.com/guyroyse https://www.linkedin.com/in/groyse https://2024.connect.tech/session/693665 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: Guy Royse.

As beloved as the chicken tenders Pub Sub is, I want you to take a chance and order something else instead. While trying to decide what to get while I was standing in line a few weeks ago, I saw a sign that seduced my taste buds. I don’t know if it’s been around a while and I just never noticed it or if it is truly a “limited time only” offering as the sign said. But I was starving and a Boars Head French Onion London Broil sub sounded like a worthy challenger to dethrone the famous Publix chicken tenders sub.

Configuration changes played an outsized role 2024 outages. Tune in to hear more about this and other outage trends—and learn how ITOps teams should plan accordingly in the year ahead.We'll also share insights from recent incidents at OpenAI and Google Cloud's Pub/Sub, and dive deeper into a degradation incident that Netflix experienced at the end of 2024.Read on to learn more, or use the chapters below to jump to the sections that most interest you.CHAPTERS00:00 Intro00:58 Cloud Service Provider (CSP) Outages Continue To Rise 01:52 Accidental Misconfigurations Trending for Clouds and Apps07:10 OpenAI Outage09:55 Google Cloud's Pub/Sub Disruption14:47 Lessons From a Netflix Incident18:57 Recent Outage Trends: By the Numbers21:01 Get in Touch———For additional insights, check out the links below:- The Internet Report blog: https://www.thousandeyes.com/blog/internet-report-configuration-change-outages?utm_source=transistor&utm_medium=referral&utm_campaign=fy25q2_internetreport_q2fy25ep5_podcast- 2024 Outage Trends Solidify; Plus OpenAI & Meta Outages: https://www.thousandeyes.com/blog/internet-report-2024-outage-trends-openai-meta-outages?utm_source=transistor&utm_medium=referral&utm_campaign=fy25q2_internetreport_q2fy25ep5_podcast- Netflix Broadcast Disruption: Lessons for Major Live Events: https://www.thousandeyes.com/blog/netflix-disruption-analysis-november-15-2024?utm_source=transistor&utm_medium=referral&utm_campaign=fy25q2_internetreport_q2fy25ep5_podcast- And join our upcoming webinar, “Top Outages of 2024, Explained: Lessons in Digital Resilience.” We'll unpack notable outages and performance degradations of 2024 and share lessons IT Operations teams can take away from these incidents to strengthen their digital resilience: https://www.thousandeyes.com/webinars/na-top-outages-2024-lessons-in-digital-resilience?utm_source=transistor&utm_medium=referral&utm_campaign=fy25q2_internetreport_q2fy25ep5_podcast ———Want to get in touch?If you have questions, feedback, or guests you would like to see featured on the show, send us a note at InternetReport@thousandeyes.com. Or follow us on LinkedIn or X at @thousandeyes

Configuration changes played an outsized role 2024 outages. Tune in to hear more about this and other outage trends—and learn how ITOps teams should plan accordingly in the year ahead. We'll also share insights from recent incidents at OpenAI and Google Cloud's Pub/Sub, and dive deeper into a degradation incident that Netflix experienced at the end of 2024. Read on to learn more, or use the chapters below to jump to the sections that most interest you. CHAPTERS 00:00 Intro 00:58 Cloud Service Provider (CSP) Outages Continue To Rise 01:52 Accidental Misconfigurations Trending for Clouds and Apps 07:10 OpenAI Outage 09:55 Google Cloud's Pub/Sub Disruption 14:47 Lessons From a Netflix Incident 18:57 Recent Outage Trends: By the Numbers 21:01 Get in Touch ——— For additional insights, check out the links below: - The Internet Report blog: https://www.thousandeyes.com/blog/internet-report-configuration-change-outages?utm_source=soundcloud&utm_medium=referral&utm_campaign=fy25q2_internetreport_q2fy25ep5_podcast - 2024 Outage Trends Solidify; Plus OpenAI & Meta Outages: https://www.thousandeyes.com/blog/internet-report-2024-outage-trends-openai-meta-outages?utm_source=soundcloud&utm_medium=referral&utm_campaign=fy25q2_internetreport_q2fy25ep5_podcast - Netflix Broadcast Disruption: Lessons for Major Live Events: https://www.thousandeyes.com/blog/netflix-disruption-analysis-november-15-2024?utm_source=soundcloud&utm_medium=referral&utm_campaign=fy25q2_internetreport_q2fy25ep5_podcast - And join our upcoming webinar, “Top Outages of 2024, Explained: Lessons in Digital Resilience.” We'll unpack notable outages and performance degradations of 2024 and share lessons IT Operations teams can take away from these incidents to strengthen their digital resilience: https://www.thousandeyes.com/webinars/na-top-outages-2024-lessons-in-digital-resilience?utm_source=soundcloud&utm_medium=referral&utm_campaign=fy25q2_internetreport_q2fy25ep5_podcast ——— Want to get in touch? If you have questions, feedback, or guests you would like to see featured on the show, send us a note at InternetReport@thousandeyes.com. Or follow us on LinkedIn or X at @thousandeyes ——— ABOUT THE INTERNET REPORT This is The Internet Report, a podcast uncovering what's working and what's breaking on the Internet—and why. Tune in to hear ThousandEyes' Internet experts dig into some of the most interesting outage events from the past couple weeks, discussing what went awry—was it the Internet, or an application issue? Plus, learn about the latest trends in ISP outages, cloud network outages, collaboration network outages, and more. Catch all the episodes on YouTube or your favorite podcast platform: - Apple Podcasts: https://podcasts.apple.com/us/podcast/the-internet-report/id1506984526 - Spotify: https://open.spotify.com/show/5ADFvqAtgsbYwk4JiZFqHQ?si=00e9c4b53aff4d08&nd=1&dlsi=eab65c9ea39d4773 - SoundCloud: https://soundcloud.com/ciscopodcastnetwork/sets/the-internet-report

Nesse episódio trouxemos as notícias e novidades do mundo da programação que nos chamaram atenção dos dias 03/08 a 09/08.

Nesse episódio trouxemos as notícias e novidades do mundo da programação que nos chamaram atenção dos dias 03/08 a 09/08.

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.

We have a co-worker of ours who admitted to us yesterday that they have never had a Pub Sub in their life! What is that one food that you've never tried?

NewsRadio WFLA Anchor Chris Trenkmann runs through today's top stories, including a Manatee County murder spree, a warning from the Surgeon General, a Florida couple stealing Publix subs, and lots more!

Welcome to episode 263 of the Cloud Pod Podcast – where the forecast is always cloudy! This week we're diving into the world of Snowflake, including announcements from their latest conference and details about their recent breach. Seriously – MFA is important! Plus we look at updates to Terraform, Claude 3, and OCI pushing the IOPS limits and much more. Join us!  Titles we almost went with this week: Snowflake Announces State-of-the-Art way for hackers to Talk to your Data Ticketmaster gets a snow job – MFA matters!  The CloudPod wouldn't use Oracle even for a million IOPS Azure finally wakes up to hibernation support JJB No one ever called a Bastion Host Premium until Today – JPB MK I look forward to connecting Kinesis to Pub Sub to Event Hub in the most rube        goldberg eventing architecture ever Hashicorp shows you the way 10 ways to say I want you Matt (I'm not bias with the name) Can we just hibernate ourselves on AI announcements Sus is how i feel about the new Susscanner from AWS OCI has enough power to run Oracle databases with 1 MIllion IOPS OCI wants 1 Million IOPS (dr evil voice) Monday, Tuesday, Hashidays… General News  Terraform AWS Cloud Control API provider is now generally available  The AWS Cloud Control Provider (AWSCC), built around the AWS Cloud Control API and designed to bring new services to Terraform faster, is now generally available.  The 1.0 release represents a step in their effort to provide launch-day support of AWS services.   This service was put into tech preview in 2021.  Glad it’s finally here; although we thought this effort was abandoned, honestly.  Interesting that you can mix HCL Terraform and AWSCC, but specify the different resource types in the configurations.   00:53 New Vault and Boundary offerings advance Security Lifecycle Management at HashiDays 2024   Hashicorp held their “Hashidays” event in London this last week, and announced improvements to their Security Lifecycle Management (SLM) products: Vault and Boundary Vault will be getting Workload Identify Federation, coming soon to Vault Enterprise which enables secretless configuration for vault plugins that integrate with external systems supporting WIF, such as AWS, Azure and Google Cloud.  By enabling secretless configuration, organizations reduce security concerns that can come with using long-lived and highly privileged security credentials.  With WIF

Any way you slice it, French bread is only legal if it has 4 ingredients. And Publix shoppers have a new flavor of sliced bread to try when ordering a PubSub.  Any way you slice it, the term "follow your heart" is not sage advice.  Some may consider it the greatest thing since sliced bread. The Chosen Season 4 is now available on The Chosen app. Bread is on the grocery lists for many. But it may be lower on the list of new parents where diapers take the top spot. Carmen...

After a quick battle with a zombified Rhodian miner, the crew of the Titan's Mercy uncovers even more of the unfolding mystery... Music by: Joshua Empyre (FreeSound and Bandcamp) NightCast Discord: see previous releases Donate to Destiny: see previous releases The StarBirds is played using the Edge Of The Empire system by Fantasy Flight Games and LucasBooks/Edge Studio    

Ok, we weren't living under rocks. Both Paul and I knew about how Jared from Subway got busted for messing with kids. But that's ALL we knew prior to doing this episode. We didn't know the sheer evil and depraved monster that hid behind the all American good guy image that he and Subway put in front of the cameras. We cover how he went from being extremely morbidly obese to becoming slim, rich and famous using the so called Subway diet. He was so famous that even famous people wanted to be seen with him. He was on every TV multiple times a day, and he became a very well paid and popular motivational speaker, while he and Subway laughed all the way to the bank. We also meet a courageous woman who Jared revealed his true nature to, causing her to launch a crusade to bring him down. This ruined her life. We also cover how his #1 man became an enabler, supplying Jared with all the forbidden treasures he wanted, and how this ultimately led to his downfall. He used his charity to fund his adventures. He flaunted how he was able to get away with his depravity, and if he hadn't been caught, he'd still be doing it, and who knows what it would have escalated to. Subway even tried to cover it up at first. He literally thought he was bulletproof, but luckily, he was taken down. So, join us. Grab a soda and a Jersey Mikes, or Firehouse Sub or a Pub Sub. Anything but a Subway sub, and get ready for an intense episode about one of the sickest pukes we've ever covered. But, there are palate cleansers along the way to lighten the mood, and we are able to ridicule him. Instagram Facebook Twitter (X) YouTube Website CKCB Discussion Pub FB Group

The biggest news story to hit our show in days: the Florida Panthers have partnered with Publix to create a signature pub sub.... the only problem is the sub itself. Hoch, Crowder and Solana poke holes in the toppings that the Panthers and Publix chose. 

In this video I talk about Apache Pulsar with Matteo Merli, CTO at StreamNative. This episode will provide you good insight about how Apache Pulsar works and more importantly differs with the most popular Pub/Sub and streaming platform Apache Kafka. Things like, what enables possibility of 1 million topics? Why is rebalancing not required? How does decoupled storage and compute architecture works? How it uses the concept of Subscriptions to avoid retaining data unnecessarily? And much more... Chapters: 00:00 Introduction and Guest Introduction 00:08 Understanding Apache Pulsar and its Origin 01:22 The Problem Apache Pulsar was Designed to Solve 02:35 The Evolution of Apache Pulsar 05:15 Understanding Basic Concepts of Apache Pulsar 09:27 Deep Dive into Apache Pulsar's Architecture 21:16 Understanding the Flow of Data in Apache Pulsar 28:54 Understanding Subscriptions in Apache Pulsar 31:57 Understanding End-to-End Latency and Subscription Creation 32:32 Broker's Role and Handling Metadata 33:05 Memory Management and Consumer Handling 34:07 Message Processing and Flow Control 34:32 Message Storage and Retrieval 36:00 Comparing Pulsar with Kafka 43:52 Understanding Multi-Tenancy in Pulsar 49:17 Exploring Tiered Storage and Future Developments Important links: StreamNative: https://streamnative.io/ Apache Pulsar: https://pulsar.apache.org/ Matteo Merli: https://twitter.com/merlimat =============================================================================== For discount on the below courses: Appsync: https://appsyncmasterclass.com/?affiliateId=41c07a65-24c8-4499-af3c-b853a3495003 Testing serverless: https://testserverlessapps.com/?affiliateId=41c07a65-24c8-4499-af3c-b853a3495003 Production-Ready Serverless: https://productionreadyserverless.com/?affiliateId=41c07a65-24c8-4499-af3c-b853a3495003 Use the button, Add Discount and enter "geeknarrator" discount code to get 20% discount. =============================================================================== Follow me on Linkedin and Twitter: https://www.linkedin.com/in/kaivalyaapte/ and https://twitter.com/thegeeknarrator If you like this episode, please hit the like button and share it with your network. Also please subscribe if you haven't yet. Database internals series: https://youtu.be/yV_Zp0Mi3xs Popular playlists: Realtime streaming systems: https://www.youtube.com/playlist?list=PLL7QpTxsA4se-mAKKoVOs3VcaP71X_LA- Software Engineering: https://www.youtube.com/playlist?list=PLL7QpTxsA4sf6By03bot5BhKoMgxDUU17 Distributed systems and databases: https://www.youtube.com/playlist?list=PLL7QpTxsA4sfLDUnjBJXJGFhhz94jDd_d Modern databases: https://www.youtube.com/playlist?list=PLL7QpTxsA4scSeZAsCUXijtnfW5ARlrsN Stay Curios! Keep Learning!

In this episode, we are joined by Steven, the CTO of PubNub, a company that has developed an edge net messaging network with over a billion connected devices. Steven explains that while message buses like Kafka or RabbitMQ are suitable for smaller scales, PubNub focuses on the challenges of connecting mobile devices and laptops at a web scale. They aim to provide instant signal delivery at a massive scale, prioritizing low latency for a seamless user experience. To achieve this, PubNub has architected their system to be globally distributed, running on AWS with Kubernetes clusters spread across all of Amazon's zones. They utilize GeoDNS to ensure users connect to the closest region for the lowest latency possible. Steven goes on to discuss the challenges they faced in building their system, particularly in terms of memory management and cleanup. They had to deal with issues such as segmentation faults and memory leaks, which caused runtime problems, outages, and potential data loss. PubNub had to invest in additional memory to compensate for these leaks and spend time finding and fixing the problems. While C was efficient, it came with significant engineering costs. As a solution, PubNub started adopting Rust, which helped alleviate some of these challenges. When they replaced a service with Rust, they observed a 5x improvement in memory and performance. Steven also talks about choosing programming languages for their platform and the difficulties in finding and retaining C experts. They didn't consider Java due to its perceived academic nature, and Go didn't make the list of options at the time. However, they now have services in production written in Go, though rewriting part of their PubSub bus in Go performed poorly compared to their existing C system. Despite this, they are favoring Rust as their language of choice for new services, citing its popularity and impressive results. The conversation delves into performance considerations with Python and the use of PyPy as a just-in-time compiler for optimization. While PyPy improved performance, it also required a lot of memory, which could be expensive. On the other hand, Rust provided a significant boost in both memory and performance, making it a favorable choice for PubNub. They also discuss provisioning, taking into account budget and aiming to be as close to what they need as possible. Kubernetes and auto scaling with HPAs (Horizontal Pod Autoscaling) are used to dynamically adjust resources based on usage. Integrating new services into PubNub's infrastructure involves both API-based communication and event-driven approaches. They use frameworks like Axiom for API-based communication and leverage Kafka with Protobuf for event sourcing. JSON is also utilized in some cases. Steven explains that they chose Protobuf for high-traffic topics and where stability is crucial. While the primary API for customers is JSON-based, PubNub recognizes the superior performance of Protobuf and utilizes it for certain cases, especially for shrinking down large character strings like booleans. They also discuss the advantages of compression enabled with Protobuf. The team reflects on the philosophy behind exploring Rust's potential for profit and its use in infrastructure and devices like IoT. Rust's optimization for smaller binaries is highlighted, and PubNub sees it as their top choice for reliability and performance. They mention developing a Rust SDK for customers using IoT devices. The open-source nature of Rust and its ability to integrate into projects and develop open standards are also praised. While acknowledging downsides like potential instabilities and longer compilation time, they remain impressed with Rust's capabilities. The conversation covers stability and safety in Rust, with the speaker expressing confidence in the compiler's ability to handle alpha software and packages. Relying on native primitives for concurrency in Rust adds to the speaker's confidence in the compiler's safety. The Rust ecosystem is seen as providing adequate coverage, although packages like libRDKafka, which are pre-1.0, can be challenging to set up or deploy. The speaker emphasizes simplicity in code and avoiding excessive abstractions, although they acknowledge the benefits of features like generics and traits in Rust. They suggest resources like a book by David McCloyd that focuses on learning Rust without overwhelming complexity. Expanding on knowledge sharing within the team, Stephen discusses how Rust advocates within the team have encouraged its use and the possibilities it holds for AI infrastructure platforms. They believe Rust could improve performance and reduce latency, particularly for CPU tasks in AI. They mention the adoption of Rust in the data science field, such as its use in the Parquet data format. The importance of tooling improvements, setting strict standards, and eliminating unsafe code is highlighted. The speaker expresses the desire for a linter that enforces a simplified version of Rust to enhance code readability, maintainability, and testability. They discuss the balance between functional and object-oriented programming in Rust, suggesting object-oriented programming for larger-scale code structure and functional paradigms within functions. Onboarding Rust engineers is also addressed, considering whether to prioritize candidates with prior Rust experience or train individuals skilled in another language on the job. Recognizing the shortage of Rust engineers, Stephen encourages those interested in Rust to pursue a career at PubNub, pointing to resources like their website and LinkedIn page for tutorials and videos. They emphasize the importance of latency in their edge messaging technology and invite users to try it out.

This week's news highlights Discord's deep-dive into how they've scaled their servers to support millions of concurrent users, leveraging Elixir's power. We cover how the Oban notifier has evolved to include Phoenix.PubSub and Redis integration, allowing more flexibility for your job processing needs. LiveView Native's tutorial experience looks promising to make mobile development smoother and more intuitive. Plus, we cover the Livebook PR merge upgrading to the Bandit library and more! Show Notes online - http://podcast.thinkingelixir.com/177 (http://podcast.thinkingelixir.com/177) Elixir Community News - https://discord.com/blog/maxjourney-pushing-discords-limits-with-a-million-plus-online-users-in-a-single-server (https://discord.com/blog/maxjourney-pushing-discords-limits-with-a-million-plus-online-users-in-a-single-server?utm_source=thinkingelixir&utm_medium=shownotes) – Discord blog post detailing the scaling of individual Discord servers and the technical challenges involved. - https://github.com/discord/manifold (https://github.com/discord/manifold?utm_source=thinkingelixir&utm_medium=shownotes) – GitHub link to Discord's opensource Elixir library "Manifold" used for batch message passing between nodes. - https://www.youtube.com/watch?v=HP86Svk4hzI (https://www.youtube.com/watch?v=HP86Svk4hzI?utm_source=thinkingelixir&utm_medium=shownotes) – Chris Grainger discusses using Elixir + Phoenix + Nx in production with machine learning on the BEAM. - https://github.com/livebook-dev/livebook/pull/2316 (https://github.com/livebook-dev/livebook/pull/2316?utm_source=thinkingelixir&utm_medium=shownotes) – A Livebook PR titled "Upgrade to bandit" merged by José Valim, signifying an endorsement for the Bandit library. - https://twitter.com/cvkmohan/status/1719489327925694682 (https://twitter.com/cvkmohan/status/1719489327925694682?utm_source=thinkingelixir&utm_medium=shownotes) – Discussion on Twitter about using Bandit as an upgrade for a Phoenix app. - https://elixirstream.dev/gendiff/phx_new/19CBA027FA97E2873CC24093F6AC1820 (https://elixirstream.dev/gendiff/phx_new/19CBA027FA97E2873CC24093F6AC1820?utm_source=thinkingelixir&utm_medium=shownotes) – A flag added to elixirstream.dev for diffing generated output, introduced in Phoenix 1.7.8. - https://github.com/sorentwo/obannotifiersphoenix (https://github.com/sorentwo/oban_notifiers_phoenix?utm_source=thinkingelixir&utm_medium=shownotes) – Release of a new Oban notifier powered by Phoenix.PubSub, compatible with OTP and now able to use Redis. - https://twitter.com/bcardarella/status/1720179762088272080 (https://twitter.com/bcardarella/status/1720179762088272080?utm_source=thinkingelixir&utm_medium=shownotes) – Tease of the upcoming LiveView Native v0.2 and its tutorial experience using Livebook. - https://podcast.thinkingelixir.com/174 (https://podcast.thinkingelixir.com/174?utm_source=thinkingelixir&utm_medium=shownotes) – Previous interview about DockYard's BeaconCMS - https://twitter.com/bcardarella/status/1721172482298663214 (https://twitter.com/bcardarella/status/1721172482298663214?utm_source=thinkingelixir&utm_medium=shownotes) – Twitter post discussing the 'Variants' feature for A/B/C/D/etc. page variant testing in BeaconCMS. - https://twitter.com/NervesMeetup/status/1721389396417728782 (https://twitter.com/NervesMeetup/status/1721389396417728782?utm_source=thinkingelixir&utm_medium=shownotes) – Announcement tweet for the next Nerves embedded systems meetup. - https://www.meetup.com/nerves/events/290189609/ (https://www.meetup.com/nerves/events/290189609/?utm_source=thinkingelixir&utm_medium=shownotes) – Meetup link for the Nerves embedded systems event featuring a walkthrough by Alex McLain. Do you have some Elixir news to share? Tell us at @ThinkingElixir (https://twitter.com/ThinkingElixir) or email at show@thinkingelixir.com (mailto:show@thinkingelixir.com) Find us online - Message the show - @ThinkingElixir (https://twitter.com/ThinkingElixir) - Message the show on Fediverse - @ThinkingElixir@genserver.social (https://genserver.social/ThinkingElixir) - Email the show - show@thinkingelixir.com (mailto:show@thinkingelixir.com) - Mark Ericksen - @brainlid (https://twitter.com/brainlid) - Mark Ericksen on Fediverse - @brainlid@genserver.social (https://genserver.social/brainlid) - David Bernheisel - @bernheisel (https://twitter.com/bernheisel) - David Bernheisel on Fediverse - @dbern@genserver.social (https://genserver.social/dbern) - Cade Ward - @cadebward (https://twitter.com/cadebward) - Cade Ward on Fediverse - @cadebward@genserver.social (https://genserver.social/cadebward)

Byron Ruth and David Gee from the NATS and the Synadia team join Lane today to chat about distributed systems, and more specifically, PubSub architectures. If you've ever wondered about the difference between a distributed monolith and a truly distributed system, this episode is for you. We break down NATS and how it relates to other systems like RabbitMQ, Kafka, and more.Learn back-end development - https://boot.devListen on your favorite podcast player: https://www.backendbanter.comByron's Twitter: https://twitter.com/thedevelDavid's Twitter: https://twitter.com/davedotdevNATS: NATS.ioNats By Example: https://natsbyexample.com/Synadia: https://www.synadia.comSynadia Newsletter: https://www.synadia.com/newsletterByron's website: byronruth.comNATSFM Podcast: Nats.FMLike & subscribe for the algo if you enjoyed the video!

Socket.IO is a library for building low-latency, bidirectional and event-based communication between a client and a server. Now you can build real-time apps with Azure Web PubSub for Socket.IO and say goodbye to using adapters. Kevin Guo and Chenyang Liu are here to show Scott Hanselman how it works, today on Azure Friday. Chapters 00:00 - Introduction 01:03 - What is Socket.IO? 02:19 - What pain point does this eliminate? 06:00 - Azure Trivia Game example app 13:05 - Scott peels back the cover 15:32 - Simple code change to implement 16:49 - Wrap-up Recommended resources Socket.IO on Azure blog post Overview Socket.IO on Azure Quickstart: Incorporate Web PubSub for Socket.IO in your app Create a Pay-as-You-Go account (Azure) Create a free account (Azure) Connect Scott Hanselman | Twitter: @SHanselman Azure Friday | Twitter: @AzureFriday Azure | Twitter: @Azure

Socket.IO is a library for building low-latency, bidirectional and event-based communication between a client and a server. Now you can build real-time apps with Azure Web PubSub for Socket.IO and say goodbye to using adapters. Kevin Guo and Chenyang Liu are here to show Scott Hanselman how it works, today on Azure Friday. Chapters 00:00 - Introduction 01:03 - What is Socket.IO? 02:19 - What pain point does this eliminate? 06:00 - Azure Trivia Game example app 13:05 - Scott peels back the cover 15:32 - Simple code change to implement 16:49 - Wrap-up Recommended resources Socket.IO on Azure blog post Overview Socket.IO on Azure Quickstart: Incorporate Web PubSub for Socket.IO in your app Create a Pay-as-You-Go account (Azure) Create a free account (Azure) Connect Scott Hanselman | Twitter: @SHanselman Azure Friday | Twitter: @AzureFriday Azure | Twitter: @Azure

AWS AppSync is a serverless GraphQL and Pub/Sub's APIs that simplify application development through a single endpoint to securely query, update, or publish data. Tune in to listen to Hawn Nguyen-Loughren, Sr. Manager, Solutions Architect and Venugopalan Vasudevan, Sr. Specialist Solutions Architect discuss cross-team API development considerations for enterprises, introduce AWS AppSync, dive deeper into how AWS AppSync enables enterprise developer teams to consolidate APIs owned and managed by independent teams into a single, federated API exposed to clients, and how this helps setup crucial guardrails to promote team collaboration and performance at scale. Merged APIs on AWS AppSync blog: https://bit.ly/3Rvp3fU AWS AppSync Merged APIs developer guide: https://bit.ly/3RxPd1p

2023-09-19 Weekly News — Episode 204Watch the video version on YouTube at https://youtube.com/live/QR78EAolYQo?feature=share Hosts:  Gavin Pickin - Senior Developer at Ortus Solutions Dan Card- Senior Developer at Ortus Solutions Thanks to our Sponsor - Ortus SolutionsThe makers of ColdBox, CommandBox, ForgeBox, TestBox and all your favorite box-es out there. A few ways  to say thanks back to Ortus Solutions: Like and subscribe to our videos on YouTube.  Help ORTUS reach for the Stars - Star and Fork our ReposStar all of your Github Box Dependencies from CommandBox with https://www.forgebox.io/view/commandbox-github  Subscribe to our Podcast on your Podcast Apps and leave us a review AND WE WILL READ IT ON THE SHOW Sign up for a free or paid account on CFCasts, which is releasing new content every week BOXLife store: https://www.ortussolutions.com/about-us/shop Buy Ortus's Books 102 ColdBox HMVC Quick Tips and Tricks on GumRoad (http://gum.co/coldbox-tips) Learn Modern ColdFusion (CFML) in 100+ Minutes - Free online https://modern-cfml.ortusbooks.com/ or buy an EBook or Paper copy https://www.ortussolutions.com/learn/books/coldfusion-in-100-minutes   Patreon SupportWe have 38 patreons: https://www.patreon.com/ortussolutions. News and AnnouncementsSept 13th - Happy Programmers DayHacktoberfest is comingCELEBRATE OUR 10TH YEAR SUPPORTING OPEN SOURCE!This year marks the 10th anniversary of Hacktoberfest, and we're calling on your support! Whether it's your first time participating—or your tenth—it's almost time to hack out four pristine pull/merge requests as we continue our month of support for open source.Hacktoberfest has grown from 676 participants in 2014 to nearly 147,000 participants last year. To help ensure Hacktoberfest can be sustained for another decade, this year we're moving away from a free t-shirt reward to a digital reward.PREPTEMBERSeptember is the perfect time to prepare for Hacktoberfest. Get a jump start by finding projects to contribute to, adding the ‘hacktoberfest' tag to your projects, or familiarizing yourself with Git.Discord: https://discord.gg/hacktoberfest https://hacktoberfest.com/ CFMLers get AWS CertifiedDaniel Garcia from Ortus, and a few other CFML Community members created a study group to complete the AWS Cloud Practitioner Certification, the first on many AWS tracks.All of the group members who took the Certification exam passed, which is great for these developers, their employers, and the community.If you are considering a certification, create a study group with friends or community members, it helps with learning, accountability and it's great to socialize with like minded people.https://d1.awsstatic.com/training-and-certification/docs/AWS_certification_paths.pdfhttps://aws.amazon.com/certification/?nc2=sb_ce_co New Releases and UpdatesLucee 5.4.3.7-Snapshot ready for TestingHey everyone, we have a new 5.4.3.7-SNAPSHOT out which addresses all the known regressions with 5.4.3LDEV-4675 Admin: requested action doesn't exist 1LDEV-3854 a fix for the pagePool locking problem 7LDEV-4480 “.” should not be accepted/converted as/to a number 2LDEV-4676 SerializeJSON() produces invalid JSON when serializing some CFC instances 5Builds are up, including docker images, It would be great if people can test this out and let us knowhttps://dev.lucee.org/t/5-4-3-7-snapshot-ready-for-testing/13001 Webinar / Meetups and WorkshopsOOP & ColdFusionNolan ErckFriday, September 29, 2023 @ 12 PM HAST (Hawaii Standard Time)Object-Oriented Programming is a common term in programming languages. It's a vast concept but to sum it up in a single line, it is a set of concepts and techniques that make use of the “object” construct, to write more reusable, maintainable, and organized code. Objects are implemented differently in every language. In ColdFusion, we have ColdFusion Components (CFCs) that can be instantiated to create objects.Anyone who has ever studied OOP must know that there are four main concepts, which are: Abstraction Encapsulation Inheritance Polymorphism https://www.meetup.com/hawaii-coldfusion-meetup-group/events/294629892/ICYMI - Hawaii CF User Group Meetup - Mark Takata on Graph QL & ColdFusionGraphQL is a query language for APIs and a runtime for fulfilling those queries with your existing data. GraphQL provides a complete and understandable description of the data in your API, gives clients the power to ask for exactly what they need and nothing more, makes it easier to evolve APIs over time, and enables powerful developer tools.https://hawaiicoldfusionusergroup.adobeconnect.com/p6cwiyco0hx7/ ICYMI - Sac Interactive - Mark Takata - ColdFusion 2023 Modern CFML Development EcosystemJoin Mark Takata, Global Technical Evangelist for Adobe ColdFusion as he delves into all of the new incredible feature additions for ColdFusion 2023. We will discuss GraphQL, a variety of GCP native features (including storage, FireStore and Pub/Sub), JWT and security additions for single sign-on for the ColdFusion administrator. Both high level overview and code samples will be highlighted, and all code will be available on GitHub for download after the talk.https://www.youtube.com/watch?v=rdRtN2YEUnE CFCasts Content Updateshttps://www.cfcasts.comRecent Releases Into the Box 2023 Videos is available for purchase as an EXCLUSIVE PREMIUM package. https://cfcasts.com/series/itb-2023  Subscribers will get access to premium packages after a 6 month exclusive window. Into the Box Attendees should have their coupon code in the email already!!!! 2023 ForgeBox Module of the Week Series - 1 new Video https://cfcasts.com/series/2023-forgebox-modules-of-the-week  2023 VS Code Hint tip and Trick of the Week Series - 1 new Video https://cfcasts.com/series/2023-vs-code-hint-tip-and-trick-of-the-week  Coming Soon More ForgeBox and VS Code Podcast snippet videos Mastering CBWIRE v3 from Grant ColdBox Elixir from Eric Conferences and TrainingAdobe CF Summit WestLas Vegas 2-4th of October.Session passes @ $199 Professional passes @ $299. Speakers have been announced - with some great sessionshttps://cfsummit.adobeevents.com/ Andy Bucklee will be there (David Wallace from The Office)Ortus CF Summit Training - ColdBox 7 Zero to Hero - SOLD OUTDate: October 4th - 5th, 2023 | Right after Adobe CFSummit, 2023Speakers: Luis Majano & Gavin PickinLocation: Las Vegas, NevadaVenue: Regus - Las Vegas - 3960 Howard Hughes Parkway Paradise #Suite 500 Las Vegas, NV 89169 United StatesSpotlight Less than 2 miles from the Mirage - 30 mins walk Next to Marriot hotel - 2 min walk 1 mile to Top Golf - 20 min walk 5 min walk to Fogo de Chão Brazilian Steakhouse 5 min walk to starbucks 5 min walk to Lo-los chicken and waffles WIN WIN WIN WINhttps://www.eventbrite.com/e/workshop-coldbox-from-zero-to-hero-tickets-659169262007?aff=oddtdtcreator Into the Box LATAMNovember 30thUniversity of Business in El Salvador.https://latam.intothebox.org/ITB 2024Location: Optica in Washington, DCAnnouncement Blog Post: https://www.ortussolutions.com/blog/our-into-the-box-2024-venue-and-dates-are-setDates: May 15-17, 2024Get Blind Tickets Now: https://www.eventbrite.com/e/into-the-box-2024-the-new-era-of-modernization-tickets-663126347757https://www.ortussolutions.com/blog/call-for-speakers-into-the-box-2024-share-your-expertiseMore conferencesNeed more conferences, this site has a huge list of conferences for almost any language/community.https://confs.tech/Blogs, Tweets, and Videos of the Week9/19/2023 - Blog - Ben Nadel - Which Whitespace Characters Does trim() Remove In ColdFusionYesterday, an external API call that I was making failed because one of the values that I was posting contained a trailing "Zero width space" character (u200b). The value in question was being passed-through ColdFusion's native trim() function; which was clearly not removing this whitespace character. As such, it occurred to me that I didn't really know which characters are (and are not) handled by the trim() function. And so, I wanted to run a test.https://www.bennadel.com/blog/4516-which-whitespace-characters-does-trim-remove-in-coldfusion.htm 9/13/2023 - Blog - Ben Nadel - Using FileReadLine() With Seekable Files In ColdFusion Last week, I started to explore seekable files in ColdFusion. A seekable file allows us to jump to an arbitrary offset within the file contents (which I believe can be done without having to read the entire file into memory). I've recently been dealing with consuming large text-files at work; and, I'm wondering if a seekable file might be something I can use to create a "resumable" consumption process. As such, I wanted to play around with using the fileReadLine() function in conjunction with seekable files in ColdFusion.https://www.bennadel.com/blog/4515-using-filereadline-with-seekable-files-in-coldfusion.htm 9/11/2023 - Tweet - Ben Nadel - Weird Application Datasource ErrorHas anyone had any luck getting per-application datasources (ie, `this.datasources`) to work in #ColdFusion 2023? My code works fine in ACF 2021; but, when I build the same Docker image using 2023, the code breaks.https://x.com/BenNadel/status/1701181955578986946?s=20 CFML JobsSeveral positions available on https://www.getcfmljobs.com/Listing over 98 ColdFusion positions from 65 companies across 43 locations in 5 Countries.3 new jobs listed in the last two weeksFull-Time - Fully Insured End of Lease Cleaners in Melbourne at Melbourn.. - Australia Posted Sep 18 for Bond Cleaning in MelbourneAs your trusted partner for end of lease cleaning, Bond Cleaning in Melbourne is dedicated to exceeding your expectations. With years of experience, we understand the critical details that ensure a successful clean. Our team works diligently to restore your rental property to its original glory, ensuring the swift return of your security deposit. Property owners and real estate agents have come to rely on our expertise, backed by the REIV-approved checklist. We offer flexible packages at affordable rates, tailored to your convenience. Don't leave your deposit to chance - contact us at 03 9068 8186 or reach out through our website. https://www.getcfmljobs.com/viewjob.cfm?jobid=11605 Full-Time - ColdFusion Developer 2 (Remote) at Remote - United States Posted: Sep 18 for Community BrandsThe Developer position is responsible for writing application code to contribute to the full lifecycle of development from concept to post-production support and maintenance of server / OS / desktop / web / mobile applications and services. This position will develop application code, contribute to version-controlled source code repositories and will managed assigned tasks to create measurable value and deliver software to market using industry recognized agile methodologies and best practices. The Developer will be responsible for coding according to prescribed standards and guidelines set forth by the architects and leadership teams and must demonstrate quality, brevity and timeliness in all deliverables.https://www.getcfmljobs.com/jobs/index.cfm/united-states/coldfusion-developer-2-remote-at-community-brands/11604 Full-Time - ColdFusion Developer at Washington, DC - United States Sep 08 for TamminaUS Citizen. Must be clearable. A clearance or an inactive clearance preferred. Government agency experience required.We are seeking an Application Developer to join our team. The developer shall perform and/or support requirements definition, design and prototyping, implementation, unit testing, debugging, verification, deployment, and maintenance activities throughout the software development life cycle (SDLC) for current and future software modules of a comprehensive web portal environment.https://www.getcfmljobs.com/jobs/index.cfm/united-states/ColdFusionDev-at-Washington-DC/11603 Other Job LinksThere is a jobs channel in the CFML slack team, and in the Box team slack now tooForgeBox Module of the WeekOrtus ORM Extension for LuceeThe Ortus ORM Extension is a native Lucee Extension that allows your CFML application to integrate with the powerful Hibernate ORM. With Hibernate, you can interact with your database records in an object oriented fashion, using components to denote each record and simple getters and setters for each field Add Object Relational Mapping to any CFML app with Hibernate ORM Use native CFML methods to update and persist entities to the database (entityNew(), entitySave(), ormFlush(), etc.) Supports 80+ database dialects, from SQLServer2005 to MySQL8 and PostgreSQL 60% faster startup than the Lucee Hibernate extension Generate your mapping XML once and never again with the autoGenMap=false ORM configuration setting React to entity changes with pre and post event listeners such as onPreInsert(), onPreUpdate() and onPreDelete() Over 20 native CFML functions: $ install D062D72F-F8A2-46F0-8CBC91325B2F067B https://orm-extension.ortusbooks.com/ https://www.forgebox.io/view/D062D72F-F8A2-46F0-8CBC91325B2F067BVS Code Hint Tips and Tricks of the WeekCSS PeekAllow peeking to css ID and class strings as definitions from html files to respective CSS. Allows peek and goto definition.This extension extends HTML and ejs code editing with Go To Definition and Go To Symbol in Workspace support for css/scss/less (classes and IDs) found in strings within the source code.This was heavily inspired by a similar feature in Brackets called CSS Inline Editors.https://marketplace.visualstudio.com/items?itemName=pranaygp.vscode-css-peek Thank you to all of our Patreon SupportersThese individuals are personally supporting our open source initiatives to ensure the great toolings like CommandBox, ForgeBox, ColdBox,  ContentBox, TestBox and all the other boxes keep getting the continuous development they need, and funds the cloud infrastructure at our community relies on like ForgeBox for our Package Management with CommandBox. You can support us on Patreon here https://www.patreon.com/ortussolutionsDon't forget, we have Annual Memberships, pay for the year and save 10% - great for businesses everyone. Bronze Packages and up, now get a ForgeBox Pro and CFCasts subscriptions as a perk for their Patreon Subscription. All Patreon supporters have a Profile badge on the Community Website All Patreon supporters have their own Private Forum access on the Community Website All Patreon supporters have their own Private Channel access BoxTeam Slack https://community.ortussolutions.com/Top Patreons (mind-boggling) John Wilson - Synaptrix Tomorrows Guides Jordan Clark Gary Knight Giancarlo Gomez  David Belanger  Dan Card Jeffry McGee - Sunstar Media Dean Maunder Kevin Wright Doug Cain  Nolan Erck  Abdul Raheen And many more PatreonsYou can see an up to date list of all sponsors on Ortus Solutions' Websitehttps://ortussolutions.com/about-us/sponsors Thanks everyone!!! ★ Support this podcast on Patreon ★

Welcome episode 227 of the Cloud Pod podcast - where the forecast is always cloudy! This week your hosts are Justin, Jonathan, Matthew and Ryan - and they're REALLY excited to tell you all about the 161 one things announced at Google Next. Literally, all the things. We're also saying farewell to EC2 Classic, Amazon SES, and Azure's Explicit Proxy - which probably isn't what you think it is.  Titles we almost went with this week:

2023-08-22 Weekly News - Episode 202Watch the video version on YouTube at https://youtube.com/live/HJHCDA-UbV8?feature=shareHosts:  Eric Peterson - Senior Developer at Ortus Solutions Grant Copley - Senior Developer at Ortus Solutions Thanks to our Sponsor - Ortus SolutionsThe makers of ColdBox, CommandBox, ForgeBox, TestBox and all your favorite box-es out there. A few ways  to say thanks back to Ortus Solutions: Like and subscribe to our videos on YouTube.  Help ORTUS reach for the Stars - Star and Fork our ReposStar all of your Github Box Dependencies from CommandBox with https://www.forgebox.io/view/commandbox-github  Subscribe to our Podcast on your Podcast Apps and leave us a review Sign up for a free or paid account on CFCasts, which is releasing new content every week BOXLife store: https://www.ortussolutions.com/about-us/shop Buy Ortus's Books 102 ColdBox HMVC Quick Tips and Tricks on GumRoad (http://gum.co/coldbox-tips) Learn Modern ColdFusion (CFML) in 100+ Minutes - Free online https://modern-cfml.ortusbooks.com/ or buy an EBook or Paper copy https://www.ortussolutions.com/learn/books/coldfusion-in-100-minutes   Patreon Support (stupendous)We have 40 patreons: https://www.patreon.com/ortussolutions. News and AnnouncementsExciting News! Only 3 Tickets Left for Our #ColdBox 7 Workshop! Luis Majano and Gavin Pickin will guide you through an incredible learning journey with insider tips and tricks. Hurry, Register now!https://twitter.com/ortussolutions/status/1692624601350643716https://www.eventbrite.com/e/workshop-coldbox-from-zero-to-hero-tickets-659169262007?aff=oddtdtcreatorLucee Critical Security Alert, August 15th, 2023 - CVE-2023-38693(XXE [XML External Entity] vulnerabilities)The Lucee team received a responsible disclosure for a security vulnerability which affects all previous releases of Lucee.After reviewing the report and confirming the vulnerability, the Lucee team then conducted a further security review and found additional vulnerabilities which have been addressed as part of this security update.Latest Stable Releases5.4.3.2 (recommended)5.3.12.1Backported Stable ReleasesIn addition, as we are aware that some Lucee users have not yet upgraded from older versions, we have also published Stable Releases for these older versions with the vulnerability.5.3.9.1735.3.8.2375.3.7.59https://dev.lucee.org/t/lucee-critical-security-alert-august-15th-2023-cve-2023-38693/12893The agenda for Adobe ColdFusion Summit 2023 is live now!https://cfsummit.adobeevents.com/agenda/https://twitter.com/coldfusion/status/1693582117203030287New Releases and UpdatesCommandBox 5.9.1 Released!We are pleased to announce the general availability of CommandBox 5.9.1. This is a very small release with two changes.Update to Lucee 5.4.3.2Update bundled JRE to 11.0.20+8Note Lucee 5.4.3.2 contains critical security patches.The new Lucee version affects the core CLI runtime as well as the default server you get when running "server start" with no cfengine specified.  Possible compatibility issues related to the major bump in Lucee version: This Lucee version does not include Hibernate, so the Ortus Hibernate extension is installed.  We will stop doing this in 6.0 This Lucee version has strict XML parsing settings on by default which may affect any servers you start which parse XML containing DTDs. https://www.ortussolutions.com/blog/commandbox-591-releasedWebinar / Meetups and WorkshopsHawaii ColdFusion Meetup Group — Graph QL & ColdFusionSpeaker: Mark TakataFriday, August 25, 2023 @ 12 PM HAST (Hawaii Standard Time)GraphQL is a query language for APIs and a runtime for fulfilling those queries with your existing data. GraphQL provides a complete and understandable description of the data in your API, gives clients the power to ask for exactly what they need and nothing more, makes it easier to evolve APIs over time, and enables powerful developer tools.GraphQL is a query language for APIs and a runtime for executing those queries with your existing data. It provides a more efficient, powerful, and flexible alternative to REST.In ColdFusion 2023 we are providing a native method of consuming and sending data across GraphQL using GQL. This includes support for fragments, variables, aliases, queries, mutations, subscriptions and more.Also, this talk will go over on why to use Graph QL over REST APIs.https://www.meetup.com/hawaii-coldfusion-meetup-group/events/294631289/Adobe Upcoming EventsWebinar - Road to Fortuna Series: Exploring the New Google Cloud Platform Features FRIDAY, AUGUST 25, 202310:00 AM PDTOnline EventMark Takatahttps://google-cloud-platform-adobe-coldfusion.meetus.adobeevents.com/ During the Road to Fortuna Series: Exploring the New Google Cloud Platform Features webinar, Mark Takata will explore the new native hooks that Adobe ColdFusion is adding to work with the Google Cloud Platform. He will focus on features related to the GCP FireStore document database, Storage capabilities, and PubSub messaging features, providing attendees with valuable insights into how these features can be leveraged to optimize application development and delivery on the Google Cloud Platform. The session will be highly technical and will provide attendees with practical examples and use cases.CFCasts Content Updateshttps://www.cfcasts.comRecent Releases Into the Box 2023 Videos is available for purchase as an EXCLUSIVE PREMIUM package. https://cfcasts.com/series/itb-2023  Subscribers will get access to premium packages after a 6 month exclusive window. Into the Box Attendees should have their coupon code in the email already!!!! 2023 ForgeBox Module of the Week Series - 1 new Video https://cfcasts.com/series/2023-forgebox-modules-of-the-week  2023 VS Code Hint tip and Trick of the Week Series - 1 new Video https://cfcasts.com/series/2023-vs-code-hint-tip-and-trick-of-the-week  Coming Soon More ForgeBox and VS Code Podcast snippet videos ColdBox Elixir from Eric Mastering CBWIRE v3 from Grant Conferences and TrainingAdobe CF Summit WestLas Vegas 2-4th of October.Get your early bird passes now. Session passes @ $199 Professional passes @ $299. First round of speakers has been announced - with some great sessionshttps://cfsummit.adobeevents.com/ STUDENTS can get a free pass if they are enrolled at tertiary level educational institutionsOrtus CF Summit Training - ColdBox 7 Zero to HeroDate: October 4th - 5th, 2023 | Right after Adobe CFSummit, 2023Speakers: Luis Majano & Gavin PickinLocation: Las Vegas, NevadaVenue: Regus - Las Vegas - 3960 Howard Hughes Parkway Paradise #Suite 500 Las Vegas, NV 89169 United StatesTicket Price Regular Price Tickets: $699 — Only 3 left! 25% Discount today: https://www.eventbrite.com/e/659169262007/?discount=modernize Spotlight Less than 2 miles from the Mirage - 30 mins walk Next to Marriot hotel - 2 min walk 1 mile to Top Golf - 20 min walk 5 min walk to Fogo de Chão Brazilian Steakhouse 5 min walk to starbucks 5 min walk to Lo-los chicken and waffles WIN WIN WIN WINhttps://www.eventbrite.com/e/workshop-coldbox-from-zero-to-hero-tickets-659169262007?aff=oddtdtcreator Into the Box LATAMNovember 30thUniversity of Business in El Salvador.https://latam.intothebox.org/ITB 2024Location: Optica in Washington, DCAnnouncement Blog Post: https://www.ortussolutions.com/blog/our-into-the-box-2024-venue-and-dates-are-setDates: May 15-17, 2024Get Blind Tickets Now: https://www.eventbrite.com/e/into-the-box-2024-the-new-era-of-modernization-tickets-663126347757More conferencesNeed more conferences, this site has a huge list of conferences for almost any language/community.https://confs.tech/Blogs, Tweets, and Videos of the Week08/10/2023 - Blog - Ben Nadel - Sanity Check: Using Overflow Scrolling On CSS Flexbox PanelsI'm a huge fan of CSS Flexbox. As someone who had (?has?) to support IE11 up until the very end, CSS Flexbox became my go-to for complex layouts. However, even with years of Flexbox experience under my belt, I'm not always confident that I understand exactly how it will behave when it contains overflowing content. One scenario in which I've been using Flexbox recently is to create a dynamic set of "panels". Consider a set of side-by-side panels in which one panel is dynamically added or removed to and from the DOM (Document Object Model), respectively. Is it safe to apply overflow:auto to these CSS Flexbox panels?https://www.bennadel.com/blog/4499-sanity-check-using-overflow-scrolling-on-css-flexbox-panels.htm08/13/2023 - Blog - Ben Nadel - Error "Type" Isn't Always A String In Adobe ColdFusionYesterday, while working on Dig Deep Fitness, my ColdFusion fitness tracker, I accidentally consumed an ordered struct as if it were an array. As expected, ColdFusion threw an error; however, my centralized error handling logic broke because the type property of the thrown error was not a string, it was a complex Java object. I don't think I'd ever run into this issue before - I've always believed that the type, message, detail, and extendedInfo properties were guaranteed to be a string. I guess not.https://www.bennadel.com/blog/4500-error-type-isnt-always-a-string-in-adobe-coldfusion.htmHere's your joke translation for the day: https://twitter.com/Updates4Devs/status/169068193489081958408/16/2023 - Blog - Brad Wood - Use CommandBox's rate limiter on only certain requestsThis came up in conversation internally at Ortus today and I wanted to write it down somewhere public. There has already been a setting in CommandBox for some time called web.maxRequests in the server.json to limit the total number of concurrently-running requests for the entire server. Once this pool is full, any additional incoming requests will be queued until there are free threads available.The problem scenario is what if you allow 25 concurrent requests (max threads) and someone whacks the refresh button 30 times on a report that takes 5 minutes to run? Well, all your available threads will be busy for the next 5 minutes and your site won't respond to other requests in the meantime, even if they are quick ones.The same potential scenario goes for CommandBox 6's new multi-site mode. The worker thread pool in Undertow is global and applies to all sites. That means if you have 2 sites and allow 100 concurrent requests and site 1 is using all of them, there will be no threads left to process any requests for site 2.The solution to both of these scenarios is a server rule that is built into Undertow called request-limit(). You can specify a request limit for an entire site or even for a specific type of request.https://community.ortussolutions.com/t/use-commandboxs-rate-limiter-on-only-certain-requests/9750CFML JobsSeveral positions available on https://www.getcfmljobs.com/Listing over 87 ColdFusion positions from 58 companies across 41 locations in 5 Countries.2 new jobs listed in the last two weeksFull-Time - ColdFusion Developer at Quincy, MAPosted: August 09, 2023https://www.getcfmljobs.com/jobs/index.cfm/united-states/CFDeveloper-Quincy-MA/11594Full-Time - Coldfusion at Thiruvananthapuram, KeralaPosted: August 18, 2023https://www.getcfmljobs.com/jobs/index.cfm/india/Coldfusion-at-Thiruvananthapuram-Kerala/11595Other Job LinksThere is a jobs channel in the CFML slack team, and in the Box team slack now tooForgeBox Module of the WeekRemember Meby David LevinRememberMe is a Coldbox module designed to work in conjunction with your authentication system to "remember" and automatically log in users on subsequent website visits.https://forgebox.io/view/rememberMeVS Code Hint Tips and Tricks of the Weeki18n AllyAll in one i18n extension for VS CodeSupports multi-root workspacesSupports remote developmentSupports numerous popular frameworksSupports linked locale messagesUses i18n for the extension itself, of course. Translation Listhttps://marketplace.visualstudio.com/items?itemName=lokalise.i18n-allyThank you to all of our Patreon SupportersThese individuals are personally supporting our open source initiatives to ensure the great toolings like CommandBox, ForgeBox, ColdBox,  ContentBox, TestBox and all the other boxes keep getting the continuous development they need, and funds the cloud infrastructure at our community relies on like ForgeBox for our Package Management with CommandBox. You can support us on Patreon here https://www.patreon.com/ortussolutionsDon't forget, we have Annual Memberships, pay for the year and save 10% - great for businesses everyone. Bronze Packages and up, now get a ForgeBox Pro and CFCasts subscriptions as a perk for their Patreon Subscription. All Patreon supporters have a Profile badge on the Community Website All Patreon supporters have their own Private Forum access on the Community Website All Patreon supporters have their own Private Channel access BoxTeam Slack https://community.ortussolutions.com/Top Patreons (stupendous) John Wilson - Synaptrix Tomorrows Guides Jordan Clark Gary Knight Giancarlo Gomez  David Belanger   Dan Card Jeffry McGee - Sunstar Media Dean Maunder Kevin Wright Doug Cain  Nolan Erck  Abdul Raheen And many more PatreonsYou can see an up to date list of all sponsors on Ortus Solutions' Websitehttps://ortussolutions.com/about-us/sponsors Thanks everyone!!! ★ Support this podcast on Patreon ★

In this episode, Amir Bormand interviews Emilio Schapira, VP of Engineering at Clear Street. They discuss the importance of innovation and migrating applications and processes with care. Emilio shares insights on the challenges and impact of migrations, especially in the complex world of finance. With his expertise in modern technology and infrastructure, Emilio sheds light on how Clear Street is revolutionizing the industry by rebuilding traditional banking practices using cloud-based solutions. Tune in to learn more about the role of engineering in the prime broker space and the careful approach required for successful migrations. Highlights: 00:02:07 Migrations require careful planning. 00:06:52 Agile testing enables faster innovation. 00:12:09 Testing and comparing systems for data quality during migration. 00:17:21 Deep specialization in the finance industry. Guest Emilio Schapira is VP of Engineering at Clear Street, a fintech prime broker building a completely cloud-native prime brokerage and clearing system designed for a complex, modern global market. Before joining Clear Street, Emilio founded two Google Cloud Platform services, Pub/Sub and IoT Core, and led engineering for Waze Ads & Monetization. Emilio has led teams of 60+ engineers and is a founding member of VideoMining Inc., which uses ML and Computer Vision for passive customer behavior research. He has a master's in Computer Science and Engineering from Penn State University and a bachelor's in Computer Science from Universidad Simon Bolivar in Venezuela. --- Thank you so much for checking out this episode of The Tech Trek, and we would appreciate it if you would take a minute to rate and review us on your favorite podcast player. Want to learn more about us? Head over at https://www.elevano.com Have questions or want to cover specific topics with our future guests? Please message me at https://www.linkedin.com/in/amirbormand (Amir Bormand)

2023-08-08 Weekly News - Episode 201Watch the video version on YouTube at https://youtube.com/live/HJHCDA-UbV8?feature=shareHosts: Eric Peterson - Senior Developer at Ortus Solutions Daniel Garcia - Senior Developer at Ortus Solutions Thanks to our Sponsor - Ortus SolutionsThe makers of ColdBox, CommandBox, ForgeBox, TestBox and all your favorite box-es out there. A few ways  to say thanks back to Ortus Solutions: Like and subscribe to our videos on YouTube.  Help ORTUS reach for the Stars - Star and Fork our Repos Star all of your Github Box Dependencies from CommandBox with https://www.forgebox.io/view/commandbox-github  Subscribe to our Podcast on your Podcast Apps and leave us a review Sign up for a free or paid account on CFCasts, which is releasing new content every week BOXLife store: https://www.ortussolutions.com/about-us/shop Buy Ortus's Books 102 ColdBox HMVC Quick Tips and Tricks on GumRoad (http://gum.co/coldbox-tips) Learn Modern ColdFusion (CFML) in 100+ Minutes - Free online https://modern-cfml.ortusbooks.com/ or buy an EBook or Paper copy https://www.ortussolutions.com/learn/books/coldfusion-in-100-minutes   Patreon Support (Amazing)We have 40 patreons: https://www.patreon.com/ortussolutions. News and AnnouncementsPassing the Baton: Lucee 5.4 and Hibernate ORMAs of Lucee 5.4.1.8, new Lucee builds will no longer bundle the (Lucee) Hibernate extension. This means that if you rely on Hibernate ORM in your CFML application, you will need to manually bundle the Hibernate extension into your Lucee server. Let's read on for more info.The NewsFirst, let's start with the official note from the Lucee 5.4.1.8 Stable Release notes (courtesy of Zac Spitzer):Lucee ORM is no longer being developed or bundled by the Lucee Team, Ortus have forked and taken over the development of ORM for Lucee, see Introducing: The Ortus ORM Extension.It seems that Lucee has made the decision to 1) trim the Lucee installation size by no longer bundling the Hibernate extension with new Lucee installations, and to 2) halt further development on the Lucee Hibernate extension. It is unclear whether "no longer being developed" is referring to new features only, or whether that includes bug fixes and security patches as well.This news means that Micha and the LAS team can focus on the Lucee server platform, bringing you speed and stability, while Ortus provides the Hibernate integration for a powerful database ORM layer.https://www.ortussolutions.com/blog/passing-the-baton-lucee-6-and-hibernate-ormNew Releases and UpdatesColdBox v7.1.0ColdBox 7.1 introduces several new features that expand the capabilities of the framework and facilitate better development practices:Scheduled Tasks DebuggingYou can now add a debug argument to your task definitions, and your console will add tons of debugging for your tasks:`task( name : "My Task", debug : true )`toRedirectTo() MatcherYou can now use this matcher to test relocations in a nice fluent expectation:`expect( event ).toRedirectTo( "main.index" )`REST on{errorType}Exception() ConventionThanks to our very own Gavin Pickin you can now create exception handlers in your REST Handlers that follow the on{type}Exception() convention and you can listen to specific error type exceptions:`function onTypeMismatchException( event, rc, prc )`https://www.ortussolutions.com/blog/coldbox-710-releasedTestBox v5.2.0 and v5.3.0v5.2.0New FeaturesFaster Performance with Updated MixerUtilTESTBOX-375Introduces enhancements to the MixerUtil module, resulting in faster performance during dynamic mixins and enhancing the flexibility of your test suites.More Control with bundlesPattern in TestBox InitTESTBOX-376Adds the bundlesPattern parameter to testbox.system.TestBox's init method. This new addition gives you greater control over defining the pattern for your test bundles, making test organization a breeze.Introducing TestBox ModulesTESTBOX-377Brings a game-changing feature to TestBox - Modules support! Now you can create and utilize modules to extend TestBox's capabilities, opening up endless possibilities for tailored testing workflows. Check out our docs: https://testbox.ortusbooks.com/in-depth/modulesBug FixesQuery Compatibility in ExpectationTESTBOX-346Addresses an issue where using expect(sut).toBeInstanceOf("something")) with a query could cause unexpected behavior. This has been resolved, ensuring a smoother testing experience with query objects.Improved cbstreams FunctionalityTESTBOX-374Fixes issues related to cbstreams outside of ColdBox, ensuring seamless functionality in various environments.ImprovementsEnhanced toBeInstanceOf() HandlingTESTBOX-20Improves the handling of toBeInstanceOf() expectations for Java classes, making it even easier to write precise and robust tests for Java objects.v5.3.0New FeaturestoBeIn() and toBeInWithCase() ExpectationsTESTBOX-379These new expectations allow you to verify the presence of a needle within a string or an array target. With the toBeIn() expectation, you can easily check if the expected needle exists in the target. Additionally, toBeInWithCase() performs a case-sensitive check for the needle in the target. These powerful expectations enhance your testing capabilities and streamline the validation of data within your tests.New Matchers and Assertions for String StartTESTBOX-380With these new matchers and assertions, namely toStartWith(), toStartWithCase(), startsWith(), and startsWithCase(), you can validate whether a string begins with an expected prefix. These matchers come with their appropriate negations, allowing you to easily test and verify the starting points of strings in your application.New Matchers and Assertions for String EndTESTBOX-381TestBox v5.3 introduces powerful matchers for checking the end of strings. The new matchers include toEndWith(), toEndWithCase(), endsWith(), and endsWithCase(). These matchers enable you to confirm the presence of an expected suffix in a given string, making it convenient to test the endings of strings during your test suite executions.Bug FixesonSpecError suiteSpecs CorrectionTESTBOX-378In previous versions, there was a minor issue with onSpecError, where the suiteSpecs attribute was mistakenly referred to as suiteStats. With TestBox v5.3, we have fixed this bug, and the attribute is now correctly recognized as suiteSpecs. This ensures that error reporting and handling in your test suites function as expected, providing you with accurate and helpful feedback during testing.https://www.ortussolutions.com/blog/testbox-v52-release-embracing-performance-and-extensibilityhttps://www.ortussolutions.com/blog/testbox-v53-releaseOrtus Redis Extension v3.0.0We are very excited to bring you another release for our Redis Lucee Extension. This release: Updates the underlying Redis java driver from v2.9.3 to v4.4.3 Added SSL and username support to RedisClusterCache configuration Added username support to RedisCache ( non-cluster ) configuration These enhancements have been made to ensure full compatibility with both standalone Redis implementations, as well as AWS Elasticache configurations and authentication mechanisms.https://www.ortussolutions.com/blog/ortus-redis-extension-v300-releasedLucee Script Runner UpdatedThe Lucee Script Runner has been updated with some additional features:luceeVersionQueryYou can now specify a query string to run with the following syntax to select which version of Lucee you want to run, it overrides `luceeVersion`.CompilePassing in `-Dcompile=true` on the command line or compile: true will compile all the code under specified webrootThis is great for catching any invalid CFML during CI before it hits production, also great for checking your code against the latest 6 snapshot to catch any errors introduced which causes errors with your codebaseWindows Runner support for Github actionsThe `action.yml` has been updated to use Windows syntax for running script-runner. You can see examples in the image extension repo: https://github.com/lucee/extension-image/actionshttps://dev.lucee.org/t/lucee-script-runner-version-query-compile-github-actions-windows-support/12865https://github.com/lucee/script-runnerWebinar / Meetups and WorkshopsICYMI — Hawaii ColdFusion Meetup Group — CF Scheduled Tasks: more than you may know, and shouldSpeaker: Charlie ArehartFriday July 28th, 2023 at 3pm PTIf folks were asked to discuss CF scheduled tasks, I suspect most would feel "there's not much 'to say", but there really is a lot more to working with them simply "setting a given url to run on a given schedule" (did you know it could be a CFC, for instance?).There are both more features than most realize, as well as solutions to common problems people can face when running them, and a lot of myths regarding old limitations that have since been lifted. In this talk, veteran CF troubleshooter Charlie Arehart will address all these and more, starting with a focus on tools and techniques for solving common problems with them, then showing several ways to create them (yes, even more than just cfschedule and the CF Admin UI).He'll then review several features of using tasks that you may have missed—to include distinguishing which few are NOT available in CF Standard.He'll also discuss briefly the underlying quartz open source framework that powers them (and offers still more extensibility), as well as the underlying neo-cron.xml file and tips for protecting that, and he'll even identify ways to control/allow access to managing tasks that may surprise many. He'll conclude with alternatives when the base features don't suit you.https://hawaiicoldfusionusergroup.adobeconnect.com/p6izv4ia43a7/Hawaii ColdFusion Meetup Group — Graph QL & ColdFusionSpeaker: Mark TakataFriday, August 25, 2023 @ 12 PM HAST (Hawaii Standard Time)GraphQL is a query language for APIs and a runtime for fulfilling those queries with your existing data. GraphQL provides a complete and understandable description of the data in your API, gives clients the power to ask for exactly what they need and nothing more, makes it easier to evolve APIs over time, and enables powerful developer tools.GraphQL is a query language for APIs and a runtime for executing those queries with your existing data. It provides a more efficient, powerful, and flexible alternative to REST.In ColdFusion 2023 we are providing a native method of consuming and sending data across GraphQL using GQL. This includes support for fragments, variables, aliases, queries, mutations, subscriptions and more.Also, this talk will go over on why to use Graph QL over REST APIs.https://www.meetup.com/hawaii-coldfusion-meetup-group/events/294631289/Adobe Upcoming EventsAdobe ColdFusion Workshop WEDNESDAY, AUGUST 9, 20239:00 AM EDTOnline EventBrian Sappeyhttps://adobecf-1day-workshop.meetus.adobeevents.com/Join the Adobe ColdFusion Workshop to learn how you and your agency can leverage ColdFusion to create amazing web content. This one-day training will cover all facets of Adobe ColdFusion that developers need to build applications that can run across multiple cloud providers or on-premise.The workshop will explore: The major features in the latest release of Adobe ColdFusion How to use CFML to develop, test, and deploy web applications Adobe ColdFusion constructs and functions How to reuse code in Adobe ColdFusion The Adobe ColdFusion application framework and basic database operations Object-oriented programming and object-relational mapping Basic error handling in Adobe ColdFusion PDF, forms, and spreadsheet support in Adobe ColdFusion  Webinar - Road to Fortuna Series: Exploring the New Google Cloud Platform Features FRIDAY, AUGUST 25, 202310:00 AM PDTOnline EventMark Takatahttps://google-cloud-platform-adobe-coldfusion.meetus.adobeevents.com/ During the Road to Fortuna Series: Exploring the New Google Cloud Platform Features webinar, Mark Takata will explore the new native hooks that Adobe ColdFusion is adding to work with the Google Cloud Platform. He will focus on features related to the GCP FireStore document database, Storage capabilities, and PubSub messaging features, providing attendees with valuable insights into how these features can be leveraged to optimize application development and delivery on the Google Cloud Platform. The session will be highly technical and will provide attendees with practical examples and use cases.CFCasts Content Updateshttps://www.cfcasts.comRecent Releases Into the Box 2023 Videos is available for purchase as an EXCLUSIVE PREMIUM package. https://cfcasts.com/series/itb-2023  Subscribers will get access to premium packages after a 6 month exclusive window. Into the Box Attendees should have their coupon code in the email already!!!! 2023 ForgeBox Module of the Week Series - 1 new Video https://cfcasts.com/series/2023-forgebox-modules-of-the-week  2023 VS Code Hint tip and Trick of the Week Series - 1 new Video https://cfcasts.com/series/2023-vs-code-hint-tip-and-trick-of-the-week  Coming Soon More ForgeBox and VS Code Podcast snippet videos ColdBox Elixir from Eric Getting Started with Inertia.js from Eric Conferences and TrainingAdobe CF Summit WestLas Vegas 2-4th of October.Get your early bird passes now. Session passes @ $199 Professional passes @ $299. First round of speakers has been announced - with some great sessionshttps://cfsummit.adobeevents.com/ STUDENTS can get a free pass if they are enrolled at tertiary level educational institutionsOrtus CF Summit Training - ColdBox 7 Zero to HeroDate: October 4th - 5th, 2023 | Right after Adobe CFSummit, 2023Speakers: Luis Majano & Gavin PickinLocation: Las Vegas, NevadaVenue: Regus - Las Vegas - 3960 Howard Hughes Parkway Paradise #Suite 500 Las Vegas, NV 89169 United StatesTicket Price Early Bird Price: $499 (Available until August 18th, 2023) Regular Price Tickets: $699 25% Discount today: https://www.eventbrite.com/e/659169262007/?discount=modernize Spotlight Less than 2 miles from the Mirage - 30 mins walk Next to Marriot hotel - 2 min walk 1 mile to Top Golf - 20 min walk 5 min walk to Fogo de Chão Brazilian Steakhouse 5 min walk to starbucks 5 min walk to Lo-los chicken and waffles WIN WIN WIN WINhttps://www.eventbrite.com/e/workshop-coldbox-from-zero-to-hero-tickets-659169262007?aff=oddtdtcreator Into the Box LATAMNovember 30th - more details to followUniversity of Business in El Salvador.ITB 2024 Locations: Washington, DC Dates: May 15-17, 2024 More conferencesNeed more conferences, this site has a huge list of conferences for almost any language/community.https://confs.tech/Blogs, Tweets, and Videos of the Week07/26/2023 - Blog - Ben Nadel - Considering UTC And Recording Activity Streak Data In ColdFusionFor as long as I can remember, I've been storing Date/Time values in UTC (Coordinated Universal Time) within my ColdFusion applications. UTC is "the primary time standard by which the world regulates clocks and time" (source). Date/Time values get stored in UTC and then - as needed - translated back into a given user's timezone during the rendering process. This is why, when I added the concept of "workout streaks" in Dig Deep Fitness (my ColdFusion fitness tracker), my initial instinct was to use UTC. Unfortunately, this approach quickly broke down.https://www.bennadel.com/blog/4492-considering-utc-and-recording-activity-streak-data-in-coldfusion.htm07/27/2023 - Tweet X Post(?) - Brad Wood - Automated CommandBox Server TestsI've fully automated the tests in my CommandBox Server Tests repo. Now, with a single Task Runner, I can fire off hundreds of tests across dozens of servers to check for regressions. https://github.com/Ortus-Solutions/commandbox-tests 07/31/2023 - Blog - Ben Nadel - Auto-Saving Form Data In The Background Using The fetch() APIIn Dig Deep Fitness, my ColdFusion fitness tracker, the main gesture of the app is the "Perform Exercise" view. In this view, the user is presented with a series of inputs for resistance weights, reps, and notes. Depending on how fast a user is moving through their workout, they may be on this one view for several minutes without submitting the form back to the ColdFusion server. This "pending data" makes me nervous. As such, I've started auto-saving the form data in the background using JavaScript's fetch() API.https://www.bennadel.com/blog/4494-auto-saving-form-data-in-the-background-using-the-fetch-api.htmBeacons : https://developer.mozilla.org/en-US/docs/Web/API/Beacon_APILocalStorage: https://developer.mozilla.org/en-US/docs/Web/API/Web_Storage_API/Using_the_Web_Storage_API08/02/2023 - Blog - Ben Nadel - My ColdFusion "Controller" Layer Is Just A Bunch Of Switch Statements And CFIncludesThe more experience I get, the more I appreciate using an appropriate amount of complexity when solving a problem. This is a big part of why I love ColdFusion so much: it allows one to easily scale-up in complexity if and when the requirements grow to warrant it. When I'm working on my own, I don't need a robust framework with all the bells-and-whistles. All I need is a simple dependency-injection strategy and a series of CFSwtich and CFInclude statements.https://www.bennadel.com/blog/4497-my-coldfusion-controller-layer-is-just-a-bunch-of-switch-statements-and-cfincludes.htmCFML JobsSeveral positions available on https://www.getcfmljobs.com/Listing over 85 ColdFusion positions from 56 companies across 39 locations in 5 Countries.2 new jobs listed in the last two weeksFull-Time - SIS New ColdFusion C1 - Pune, Maharashtra, IndiaPosted: July 26, 2023https://www.getcfmljobs.com/jobs/index.cfm/india/SIS-New-ColdFusion-C1-at-Pune-Maharashtra/11592Full-Time - ColdFusion Developer - Washington, DC,  United StatesPosted: August 01, 2023https://www.getcfmljobs.com/jobs/index.cfm/united-states/CFDeveloper-Washington-DC/11593Other Job LinksThere is a jobs channel in the CFML slack team, and in the Box team slack now tooForgeBox Module of the WeekColdBox Vite & ColdBox Vite Helpers by Eric PetersonThis module provides a `vite` helper function in your views for loading files generated byVite and the coldbox-vite-plugin in your ColdBox applications.https://www.forgebox.io/view/vite-helpershttps://www.npmjs.com/package/coldbox-vite-pluginVS Code Hint Tips and Tricks of the WeekHeadwindBy Ryan HeybournHeadwind is an opinionated Tailwind CSS class sorter for Visual Studio Code. It enforces consistent ordering of classes by parsing your code and reprinting class tags to follow a given order.Headwind runs on save, will remove duplicate classes and can even sort entire workspaces.https://marketplace.visualstudio.com/items?itemName=heybourn.headwindThank you to all of our Patreon SupportersThese individuals are personally supporting our open source initiatives to ensure the great toolings like CommandBox, ForgeBox, ColdBox,  ContentBox, TestBox and all the other boxes keep getting the continuous development they need, and funds the cloud infrastructure at our community relies on like ForgeBox for our Package Management with CommandBox. You can support us on Patreon here https://www.patreon.com/ortussolutionsDon't forget, we have Annual Memberships, pay for the year and save 10% - great for businesses everyone. Bronze Packages and up, now get a ForgeBox Pro and CFCasts subscriptions as a perk for their Patreon Subscription. All Patreon supporters have a Profile badge on the Community Website All Patreon supporters have their own Private Forum access on the Community Website All Patreon supporters have their own Private Channel access BoxTeam Slack https://community.ortussolutions.com/Top Patreons (amazing) John Wilson - Synaptrix Tomorrows Guides Jordan Clark Gary Knight Giancarlo Gomez  David Belanger   Dan Card Jeffry McGee - Sunstar Media Dean Maunder Kevin Wright Doug Cain  Nolan Erck  Abdul Raheen And many more PatreonsYou can see an up to date list of all sponsors on Ortus Solutions' Websitehttps://ortussolutions.com/about-us/sponsors Thanks everyone!!! ★ Support this podcast on Patreon ★

In this special episode of the podcast, we welcome back a familiar and beloved face, Wade, a close friend of the show. Join us as we catch up with Wade and dive into various topics close to our hearts. We start by reviewing the highly anticipated sci-fi blockbuster, "The Cloned Tyron," discussing its thrilling plot twists and mind-bending special effects. Along the way, we share our differing perspectives on the film's deeper themes, making for a lively and engaging conversation that's sure to captivate movie enthusiasts. Later in the episode, the conversation takes a delicious turn as we discuss our mutual love for Publix subs. Surprisingly, Wade and our host Josh reveal that they have a unique preference for their subs – they are among the few who prefer their subs without any condiments! As they share their reasons for this unconventional choice, laughter ensues, and the banter highlights the beauty of friendship and how it can embrace even the quirkiest preferences. Tune in for a heartwarming and entertaining reunion with Wade, where camaraderie, movie reviews, and sandwich choices come together in an unforgettable podcast experience.

In Hour 3 we talk Pub Subs, Crowder's computer issues, Jalen Ramsey's injury, Headlines, we replay a Best of on Overwhelmed guy at Publix ordering a Pub Sub. Also we talk about people who take forever at the drive thru.

Evidently, the sandwich is a life changing.

In this uproarious episode of the Not Well podcast, hosts Bobby and Jim are celebrating their mind-blowing 200th episode milestone, and they can't believe they made it this far. These two laugh-out-loud funny individuals have been on an absolute tear, recording episodes even in the most outlandish situations like a nuclear holocaust or acid rain. Now, that's some serious dedication!Jim and Bobby dive headfirst into the giggles with their eccentric banter about breast milk (trust us, it's a long story) and sibling preferences (we all have our top picks, right?). They also spill the beans on hilarious anecdotes about their drinking habits and how they handle those dreaded hangovers. When it comes to combating the morning-after blues, mimosas during brunch are their secret weapon. Because, really, who can resist the enchanting fusion of bubbly champagne and tangy orange juice?The hosts get real about relationships, stressing the importance of staying true to oneself while being the ultimate cheerleader for your partner. They play a side-splitting voicemail from a listener grappling with the single life after a long-term relationship. Their witty advice includes personal growth, making new buddies, and even pondering therapy as a way to navigate solo living. Jim tells us about how he hit up various bars, including an electrifying drag king show, and boy, do they have some knee-slapping observations to share. From critiquing jaw-dropping performances to discussing mind-boggling makeup choices, their sharp-witted commentary leaves no stone unturned.Trey table upright, Bobby is about to take you on a hilarious adventure through his travel mishaps. Get ready for seat upgrades gone awry (middle seats, anyone?), encounters with talkative Uber drivers who love cranking up the volume and indulging in lengthy phone conversations. It's a rollercoaster of comedic moments and travel-related blunders that'll have you in stitches.In Atlanta, the fun keeps rolling as Jim reunites with their mom and savors a delectable Pub Sub sandwich that's beyond words. They regale us with tales of their outrageous exploits with family and friends, hitting up bars and unleashing their inner party animals. From sassy encounters to captivating conversations, their time in Atlanta is an absolute riot.Finally, Jim and Bobby spill their secrets for surviving the aftermath of a wild night, with mimosas reigning supreme. They also tantalize us with the idea of a Labor Day trip and the intriguing concept of gay campgrounds. Who knew camping could be such a barrel of laughs?As the episode comes to a close, Bobby shares a hysterical observation about pilots owning up to less-than-stellar landings, and they delve into their fascination with tracking planes on flight maps. Massive thank you to out incredible listeners!!! We love youSupport the showAs always you can write us at nowellpodcast@gmail.com or call us at ‪(614) 721-5336‬ and tell us your Not Wells of the week InstagramTwitterBobby's Only FansHelp us continue to grow and create amazing content, like a live tour or just help fund some new headphones when needed. Any help is appreacited. https://www.buzzsprout.com/510487/subscribe#gaypodcast #podcast #gay #lgbtq #queerpodcast #lgbt #lgbtpodcast #lgbtqpodcast #gaypodcaster #queer#instagay #podcasts #podcasting #gaylife #pride #lesbian #bhfyp #gaycomedy #comedypodcast #comedy #nyc #614 #shesnotdoingsowell #wiltonmanor #notwell

Phoenix core team members Chris McCord and Jason Stiebs join Elixir Wizards Sundi Myint and Owen Bickford the growth of Phoenix and LiveView, the latest updates, and what they're excited to see in the future. They express excitement for the possibilities of machine learning, AI, and distributed systems and how these emerging technologies will enhance the user experience of Elixir and LiveView applications in the next decade. Key Topics Discussed in this Episode: How community contributions and feedback help improve Phoenix LiveView The addition of function components, declarative assigns, HEEx, and streams Why Ecto changesets should be used as "fire and forget" data structures Excitement about machine learning and AI with libraries like NX The possibility of distributed systems and actors in the future Verifying and solving issues in the Phoenix and LiveView issue trackers Why marketing plays a part in the adoption and mindshare of Phoenix How streams provide a primitive for arbitrarily large dynamic lists Elixir VM's ability to scale to millions of connections A creative use of form inputs for associations with dynamic children Links Mentioned in this Episode: Fly Site https://fly.io/ Keynote: The Road To LiveView 1.0 by Chris McCord | ElixirConf EU 2023 (https://youtu.be/FADQAnq0RpA) Keynote: I Was Wrong About LiveView by Jason Stiebs | ElixirConf 2022 (https://youtu.be/INgpJ3eIKZY) Phoenix Site https://www.phoenixframework.org/ Phoenix Github https://github.com/phoenixframework Two-Story, 10-Room Purple Martin House (https://suncatcherstudio.com/uploads/birds/birdhouses/purple-martin-house-plans/images-large/purple-martin-birdhouse-plans-labeled.png) Blog: The Road to 2 Million Websocket Connections in Phoenix (https://phoenixframework.org/blog/the-road-to-2-million-websocket-connections) Raxx Elixir Webserver Interface https://hexdocs.pm/raxx/0.4.1/readme.html Livebook Site https://livebook.dev/ Sundi's 6'x 6' Phoenix painting (https://twitter.com/sundikhin/status/1663930854928728064) Surface on Hex https://hex.pm/packages/surface Axon Deep Learning Framework https://hexdocs.pm/axon/Axon.html Nx Numerical Elixir https://hexdocs.pm/nx/intro-to-nx.html Phoenix PubSub https://hexdocs.pm/phoenix_pubsub/Phoenix.PubSub.html Jason Stiebs on Twitter https://twitter.com/peregrine Jason Stiebs on Mastodon https://merveilles.town/@peregrine Special Guests: Chris McCord and Jason Stiebs.

Welcome to this episode of The Context Podcast where we explore the incredible capabilities of SimpleQ! This week includes our host Martha Zink, along with Corn Walker, Todd Geist, and Mike Perley.Join us as we delve into the intricacies of SimpleQ, explaining its seamless task handling and compatibility with various systems. Discover the advantages of this approach and how it revolutionizes business processes. Additionally, we explore the origins of SimpleQ, discussing the hybrid PubSub and queuing system that gave birth to this remarkable tool. We also shine a spotlight on Otto and its crucial role in accepting webhooks from third-party systems. See how Otto seamlessly integrates with SimpleQ to streamline data flow and enhance communication across different FileMaker apps.Tune in to The Context Podcast and embrace the efficiency of SimpleQ—a game-changer in the world of FileMaker and business process automation. You can also find this episode on Youtube or your favorite podcasting platforms.

Bruno Aziza – Head of Data and Analytics at Google Cloud – has a unique expert perspective on the data industry  through his work with data executives and visionaries while managing a broad portfolio of products at Google including  BigQuery, Dataflow, Dataproc, Looker, Data Studio, PubSub, Composer, Data Fusion, Catalog, Dataform, Dataprep and Dataplex. In this episode, Bruno we dive into  topics such as the development (and disappointment) of Data Mesh, how it relates to Data Products, along with how data leaders can transform their organizations by first looking inward and transforming one's self.We also speak to why Chief Data Officers are navigating from 'reactive analytics' to data products that are driven by real-time. Follow Bruno Aziza on Linkedin, Twitter, and Medium.What's New In Data is a data thought leadership series hosted by John Kutay who leads data and products at Striim. What's New In Data hosts industry practitioners to discuss latest trends, common patterns for real world data patterns, and analytics success stories.

Which member of THEjoeSHOW left a Pub Sub in their car and had it rot?!

Raj Advani is the Senior Director of Product Management here at Salesforce. Raj has held a variety of different roles at the company, beginning with an Engagement Manager when he started 17 years ago. He now owns many of the event driven architectures for Salesforce, including Change Data Capture and Platform Events.  In this episode, we have a conversation with Raj about various integration solutions on the platform. We discuss what Change Data Capture and Platform Events are, the advantages of a Pub/Sub API, and more! Show Highlights: Some of the internal features using Platform Events. Moving toward a bus centric world in Platform Events. The filtering conditions in Change Data Capture. The benefits of event driven architecture. The options for a distinct integrations from Salesforce. How Pub/Sub API plays into the event architecture. Links: Raj on Twitter Raj on LinkedIn Architecture Decision Guides Episode 115: Event Relays with Tyson Read Episode 93: Pub/Sub with Emmett Chan-Ran    

It's the season 10 premiere of the Elixir Wizards podcast! Sundi Myint, Owen Bickford, and Dan Ivovich kick off the season with a spirited conversation about what they hope to see in the future of the Elixir programming language, experiences that inform their predictions, and excitement for this season's lineup of guests. They touch on how Elixir has evolved in the previous ten years and how the range of use cases has expanded beyond web development. The hosts introduce the season 10 theme: The Next Ten Years of Elixir Dan explains his initial hesitation and how he was ultimately won over by the language Owen talks about functional programming and why Elixir piqued his interest Sundi compares Elixir to other languages she's worked with and why she thinks it's more intuitive and readable Sundi talks about her recent experience using Flutter for mobile application development The hosts express excitement about the various ways Elixir is currently being used and its potential for growth The Wizards express interest in hearing from guests this season to gain more perspective They discuss Phoenix, LiveView, documentation, Flutter, Dart, and resources available to the Elixir community, and the benefits of being fluent in different programming languages Owen suggests that Elixir and Phoenix are optimal for projects with limited resources and leaner teams They highlight the importance of building resource-efficient apps that work well on low-powered devices Dan expresses his desire to embrace types more but acknowledges that a first-party typing system is unlikely The speakers discuss how Elixir has made complex tasks more accessible through features like LiveView, Phoenix Presence, WebSockets, Pub/Sub, Nerves, and ML libraries They express excitement about the possibilities for the future of Elixir Links mentioned in this episode: SmartLogic — https://smartlogic.io/ SmartLogic Twitter — https://twitter.com/smartlogic Axon – https://hexdocs.pm/axon/Axon.html Bumblebee – https://hex.pm/packages/bumblebee HEEx – https://hexdocs.pm/phoenixliveview/assigns-eex.html Phoenix LiveView – https://hexdocs.pm/phoenixliveview/Phoenix.LiveView.html Numerical Elixir – https://hexdocs.pm/nx/intro-to-nx.html Hugging Face – https://huggingface.co/docs Flutter – https://docs.flutter.dev/ Dart – https://dart.dev/ Broadway – https://hexdocs.pm/broadway/Broadway.html Phoenix Presence – https://hexdocs.pm/phoenix/Phoenix.Presence.html Nerves – https://hexdocs.pm/nerves/getting-started.html WebSocket – https://hexdocs.pm/web_socket/readme.html

In this episode of season 2, we're talking about Pub/Sub pattern

Warning! this podcast episode is not as boring as it sounds!   While geospatial standards are boring on purpose ... this episode is not .- If you woke up this morning wanting to listen to a boring podcast episode about geospatial standards this is not for you!    Scott Simmons ( OGC's Chief Standards Officer )  https://www.ogc.org/about/team/scott-simmons/ helps us understand what a Geopose is and how it might be used, why we need GeoRSS, and something called SensorThings!     You will also learn about the PubSub standard for the syndication of spatial data and why streaming data is not always the answer.   We also discover what the most boring geospatial standard is and when the shapefile "might" die.    All in all, this is a light-hearted look at a very serious topic and I hope you enjoy it!    What to know more about the Open Geospatial Consortium? this is a good place to start! https://mapscaping.com/podcast/the-open-geospatial-consortium/                

Asynchrone Verarbeitung durch Message Queues: Was ist das und wofür ist das gut?In vielen Applikationen gibt es Bereiche, die einfach etwas Zeit für die Verarbeitung brauchen, aber das klassische Anfrage/Antwort (Request/Response) Verhalten nicht blockieren sollen. Oft werden dafür asynchrone Prozesse verwendet. Durch den Einsatz von Message Queues ergeben sich weitere Vorteile wie u.a. granulare Skalierbarkeit und Unabhängigkeit von einzelnen Programmiersprachen. RabbitMQ ist einer der Platzhirsche im Bereich Open-Source-Message-Broker.In dieser Episode klären wir wofür Message Queues gut sind, bei welchen klassischen Anwendungsfällen diese helfen können, welche Herausforderungen diese Darstellen, wo der Unterschied zu Pub/Sub oder Streams ist und was Redis, Kafka und ZeroMQ damit zu tun hat.Bonus: Warum Software rostet.Feedback (gerne auch als Voice Message)Email: stehtisch@engineeringkiosk.devMastodon: https://podcasts.social/@engkioskTwitter: https://twitter.com/EngKioskWhatsApp +49 15678 136776Gerne behandeln wir auch euer Audio Feedback in einer der nächsten Episoden, einfach Audiodatei per Email oder WhatsApp Voice Message an +49 15678 136776LinksRabbitMQ: https://www.rabbitmq.com/ActiveMQ: https://activemq.apache.org/AMQP: https://www.amqp.org/Jakarta Messaging: https://de.wikipedia.org/wiki/Jakarta_MessagingRed Hat / JBoss AMQ: https://www.redhat.com/de/technologies/jboss-middleware/amqApache Kafka: https://kafka.apache.org/ZeroMQ: https://zeromq.org/Erlang mnesia: https://www.erlang.org/doc/man/mnesia.htmlSprungmarken(00:00:00) Intro(00:00:41) Post-Retouren an der Haustür, Warteschlangen und Reservierungs-Scheduling mit Process Mining(00:05:49) Das heutige Thema: Message Queuing (mit RabbitMQ)(00:07:23) Was sind Message Queues und was sind typische Anwendungsfälle?(00:10:48) Komponenten einer Message Queues und deine Datenbank als Message Queues(00:12:30) Herausforderungen beim Message Queuing: Exactly once delivery(00:15:15) Möglichkeiten durch Message Queuing: Granulare Skalierbarkeit, Micro-Service Kommunikation und Serverless(00:16:56) Was ist RabbitMQ? (Erlang, AMQP)(00:21:53) Advanced Features von Message Queuing-Systemen: Exchanges, Routing, Priority Queues, Time to live (TTL)(00:27:01) Message Acknowledgement + Rejetion und Dead Letter Queues(00:31:11) Ist Amazon SQS oder Google PubSub eine gute Alternative?(00:34:22) Alternative mit Redis: PubSub, Listen und Streams(00:36:18) Wo ist der Unterschied zwischen einer Message Queue und einem Stream?(00:38:51) Kann ich Apache Kafka als Message Queuing System verwenden?(00:40:29) Ist RabbitMQ oder Apache Kafka einfacher zu installieren und zu betreiben?(00:42:56) ZeroMQ(00:44:53) Was spricht gegen RabbitMQ? Operations, idempotente Consumer(00:48:34) Andere Protokolle fürs Message Queuing: MQTT, HTTP und WebSockets(00:49:46) Erfahrung durch die Nutzung in Side Projects und ZusammenfassungHostsWolfgang Gassler (https://mastodon.social/@woolf)Andy Grunwald (https://twitter.com/andygrunwald)Feedback (gerne auch als Voice Message)Email: stehtisch@engineeringkiosk.devMastodon: https://podcasts.social/@engkioskTwitter: https://twitter.com/EngKioskWhatsApp +49 15678 136776

About BrianBrian leads the Google Cloud Product and Industry Marketing team. This team is focused on accelerating the growth of Google Cloud by establishing thought leadership, increasing demand and usage, enabling their sales teams and partners to tell their product stories with excellence, and helping their customers be the best advocates for them.Before joining Google, Brian spent over 25 years in product marketing or engineering in different forms. He started his career at Microsoft and had a very non-traditional path for 20 years. Brian worked in every product division except for cloud. He did marketing, product management, and engineering roles. And, early on, he was the first speech writer for Steve Ballmer and worked on Bill Gates' speeches too. His last role was building up the Microsoft Surface business from scratch as VP of the hardware businesses. After Microsoft, Brian spent a year as CEO at a hardware startup called Doppler Labs, where they made a run at transforming hearing, and then spent two years as VP at Amazon Web Services leading product marketing, developer advocacy, and a bunch more marketing teams.Brian has three kids still at home, Barty, Noli, and Alder, who are all named after trees in different ways. His wife Edie and him met right at the beginning of their first year at Yale University, where Brian studied math, econ, and philosophy and was the captain of the Swim and Dive team his senior year. Edie has a PhD in forestry and runs a sustainability and forestry consulting firm she started, that is aptly named “Three Trees Consulting”. As a family they love the outdoors, tennis, running, and adventures in Brian's 1986 Volkswagen Van, which is his first and only car, that he can't bring himself to get rid of.Links Referenced: Google Cloud: https://cloud.google.com @isforat: https://twitter.com/IsForAt LinkedIn: https://www.linkedin.com/in/brhall/ 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: This episode is brought to us by our friends at Pinecone. They believe that all anyone really wants is to be understood, and that includes your users. AI models combined with the Pinecone vector database let your applications understand and act on what your users want… without making them spell it out. Make your search application find results by meaning instead of just keywords, your personalization system make picks based on relevance instead of just tags, and your security applications match threats by resemblance instead of just regular expressions. Pinecone provides the cloud infrastructure that makes this easy, fast, and scalable. Thanks to my friends at Pinecone for sponsoring this episode. Visit Pinecone.io to understand more.Corey: This episode is brought to you in part by our friends at Veeam. Do you care about backups? Of course you don't. Nobody cares about backups. Stop lying to yourselves! You care about restores, usually right after you didn't care enough about backups. If you're tired of the vulnerabilities, costs, and slow recoveries when using snapshots to restore your data, assuming you even have them at all living in AWS-land, there is an alternative for you. Check out Veeam, that's V-E-E-A-M for secure, zero-fuss AWS backup that won't leave you high and dry when it's time to restore. Stop taking chances with your data. Talk to Veeam. My thanks to them for sponsoring this ridiculous podcast.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. This episode is brought to us by our friends at Google Cloud and, as a part of that, they have given me someone to, basically, harass for the next half hour. Brian Hall is the VP of Product Marketing over at Google Cloud. Brian, welcome back.Brian: Hello, Corey. It's good to be here, and technically, we've given you time to harass me by speaking with me because you never don't have the time to harass me on Twitter and other places, and you're very good at it.Corey: Well, thank you. Again, we first met back when you were doing, effectively, the same role over at AWS. And before that, you spent only 20 years or so at Microsoft. So, you've now worked at all three of the large hyperscale cloud providers. You probably have some interesting perspectives on how the industry has evolved over that time. So, at the time of this recording, it is after Google Next and before re:Invent. There was also a Microsoft event there that I didn't pay much attention to. Where are we as a culture, as an industry, when it comes to cloud?Brian: Well, I'll start with it is amazing how early days it still is. I don't want to be put on my former Amazon cap too much, and I think it'd be pushing it a little bit to say it's complete and total day one with the cloud. But there's no question that there is a ton of evolution still to come. I mean, if you look at it, you can kind of break it into three eras so far. And roll with me here, and happy to take any dissent from you.But there was kind of a first era that was very much led by Amazon. We can call it the VM era or the component era, but being able to get compute on-demand, get nearly unlimited or actually unlimited storage with S3 was just remarkable. And it happened pretty quickly that startups, new tech companies, had to—like, it would be just wild to not start with AWS and actually start ordering servers and all that kind of stuff. And so, I look at that as kind of the first phase. And it was remarkable how long Amazon had a run really as the only player there. And maybe eight years ago—six years ago—we could argue on timeframes, things shifted a little bit because the enterprises, the big companies, and the governments finally realized, “Holy crow. This thing has gotten far enough that it's not just for these startups.”Corey: Yeah. There was a real change. There was an eye-opening moment there where it isn't just, “I want to go and sell things online.” It's, “And I also want to be a bank. Can we do that with you?” And, “Huh.”Brian: My SAP—like I don't know big that darn thing is going to get. Could I put it in your cloud? And, “Oh, by the way, CapEx forecasting stinks. Can you get me out of that?” And so, it became like the traditional IT infrastructure. All of the sudden, the IT guys showed up at the party, which I know is—it sounds fun to me, but that doesn't sound like the best addition to a party for many people. And so essentially, old-school IT infrastructure finally came to the cloud and Microsoft couldn't miss that happening when it did. But it was a major boon for AWS just because of the position that they had already.Corey: And even Google as well. All three of you now are pivoting in a lot of the messaging to talk to the big E enterprises out there. And I've noticed for the last few years, and I'm not entirely alone. When I go to re:Invent, and I look at announcements they're making, sure they have for the serverless stuff and how to run websites and EC2 nonsense. And then they're talking about IOT things and other things that just seem very oriented on a persona I don't understand. Everyone's doing stuff with mainframes now for example. And it feels like, “Oh, those of us who came here for the web services like it says on the name of the company aren't really feeling like it's for us anymore.” It's the problem of trying to be for everyone and pivoting to where the money is going, but Google's done this at least as much as anyone has in recent years. Are those of us who don't have corporate IT-like problems no longer the target market for folks or what's changed?Brian: It's still the target market, so like, you take the corporate IT, they're obviously still moving to the cloud. And there's a ton of opportunity. Just take existing IT spending and see a number over $1 trillion per year, and if you take the run rates of Microsoft, Amazon, Google Cloud, it's certainly over $100 billion, but that means it's still less than ten percent of what is existing IT spending. There are many people that think that existing IT spend number is significantly higher than that. But to your point on what's changing, there's actually a third wave that's happening.So, if the first wave was you start a company. You're a tech company, of course, you start it on AWS or on the Cloud. Second wave is all the IT people, IT departments, the central organizations that run technology for all the people that are not technology people come to the cloud. This third wave is everybody has to become a technology person. If you're a business leader, like you're at a fast-food restaurant and you're responsible for the franchisee relations, before, like, you needed to get an EDI system running or something, and so you told your IT department to figure out.Now, you have to actually think about what apps do we want to provide to our customers. How do I get the right data to my franchisees so that they can make business decisions? How can I automate all that? And you know, whereas before I was a guy wearing a suit or a gal wearing a suit who didn't need to know technology, I now have to. And that's what's changing the most. And it's why the Target Addressable Market—or the TAM as business folk sometimes say—it's really hard to estimate looking forward if every business is really needing to become a technology business in many ways. And it didn't dawn on me, honestly, and you can give me all the ribbing that I probably deserve for this—but it didn't really dawn on me until I came to Google and kept hearing the transformation word, “Digital transformation, digital transformation,” and honestly, having been in software for so long, I didn't really know what digital transformation meant until I started seeing all of these folks, like every company have to become a tech company effectively.Corey: Yeah. And it turns out there aren't enough technologists to go around, so it's very challenging to wind up getting the expertise in-house. It's natural to start looking at, “Well, how do we effectively outsource this?” And well, you can absolutely have a compression algorithm for experience. It's called, “Buying products and services and hiring people who have that experience already baked in either to the product or they show up knowing how to do something because they've done this before.”Brian: That's right. The thing I think we have to—for those of us that come from the technology side, this transformation is scary for the people who all of the sudden have to get tech and be like—Corey, if you or I—actually, you're very artistic, so maybe this wouldn't do it for you—but if I were told, “Hey, Brian, for your livelihood, you now need to incorporate painting,” like…Corey: [laugh]. I can't even write legibly let alone draw or paint. That is not my skill set. [laugh].Brian: I'd be like, “Wait, what? I'm not good at painting. I've never been a painting person, like I'm not creative.” “Okay. Great. Then we're going to fire you, or we're going to bring someone in who can.” Like, that'd be scary. And so, having more services, more people that can help as every company goes through a transition like that—and it's interesting, it's why during Covid, the cloud did really well, and some people kind of said, “Well, it's because they—people didn't want to send their people into their data centers.” No. That wasn't it. It was really because it just forced the change to digital. Like the person to, maybe, batter the analogy a little bit—the person who was previously responsible for all of the physical banks, which are—a bank has, you know, that are retail locations—the branches—they have those in order to service the retail customers.Corey: Yeah.Brian: That person, all of the sudden, had to figure out, “How do I do all that service via phone, via agents, via an app, via our website.” And that person, that entire organization, was forced digital in many ways. And that certainly had a lot of impact on the cloud, too.Corey: Yeah. I think that some wit observed a few years back that Covid has had more impact on your digital transformation than your last ten CIOs combined.Brian: Yeah.Corey: And—yeah, suddenly, you're forcing people into a position where there really is no other safe option. And some of that has unwound but not a lot of it. There's still seem to be those same structures and ability to do things from remote locations then there were before 2020.Brian: Yeah. Since you asked, kind of, where we are in the industry, to bring all of that to an endpoint, now what this means is people are looking for cloud providers, not just to have the primitives, not just to have the IT that they—their central IT needed, but they need people who can help them build the things that will help their business transform. It makes it a fun, new stage, new era, a transformation era for companies like Google to be able to say, “Hey, here's how we build things. Here's what we've learned over a period of time. Here's what we've most importantly learned from other customers, and we want to help be your strategic partner in that transformation.” And like I said, it'd be almost impossible to estimate what the TAM is for that. The real question is how quickly can we help customers and innovate in our Cloud solutions in order to make more of the stuff more powerful and faster to help people build.Corey: I want to say as well that—to be clear—you folks can buy my attention but not my opinion. I will not say things if I do not believe them. That's the way the world works here. But every time I use Google Cloud for something, I am taken aback yet again by the developer experience, how polished it is. And increasingly lately, it's not just that you're offering those low-lying primitives that composed together to build things higher up the stack, you're offering those things as well across a wide variety of different tooling options. And they just tend to all make sense and solve a need rather than requiring me to build it together myself from popsicle sticks.And I can't shake the feeling that that's where the industry is going. I'm going to want someone to sell me an app to do expense reports. I'm not going to want—well, I want a database and a front-end system, and how I wind up storing all the assets on the backend. No. I just want someone to give me something that solves that problem for me. That's what customers across the board are looking for as best I can see.Brian: Well, it certainly expands the number of customers that you can serve. I'll give you an example. We have an AI agent product called Call Center AI which allows you to either build a complete new call center solution, or more often it augments an existing call center platform. And we could sell that on an API call basis or a number of agent seats basis or anything like that. But that's not actually how call center leaders want to buy. Imagine we come in and say, “This many API calls or $4 per seat or per month,” or something like that. There's a whole bunch of work for that call center leader to go figure out, “Well, do I want to do this? Do I not? How should I evaluate it versus others?” It's quite complex. Whereas, if we come in and say, “Hey, we have a deal for you. We will guarantee higher customer satisfaction. We will guarantee higher agent retention. And we will save you money. And we will only charge you some percentage of the amount of money that you're saved.”Corey: It's a compelling pitch.Brian: Which is an easier one for a business decision-maker to decide to take?Corey: It's no contest. I will say it's a little odd that—one thing—since you brought it up, one thing that struck me as a bit strange about Contact Center AI, compared to most of the services I would consider to be Google Cloud, instead of, “Click here to get started,” it's, “Click here to get a demo. Reach out to contact us.” It feels—Brian: Yeah.Corey: —very much like the deals for these things are going to get signed on a golf course.Brian: [laugh]. They—I don't know about signed on a golf course. I do know that there is implementation work that needs to be done in order to build the models because it's the model for the AI, figuring out how your particular customers are served in your particular context that takes the work. And we need to bring in a partner or bring in our expertise to help build that out. But it sounds to me like you're looking to go golfing since you've looked into this situation.Corey: Just like painting, I'm no good at golfing either.Brian: [laugh].Corey: Honestly, it's—it just doesn't have the—the appeal isn't there for me for whatever reason. I smile; I nod; I tend to assume that, “Yeah, that's okay. I'll leave some areas for other people to go exploring in.”Brian: I see. I see.Corey: So, two weeks before Google Cloud Next occurred, you folks wound up canceling Stadia, which had been rumored for a while. People had been predicting it since it was first announced because, “Just wait. They're going to Google Reader it.” And yeah, it was consumer-side, and I do understand that that was not Cloud. But it did raise the specter of—for people to start talking once again about, “Oh, well, Google doesn't have any ability to focus on things long-term. They're going to turn off Cloud soon, too. So, we shouldn't be using it at all.” I do not agree with that assessment.But I want to get your take on it because I do have some challenges with the way that your products and services go to market in some ways. But I don't have the concern that you're going to turn it all off and decide, “Yeah, that was a fun experiment. We're done.” Not with Cloud, not at this point.Brian: Yeah. So, I'd start with at Google Cloud, it is our job to be a trusted enterprise platform. And I can't speak to before I was here. I can't speak to before Thomas Kurian, who's our CEO, was here before. But I can say that we are very, very focused on that. And deprecating products in a surprising way or in a way that doesn't take into account what customers are on it, how can we help those customers is certainly not going to help us do that. And so, we don't do that anymore.Stadia you brought up, and I wasn't part of starting Stadia. I wasn't part of ending Stadia. I honestly don't know anything about Stadia that any average tech-head might not know. But it is a different part of Google. And just like Amazon has deprecated plenty of services and devices and other things in their consumer world—and Microsoft has certainly deprecated many, many, many consumer and other products—like, that's a different model. And I won't say whether it's good, bad, or righteous, or not.But I can say at Google Cloud, we're doing a really good job right now. Can we get better? Of course. Always. We can get better at communicating, engaging customers in advance. But we now have a clean deprecation policy with a set of enterprise APIs that we commit to for stated periods of time. We also—like people should take a look. We're doing ten-year deals with companies like Deutsche Bank. And it's a sign that Google is here to last and Google Cloud in particular. It's also at a market level, just worth recognizing.We are a $27 billion run rate business now. And you earn trust in drips. You lose it in buckets. And we're—we recognize that we need to just keep every single day earning trust. And it's because we've been able to do that—it's part of the reason that we've gotten as large and as successful as we have—and when you get large and successful, you also tend to invest more and make it even more clear that we're going to continue on that path. And so, I'm glad that the market is seeing that we are enterprise-ready and can be trusted much, much more. But we're going to keep earning every single day.Corey: Yeah. I think it's pretty fair to say that you have definitely gotten yourselves into a place where you've done the things that I would've done if I wanted to shore up trust that the platform was not going to go away. Because these ten-year deals are with the kinds of companies that, shall we say, do not embark on signing contracts lightly. They very clearly, have asked you the difficult, pointed questions that I'm basically asking you now as cheap shots. And they ask it in very serious ways through multiple layers of attorneys. And if the answers aren't the right answers, they don't sign the contract. That is pretty clearly how the world works.The fact that companies are willing to move things like core trading systems over to you on a ten-year time horizon, tells me that I can observe whatever I want from the outside, but they have actual existential risk questions tied to what they're doing. And they are in some ways betting their future on your folks. You clearly know what those right answers are and how to articulate them. I think that's the side of things that the world does not get to see or think about very much. Because it is easy to point at all the consumer failings and the hundreds of messaging products that you continually replenish just in order to kill.Brian: [laugh].Corey: It's—like, what is it? The tree of liberty must be watered periodically from time to time, but the blood of patriots? Yeah. The logo of Google must be watered by the blood of canceled messaging products.Brian: Oh, come on. [laugh].Corey: Yeah. I'm going to be really scared if there's an actual, like, Pub/Sub service. I don't know. That counts as messaging, sort of. I don't know.Brian: [laugh]. Well, thank you. Thank you for the recognition of how far we've come in our trust from enterprises and trust from customers.Corey: I think it's the right path. There's also reputational issues, too. Because in the absence of new data, people don't tend to change their opinion on things very easily. And okay, there was a thing I was using. It got turned off. There was a big kerfuffle. That sticks in people's minds. But I've never seen an article about a Google service saying, “Oh, yeah. It hasn't been turned off or materially changed. In fact, it's gotten better with time. And it's just there working reliably.” You're either invisible, or you're getting yelled at.It feels like it's a microcosm of my early career stage of being a systems administrator. I'm either invisible or the mail system's broke, and everyone wants my head. I don't know what the right answer is—Brian: That was about right to me.Corey: —in this thing. Yeah. I don't know what the right answer on these things is, but you're definitely getting it right. I think the enterprise API endeavors that you've gone through over the past year or two are not broadly known. And frankly, you've definitely are ex-AWS because enterprise APIs is a terrible name for what these things are.Brian: [laugh].Corey: I'll let you explain it. Go ahead. And bonus points if you can do it without sounding like a press release. Take it away.Brian: There are a set of APIs that developers and companies should be able to know are going to be supported for the period of time that they need in order to run their applications and truly bet on them. And that's what we've done.Corey: Yeah. It's effectively a commitment that there will not be meaningful deprecations or changes to the API that are breaking changes without significant notice periods.Brian: Correct.Corey: And to be clear, that is exactly what all of the cloud providers have in their enterprise contracts. They're always notice periods around those things. There are always, at least, certain amounts of time and significant breach penalties in the event that, “Yeah, today, I decided that we were just not going to spin up VMs in that same way as we always have before. Sorry. Sucks to be you.” I don't see that happening on the Google Cloud side of the world very often, not like it once did. And again, we do want to talk about reputations.There are at least four services that I'm aware of that AWS has outright deprecated. One, Sumerian has said we're sunsetting the service in public. But on the other end of the spectrum, RDS on VMWare has been completely memory-holed. There's a blog post or two but nothing else remains in any of the AWS stuff, I'm sure, because that's an, “Enterprise-y” service, they wound up having one on one conversations with customers or there would have been a hue and cry. But every cloud provider does, in the fullness of time, turn some things off as they learn from their customers.Brian: Hmm. I hadn't heard anything about AWS Infinidash for a while either.Corey: No, no. It seems to be one of those great services that we made up on the internet one day for fun. And I love that just from a product marketing perspective. I mean, you know way more about that field than I do given that it's your job, and I'm just sitting here in this cheap seats throwing peanuts at you. But I love the idea of customers just come up and make up a product one day in your space and then the storytelling that immediately happens thereafter. Most companies would kill for something like that just because you would expect on some level to learn so much about how your reputation actually works. When there's a platonic ideal of a service that isn't bothered by pesky things like, “It has to exist,” what do people say about it? And how does that work?And I'm sort of surprised there wasn't more engagement from Amazon on that. It always seems like they're scared to say anything. Which brings me to a marketing question I have for you. You and Amazing have similar challenges—you being Google in this context, not you personally—in that your customers take themselves deadly seriously. And as a result, you have to take yourselves with at least that same level of seriousness. You can't go on Twitter and be the Wendy's Twitter account when you're dealing with enterprise buyers of cloud platforms. I'm kind of amazed, and I'd love to know. How can you manage to say anything at all? Because it just seems like you are so constrained, and there's no possible thing you can say that someone won't take issue with. And yes, some of the time, that someone is me.Brian: Well, let's start with going back to Infinidash a little bit. Yes, you identified one interesting thing about that episode, if I can call it an episode. The thing that I tell you though that didn't surprise me is it shows how much of cloud is actually learned from other people, not from the cloud provider itself. I—you're going to be going to re:Invent. You were at Google Cloud Next. Best thing about the industry conferences is not what the provider does. It's the other people that are there that you learn from. The folks that have done something that you've been trying to do and couldn't figure out how to do, and then they explained it to you, just the relationships that you get that help you understand what's going on in this industry that's changing so fast and has so much going on.And so,   And so, that part didn't surprise me. And that gets a little bit to the second part of your—that we're talking about. “How do you say anything?” As long as you're helping a customer say it. As long as you're helping someone who has been a fan of a product and has done interesting things with it say it, that's how you communicate for the most part, putting a megaphone in front of the people who already understand what's going on and helping their voice be heard, which is a lot more fun, honestly, than creating TV ads and banner ads and all of the stuff that a lot of consumer and traditional companies. We get to celebrate our customers and our creators much, much more.Corey: This episode is sponsored in part by our friends at Uptycs, because they believe that many of you are looking to bolster your security posture with CNAPP and XDR solutions. They offer both cloud and endpoint security in a single UI and data model. Listeners can get Uptycs for up to 1,000 assets through the end of 2023 (that is next year) for $1. But this offer is only available for a limited time on UptycsSecretMenu.com. That's U-P-T-Y-C-S Secret Menu dot com.Corey: I think that it's not super well understood by a lot of folks out there that the official documentation that any cloud provider puts out there is kind of a last resort. Or I'm looking for the specific flag to a specific parameter of a specific command. Great. Sure. But what I really want to do whenever I'm googling how to do something—and yes, that—we're going to be googling—welcome. You've successfully owned that space to the point where it's become common parlance. Good work is I want to see what other people had said. I want to find blog posts, ideally recent ones, talking about how to do the thing that I'm trying to do. If I'm trying to do something relatively not that hard or not that uncommon, if I spin up three web servers behind a load-balancer, and I can't find any community references on how to do that thing, either I'm trying to do something absolutely bizarre and I should re-think it, or there is no community/customer base for the product talking about how to do things with it.And I have noticed a borderline Cambrian explosion over the last few years of the Google Cloud community. I'm seeing folks who do not work at Google, and also who have never worked at Google, and sometimes still think they work at Google in some cases. It's not those folks. It is people who are just building things as a customer. And they, in turn, become very passionate advocates for the platform. And they start creating content on these things.Brian: Yeah. We've been blessed to have, not only, the customer base grow, but essentially the passion among that customer base, and we've certainly tried to help building community and catalyzing the community, but it's been fun to watch how our customers' success turns into our success which turns into customer success. And it's interesting, in particular, to see too how much of that passion comes from people seeing that there is another way to do things.It's clear that many people in our industry knew cloud through the lens of Amazon, knew tech in general through the lenses of Microsoft and Oracle and a lot of other companies. And Google, which we try and respect specifically what people are trying to accomplish and how they know how to do it, we also many ways have taken a more opinionated approach, if you will, to say, “Hey, here's how this could be done in a different way.” And when people find something that's unexpectedly different and also delightful, it's more likely that they're going to be strong advocates and share that passion with the world.Corey: It's a virtuous cycle that leads to the continued growth and success of a platform. Something I've been wondering about in the broader sense, is what happens after this? Because if, let's say for the sake of argument, that one of the major cloud providers decided, “Okay. You know, we're going to turn this stuff off. We've decided we don't really want to be in the cloud business.” It turns out that high-margin businesses that wind up turning into cash monsters as soon as you stop investing heavily in growing them, just kind of throw off so much that, “We don't know what to do with. And we're running out of spaces to store it. So, we're getting out of it.” I don't know how that would even be possible at some point. Because given the amount of time and energy some customers take to migrate in, it would be a decade-long project for them to migrate back out again.So, it feels on some level like on the scale of a human lifetime, that we will be seeing the large public cloud providers, in more or less their current form, for the rest of our lives. Is that hopelessly naïve? Am I missing—am I overestimating how little change happens in the sweep of a human lifetime in technology?Brian: Well, I've been in the tech industry for 27 years now. And I've just seen a continual moving up the stack. Where, you know, there are fundamental changes. I think the PC becoming widespread, fundamental change; mobile, certainly becoming primary computing experience—what I know you call a toilet computer, I call my mobile; that's certainly been a change. Cloud has certainly been a change. And so, there are step functions for sure. But in general, what has been happening is things just keep moving up the stack. And as things move up the stack, there are companies that evolve and learn to do that and provide more value and more value to new folks. Like I talked about how businesspeople are leaders in technology now in a way that they never were before. And you need to give them the value in a way that they can understand it, and they can consume it, and they can trust it. And it's going to continue to move in that direction.And so, what happens then as things move up the stack, the abstractions start happening. And so, there are companies that were just major players in the ‘90s, whether it's Novell or Sun Microsystems or—I was actually getting a tour of the Sunnyvale/Mountain View Google Campuses yesterday. And the tour guide said, “This used to be the site of a company that was called Silicon Graphics. They did something around, like, making things for Avatar.” I felt a little aged at that point.But my point is, there are these companies that were amazing in their time. They didn't move up the stack in a way that met the net set of needs. And it's not like that crater the industry or anything, it's just people were able to move off of it and move up. And I do think that's what we'll see happening.Corey: In some cases, it seems to slip below the waterline and become, effectively, plumbing, where everyone uses it, but no one knows who they are or what they do. The Tier 1 backbone providers these days tend to be in that bucket. Sure, some of them have other businesses, like Verizon. People know who Verizon is, but they're one of the major Tier 1 carriers in the United States just of the internet backbone.Brian: That's right. And that doesn't mean it's not still a great business.Corey: Yeah.Brian: It just means it's not front of mind for maybe the problems you're trying to solve or the opportunities we're trying to capture at that point in time.Corey: So, my last question for you goes circling back to Google Cloud Next. You folks announced an awful lot of things. And most of them, from my perspective, were actually pretty decent. What do you think is the most impactful announcement that you made that the industry largely overlooked?Brian: Most impactful that the industry—well, overlooked might be the wrong way to put this. But there's this really interesting thing happening in the cloud world right now where whereas before companies, kind of, chose their primary cloud writ large, today because multi-cloud is actually happening in the vast majority of companies have things in multiple places, people make—are making also the decision of, “What is going to be my strategic data provider?” And I don't mean data in the sense of the actual data and meta-data and the like, but my data cloud.Corey: Mm-hmm.Brian: How do I choose my data cloud specifically? And there's been this amazing profusion of new data companies that do better ETL or ELT, better data cleaning, better packaging for AI, new techniques for scaling up/scaling down at cost. A lot of really interesting stuff happening in the dataspace. But it's also created almost more silos. And so, the most important announcement that we made probably didn't seem like a really big announcement to a lot of people, but it really was about how we're connecting together more of our data cloud with BigQuery, with unstructured and structured data support, with support for data lakes, including new formats, including Iceberg and Delta and Hudi to come how—Looker is increasingly working with BigQuery in order to make it, so that if you put data into Google Cloud, you not only have these super first-class services that you can use, ranging from databases like Spanner to BigQuery to Looker to AI services, like Vertex AI, but it's also now supporting all these different formats so you can bring third-party applications into that one place. And so, at the big cloud events, it's a new service that is the biggest deal. For us, the biggest deal is how this data cloud is coming together in an open way to let you use the tool that you want to use, whether it's from Google or a third party, all by betting on Google's data cloud.Corey: I'm really impressed by how Google is rather clearly thinking about this from the perspective of the data has to be accessible by a bunch of different things, even though it may take wildly different forms. It is making the data more fluid in that it can go to where the customer needs it to be rather than expecting the customer to come to it where it lives. That, I think, is a trend that we have not seen before in this iteration of the tech industry.Brian: I think you got that—you picked that up very well. And to some degree, if you step back and look at it, it maybe shouldn't be that surprising that Google is adept at that. When you think of what Google search is, how YouTube is essentially another search engine producing videos that deliver on what you're asking for, how information is used with Google Maps, with Google Lens, how it is all about taking information and making it as universally accessible and helpful as possible. And if we can do that for the internet's information, why can't we help businesses do it for their business information? And that's a lot of where Google certainly has a unique approach with Google Cloud.Corey: I really want to thank you for being so generous with your time. If people want to learn more about what you're up to, where's the best place for them to find you?Brian: cloud.google.com for Google Cloud information of course. And if it's still running when this podcast goes, @isforat, I-S-F-O-R-A-T, on Twitter.Corey: And we will put links to both of those in the show notes. Thank you so much for you time. I appreciate it.Brian: Thank you, Corey. It's been good talking with you.Corey: Brian Hall, VP of Product Marketing at Google Cloud. 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 insulting angry comment dictating that, “No. Large companies make ten-year-long commitments casually all the time.”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.Announcer: This has been a HumblePod production. Stay humble.

About ChetanChetan Venkatesh is a technology startup veteran focused on distributed data, edge computing, and software products for enterprises and developers. He has 20 years of experience in building primary data storage, databases, and data replication products. Chetan holds a dozen patents in the area of distributed computing and data storage.Chetan is the CEO and Co-Founder of Macrometa – a Global Data Network featuring a Global Data Mesh, Edge Compute, and In-Region Data Protection. Macrometa helps enterprise developers build real-time apps and APIs in minutes – not months.Links Referenced: Macrometa: https://www.macrometa.com Macrometa Developer Week: https://www.macrometa.com/developer-week 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: Forget everything you know about SSH and try Tailscale. Imagine if you didn't need to manage PKI or rotate SSH keys every time someone leaves. That'd be pretty sweet, wouldn't it? With Tailscale SSH, you can do exactly that. Tailscale gives each server and user device a node key to connect to its VPN, and it uses the same node key to authorize and authenticate SSH.Basically you're SSHing the same way you manage access to your app. What's the benefit here? Built in key rotation permissions is code connectivity between any two devices, reduce latency and there's a lot more, but there's a time limit here. You can also ask users to reauthenticate for that extra bit of security. Sounds expensive?Nope, I wish it were. tail scales. Completely free for personal use on up to 20 devices. To learn more, visit snark.cloud/tailscale. Again, that's snark.cloud/tailscaleCorey: Managing shards. Maintenance windows. Overprovisioning. ElastiCache bills. I know, I know. It's a spooky season and you're already shaking. It's time for caching to be simpler. Momento Serverless Cache lets you forget the backend to focus on good code and great user experiences. With true autoscaling and a pay-per-use pricing model, it makes caching easy. No matter your cloud provider, get going for free at gomomento.co/screaming That's GO M-O-M-E-N-T-O dot co slash screamingCorey: Welcome to Screaming in the Cloud. I'm Corey Quinn. Today, this promoted guest episode is brought to us basically so I can ask a question that has been eating at me for a little while. That question is, what is the edge? Because I have a lot of cynical sarcastic answers to it, but that doesn't really help understanding. My guest today is Chetan Venkatesh, CEO and co-founder at Macrometa. Chetan, thank you for joining me.Chetan: It's my pleasure, Corey. You're one of my heroes. I think I've told you this before, so I am absolutely delighted to be here.Corey: Well, thank you. We all need people to sit on the curb and clap as we go by and feel like giant frauds in the process. So let's start with the easy question that sets up the rest of it. Namely, what is Macrometa, and what puts you in a position to be able to speak at all, let alone authoritatively, on what the edge might be?Chetan: I'll answer the second part of your question first, which is, you know, what gives me the authority to even talk about this? Well, for one, I've been trying to solve the same problem for 20 years now, which is build distributed systems that work really fast and can answer questions about data in milliseconds. And my journey's sort of been like the spiral staircase journey, you know, I keep going around in circles, but the view just keeps getting better every time I do one of these things. So I'm on my fourth startup doing distributed data infrastructure, and this time really focused on trying to provide a platform that's the antithesis of the cloud. It's kind of like taking the cloud and flipping it on its head because instead of having a single region application where all your stuff runs in one place, on us-west-1 or us-east-1, what if your apps could run everywhere, like, they could run in hundreds and hundreds of cities around the world, much closer to where your users and devices and most importantly, where interesting things in the real world are happening?And so we started Macrometa about five years back to build a new kind of distributed cloud—let's call the edge—that kind of looks like a CDN, a Content Delivery Network, but really brings very sophisticated platform-level primitives for developers to build applications in a distributed way around primitives for compute, primitives for data, but also some very interesting things that you just can't do in the cloud anymore. So that's Macrometa. And we're doing something with edge computing, which is a big buzzword these days, but I'm sure you'll ask me about that.Corey: It seems to be. Generally speaking, when I look around and companies are talking about edge, it feels almost like it is a redefining of what they already do to use a term that is currently trending and deep in the hype world.Chetan: Yeah. You know, I think humans just being biologically social beings just tend to be herd-like, and so when we see a new trend, we like to slap it on everything we have. We did that 15 years back with cloud, if you remember, you know? Everybody was very busy trying to stick the cloud label on everything that was on-prem. Edge is sort of having that edge-washing moment right now.But I define edge very specifically is very different from the cloud. You know, where the cloud is defined by centralization, i.e., you've got a giant hyperscale data center somewhere far, far away, where typically electricity, real estate, and those things are reasonably cheap, i.e., not in urban centers, where those things tend to be expensive.You know, you have platforms where you run things at scale, it's sort of a your mess for less business in the cloud and somebody else manages that for you. The edge is actually defined by location. And there are three types of edges. The first edge is the CDN edge, which is historically where we've been trying to make things faster with the internet and make the internet scale. So Akamai came about, about 20 years back and created this thing called the CDN that allowed the web to scale. And that was the first killer app for edge, actually. So that's the first location that defines the edge where a lot of the peering happens between different network providers and the on-ramp around the cloud happens.The second edge is the telecom edge. That's actually right next to you in terms of, you know, the logical network topology because every time you do something on your computer, it goes through that telecom layer. And now we have the ability to actually run web services, applications, data, directly from that telecom layer.And then the third edge is—sort of, people have been familiar with this for 30 years. The third edge is your device, just your mobile phone. It's your internet gateway and, you know, things that you carry around in your pocket or sit on your desk, where you have some compute power, but it's very restricted and it only deals with things that are interesting or important to you as a person, not in a broad range. So those are sort of the three things. And it's not the cloud. And these three things are now becoming important as a place for you to build and run enterprise apps.Corey: Something that I think is often overlooked here—and this is sort of a natural consequence of the cloud's own success and the joy that we live in a system that we do where companies are required to always grow and expand and find new markets—historically, for example, when I went to AWS re:Invent, which is a cloud service carnival in the desert that no one in the right mind should ever want to attend but somehow we keep doing, it used to be that, oh, these announcements are generally all aligned with people like me, where I have specific problems and they look a lot like what they're talking about on stage. And now they're talking about things that, from that perspective, seem like Looney Tunes. Like, I'm trying to build Twitter for Pets or something close to it, and I don't understand why there's so much talk about things like industrial IoT and, “Machine learning,” quote-unquote, and other things that just do not seem to align with. I'm trying to build a web service, like it says on the name of a company; what gives?And part of that, I think, is that it's difficult to remember, for most of us—especially me—that what they're coming out with is not your shopping list. Every service is for someone, not every service is for everyone, so figuring out what it is that they're talking about and what those workloads look like, is something that I think is getting lost in translation. And in our defense—collective defense—Amazon is not the best at telling stories to realize that, oh, this is not me they're talking to; I'm going to opt out of this particular thing. You figure it out by getting it wrong first. Does that align with how you see the market going?Chetan: I think so. You know, I think of Amazon Web Services, or even Google, or Azure as sort of Costco and, you know, Sam's Wholesale Club or whatever, right? They cater to a very broad audience and they sell a lot of stuff in bulk and cheap. And you know, so it's sort of a lowest common denominator type of a model. And so emerging applications, and especially emerging needs that enterprises have, don't necessarily get solved in the cloud. You've got to go and build up yourself on sort of the crude primitives that they provide.So okay, go use your bare basic EC2, your S3, and build your own edgy, or whatever, you know, cutting edge thing you want to build over there. And if enough people are doing it, I'm sure Amazon and Google start to pay interest and you know, develop something that makes it easier. So you know, I agree with you, they're not the best at this sort of a thing. The edge is phenomenon also that's orthogonally, and diametrically opposite to the architecture of the cloud and the economics of the cloud.And we do centralization in the cloud in a big way. Everything is in one place; we make giant piles of data in one database or data warehouse slice and dice it, and almost all our computer science is great at doing things in a centralized way. But when you take data and chop it into 50 copies and keep it in 50 different places on Earth, and you have this thing called the internet or the wide area network in the middle, trying to keep all those copies in sync is a nightmare. So you start to deal with some very basic computer science problems like distributed state and how do you build applications that have a consistent view of that distributed state? So you know, there have been attempts to solve these problems for 15, 18 years, but none of those attempts have really cracked the intersection of three things: a way for programmers to do this in a way that doesn't blow their heads with complexity, a way to do this cheaply and effectively enough where you can build real-world applications that serve billions of users concurrently at a cost point that actually is economical and make sense, and third, a way to do this with adequate levels of performance where you don't die waiting for the spinning wheel on your screen to go away.So these are the three problems with edge. And as I said, you know, me and my team, we've been focused on this for a very long while. And me and my co-founder have come from this world and we created a platform very uniquely designed to solve these three problems, the problems of complexity for programmers to build in a distributed environment like this where data sits in hundreds of places around the world and you need a consistent view of that data, being able to operate and modify and replicate that data with consistency guarantees, and then a third one, being able to do that, at high levels of performance, which translates to what we call ultra-low latency, which is human perception. The threshold of human perception, visually, is about 70 milliseconds. Our finest athletes, the best Esports players are about 70 to 80 milliseconds in their twitch, in their ability to twitch when something happens on the screen. The average human is about 100 to 110 milliseconds.So in a second, we can maybe do seven things at rapid rates. You know, that's how fast our brain can process it. Anything that falls below 100 milliseconds—especially if it falls into 50 to 70 milliseconds—appears instantaneous to the human mind and we experience it as magic. And so where edge computing and where my platform comes in is that it literally puts data and applications within 50 milliseconds of 90% of humans and devices on Earth and allows now a whole new set of applications where latency and location and the ability to control those things with really fine-grained capability matters. And we can talk a little more about what those apps are in a bit.Corey: And I think that's probably an interesting place to dive into at the moment because whenever we talk about the idea of new ways of building things that are aimed at decentralization, first, people at this point automatically have a bit of an aversion to, “Wait, are you talking about some of the Web3 nonsense?” It's one of those look around the poker table and see if you can spot the sucker, and if you can't, it's you. Because there are interesting aspects to that entire market, let's be clear, but it also seems to be occluded by so much of the grift and nonsense and spam and the rest that, again, sort of characterize the early internet as well. The idea though, of decentralizing out of the cloud is deeply compelling just to anyone who's really ever had to deal with the egress charges, or even the data transfer charges inside of one of the cloud providers. The counterpoint is it feels that historically, you either get to pay the tax and go all-in on a cloud provider and get all the higher-level niceties, or otherwise, you wind up deciding you're going to have to more or less go back to physical data centers, give or take, and other than the very baseline primitives that you get to work with of VMs and block storage and maybe a load balancer, you're building it all yourself from scratch. It seems like you're positioning this as setting up for a third option. I'd be very interested to hear it.Chetan: Yeah. And a quick comment on decentralization: good; not so sure about the Web3 pieces around it. We tend to talk about computer science and not the ideology of distributing data. There are political reasons, there are ideological reasons around data and sovereignty and individual human rights, and things like that. There are people far smarter than me who should explain that.I fall personally into the Nicholas Weaver school of skepticism about Web3 and blockchain and those types of things. And for readers who are not familiar with Nicholas Weaver, please go online. He teaches at UC Berkeley is just one of the finest minds of our time. And I think he's broken down some very good reasons why we should be skeptical about, sort of, Web3 and, you know, things like that. Anyway, that's a digression.Coming back to what we're talking about, yes, it is a new paradigm, but that's the challenge, which is I don't want to introduce a new paradigm. I want to provide a continuum. So what we've built is a platform that looks and feels very much like Lambdas, and a poly-model database. I hate the word multi. It's a pretty dumb word, so I've started to substitute ‘multi' with ‘poly' everywhere, wherever I can find it.So it's not multi-cloud; it's poly-cloud. And it's not multi-model; it's poly-model. Because what we want is a world where developers have the ability to use the best paradigm for solving problems. And it turns out when we build applications that deal with data, data doesn't just come in one form, it comes in many different forms, it's polymorphic, and so you need a data platform, that's also, you know, polyglot and poly-model to be able to handle that. So that's one part of the problem, which is, you know, we're trying to provide a platform that provides continuity by looking like a key-value store like Redis. It looks like a document database—Corey: Or the best database in the world Route 53 TXT records. But please, keep going.Chetan: Well, we've got that too, so [laugh] you know? And then we've got a streaming graph engine built into it that kind of looks and behaves like a graph database, like Neo4j, for example. And, you know, it's got columnar capabilities as well. So it's sort of a really interesting data platform that is not open-source; it's proprietary because it's designed to solve these problems of being able to distribute data, put it in hundreds of locations, keep it all in sync, but it looks like a conventional NoSQL database. And it speaks PostgreSQL, so if you know PostgreSQL, you can program it, you know, pretty easily.What it's also doing is taking away the responsibility for engineers and developers to understand how to deal with very arcane problems like conflict resolution in data. I made a change in Mumbai; you made a change in Tokyo; who wins? Our systems in the cloud—you know, DynamoDB, and things like that—they have very crude answers for this something called last writer wins. We've done a lot of work to build a protocol that brings you ACID-like consistency in these types of problems and makes it easy to reason with state change when you've got an application that's potentially running in 100 locations and each of those places is modifying the same record, for example.And then the second part of it is it's a converged platform. So it doesn't just provide data; it provides a compute layer that's deeply integrated directly with the data layer itself. So think of it as Lambdas running, like, stored procedures inside the database. That's really what it is. We've built a very, very specialized compute engine that exposes containers in functions as stored procedures directly on the database.And so they run inside the context of the database and so you can build apps in Python, Go, your favorite language; it compiles down into a [unintelligible 00:15:02] kernel that actually runs inside the database among all these different polyglot interfaces that we have. And the third thing that we do is we provide an ability for you to have very fine-grained control on your data. Because today, data's become a political tool; it's become something that nation-states care a lot about.Corey: Oh, do they ever.Chetan: Exactly. And [unintelligible 00:15:24] regulated. So here's the problem. You're an enterprise architect and your application is going to be consumed in 15 countries, there are 13 different frameworks to deal with. What do you do? Well, you spin up 13 different versions, one for each country, and you know, build 13 different teams, and have 13 zero-day attacks and all that kind of craziness, right?Well, data protection is actually one of the most important parts of the edge because, with something like Macrometa, you can build an app once, and we'll provide all the necessary localization for any region processing, data protection with things like tokenization of data so you can exfiltrate data securely without violating potentially PII sensitive data exfiltration laws within countries, things like that, i.e. It's solving some really hard problems by providing an opinionated platform that does these three things. And I'll summarize it as thus, Corey, we can kind of dig into each piece. Our platform is called the Global Data Network. It's not a global database; it's a global data network. It looks like a frickin database, but it's actually a global network available in 175 cities around the world.Corey: The challenge, of course, is where does the data actually live at rest, and—this is why people care about—well, they're two reasons people care about that; one is the data residency locality stuff, which has always, honestly for me, felt a little bit like a bit of a cloud provider shakedown. Yeah, build a data center here or you don't get any of the business of anything that falls under our regulation. The other is, what is the egress cost of that look like? Because yeah, I can build a whole multicenter data store on top of AWS, for example, but minimum, we're talking two cents, a gigabyte of transfer, even with inside of a region in some cases, and many times that externally.Chetan: Yeah, that's the real shakedown: the egress costs [laugh] more than the other example that you talked about over there. But it's a reality of how cloud pricing works and things like that. What we have built is a network that is completely independent of the cloud providers. We're built on top of five different service providers. Some of them are cloud providers, some of them are telecom providers, some of them are CDNs.And so we're building our global data network on top of routes and capacity provided by transfer providers who have different economics than the cloud providers do. So our cost for egress falls somewhere between two and five cents, for example, depending on which edge locations, which countries, and things that you're going to use over there. We've got a pretty generous egress fee where, you know, for certain thresholds, there's no egress charge at all, but over certain thresholds, we start to charge between two to five cents. But even if you were to take it at the higher end of that spectrum, five cents per gigabyte for transfer, the amount of value our platform brings in architecture and reduction in complexity and the ability to build apps that are frankly, mind-boggling—one of my customers is a SaaS company in marketing that uses us to inject offers while people are on their website, you know, browsing. Literally, you hit their website, you do a few things, and then boom, there's a customized offer for them.In banking that's used, for example, you know, you're making your minimum payments on your credit card, but you have a good payment history and you've got a decent credit score, well, let's give you an offer to give you a short-term loan, for example. So those types of new applications, you know, are really at this intersection where you need low latency, you need in-region processing, and you also need to comply with data regulation. So when you building a high-value revenue-generating app like that egress cost, even at five cents, right, tends to be very, very cheap, and the smallest part of you know, the complexity of building them.Corey: One of the things that I think we see a lot of is that the tone of this industry is set by the big players, and they have done a reasonable job, by and large, of making anything that isn't running in their blessed environments, let me be direct, sound kind of shitty, where it's like, “Oh, do you want to be smart and run things in AWS?”—or GCP? Or Azure, I guess—“Or do you want to be foolish and try and build it yourself out of popsicle sticks and twine?” And, yeah, on some level, if I'm trying to treat everything like it's AWS and run a crappy analog version of DynamoDB, for example, I'm not going to have a great experience, but if I also start from a perspective of not using things that are higher up the stack offerings, that experience starts to look a lot more reasonable as we start expanding out. But it still does present to a lot of us as well, we're just going to run things in VM somewhere and treat them just like we did back in 2005. What's changed in that perspective?Chetan: Yeah, you know, I can't talk for others but for us, we provide a high-level Platform-as-a-Service, and that platform, the global data network, has three pieces to it. First piece is—and none of this will translate into anything that AWS or GCP has because this is the edge, Corey, is completely different, right? So the global data network that we have is composed of three technology components. The first one is something that we call the global data mesh. And this is Pub/Sub and event processing on steroids. We have the ability to connect data sources across all kinds of boundaries; you've got some data in Germany and you've got some data in New York. How do you put these things together and get them streaming so that you can start to do interesting things with correlating this data, for example?And you might have to get across not just physical boundaries, like, they're sitting in different systems in different data centers; they might be logical boundaries, like, hey, I need to collaborate with data from my supply chain partner and we need to be able to do something that's dynamic in real-time, you know, to solve a business problem. So the global data mesh is a way to very quickly connect data wherever it might be in legacy systems, in flat files, in streaming databases, in data warehouses, what have you—you know, we have 500-plus types of connectors—but most importantly, it's not just getting the data streaming, it's then turning it into an API and making that data fungible. Because the minute you put an API on it and it's become fungible now that data is actually got a lot of value. And so the data mesh is a way to very quickly connect things up and put an API on it. And that API can now be consumed by front-ends, it can be consumed by other microservices, things like that.Which brings me to the second piece, which is edge compute. So we've built a compute runtime that is Docker compatible, so it runs containers, it's also Lambda compatible, so it runs functions. Let me rephrase that; it's not Lambda-compatible, it's Lambda-like. So no, you can't take your Lambda and dump it on us and it won't just work. You have to do some things to make it work on us.Corey: But so many of those things are so deeply integrated to the ecosystem that they're operating within, and—Chetan: Yeah.Corey: That, on the one hand, is presented by cloud providers as, “Oh, yes. This shows how wonderful these things are.” In practice, talk to customers. “Yeah, we're using it as spackle between the different cloud services that don't talk to one another despite being made by the same company.”Chetan: [laugh] right.Corey: It's fun.Chetan: Yeah. So the second edge compute piece, which allows you now to build microservices that are stateful, i.e., they have data that they interact with locally, and schedule them along with the data on our network of 175 regions around the world. So you can build distributed applications now.Now, your microservice back-end for your banking application or for your HR SaaS application or e-commerce application is not running in us-east-1 and Virginia; it's running literally in 15, 18, 25 cities where your end-users are, potentially. And to take an industrial IoT case, for example, you might be ingesting data from the electricity grid in 15, 18 different cities around the world; you can do all of that locally now. So that's what the edge functions does, it flips the cloud model around because instead of sending data to where the compute is in the cloud, you're actually bringing compute to where the data is originating, or the data is being consumed, such as through a mobile app. So that's the second piece.And the third piece is global data protection, which is hey, now I've got a distributed infrastructure; how do I comply with all the different privacy and regulatory frameworks that are out there? How do I keep data secure in each region? How do I potentially share data between regions in such a way that, you know, I don't break the model of compliance globally and create a billion-dollar headache for my CIO and CEO and CFO, you know? So that's the third piece of capabilities that this provides.All of this is presented as a set of serverless APIs. So you simply plug these APIs into your existing applications. Some of your applications work great in the cloud. Maybe there are just parts of that app that should be on our edge. And that's usually where most customers start; they take a single web service or two that's not doing so great in the cloud because it's too far away; it has data sensitivity, location sensitivity, time sensitivity, and so they use us as a way to just deal with that on the edge.And there are other applications where it's completely what I call edge native, i.e., no dependancy on the cloud comes and runs completely distributed across our network and consumes primarily the edges infrastructure, and just maybe send some data back on the cloud for long-term storage or long-term analytics.Corey: And ingest does remain free. The long-term analytics, of course, means that once that data is there, good luck convincing a customer to move it because that gets really expensive.Chetan: Exactly, exactly. It's a speciation—as I like to say—of the cloud, into a fast tier where interactions happen, i.e., the edge. So systems of record are still in the cloud; we still have our transactional systems over there, our databases, data warehouses.And those are great for historical types of data, as you just mentioned, but for things that are operational in nature, that are interactive in nature, where you really need to deal with them because they're time-sensitive, they're depleting value in seconds or milliseconds, they're location sensitive, there's a lot of noise in the data and you need to get to just those bits of data that actually matter, throw the rest away, for example—which is what you do with a lot of telemetry in cybersecurity, for example, right—those are all the things that require a new kind of a platform, not a system of record, a system of interaction, and that's what the global data network is, the GDN. And these three primitives, the data mesh, Edge compute, and data protection, are the way that our APIs are shaped to help our enterprise customers solve these problems. So put it another way, imagine ten years from now what DynamoDB and global tables with a really fast Lambda and Kinesis with actually Event Processing built directly into Kinesis might be like. That's Macrometa today, available in 175 cities.Corey: This episode is brought to us in part by our friends at Datadog. Datadog is a SaaS monitoring and security platform that enables full-stack observability for modern infrastructure and applications at every scale. Datadog enables teams to see everything: dashboarding, alerting, application performance monitoring, infrastructure monitoring, UX monitoring, security monitoring, dog logos, and log management, in one tightly integrated platform. With 600-plus out-of-the-box integrations with technologies including all major cloud providers, databases, and web servers, Datadog allows you to aggregate all your data into one platform for seamless correlation, allowing teams to troubleshoot and collaborate together in one place, preventing downtime and enhancing performance and reliability. Get started with a free 14-day trial by visiting datadoghq.com/screaminginthecloud, and get a free t-shirt after installing the agent.Corey: I think it's also worth pointing out that it's easy for me to fall into a trap that I wonder if some of our listeners do as well, which is, I live in, basically, downtown San Francisco. I have gigabit internet connectivity here, to the point where when it goes out, it is suspicious and more a little bit frightening because my ISP—Sonic.net—is amazing and deserves every bit of praise that you never hear any ISP ever get. But when I travel, it's a very different experience. When I go to oh, I don't know, the conference center at re:Invent last year and find that the internet is patchy at best, or downtown San Francisco on Verizon today, I discover that the internet is almost non-existent, and suddenly applications that I had grown accustomed to just working suddenly didn't.And there's a lot more people who live far away from these data center regions and tier one backbones directly to same than don't. So I think that there's a lot of mistaken ideas around exactly what the lower bandwidth experience of the internet is today. And that is something that feels inadvertently classist if that make sense. Are these geographically bigoted?Chetan: Yeah. No, I think those two points are very well articulated. I wish I could articulate it that well. But yes, if you can afford 5G, some of those things get better. But again, 5G is not everywhere yet. It will be, but 5G can in many ways democratize at least one part of it, which is provide an overlap network at the edge, where if you left home and you switched networks, on to a wireless, you can still get the same quality of service that you used to getting from Sonic, for example. So I think it can solve some of those things in the future. But the second part of it—what did you call it? What bigoted?Corey: Geographically bigoted. And again, that's maybe a bit of a strong term, but it's easy to forget that you can't get around the speed of light. I would say that the most poignant example of that I had was when I was—in the before times—giving a keynote in Australia. So ah, I know what I'll do, I'll spin up an EC2 instance for development purposes—because that's how I do my development—in Australia. And then I would just pay my provider for cellular access for my iPad and that was great.And I found the internet was slow as molasses for everything I did. Like, how do people even live here? Well, turns out that my provider would backhaul traffic to the United States. So to log into my session, I would wind up having to connect with a local provider, backhaul to the US, then connect back out from there to Australia across the entire Pacific Ocean, talk to the server, get the response, would follow that return path. It's yeah, turns out that doing laps around the world is not the most efficient way of transferring any data whatsoever, let alone in sizable amounts.Chetan: And that's why we decided to call our platform the global data network, Corey. In fact, it's really built inside of sort of a very simple reason is that we have our own network underneath all of this and we stop this whole ping-pong effect of data going around and help create deterministic guarantees around latency, around location, around performance. We're trying to democratize latency and these types of problems in a way that programmers shouldn't have to worry about all this stuff. You write your code, you push publish, it runs on a network, and it all gets there with a guarantee that 95% of all your requests will happen within 50 milliseconds round-trip time, from any device, you know, in these population centers around the world.So yeah, it's a big deal. It's sort of one of our je ne sais quoi pieces in our mission and charter, which is to just democratize latency and access, and sort of get away from this geographical nonsense of, you know, how networks work and it will dynamically switch topology and just make everything slow, you know, very non-deterministic way.Corey: One last topic that I want to ask you about—because I near certain given your position, you will have an opinion on this—what's your take on, I guess, the carbon footprint of clouds these days? Because a lot of people been talking about it; there has been a lot of noise made about, justifiably so. I'm curious to get your take.Chetan: Yeah, you know, it feels like we're in the '30s and the '40s of the carbon movement when it comes to clouds today, right? Maybe there's some early awareness of the problem, but you know, frankly, there's very little we can do than just sort of put a wet finger in the air, compute some carbon offset and plant some trees. I think these are good building blocks; they're not necessarily the best ways to solve this problem, ultimately. But one of the things I care deeply about and you know, my company cares a lot about is helping make developers more aware off what kind of carbon footprint their code tangibly has on the environment. And so we've started two things inside the company. We've started a foundation that we call the Carbon Conscious Computing Consortium—the four C's. We're going to announce that publicly next year, we're going to invite folks to come and join us and be a part of it.The second thing that we're doing is we're building a completely open-source, carbon-conscious computing platform that is built on real data that we're collecting about, to start with, how Macrometa's platform emits carbon in response to different types of things you build on it. So for example, you wrote a query that hits our database and queries, you know, I don't know, 20 billion objects inside of our database. It'll tell you exactly how many micrograms or how many milligrams of carbon—it's an estimate; not exactly. I got to learn to throttle myself down. It's an estimate, you know, you can't really measure these things exactly because the cost of carbon is different in different places, you know, there are different technologies, et cetera.Gives you a good decent estimate, something that reliably tells you, “Hey, you know that query that you have over there, that piece of SQL? That's probably going to do this much of micrograms of carbon at this scale.” You know, if this query was called a million times every hour, this is how much it costs. A million times a day, this is how much it costs and things like that. But the most important thing that I feel passionate about is that when we give developers visibility, they do good things.I mean, when we give them good debugging tools, the code gets better, the code gets faster, the code gets more efficient. And Corey, you're in the business of helping people save money, when we give them good visibility into how much their code costs to run, they make the code more efficient. So we're doing the same thing with carbon, we know there's a cost to run your code, whether it's a function, a container, a query, what have you, every operation has a carbon cost. And we're on a mission to measure that and provide accurate tooling directly in our platform so that along with your debug lines, right, where you've got all these print statements that are spitting up stuff about what's happening there, we can also print out, you know, what did it cost in carbon.And you can set budgets. You can basically say, “Hey, I want my application to consume this much of carbon.” And down the road, we'll have AI and ML models that will help us optimize your code to be able to fit within those carbon budgets. For example. I'm not a big fan of planting—you know, I love planting trees, but don't get me wrong, we live in California and those trees get burned down.And I was reading this heartbreaking story about how we returned back into the atmosphere a giant amount of carbon because the forest reserve that had been planted, you know, that was capturing carbon, you know, essentially got burned down in a forest fire. So, you know, we're trying to just basically say, let's try and reduce the amount of carbon, you know, that we can potentially create by having better tooling.Corey: That would be amazing, and I think it also requires something that I guess acts almost as an exchange where there's a centralized voice that can make sure that, well, one, the provider is being honest, and two, being able to ensure you're doing an apples-to-apples comparison and not just discounting a whole lot of negative externalities. Because, yes, we're talking about carbon released into the environment. Okay, great. What about water effects from what's happening with your data centers are located? That can have significant climate impact as well. It's about trying to avoid the picking and choosing. It's hard, hard problem, but I'm unconvinced that there's anything more critical in the entire ecosystem right now to worry about.Chetan: So as a startup, we care very deeply about starting with the carbon part. And I agree, Corey, it's a multi-dimensional problem; there's lots of tentacles. The hydrocarbon industry goes very deeply into all parts of our lives. I'm a startup, what do I know? I can't solve all of those things, but I wanted to start with the philosophy that if we provide developers with the right tooling, they'll have the right incentives then to write better code. And as we open-source more of what we learn and, you know, our tooling, others will do the same. And I think in ten years, we might have better answers. But someone's got to start somewhere, and this is where we'd like to start.Corey: I really want to thank you for taking as much time as you have for going through what you're up to and how you view the world. If people want to learn more, where's the best place to find you?Chetan: Yes, so two things on that front. Go to www.macrometa.com—M-A-C-R-O-M-E-T-A dot com—and that's our website. And you can come and experience the full power of the platform. We've got a playground where you can come, open an account and build anything you want for free, and you can try and learn. You just can't run it in production because we've got a giant network, as I said, of 175 cities around the world. But there are tiers available for you to purchase and build and run apps. Like I think about 80 different customers, some of the biggest ones in the world, some of the biggest telecom customers, retail, E-Tail customers, [unintelligible 00:34:28] tiny startups are building some interesting things on.And the second thing I want to talk about is November 7th through 11th of 2022, just a couple of weeks—or maybe by the time this recording comes out, a week from now—is developer week at Macrometa. And we're going to be announcing some really interesting new capabilities, some new features like real-time complex event processing with low, ultra-low latency, data connectors, a search feature that allows you to build search directly on top of your applications without needing to spin up a giant Elastic Cloud Search cluster, or providing search locally and regionally so that, you know, you can have search running in 25 cities that are instant to search rather than sending all your search requests back in one location. There's all kinds of very cool things happening over there.And we're also announcing a partnership with the original, the OG of the edge, one of the largest, most impressive, interesting CDN players that has become a partner for us as well. And then we're also announcing some very interesting experimental work where you as a developer can build apps directly on the 5G telecom cloud as well. And then you'll hear from some interesting companies that are building apps that are edge-native, that are impossible to build in the cloud because they take advantage of these three things that we talked about: geography, latency, and data protection in some very, very powerful ways. So you'll hear actual customer case studies from real customers in the flesh, not anonymous BS, no marchitecture. It's a week-long of technical talk by developers, for developers. And so, you know, come and join the fun and let's learn all about the edge together, and let's go build something together that's impossible to do today.Corey: And we will, of course, put links to that in the [show notes 00:36:06]. Thank you so much for being so generous with your time. I appreciate it.Chetan: My pleasure, Corey. Like I said, you're one of my heroes. I've always loved your work. The Snark-as-a-Service is a trillion-dollar market cap company. If you're ever interested in taking that public, I know some investors that I'd happily put you in touch with. But—Corey: Sadly, so many of those investors lack senses of humor.Chetan: [laugh]. That is true. That is true [laugh].Corey: [laugh]. [sigh].Chetan: Well, thank you. Thanks again for having me.Corey: Thank you. Chetan Venkatesh, CEO and co-founder at Macrometa. 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 and insulting comment about why we should build everything on the cloud provider that you work for and then the attempt to challenge Chetan for the title of Edgelord.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.Announcer: This has been a HumblePod production. Stay humble.

What a difference a week makes. Goobie is no longer sitting at the bottom and Melk is no longer on cloud 9. That's okay. Week 5 looks to be very promising because the guys have a special play-caller blowing the whistle. Matt Miller makes his TDs debut. Get into formation, because the pain is coming!

On The Cloud Pod this week, AWS Enterprise Support adds incident detection and response, the announcement of Google Cloud Spanner, and Oracle expands to Spain. Thank you to our sponsor, Foghorn Consulting, which provides top notch cloud and DevOps engineers to the world's most innovative companies. Initiatives stalled because you're having trouble hiring? Foghorn can be burning down your DevOps and Cloud backlogs as soon as next week. Episode Highlights ⏰ AWS Enterprise Support adds incident detection and response ⏰ You can now get a 90-day free trial of Google Cloud Spanner ⏰ Oracle opens its newest cloud infrastructure region in Spain Top Quote

On The Cloud Pod this week, the team discusses why Ryan's yelling all day (hint: he's learning). Plus: Peter misses the all-important cloud earnings, AWS Skill Builder subscriptions are now available, and Google Eventarc connects SaaS platforms.  A big thanks to this week's sponsor, Foghorn Consulting, which provides full-stack cloud solutions with a focus on strategy, planning and execution for enterprises seeking to take advantage of the transformative capabilities of AWS, Google Cloud and Azure. This week's highlights

Stephanie Wong and Brian Dorsey are joined today by fellow Googlers Jaisen Mathai and Sara Ford to hear all about Cloud Functions (2nd gen) and how it differs from the original. Jaisen gives us some background on Cloud Functions and why it was built. Supporting seven languages, this tool allows clients to write a function without worrying about scaling, devops, and a number of other things that are handled by Cloud Functions automatically. Customer feedback led to new features, and that's how the second evolution of Cloud Functions came about. Don't worry, first gen users! This will continue to be available and supported. Features in the 2nd gen fit into three categories: performance, cost, and control. Among other benefits, costs stay low or may even be reduced with some of the new features, larger instances and longer processing times mean better performance, and traffic splitting means better control over projects. Sara details an example illustrating the power of the new concurrency features, and Jaisen helps us understand when Cloud Functions is the right choice for your project and when it's not. Our guests walk us through getting started with Cloud Functions and using the 2nd gen additions. Companies like Lucille Games are using Cloud Functions, and our guests talk more about how specific users are leveraging the new features of the 2nd gen. Jaisen Mathai Jaisen is a product manager for Cloud Functions. He's been at Google for about six years and before joining Google was both a developer and product manager. Sara Ford Sara is a Cloud Developer Advocate focusing on Cloud Functions and enjoys working on serverless. Cool things of the week No pipelines needed. Stream data with Pub/Sub direct to BigQuery blog Cloud IAM Google Cloud blog The Diversity Annual Report is now a BigQuery public dataset blog Interview Cloud Functions site Cloud Functions 2nd gen walkthrough video Cloud Functions version comparison docs Lucille Games: Playing to win with Google Cloud Platform site BigQuery site Cloud Run site Eventarc docs Cloud Shell site GCP Podcast Episode 261: Full Stack Dart with Tony Pujals and Kevin Moore podcast Working with Remote Functions docs Cloud Console site Where should I run my stuff? Choosing compute options video What's something cool you're working on? Stephanie has been working on GCP Support Shorts. Hosts Stephanie Wong and Brian Dorsey

Theodore Blackman Urbit Core Dev & Manage projects at Tlon Arvo Kernel Find him on ~rovnys-ricfer on Urbit What are metapolitics? What is content distribution for Urbit? What is the networking protocol for Urbit? How is Urbiit different from other networking protocols? What is Subscription Reform? What is a Pub-Sub system? What is the Scriname Space?Are there already scalable networking systems? What is the limit on users right now on Urbit? How do analytics work on Urbit? How long have you been programming in Hoon and Knock? What is an overlay OS? If I'm programming something for a Rasberry Pi, does it make it harder or easier?  Why would somebody want a peer-to-peer operating system? What does it mean to have a personal server? Why is it important? What is a root node and a routing node? What is the key to a distributed system? What are the pillars of it?What is transactional networking or persistent networking? Is Port my own server? How does that work? How easy is it to interface with APIs and connect Urbit apps to web apps? What is your favorite Urbit app? Have you used Urtweet? Do you have access to Dallee? Dalton Collective Octupus @_dalton  What is Urbit trying to do? Urbit destroys the need for a server admin (24 minutes) Are there any hardware wallets that can keep my Urbit planets? Ledger What is the PKI (Urbit ID system)? Azimuth What is the world going to look like in ten years when/if Urbit is much larger? What are autonomous digital communities? Bridge.urbit.org (33 minutes) What is the intersection between Crypto and Urbit? What is the software supply chain (47 minutes)? What are your thoughts on Holochain? ~Datnutpollen What is a categorization theorist?

Full Description / Show Notes Steren and Corey talk about how Google Cloud Run got its name (00:49) Corey talks about his experiences using Google Cloud (2:42) Corey and Steven discuss Google Cloud's cloud run custom domains (10:01) Steren talks about Cloud Run's high developer satisfaction and scalability (15:54) Corey and Steven talk about Cloud Run releases at Google I/O (23:21) Steren discusses the majority of developer and customer interest in Google's cloud product (25:33) Steren talks about his 20% projects around sustainability (29:00) About SterenSteren is a Senior Product Manager at Google Cloud. He is part of the serverless team, leading Cloud Run. He is also working on sustainability, leading the Google Cloud Carbon Footprint product.Steren is an engineer from École Centrale (France). Prior to joining Google, he was CTO of a startup building connected objects and multi device solutions.Links Referenced: Google Cloud Run: https://cloud.run sheets-url-shortener: https://github.com/ahmetb/sheets-url-shortener snark.cloud/run: https://snark.cloud/run Twitter: https://twitter.com/steren 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. I'm joined today by Steren Giannini, who is a senior product manager at Google Cloud, specifically on something called Google Cloud Run. Steren, thank you for joining me today.Steren: Thanks for inviting me, Corey.Corey: So, I want to start at the very beginning of, “Oh, a cloud service. What are we going to call it?” “Well, let's put the word cloud in it.” “Okay, great. Now, it is cloud, so we have to give it a vague and unassuming name. What does it do?” “It runs things.” “Genius. Let's break and go for work.” Now, it's easy to imagine that you spent all of 30 seconds on a name, but it never works that way. How easy was it to get to Cloud Run as a name for the service?Steren: [laugh]. Such a good question because originally it was not named Cloud Run at all. The original name was Google Serverless Engine. But a few people know that because they've been helping us since the beginning, but originally it was Google Serverless Engine. Nobody liked the name internally, and I think at one point, we wondered, “Hey, can we drop the engine structure and let's just think about the name. And what does this thing do?” “It runs things.”We already have Cloud Build. Well, wouldn't it be great to have Cloud Run to pair with Cloud Build so that after you've built your containers, you can run them? And that's how we ended up with this very simple Cloud Run, which today seems so obvious, but it took us a long time to get to that name, and we actually had a lot of renaming to do because we were about to ship with Google Serverless Engine.Corey: That seems like a very interesting last-minute change because it's not just a find and replace at that point, it's—Steren: No.Corey: —“Well, okay, if we call it Cloud Run, which can also be a verb or a noun, depending, is that going to change the meaning of some sentences?” And just doing a find and replace without a proofread pass as well, well, that's how you wind up with funny things on Twitter.Steren: API endpoints needed to be changed, adding weeks of delays to the launch. That is why we—you know, [laugh] announced in 2018 and publicly launched in 2019.Corey: I've been doing a fair bit of work in cloud for a while, and I wound up going down a very interesting path. So, the first native Google Cloud service—not things like WP Engine that ride on top of GCP—but my first native Google Cloud Service was done in service of this podcast, and it is built on Google Cloud Run. I don't think I've told you part of this story yet, but it's one of the reasons I reached out to invite you onto the show. Let me set the stage here with a little bit of backstory that might explain what the hell I'm talking about.As listeners of this show are probably aware, we have sponsors whom we love and adore. In the early days of this show, they would say, “Great, we want to tell people about our product”—which is the point of a sponsorship—“And then send them to a URL.” “Great. What's the URL?” And they would give me something that was three layers deep, then with a bunch of UTM tracking parameters at the end.And it's, “You do realize that no one is going to be sitting there typing all of that into a web browser?” At best, you're going to get three words or so. So, I built myself a URL redirector, snark.cloud. I can wind up redirecting things in there anywhere it needs to go.And for a long time, I did this on top of S3 and then put CloudFront in front of it. And this was all well and good until, you know, things happened in the fullness of time. And now holy crap, I have an operations team involved in things, and maybe I shouldn't be the only person that knows how to work on all of these bits and bobs. So, it was time to come up with something that had a business user-friendly interface that had some level of security, so I don't wind up automatically building out a spam redirect service for anything that wants to, and it needs to be something that's easy to work with. So, I went on an exploration.So, at first it showed that there were—like, I have an article out that I've spoken about before that there are, “17 Ways to Run Containers on AWS,” and then I wrote the sequel, “17 More Ways to Run Containers on AWS.” And I'm keeping a list, I'm almost to the third installation of that series, which is awful. So, great. There's got to be some ways to build some URL redirect stuff with an interface that has an admin panel. And I spent three days on this trying a bunch of different things, and some were running on deprecated versions of Node that wouldn't build properly and others were just such complex nonsense things that had got really bad. I was starting to consider something like just paying for Bitly or whatnot and making it someone else's problem.And then I stumbled upon something on GitHub that really was probably one of the formative things that changed my opinion of Google Cloud for the better. And within half an hour of discovering this thing, it was up and running. I did the entire thing, start to finish, from my iPad in a web browser, and it just worked. It was written by—let me make sure I get his name correct; you know, messing up someone's name is a great way to say that we don't care about them—Ahmet Balkan used to work at Google Cloud; now he's over at Twitter. And he has something up on GitHub that is just absolutely phenomenal about this, called sheets-url-shortener.And this is going to sound wild, but stick with me. The interface is simply a Google Sheet, where you have one column that has the shorthand slug—for example, run; if you go to snark.cloud/run, it will redirect to Google Cloud Run's website. And the second column is where you want it to go. The end.And whenever that gets updated, there's of course some caching issues, which means it can take up to five seconds from finishing that before it will actually work across the entire internet. And as best I can tell, that is fundamentally magic. But what made it particularly useful and magic, from my perspective, was how easy it was to get up and running. There was none of this oh, but then you have to integrate it with Google Sheets and that's a whole ‘nother team so there's no way you're going to be able to figure that out from our Docs. Go talk to them and then come back in the day.They were the get started, click here to proceed. It just worked. And it really brought back some of the magic of cloud for me in a way that I hadn't seen in quite a while. So, all which is to say, amazing service, I continue to use it for all of these sponsored links, and I am still waiting for you folks to bill me, but it fits comfortably in the free tier because it turns out that I don't have hundreds of thousands of people typing it in every week.Steren: I'm glad it went well. And you know, we measure tasks success for Cloud Run. And we do know that most new users are able to deploy their apps very quickly. And that was the case for you. Just so you know, we've put a lot of effort to make sure it was true, and I'll be glad to tell you more about all that.But for that particular service, yes, I suppose Ahmet—who I really enjoyed working with on Cloud Run, he was really helpful designing Cloud Run with us—has open-sourced this side project. And basically, you might even have clicked on a deploy to Cloud Run button on GitHub, right, to deploy it?Corey: That is exactly what I did and it somehow just worked and—Steren: Exactly.Corey: And it knew, even logging into the Google Cloud Console because it understands who I am because I use Google Docs and things, I'm already logged in. None of this, “Oh, which one of these 85 credential sets is it going to be?” Like certain other clouds. It was, “Oh, wow. Wait, cloud can be easy and fun? When did that happen?”Steren: So, what has happened when you click that deploy to Google Cloud button, basically, the GitHub repository was built into a container with Cloud Build and then was deployed to Cloud Run. And once on Cloud Run, well, hopefully, you have forgotten about it because that's what we do, right? We—give us your code, in a container if you know containers if you don't just—we support, you know, many popular languages, and we know how to build them, so don't worry about that. And then we run it. And as you said, when there is low traffic or no traffic, it scales to zero.When there is low traffic, you're likely going to stay under the generous free tier. And if you have more traffic for, you know, Screaming in the Cloud suddenly becoming a high destination URL redirects, well, Cloud Run will scale the number of instances of this container to be able to handle the load. Cloud Run scales automatically and very well, but only—as always—charging you when you are processing some requests.Corey: I had to fork and make a couple of changes myself after I wound up doing some testing. The first was to make the entire thing case insensitive, which is—you know, makes obvious sense. And the other was to change the permanent redirect to a temporary redirect because believe it or not, in the fullness of time, sometimes sponsors want to change the landing page in different ways for different campaigns and that's fine by me. I just wanted to make sure people's browser cache didn't remember it into perpetuity. But it was easy enough to run—that was back in the early days of my exploring Go, which I've been doing this quarter—and in the couple of months this thing has been running it has been effectively flawless.It's set it; it's forget it. The only challenges I had with it are it was a little opaque getting a custom domain set up that—which is still in beta, to be clear—and I've heard some horror stories of people saying it got wedged. In my case, no, I deployed it and I started refreshing it and suddenly, it start throwing an SSL error. And it's like, “Oh, that's not good, but I'm going to break my own lifestyle here and be patient for ten minutes.” And sure enough, it cleared itself and everything started working. And that was the last time I had to think about any of this. And it just worked.Steren: So first, Cloud Run is HTTPS only. Why? Because it's 2020, right? It's 2022, but—Corey: [laugh].Steren: —it's launched in 2020. And so basically, we have made a decision that let's just not accept HTTP traffic; it's only HTTPS. As a consequence, we need to provision a cert for your custom domain. That is something that can take some time. And as you said, we keep it in beta or in preview because we are not yet satisfied with the experience or even the performance of Cloud Run custom domains, so we are actively working on fixing that with a different approach. So, expect some changes, hopefully, this year.Corey: I will say it does take a few seconds when people go to a snark.cloud URL for it to finish resolving, and it feels on some level like it's almost like a cold start problem. But subsequent visits, the same thing also feel a little on the slow and pokey side. And I don't know if that's just me being wildly impatient, if there's an optimization opportunity, or if that's just inherent to the platform that is not under current significant load.Steren: So, it depends. If the Cloud Run service has scaled down to zero, well of course, your service will need to be started. But what we do know, if it's a small Go binary, like something that you mentioned, it should really take less than, let's say, 500 milliseconds to go from zero to one of your container instance. Latency can also be due to the way the code is running. If it occurred is fetching things from Google Sheets at every startup, that is something that could add to the startup latency.So, I would need to take a look, but in general, we are not spinning up a virtual machine anytime we need to scale horizontally. Like, our infrastructure is a multi-tenant, rapidly scalable infrastructure that can materialize a container in literally 300 milliseconds. The rest of the latency comes from what does the container do at startup time?Corey: Yeah, I just ran a quick test of putting time in front of a curl command. It looks like it took 4.83 seconds. So, enough to be perceptive. But again, for just a quick redirect, it's generally not the end of the world and there's probably something I'm doing that is interesting and odd. Again, I did not invite you on the show to file a—Steren: [laugh].Corey: Bug report. Let's be very clear here.Steren: Seems on the very high end of startup latencies. I mean, I would definitely expect under the second. We should deep-dive into the code to take a look. And by the way, building stuff on top of spreadsheets. I've done that a ton in my previous lives as a CTO of a startup because well, that's the best administration interface, right? You just have a CRUD UI—Corey: [unintelligible 00:12:29] world and all business users understand it. If people in Microsoft decided they were going to change Microsoft Excel interface, even a bit, they would revert the change before noon of the same day after an army of business users grabbed pitchforks and torches and marched on their headquarters. It's one of those things that is how the world runs; it is the world's most common IDE. And it's great, but I still think of databases through the lens of thinking about it as a spreadsheet as my default approach to things. I also think of databases as DNS, but that's neither here nor there.Steren: You know, if you have maybe 100 redirects, that's totally fine. And by the way, the beauty of Cloud Run in a spreadsheet, as you mentioned is that Cloud Run services run with a certain identity. And this identity, you can grant it permissions. And in that case, what I would recommend if you haven't done so yet, is to give an identity to your Cloud Run service that has the permission to read that particular spreadsheet. And how you do that you invite the email of the service account as a reader of your spreadsheet, and that's probably what you did.Corey: The click button to the workflow on Google Cloud automatically did that—Steren: Oh, wow.Corey: —and taught me how to do it. “Here's the thing that look at. The end.” It was a flawless user-onboarding experience.Steren: Very nicely done. But indeed, you know, there is this built-in security which is the principle of minimal permission, like each of your Cloud Run service should basically only be able to read and write to the backing resources that they should. And by default, we give you a service account which has a lot of permissions, but our recommendation is to narrow those permissions to basically only look at the cloud storage buckets that the service is supposed to look at. And the same for a spreadsheet.Corey: Yes, on some level, I feel like I'm going to write an analysis of my own security approach. It would be titled, “My God, It's Full Of Stars” as I look at the IAM policies of everything that I've configured. The idea of least privilege is great. What I like about this approach is that it made it easy to do it so I don't have to worry about it. At one point, I want to go back and wind up instrumenting it a bit further, just so I can wind up getting aggregate numbers of all right, how many times if someone visited this particular link? It'll be good to know.And I don't know… if I have to change permissions to do that yet, but that's okay. It's the best kind of problem: future Corey. So, we'll deal with that when the time comes. But across the board, this has just been a phenomenal experience and it's clear that when you were building Google Cloud Run, you understood the assignment. Because I was looking for people saying negative things about it and by and large, all of its seem to come from a perspective of, “Well, this isn't going to be the most cost-effective or best way to run something that is hyperscale, globe-spanning.”It's yes, that's the thing that Kubernetes was originally built to run and for some godforsaken reason people run their blog on it instead now. Okay. For something that is small, scales to zero, and has long periods where no one is visiting it, great, this is a terrific answer and there's absolutely nothing wrong with that. It's clear that you understood who you were aiming at, and the migration strategy to something that is a bit more, I want to say robust, but let's be clear what I mean when I'm saying that if you want something that's a little bit more impressive on your SRE resume as you're trying a multi-year project to get hired by Google or pretend you got hired by Google, yeah, you can migrate to something else in a relatively straightforward way. But that this is up, running, and works without having to think about it, and that is no small thing.Steren: So, there are two things to say here. The first is yes, indeed, we know we have high developer satisfaction. You know, we measure this—in Google Cloud, you might have seen those small satisfaction surveys popping up sometimes on the user interface, and you know, we are above 90% satisfaction score. We hire third parties to help us understand how usable and what satisfaction score would users get out of Cloud Run, and we are constantly getting very, very good results, in absolute but also compared to the competition.Now, the other thing that you said is that, you know, Cloud Run is for small things, and here while it is definitely something that allows you to be productive, something that strives for simplicity, but it also scales a lot. And contrary to other systems, you do not have any pre-provisioning to make. So, we have done demos where we go from zero to 10,000 container instances in ten seconds because of the infrastructure on which Cloud Run runs, which is fully managed and multi-tenant, we can offer you this scale on demand. And many of our biggest customers have actually not switched to something like Kubernetes after starting with Cloud Run because they value the low maintenance, the no infrastructure management that Cloud Run brings them.So, we have like Ikea, ecobee… for example ecobee, you know, the smart thermostats are using Cloud Run to ingest events from the thermostat. I think Ikea is using Cloud Run more and more for more of their websites. You know, those companies scale, right? This is not, like, scale to zero hobby project. This is actually production e-commerce and connected smart objects production systems that have made the choice of being on a fully-managed platform in order to reduce their operational overhead.[midroll 00:17:54]Corey: Let me be clear. When I say scale—I think we might be talking past each other on a small point here. When I say scale, I'm talking less about oh tens or hundreds of thousands of containers running concurrently. I'm talking in a more complicated way of, okay, now we have a whole bunch of different microservices talking to one another and affinity as far as location to each other for data transfer reasons. And as you start beginning to service discovery style areas of things, where we build a really complicated applications because we hired engineers and failed to properly supervise them, and that type of convoluted complex architecture.That's where it feels like Cloud Run increasingly, as you move in that direction, starts to look a little bit less like the tool of choice. Which is fine, I want to be clear on that point. The sense that I've gotten of it is a great way to get started, it's a great way to continue running a thing you don't have to think about because you have a day job that isn't infrastructure management. And it is clear to—as your needs change—to either remain with the service or pivot to a very close service without a whole lot of retooling, which is key. There's not much of a lock-in story to this, which I love.Steren: That was one of the key principles when we started to design Cloud Run was, you know, we realized the industry had agreed that the container image was the standard for the deployment artifact of software. And so, we just made the early choice of focusing on deploying containers. Of course, we are helping users build those containers, you know, we have things called build packs, we can continuously deploy from GitHub, but at the end of the day, the thing that gets auto-scaled on Cloud Run is a container. And that enables portability.As you said. You can literally run the same container, nothing proprietary in it, I want to be clear. Like, you're just listening on a port for some incoming requests. Those requests can be HTTP requests, events, you know, we have products that can push events to Cloud Run like Eventarc or Pub/Sub. And this same container, you can run it on your local machine, you can run it on Kubernetes, you can run it on another cloud. You're not locked in, in terms of API of the compute.We even went even above and beyond by having the Cloud Run API looks like a Kubernetes API. I think that was an extra effort that we made. I'm not sure people care that much, but if you look at the Cloud Run API, it is actually exactly looking like Kubernetes, Even if there is no Kubernetes at all under the hood; we just made it for portability. Because we wanted to address this concern of serverless which was lock-in. Like, when you use a Function as a Service product, you are worried that the architecture that you are going to develop around this product is going to be only working in this particular cloud provider, and you're not in control of the language, the version that this provider has decided to offer you, you're not in control of more of the complexity that can come as you want to scan this code, as you want to move this code between staging and production or test this code.So, containers are really helping with that. So, I think we made the right choice of this new artifact that to build Cloud Run around the container artifact. And you know, at the time when we launched, it was a little bit controversial because back in the day, you know, 2018, 2019, serverless really meant Functions as a Service. So, when we launched, we little bit redefined serverless. And we basically said serverless containers. Which at the time were two worlds that in the same sentence were incompatible. Like, many people, including internally, had concerns around—Corey: Oh, the serverless versus container war was a big thing for a while. Everyone was on a different side of that divide. It's… containers are effectively increasingly—and I know, I'll get email for this, and I don't even slightly care, they're a packaging format—Steren: Exactly.Corey: —where it solves the problem of how do I build this thing to deploy on Debian instances? And Ubuntu instances, and other instances, God forbid, Windows somewhere, you throw a container over the wall. The end. Its DevOps is about breaking down the walls between Dev and Ops. That's why containers are here to make them silos that don't have to talk to each other.Steren: A container image is a glorified zip file. Literally. You have a set of layers with files in them, and basically, we decided to adopt that artifact standard, but not the perceived complexity that existed at the time around containers. And so, we basically merged containers with serverless to make something as easy to use as a Function as a Service product but with the power of bringing your own container. And today, we are seeing—you mentioned, what kind of architecture would you use Cloud Run for?So, I would say now there are three big buckets. The obvious one is anything that is a website or an API, serving public internet traffic, like your URL redirect service, right? This is, you have an API, takes a request and returns a response. It can be a REST API, GraphQL API. We recently added support for WebSockets, which is pretty unique for a service offering to support natively WebSockets.So, what I mean natively is, my client can open a socket connection—a bi-directional socket connection—with a given instance, for up to one hour. This is pretty unique for something that is as fully managed as Cloud Run.Corey: Right. As we're recording this, we are just coming off of Google I/O, and there were a number of announcements around Cloud Run that were touching it because of, you know, strange marketing issues. I only found out that Google I/O was a thing and featured cloud stuff via Twitter at the time it was happening. What did you folks release around Cloud Run?Steren: Good question, actually. Part of the Google I/O Developer keynote, I pitched a story around how Cloud Run helps developers, and the I/O team liked the story, so we decided to include that story as part of the live developer keynote. So, on stage, we announced Cloud Run jobs. So now, I talked to you about Cloud Run services, which can be used to expose an API, but also to do, like, private microservice-to-microservice communication—because cloud services don't have to be public—and in that case, we support GRPC and, you know, a very strong security mechanism where only Service A can invoke Service B, for example, but Cloud Run jobs are about non-request-driven containers. So, today—I mean, before Google I/O a few days ago, the only requirement that we imposed on your container image was that it started to listen for requests, or events, or GRPC—Corey: Web requests—Steren: Exactly—Corey: It speaks [unintelligible 00:24:35] you want as long as it's HTTP. Yes.Steren: That was the only requirement we asked you to have on your container image. And now we've changed that. Now, if you have a container that basically starts and executes to completion, you can deploy it on a Cloud Run job. So, you will use Cloud Run jobs for, like, daily batch jobs. And you have the same infrastructure, so on-demand, you can go from zero to, I think for now, the maximum is a hundred tasks in parallel, for—of course, you can run many tasks in sequence, but in parallel, you can go from zero to a hundred, right away to run your daily batch job, daily admin job, data processing.But this is more in the batch mode than in streaming mode. If you would like to use a more, like, streaming data processing, than a Cloud Run service would still be the best fit because you can literally push events to it, and it will auto-scale to handle any number of events that it receives.Corey: Do you find that the majority of customers are using Cloud Run for one-off jobs that barely will get more than a single container, like my thing, or do you find that they're doing massively parallel jobs? Where's the lion's share of developer and customer interest?Steren: It's both actually. We have both individual developers, small startups—which really value the scale to zero and pay per use model of Cloud Run. Your URL redirect service probably is staying below the free tier, and there are many, many, many users in your case. But at the same time, we have big, big, big customers who value the on-demand scalability of Cloud Run. And for these customers, of course, they will probably very likely not scale to zero, but they value the fact that—you know, we have a media company who uses Cloud Run for TV streaming, and when there is a soccer game somewhere in the world, they have a big spike of usage of requests coming in to their Cloud Run service, and here they can trust the rapid scaling of Cloud Run so they don't have to pre-provision things in advance to be able to serve that sudden traffic spike.But for those customers, Cloud Run is priced in a way so that if you know that you're going to consume a lot of Cloud Run CPU and memory, you can purchase Committed Use Discounts, which will lower your bill overall because you know you are going to spend one dollar per hour on Cloud Run, well purchase a Committed Use Discount because you will only spend 83 cents instead of one dollar. And also, Cloud Run and comes with two pricing model, one which is the default, which is the request-based pricing model, which is basically you only have CPU allocated to your container instances if you are processing at least one request. But as a consequence of that, you are not paying outside of the processing of those requests. Those containers might stay up for you, one, ready to receive new requests, but you're not paying for them. And so, that is—you know, your URL redirect service is probably in that mode where yes when you haven't used it for a while, it will scale down to zero, but if you send one request to it, it will serve that request and then it will stay up for a while until it decides to scale down. But you the user only pays when you are processing these specific requests, a little bit like a Function as a Service product.Corey: Scales to zero is one of the fundamental tenets of serverless that I think that companies calling something serverless, but it always charges you per hour anyway. Yeah, that doesn't work. Storage, let's be clear, is a separate matter entirely. I'm talking about compute. Even if your workflow doesn't scale down to zero ever as a workload, that's fine, but if the workload does, you don't get to keep charging me for it.Steren: Exactly. And so, in that other mode where you decide to always have CPU allocated to your Cloud Run container instances, then you pay for the entire lifecycle of this container instances. You still benefit from the auto-scaling of Cloud Run, but you will pay for the lifecycle and in that case, the price points are lower because you pay for a longer period of time. But that's more the price model that those bigger customers will take because at their scale, they basically always receive requests, so they already to pay always, basically.Corey: I really want to thank you for taking the time to chat with me. Before you go, one last question that we'll be using as a teaser for the next episode that we record together. It seems like this is a full-time job being the product manager on Cloud Run, but no Google, contrary to popular opinion, does in fact, still support 20% projects. What's yours?Steren: So, I've been looking to work on Cloud Run since it was a prototype, and you know, for a long time, we've been iterating privately on Cloud Run, launching it, seeing it grow, seeing it adopted, it's great. It's my full-time job. But on Fridays, I still find the time to have a 20% project, which also had quite a bit of impact. And I work on some sustainability efforts for Google Cloud. And notably, we've released two things last year.The first one is that we are sharing some carbon characteristics of Google Cloud regions. So, if you have seen those small leaves in the Cloud Console next to the regions that are emitting the less carbon, that's something that I helped bring to life. And the second one, which is something quite big, is we are helping customers report and reduce their gross carbon emissions of their Google Cloud usage by providing an out of the box reporting tool called Google Cloud Carbon Footprint. So, that's something that I was able to bootstrap with a team a little bit on the side of my Cloud Run project, but I was very glad to see it launched by our CEO at the last Cloud Next Conference. And now it is a fully-funded project, so we are very glad that we are able to help our customers better meet their sustainability goals themselves.Corey: And we will be talking about it significantly on the next episode. We're giving a teaser, not telling the whole story.Steren: [laugh].Corey: I really want to thank you for being as generous with your time as you are. If people want to learn more, where can they find you?Steren: Well, if they want to learn more about Cloud Run, we talked about how simple was that name. It was obviously not simple to find this simple name, but the domain is https://cloud.run.Corey: We will also accept snark.cloud/run, I will take credit for that service, too.Steren: [laugh]. Exactly.Corey: There we are.Steren: And then, people can find me on Twitter at @steren, S-T-E-R-E-N. I'll be happy—I'm always happy to help developers get started or answer questions about Cloud Run. And, yeah, thank you for having me. As I said, you successfully deployed something in just a few minutes to Cloud Run. I would encourage the audience to—Corey: In spite of myself. I know, I'm as surprised as anyone.Steren: [laugh].Corey: The only snag I really hit was the fact that I was riding shotgun when we picked up my daughter from school and went through a dead zone. It's like, why is this thing not loading in the Google Cloud Console? Yeah, fix the cell network in my area, please.Steren: I'm impressed that you did all of that from an iPad. But yeah, to the audience give Cloud Run the try. You can really get started connecting your GitHub repository or deploy your favorite container image. And we've worked very hard to ensure that usability was here, and we know we have pretty strong usability scores. Because that was a lot of work to simplicity, and product excellence and developer experience is a lot of work to get right, and we are very proud of what we've achieved with Cloud Run and proud to see that the developer community has been very supportive and likes this product.Corey: I'm a big fan of what you've built. And well, of course, it links to all of that in the show notes. I just want to thank you again for being so generous with your time. And thanks again for building something that I think in many ways showcases the best of what Google Cloud has to offer.Steren: Thanks for the invite.Corey: We'll talk again soon. Steren Giannini is a senior product manager at Google Cloud, on Cloud Run. 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. If it's on YouTube, put the thumbs up and the subscribe buttons as well, but in the event that you hated it also include an angry comment explaining why your 20% project is being a shithead on the internet.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.Announcer: This has been a HumblePod production. Stay humble.

Kaslin Fields and Mark Mirchandani learn how GKE manages their releases and how customers can take advantage of the GKE release channels for smooth transitions. Guests Abdelfettah Sghiouar and Kobi Magnezi of the Google Cloud GKE team are here to explain. With releases every four months or so, Kobi tells us that Kubernetes requires two pieces to be managed with each release: the control plane and the nodes. Both are managed for the customer in GKE. The new addition of release channels allows flexibility with release updating so customers can adjust to their specific project needs. Each channel offers a different updating mix and speed, and clients choose the channel that's right for their project. The idea for release channels isn't a new one, Kobi explains. In fact, Google's frequent project releases, while keeping things secure and running well, also can be customized by choosing from an assortment of channels in other Google offerings like Chrome. Our guests talk us through the process of releasing through channels and how each release marinates in the Rapid channel to be sure the version is supported and secure before being pushed to customers through other channels. We hear how release channels differ from no-channel releases, the benefits of specialized channels, and recommendations for customers as far as which channels to use with different development environments. Abdel describes real-world use cases for the Rapid, Regular, and Stable channels, the Surge Upgrade feature, and how GKE notifications with Pub/Sub helps in the updating process. Kobi talks about maintenance and exclusion windows to help customers further customize when and how their projects will update. Kobi and Abdel wrap up with a discussion of the future of GKE release channels. Kobi Magnezi Kobi is the Product Manager for GKE at Google Cloud. Abdelfettah Sghiouar Abdel is a Cloud Dev Advocate with a focus on Cloud native, GKE, and Service Mesh technologies. Cool things of the week GKE Essentials videos KubeCon EU 2023 site KubeCon Call for Proposals site Kubernetes 1.24: Stargazer site GCP Podcast Episode 292: Pulumi and Kubernetes Releases with Kat Cosgrove podcast Optimize and scale your startup on Google Cloud: Introducing the Build Series blog Interview Kubernetes site GKE site Autoscaling with GKE: Overview and pods video GKE release schedule dcos Release channels docs Upgrade-scope maintenance windows docs Configure cluster notifications for third-party services docs Cluster notifications docs Pub/Sub site Agones site What's something cool you're working on? Kaslin is working on KubeCon and new episodes of GKE Essentials. Hosts Mark Mirchandani and Kaslin Fields

Eric Sullivan joins the mix to discuss Project Severus. He started out with greeting carts and it grew into a way of sharing and keeping up on contact information. He dives into how it works and then into the technical details of how he build it. This is an interesting discussion about the architecture and design of the system. Sponsors Top End Devs (https://topenddevs.com/) Coaching | Top End Devs (https://topenddevs.com/coaching) Links Severus (https://getseverus.com/) Severus - Initial MVP Demo (https://www.youtube.com/watch?v=JetDW221ajo) Using Ecto.Multi and Phoenix.PubSub to update Phoenix Liveview (https://intever.co/blog/ecto-liveview-pubsub) Picks Adi- Creative Projects for Rust Programmers (https://amzn.to/3xLiL1C) Allen- Phoenix LiveView Free Course | The Pragmatic Studio (https://pragmaticstudio.com/phoenix-liveview) Allen- Nature Calls Calendar 2022 (https://amzn.to/3MoFTXT) Eric- Belgian Malinois Eric- Horizon Forbidden West - Wikipedia (https://en.wikipedia.org/wiki/Horizon_Forbidden_West) Sascha- Stand with Ukraine Bundle (https://www.humblebundle.com/stand-with-ukraine-bundle) Sascha- Bundle for Ukraine by Necrosoft Games and 736 others - itch.io (https://itch.io/b/1316/bundle-for-ukraine) Special Guest: Eric Sullivan.

SponsorsAudible - get a free audiobook from Audible with no strings attached at https://workingcode.dev/audibleThis week, Carol talks to us about how her Support team manages communication with their customers. And, how she'd love to find an easy way for one Support engineer to know that another Support engineer is currently working on a given ticket. She's been exploring the use of WebSockets and "presence channels" as a means to provide feedback within the Support platform. And, more generally, she's been looking into the concept of Publish and Subscribe (often referred to as Pub/Sub) as a means to push information from one service to another. We talk a lot about Pusher - a fully-managed WebSocket SaaS offering; and, consider other techniques that might be helpful.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.