Podcasts about Graviton

What is string theory, really? Why does it need extra dimensions? Neil deGrasse Tyson and comedian Chuck Nice welcome theoretical physicist and mathematician Lara Anderson to guide us through string theory, higher dimensions, and finding a unifying theory of everything.NOTE: StarTalk+ Patrons can listen to this entire episode commercial-free here: https://startalkmedia.com/show/consider-a-spherical-cow-with-lara-anderson/Thanks to our Patrons Rachel Burns, GTH, Ali Al-Mubarak, Tinashe Munyaradzi Majada Duma, Lester Hairston, Shelbi Frowein, Daryl Sheppard, Carlos Fernandez, Bryan Skelton, SHONE JOE, Beverly Jo, Dr. Rob Bryan, Mark Swehla Jr, Jake, Jake, Parvaneh Alavi, Caleb Rohrer, Cryosminitar, Joe Oggier, A Tedla, Chris Crisco, Olga, Colby Hyde, Trevor Morrison, Elizabeth P, Adam Haynes, ice age, craig henry, McKenna Lineback, Emily Martinez, Laura V Pagliaro, Tactalpotato750, Raymond Hal Bonnin II, Vladlen Kogan, Matthias Sabourin, Allan Watson, Jimmy Rose, Joe DiRosa, Cal Mathison, Lex Hayes, Quince Poston, Kathleen OBrien, Ryan Enright, Mahi, and Thomas S. for supporting us this week. Subscribe to SiriusXM Podcasts+ to listen to new episodes of StarTalk Radio ad-free and a whole week early.Start a free trial now on Apple Podcasts or by visiting siriusxm.com/podcastsplus.

Wednesday 3-26-25 Show #1129: Lil Shawn joins us tonight and we talk about janky fair rides and Jeff goes viral.

This week we have brand new guest Tim Schneider from Germany! Tim is an incredibly talented Leagues of Votann player who was the highest point scorer of the event at the Pyra Cup in Poland.In part 1 of the show we review his list and how it operates, and then in part 2 we go through the actual play by plays of all of Tim's games.Part two of this show is for our patrons. You can subscribe and get access at patreon.com/aow40kDon't forget to join our discord as well when you become a patron!Pyra Cup NationsTim Schneider++++++++++++++++++++++++++++++++++++++++++++++++ FACTION KEYWORD: Xenos - Leagues of Votann+ DETACHMENT: Oathband+ TOTAL ARMY POINTS: 1990pts++ WARLORD: Char1: Brôkhyr Iron-master+ ENHANCEMENT: Appraising Glare (on Char1: Brôkhyr Iron-master)+ NUMBER OF UNITS: 14+ SECONDARY: - Bring It Down: (3x2) + (2x4) - Assassination: 2 Characters+++++++++++++++++++++++++++++++++++++++++++++++CHARACTERChar1: 5x Brôkhyr Iron-master (85 pts)• 1x Brôkhyr Iron-master Warlord1 with Graviton hammer, Graviton rifle• 3x E-COG1 with Autoch-pattern bolt pistol, Close combat weapon1 with Plasma torch1 with Manipulator arms• 1x Ironkyn Assistant1 with Close combat weapon, Las-beam cutterEnhancement: Appraising Glare (+20 pts)Char2: 1x Einhyr Champion (60 pts)1 with Autoch-pattern combi-bolter, Darkstar axe• Weavefield crest (edited)[2:04 AM]BATTLELINE10x Hearthkyn Warriors (100 pts)• 9x Hearthkyn Warrior4 with Autoch-pattern bolt pistol, Close combat weapon, Autoch-pattern bolter1 with Autoch-pattern bolt pistol, Close combat weapon, Autoch-pattern bolter• Pan spectral scanner1 with Autoch-pattern bolt pistol, Close combat weapon, Autoch-pattern bolter• Medipack1 with Autoch-pattern bolt pistol, Close combat weapon, Autoch-pattern bolter• Comms array1 with Autoch-pattern bolt pistol, Close combat weapon, HYLas auto rifle*1 with Autoch-pattern bolt pistol, Close combat weapon, HYLas rotary cannon*• 1x Theyn1 with Close combat weapon, Etacarn plasma pistol, Kin melee weapon• Weavefield crest10x Hearthkyn Warriors (100 pts)• 9x Hearthkyn Warrior4 with Autoch-pattern bolt pistol, Close combat weapon, Autoch-pattern bolter1 with Autoch-pattern bolt pistol, Close combat weapon, Autoch-pattern bolter• Pan spectral scanner1 with Autoch-pattern bolt pistol, Close combat weapon, Autoch-pattern bolter• Medipack1 with Autoch-pattern bolt pistol, Close combat weapon, Autoch-pattern bolter• Comms array1 with Autoch-pattern bolt pistol, Close combat weapon, HYLas auto rifle*1 with Autoch-pattern bolt pistol, Close combat weapon, HYLas rotary cannon*• 1x Theyn1 with Close combat weapon, Etacarn plasma pistol, Kin melee weapon• Weavefield crest[2:05 AM]OTHER DATASHEETS10x Cthonian Beserks (200 pts)• 10x Beserk8 with Concussion maul2 with Mole grenade launcher, Concussion maul10x Cthonian Beserks (200 pts)• 10x Beserk8 with Concussion maul2 with Mole grenade launcher, Concussion maul10x Hernkyn Yaegirs (90 pts)• 10x Hernkyn Yaegir8 with Close combat weapon, Bolt revolver and plasma knife1 with APM launcher, Close combat weapon1 with Close combat weapon, Magna-coil rifle6x Hernkyn Pioneers (180 pts)• 6x Hernkyn Pioneer1 with Bolt revolver, Bolt shotgun, Magna-coil autocannon, Plasma knife1 with Bolt revolver, Bolt shotgun, Magna-coil autocannon, Plasma knife• Comms array2 with Bolt revolver, Bolt shotgun, HYLas rotary cannon, Magna-coil autocannon, Plasma knife1 with Bolt revolver, Bolt shotgun, Magna-coil autocannon, Plasma knife• Pan-spectral scanner1 with Bolt revolver, Bolt shotgun, Magna-coil autocannon, Plasma knife• Rollbar searchlight6x Hernkyn Pioneers (180 pts)• 6x Hernkyn Pioneer1 with Bolt revolver, Bolt shotgun, Magna-coil autocannon, Plasma knife1 with Bolt revolver, Bolt shotgun, Magna-coil autocannon, Plasma knife• Comms array2 with Bolt revolver, Bolt shotgun, HYLas rotary cannon, Magna-coil autocannon, Plasma knife1 with Bolt revolver, Bolt shotgun, Magna-coil autocannon, Plasma knife• Pan-spectral scanner1 with Bolt revolver, Bolt shotgun, Magna-coil autocannon, Plasma knife• Rollbar searchlight1x Hekaton Land Fortress (225 pts)1 with Armoured wheels, MATR autocannon, SP heavy conversion beamer, 2x Twin bolt cannon• Pan spectral scanner1x Hekaton Land Fortress (225 pts)1 with Armoured wheels, MATR autocannon, SP heavy conversion beamer, 2x Twin bolt cannon• Pan spectral scanner1x Sagitaur (115 pts)1 with Armoured wheels, Twin bolt cannon, HYLas beam cannon1x Sagitaur (115 pts)1 with Armoured wheels, Twin bolt cannon, HYLas beam cannon1x Sagitaur (115 pts)1 with Armoured wheels, Twin bolt cannon, HYLas beam cannon

This week we have returning guest and Art of War coach Brian Jones! Brian is fresh off a first place finish at the Cherokee Open Super Major where he used his latest and greatest Imperial Knight army to go undefeated after 8 grueling rounds.In part 1 of the show we review his list and how it operates, and then in part 2 we go through the actual play by plays of all of Brian's games.Part two of this show is for our patrons. You can subscribe and get access at patreon.com/aow40kDon't forget to join our discord as well when you become a patron!2 big sisters (1995 Points)Imperial KnightsNoble LanceStrike Force (2000 Points)CHARACTERSCanis Rex (450 Points)• 1x Chainbreaker las-impulsor• 1x Chainbreaker multi-laser• 1x Freedom's HandCerastus Knight Atrapos (450 Points)• Warlord• 1x Atrapos lascutter• 1x Graviton singularity cannon• Enhancements: Mysterious GuardianBATTLELINEArmiger Helverin (130 Points)• 2x Armiger autocannon• 1x Armoured feet• 1x Questoris heavy stubberArmiger Warglaive (140 Points)• 1x Questoris heavy stubber• 1x Reaper chain-cleaver• 1x Thermal spearArmiger Warglaive (140 Points)• 1x Questoris heavy stubber• 1x Reaper chain-cleaver• 1x Thermal spearArmiger Warglaive (140 Points)• 1x Questoris heavy stubber• 1x Reaper chain-cleaver• 1x Thermal spearALLIED UNITSCallidus Assassin (100 Points)• 1x Neural shredder• 1x Phase sword and poison bladesSisters of Battle Immolator (115 Points)• 1x Armoured tracks• 1x Heavy bolter• 1x Hunter-killer missile• 1x Immolation flamersSisters of Battle Immolator (115 Points)• 1x Armoured tracks• 1x Heavy bolter• 1x Hunter-killer missile• 1x Immolation flamersSisters of Battle Squad (115 Points)• 1x Sister Superior◦ 1x Bolt pistol◦ 1x Close combat weapon◦ 1x Condemnor boltgun◦ 1x Power weapon• 9x Battle Sister◦ 9x Bolt pistol◦ 7x Boltgun◦ 9x Close combat weapon◦ 1x Meltagun◦ 1x Multi-melta◦ 1x Simulacrum ImperialisSubductor Squad (100 Points)• 1x Proctor-Subductor◦ 1x Arbites shotpistol◦ 1x Nuncio-acquila◦ 1x Shock maul• 9x Subductor◦ 9x Arbites shotpistol◦ 9x Shock maul• 1x Cyber-mastiff◦ 1x Mechanical bite

Send us a textIn this chat, Frank, Stephen, and Anthony share their thoughts on how cloud computing and AI have evolved from 2024 to 2025. They discuss the growth in the GPU market and how views on cloud versus on-premises solutions have changed. They also talk about the quality and performance of AI models and consider the environmental impact of AI. The group highlights the need for specialized AI models and the efficiency of the hardware used in AI applications. They wrap up with some insights into future trends in cloud instances and pricing.In their chat, the speakers look at how AMD and Intel processors perform. They also discuss the future of ARM and Graviton technologies. Finally, they touch on the shifting world of cloud computing. They examine the competition among major cloud providers, such as AWS and Microsoft. They also highlight how important it is to be transparent in cloud operations, especially when comparing European and American providers. Here are the key takeaways.The GPU market saw a significant increase in providers in 2024.Many organisations are reconsidering their cloud strategies due to pricing and privacy concerns over AI.AI adoption is still in its early stages for many companies.Quality of AI models has plateaued, with a few major players dominating the market.Training models in the cloud may not be the best solution for everyone.Specialised AI models are becoming increasingly important.The environmental impact of AI and cloud computing is a growing concern.Efficiency in hardware usage is crucial for AI applications.Transparency in cloud provider operations varies significantly between vendors.The cloud market is stabilizing, with slower growth rates observed.Energy consumption and cost are critical factors.Benchmarking is essential for understanding cloud performance.The competitive landscape among cloud providers is shifting, with pricing diverging.

Through case studies of Graviton implementation and GPU integration, Justin Fitzhugh, Snowflake's VP of Engineering, demonstrates how cloud-native architecture combined with strategic partnerships can drive technical innovation and build business value.Topics Include:Cloud engineering and AWS partnershipTraditional databases had fixed hardware ratios for compute/storageSnowflake built cloud-native with separated storage and computeCompany has never owned physical infrastructureApplications must be cloud-optimized to leverage elastic scalingSnowflake uses credit system for customer billingCredits loosely based on compute resources providedCompany maintains cloud-agnostic approach across providersInitially aimed for identical pricing across cloud providersNow allows price variation while maintaining consistent experienceConsumption-based revenue model ties to actual usagePerformance improvements can actually decrease revenueCompany tracked ARM's move to data centersInitially skeptical of Graviton performance claimsPorting to ARM required complete pipeline reconstructionDiscovered floating point rounding differences between architecturesAmazon partnership crucial for library optimizationGraviton migration took two years instead of oneAchieved 25% performance gain with 20% cost reductionTeam requested thousands of GPUs within two monthsGPU infrastructure was new territory for SnowflakeNeeded flexible pricing for uncertain future needsSigned three to five-year contracts with flexibilityTeam pivoted from building to fine-tuning modelsPartnership allowed adaptation to business changesEmphasizes importance of leveraging provider expertiseRecommends early engagement with cloud providersBuild relationships before infrastructure needs ariseMaintain personal connections with provider executivesParticipants:Justin Fitzhugh – VP of Engineering, SnowflakeSee how Amazon Web Services gives you the freedom to migrate, innovate, and scale your software company at https://aws.amazon/isv/

How much more physics is out there to be discovered? Neil deGrasse Tyson sits down with physicist, professor, and rockstar Brian Cox, to discuss everything from the Higgs boson, life beyond our planet, and the fundamental forces that guide our universe.NOTE: StarTalk+ Patrons can listen to this entire episode commercial-free here: https://startalkmedia.com/show/our-world-of-particles-with-brian-cox/Thanks to our Patrons Anthony Sclafani, Alejandro Arriola-Flores, Brian Christensen, Allen Baker, Atlanta Gamer, Nigel Gandy, Gene, Lisa Mettler, Daniel Johansson, Sunny Malhotra, Omar Marcelino, yoyodave, Mo TheRain, William Wilson, ChrissyK, David, Prabakar Venkataraman, PiaThanos22, BlackPiano, Radak Bence, Obaid Mohammadi, the1eagleman1, Scott Openlander, Brandon Micucci, Anastasios Kotoros, Thomas Ha, Phillip Thompson, Bojemo, Kenan Brooks, jmamblat@duck.com, TartarXO, Trinnie Schley, Davidson Zetrenne, and William Kramer for supporting us this week. Subscribe to SiriusXM Podcasts+ on Apple Podcasts to listen to new episodes ad-free and a whole week early.

Dans cet épisode, Seb et Arthur discutent de la technologie Graviton d'AWS, en explorant son évolution, ses avantages et les défis liés à la migration. Ils se penchent sur les atouts de l'architecture ARM, les stratégies d'optimisation des performances et des cas d'usage concrets, en soulignant l'importance de comprendre la technologie sous-jacente pour une mise en œuvre efficace.

At Amazon's reInvent conference the company unveiled a range of AI-centric innovations. AWS CEO Matt Garman highlighted the transformative potential of generative AI across various industries, introducing Amazon Bedrock, which aims to streamline model training and reduce costs. The new Nova family of foundation models, including Nova Micro, Nova Lite, and Nova Premier, was also announced, showcasing AWS's commitment to enhancing AI capabilities. Additionally, updates to Q-Business, AWS's AI assistant, promise seamless integration with over 40 enterprise tools, enhancing workflow efficiency.The episode also delves into AWS's hardware advancements, particularly the Graviton processor, which offers significant improvements in price performance and energy efficiency. New instances featuring NVIDIA's Blackwell chips and the launch of Tranium 2, AWS's second-generation AI chip, further emphasize the company's focus on supporting AI workloads. To address reliability concerns, AWS introduced automated reasoning to combat AI hallucinations and model distillation for efficient multi-agent collaboration. Furthermore, AWS's new Aurora DSQL engine and Data Transfer Terminal locations aim to enhance data processing and storage capabilities.Shifting gears, Host Dave Sobel discusses a major cyber attack on U.S. telecommunications companies, urging the use of encrypted messaging apps to safeguard communications. The hacking campaign, attributed to China, has raised significant privacy concerns, with officials recommending encryption to protect sensitive information. The episode also touches on the role of AI in the recent global elections, where despite fears of misinformation, AI was utilized positively for language translation and voter engagement, highlighting a more balanced narrative than anticipated.Finally, the episode explores broader industry trends, including Intel's challenges following the forced exit of its CEO and the potential resurgence of monolithic architectures as companies reconsider the complexities of microservices. Sobel emphasizes the evolving role of IT departments, which are gaining recognition and influence within organizations due to the rise of AI. The discussion encourages listeners to reflect on their technology choices, partnerships, and the strategic contributions of IT in navigating these changes.Three things to know today00:00 Amazon Unveils AI-Centric Updates at re:Invent: Nova Models, Hardware Breakthroughs, and Legacy System Modernization06:04 Balancing Risks and Relief: Encryption and AI Oversight Take Center Stage in 2024's Security Landscape08:41 From Intel's Future to Microservices' Decline and IT's Strategic Rise  Supported by:  http://blumira.com/radio/https://www.coreview.com/msp   All our Sponsors: https://businessof.tech/sponsors/ Do you want the show on your podcast app or the written versions of the stories? Subscribe to the Business of Tech: https://www.businessof.tech/subscribe/Looking for a link from the stories? The entire script of the show, with links to articles, are posted in each story on https://www.businessof.tech/ Support the show on Patreon: https://patreon.com/mspradio/ Want to be a guest on Business of Tech: Daily 10-Minute IT Services Insights? Send Dave Sobel a message on PodMatch, here: https://www.podmatch.com/hostdetailpreview/businessoftech Want our stuff? Cool Merch? Wear “Why Do We Care?” - Visit https://mspradio.myspreadshop.com Follow us on:LinkedIn: https://www.linkedin.com/company/28908079/YouTube: https://youtube.com/mspradio/Facebook: https://www.facebook.com/mspradionews/Instagram: https://www.instagram.com/mspradio/TikTok: https://www.tiktok.com/@businessoftechBluesky: https://bsky.app/profile/businessof.tech

Мы просмотрели более 850 обновлений и отобрали самое важное перед re:Invent 2024!   В этом выпуске вы узнаете: •

Good morning, Welcome to Top of the Morning by Mint, your weekday newscast that brings you five major stories from the world of business. It's Friday, November 29, 2024. This is Nelson John, let's get started. At COP29 in Baku, Azerbaijan, the focus was all about climate finance, but the outcome left many wanting more. Initially aiming for $1.3 trillion annually, negotiators ended up agreeing on $300 billion a year by 2035, which didn't sit well with developing countries. They found the amount too low and the decision unambitious, expressing disappointment over the developed countries' reluctance to commit more. The conference also felt the impact of geopolitical tensions, particularly with Donald Trump's re-election, raising concerns about the U.S.'s commitment to climate finance. This scepticism influenced the negotiations, contributing to the lower-than-expected financial commitment. P Anima takes a deep dive into the happenings of the recently-concluded COP29 in the Azeri capital. Stellaris Venture Partners just launched its biggest fund yet at $300 million, sticking to that number despite heavy interest. Similarly, other investment firms like Blume Ventures and Peak XV are either holding steady or shrinking their funds, pointing to a shift towards more cautious investment strategies. Venture capital firms are getting more selective, influenced by past fund performances and the current economic climate, which demands realistic startup valuations. Priyamvada C reports on how VC firms are finding smaller fund sizes a better fit for the Indian market.  India just kicked off a massive ₹2,481 crore National Mission on Natural Farming to help 10 million farmers go chemical-free. The plan? Roll out 10,000 bio input resource centers and train farmers using model farms. The government is also deploying 30,000 krishi sakhis who will guide the farmers. What's the difference between natural and organic farming, you ask? Both avoid chemicals, but organic farming needs strict certification and a few years to switch from conventional methods. Natural farming lets farmers switch at their own pace, which is great for flexibility but might make it harder to sell produce at premium prices like organic goods fetch. In today's Primer, Sayantan Bera explains how natural farming can affect the kind of food you consume and whether the method will make it safer to eat.  This year, one company wants to hire an IITian at a salary of ₹1.9 crore. The catch? The AI company from San Francisco wants aspirants to create a Google-proof questionnaire that ChatGPT can't solve. Devina Sengupta and Pratishtha Bagai write that other AI companies like Turing, Graviton, and Da Vinci are also looking to hire students by providing remote working options and hefty salaries of more than ₹2 crore. Students well versed in machine learning seem to be the top choice as of now. Traditional employers like Goldman Sachs and Microsoft too are emphasising on AI-forward roles.  There are a couple of new 10-minute delivery players in the market. Yes, their names start with an S and Z, but they're Swish and Zing. These startups are aiming to capitalise on the growing demand for quick commerce in India. Sowmya Ramasubramanian writes that these companies focus specifically on 10-minute food deliveries, catering to impulsive consumers seeking convenience. Gross merchandise value for quick commerce deliveries is projected to reach $9.9 billion in five years in this sector. Turns out, hunger can't really wait after all.  COP kicks the climate can down the road, againIndia's venture capital firms are finding that leaner might be betterMint Primer | Natural farming: Will it make your food safe?Battle of AI versus the rest as offers promise ₹2 crore and above at IITsNew 10-minute food delivery startups are ready to test your impulse control

En este episodio del Podcast de Charlas Técnicas de AWS nos acompañan Damian Munafo y Victor García para sumergirnos en el mundo de FinOps. Hablaremos sobre cómo esta práctica impacta tanto en la nube como en entornos on-premises y cómo podemos adoptar una cultura más eficiente en la gestión de costes.Este es el episodio 18 de la temporada 5ta.Tabla de Contenidos:00:38 - Conociendo a Damian Munafo y Victor García.02:01 - ¿Qué es FinOps?03:54 - Una responsabilidad compartida: Equipos, roles y la colaboración clave.05:15 - Cómo iniciar una cultura FinOps.08:40 - El Arquitecto Frugal: Diseño eficiente y consciente de costos.09:52 - Mapeando nuestra infraestructura: Entender dónde y cómo se usan los recursos.12:18 - Visualizaciones para decisiones inteligentes.13:30 - Tecnologías clave: Karpenter, instancias Spot y Graviton.15:10 - Estrategias FinOps: Las etapas Inform, Optimize y Operate.18:03 - Caso práctico: Costes alineados al negocio, la estrategia de Ryanair.19:48 - Trade-Offs: Balance entre coste, rendimiento y resiliencia.22:43 - Monitorización por roles: Métricas relevantes para cada equipo.23:40 - Empoderando a los DevOps: La responsabilidad en manos de los equipos técnicos.26:54 - Granularidad de datos: Profundizando en el análisis de costos.28:00 - Stacks tecnológicos y control de gastos: Una vista estratégica.29:46 - La optimización como proceso continuo: Más allá de las acciones puntuales.31:27 - El peligro de la complacencia: Cómo evitar el estancamiento.33:40 - KPIs combinados: Negocio e infraestructura trabajando juntos.34:30 - On-prem vs Cloud: Descubriendo adónde se va el dinero.39:11 - El desafío de las licencias: Una gestión crítica en cualquier entorno.44:15 - Recomendaciones clave y highlightsRedes sociales de nuestros invitados:Damian Munafo: LinkedinVíctor García: LinkedIn Podcast y Newsletters:Podcast FinOps mas que costes  Newsletter: FinOps weeklyNewsletter: SpainClouds Enlaces de Interés:AWS Cloud Financial Management Technical Implementation PlaybooksThe FinOps Foundation✉️ Si quieren escribirnos pueden hacerlo a este correo: podcast-aws-espanol@amazon.comPodes encontrar el podcast en este link: https://aws-espanol.buzzsprout.com/O en tu plataforma de podcast favoritaMás información y tutoriales en el canal de youtube de Charlas Técnicas☆☆ NUESTRAS REDES SOCIALES ☆☆

There's an AI chip battle brewing among the major cloud vendors. Google's Trillium, a custom chip for training and running AI models, recently entered preview, and Microsoft's Maia is expected to follow in short order. Not to be outdone, Amazon Web Services has AI chips, too: Trainium, Inferentia, and Graviton. Learn more about your ad choices. Visit podcastchoices.com/adchoices

Josh Peck talks about the connection between Revelation 9 and CERN in Bible prophecy.Donate: http://PayPal.me/JoshPeckDisclosureCashApp: $JoshScottPeck

It's time to chew over a big beatdown bonanza as Paul and Al look at the climactic clash between the Thunderbolts and Graviton in issues 56-58, and take the time to say goodbye to Marvel's breakout character of 1998. Then it's time for something completely different, as one of the least fondly remembered gimmicks of the Bill Jemas era rears its very quiet head in issue 59.

Send us a textIn this episode, Frank and Steve discuss the latest news in Cloud FinOps, including AWS G4DN Workspaces, AWS Parallel Computing Service, Google Compute Engine C3 and X4 instances, Azure C4 VMs, Amazon Open Search Service, AlloyDB free trial, Azure NetApp file storage, and more. They also touch on topics like cost optimization, carbon emissions, and the AWS Console mobile app.takeawaysAWS announces G4DN Workspaces, Parallel Computing Service, and support for Graviton 3 in Open Search ServiceGoogle introduces C3 and X4 instances in Compute EngineAzure releases C4 VMs and NetApp file storage with cool accessAmazon S3 no longer charges for certain HTTP error codesAWS introduces enhanced rate-based rules for lower rate limitsAzure offers Carbon Optimization and Spanner GraphDelegated administrator for cost optimization hub in AWSAlloyDB offers a free trial and Azure updates pricing and calculators

Join Geoff and Whisp as they broadcast live from the wildest Labor Day fair you've ever heard at the Val Verde Unemployment Office! This episode is packed with: Celebrity Sightings: From Jean-Claude Van Damme and a skeleton impersonating Mick Mars all the way to Jeff Foxworthy holding job interviews in a Graviton. The stars are out in VAL VERDE! Hope you like the song, “Live Wire!” Labor Day Countdown: Get ready to sing along to the most iconic Labor Day anthems, from classic rock hits to modern-day work songs like “Work Is Pain” by Loverboy! A "Skeet Ulrich Resume Builder" Booth: Build a killer resume with the legendary actor who played a killer in “Scream!” Plus: Learn about the Bon Jovi coke mirror that talks to you! Hear from the head of the Val Verde Unemployment Office, FLIRT SKIRTLER. News about The Chicken Man, now that he's moved to Val Verde. Whisp released a soundtrack song in the 90's?? And a brand new PSA from Geoff “The Angry Man” Garlock about text etiquette!  This episode is sponsored by: The Law Cousins Steve The Comic Guy Pizza Emporium Love 108.9 The Hawk? Subscribe to the podcast and spread the word! Get official merch: http://tee.pub/lic/goodrockshirts Support the show: https://patreon.com/1089thehawk Follow us on social media: YouTube, Twitter, Instagram, TikTok, Bluesky, Threads Learn more: https://1089thehawk.com Keywords: 108.9 The Hawk, Season 5, Podcast, Classic Rock, Val Verde, Geoff Garlock, Whisp Turlington, Jason Gore, Labor Day, 80s Rock Music, The Geoff and Whisp Show, Val Verde, unemployment, unemployment office, celebrity sightings, Bon Jovi, Loverboy, Styx, Bryan Adams, Classic Rock Podcast, Dog Cop, Batman Returns, Skeet Ulrich, Classic Rock Radio

Neste episódio, a equipe da Frete.com compartilha detalhes sobre sua plataforma de autoatendimento para desenvolvedores. Eles abordam como identificaram as dores dos times de tecnologia e escolheram uma solução open source para permitir o rápido provisionamento de novos serviços com todos os padrões e boas práticas já implementados, agilizando entregas. Além disso, discutem estratégias de redução de custos na AWS, como instâncias Spot e adoção de Graviton.

Episode 271.  James B and Eddie talk about big time villains such as The Beetle, The Brothers Grimm, Titania, Graviton, Jonathan Caesar and the Trapster.  Acts of Vengeance is back! and Venom makes an appearance too. The Amazing Spider-Man 332 Web of Spider-Man 64 65 The Spectacular Spider-Man 164 Theme Music by Jeff Kenniston.  This Episode Edited by James B using Audacity and Cleanfeed.  Summaries written by James B and Eddie and Edna Gortch.  Most Sound effects and music generously provided royalty free by www.fesliyanstudios.com and https://www.zapsplat.com/  Sponsor: Madison Ave Jewelers Check out all the episodes on letsreadspiderman.podbean.com or wherever you get your podcasts. Check out our live meetup and Discord Channel here https://docs.google.com/document/d/1_mW6htjJUHOzlViEvPQqR-k68tClMGAi85Bi_xrlV7w/edit

Welcome to episode 269 of the Cloud Pod Podcast – where the forecast is always cloudy! Justin, Matthew and Ryan are your hosts this week as we talk about – you guessed it – the Crowdstrike update that broke, well, everything! We're also looking at Databricks, Google potentially buying Wiz, NY Summit news, and more!   Titles we almost went with this week: You can't take Justin down; but a 23-hour flight to India (or Crowdstrike updates) can Google wants Wiz, and Crowdstrike Strikes all Crowdstrike, does anyone know the Graviton of this situation?  We are called to this summit to talk AWS AI Supremacy Crowdstrike, Wiz and Chat GPT 4o Mini… oh my An Impatient Wiz builds his own data centers not impacted by Crowdstrike A big thanks to this week's sponsor: We're sponsorless! Want to reach a dedicated audience of cloud engineers? Send us an email or hit us up on our Slack Channel and let's chat!  General News 00:58 You Guessed It – Crowdstrike  Microsoft, CrowdStrike outage disrupts travel and business worldwide Our Statement on Today's Outage   (listener note: paywall article)  It’s not every day you get to experience one of the largest IT Outages in history,  and it even impacted our recording of the show last week.   Crowdstrike, a popular EDR solution caused major disruption to the worlds IT systems with an errant update to their software that caused servers to BSOD, disrupting travel (airplanes, trains, etc), governments, news organizations and more.   Crowdstrike removed the errant file quickly, but still the damage was done with tons of systems requiring manual intervention to be recovered. The fix required booting into safe mode, and removing a file from the crowdstrike directory. This was all complicated by bitlocker and lack of local admin rights for many end user devices. Sometimes doing up to 15 reboots would bring the server back to life. Swinging the hard drives from one broken server to a working server manually removes the files and puts them back. The issue also caused a large-scale outage in the Azure Central region.    In addition to services on AWS being impacted that run Windows (Amazon is a well-known large Crowdstrike customer) Crowdstrike CEO Goerge Kurtz (who happened to be the CTO at Mcafee during the 2010 Update Fiasco that impacted Mcafee clients globally) stated that he was deeply sorry and vowed to make sure every customer is fully recovered.  By the time of this recording, most clients should be mostly fixed and recovered, and we are all anxiously waiting to hear how this could have happened.  04:50 Justin – “It’s really an Achilles heel of the cloud. I mean, to fix this, you need to be able to boot a server into safe mode or into recovery mode and then remove this file manually, which requires that you have console access, which, you know, Amazon just added a couple of years ago.” 07:45 Matthew – “It’s always fun when you’re like, okay, everyone si

There's a hundred-year-old conundrum in physics that we're still yet to untangle, and it has to do with the very nature of space-time itself.

Bret and Nirmal are joined by Michael Fischer of AWS to discuss why we should use Graviton, their arm64 compute with AWS-designed CPUs.Graviton is AWS' term for their custom ARM-based EC2 instances. We now have all major clouds offering an ARM-based option for their server instances, but AWS was first, way back in 2018. Fast forward 6 years and AWS is releasing their 4th generation Graviton instances, and they deliver all the CPU, networking, memory and storage performance that you'd expect from their x86 instances and beyond.I'm a big fan of ARM-based servers and the price points that AWS gives us. They have been my default EC2 instance type for years now, and I recommend it for all projects I'm working on with companies.We get into the history of Graviton, how easy it is to build and deploy containers and Kubernetes clusters that have Graviton and even two different platform types in the same cluster. We also cover how to build multi-platform images using Docker BuildKit.Be sure to check out the live recording of the complete show from May 9, 2024 on YouTube (Ep. 265). Includes demos. ★Topics★Graviton + GitLab + EKSPorting Advisor for GravitonGraviton Getting StartedCreators & Guests Cristi Cotovan - Editor Beth Fisher - Producer Bret Fisher - Host Nirmal Mehta - Host Michael Fischer - Guest (00:00) - Intro (06:19) - AWS and ARM64: Evolution to Graviton 4 (07:55) - AWS EC2 Nitro: Why and How? (11:53) - Nitro and Graviton's Evolution (18:35) - What Can't Run on Graviton? (23:15) - Moving Your Workloads to Graviton (27:19) - K8s Tooling and Multi-Platform Images (37:07) - Tips for Getting Started with Graviton You can also support my free material by subscribing to my YouTube channel and my weekly newsletter at bret.news!Grab the best coupons for my Docker and Kubernetes courses.Join my cloud native DevOps community on Discord.Grab some merch at Bret's Loot BoxHomepage bretfisher.com

Could the AI revolution be the key that unlocks a new era in cloud service adoption and developer preferences? We're slicing through the hype to bring you the real scoop from Google Cloud Next, contrasting it with Amazon's Q announcement. Join Alex, Chris and Tim as we shed light on groundbreaking AI developments like the Gemini 1.5 Pro model, which is pushing the boundaries with its token limits, and how these advancements might shape the terrain for Azure's upcoming Ignite event. We're not just talking enhancements – we're discussing the transformative potential these technologies hold for the cloud ecosystem.Navigating the cloud can sometimes feel like steering through a nebula, but fear not, our latest installment doesn't shy away from the technical nitty-gritty. We're tackling the big questions: Are the cost savings and performance optimizations from custom silicon like AWS's Graviton processor making a real difference for the end-user? We scrutinize Google Cloud's Cloud Assist and Cloud Service Mesh, dissecting their role in refining application latency and ponder if the benefits truly outweigh the costs. It's a candid look at the balance between proprietary technology and customer-centric strategies, where we don't just accept the status quo – we question it.Cross-cloud networking and integration are like the high-wire acts of the cloud circus, and we're here to demystify the acrobatics involved. This episode walks you through the intricate steps of Google's Cross-Cloud Interconnect and Private Service Connect, comparing them to the likes of AWS's Private Link. Plus, we celebrate the unsung heroes of cloud networking – specifically Google Cloud and Oracle Cloud Infrastructure – by sharing their success stories and the significant strides they've made in the domain. From the complexities of Google Cloud VMware Engine's latest moves to the reasons why you should never use auto mode in your networking configurations, we're peeling back layers to reveal the core of effective cloud strategies.Check out the Fortnightly Cloud Networking NewsVisit our website and subscribe: https://www.cables2clouds.com/Follow us on Twitter: https://twitter.com/cables2cloudsFollow us on YouTube: https://www.youtube.com/@cables2clouds/Follow us on TikTok: https://www.tiktok.com/@cables2cloudsMerch Store: https://store.cables2clouds.com/Join the Discord Study group: https://artofneteng.com/iaatjArt of Network Engineering (AONE): https://artofnetworkengineering.com

Could the same cosmic forces that sculpt galaxies also hold the key to the very origins of life? Might subtle gravitational influences guide the assembly of cells or even carry whispers of consciousness from distant stars? Could ancient gravitational waves, echoes of the universe's birth, have left subtle imprints on our own biology? The boundary between science and the fantastical blurs as we ponder the role of gravity and stardust in the breathtaking emergence of life itself.  Are these merely wild speculations, or might they hold a grain of truth about our extraordinary place within the cosmos?If you are having a mental health crisis and need immediate help please go to https://troubledminds.org/help/ and call somebody right now. Reaching out for support is a sign of strength.LIVE ON Digital Radio! http://bit.ly/3m2Wxom or http://bit.ly/40KBtlWhttp://www.troubledminds.org Support The Show!https://www.spreaker.com/podcast/troubled-minds-radio--4953916/supporthttps://rokfin.com/creator/troubledmindshttps://patreon.com/troubledmindshttps://www.buymeacoffee.com/troubledmindshttps://troubledfans.comFriends of Troubled Minds! - https://troubledminds.org/friendsShow Schedule Sun-Mon-Tues-Wed-Thurs 7-10pstiTunes - https://apple.co/2zZ4hx6Spotify - https://spoti.fi/2UgyzqMTuneIn - https://bit.ly/2FZOErSTwitter - https://bit.ly/2CYB71U----------------------------------------https://troubledminds.org/the-cosmic-forge-graviton-rhythms-and-ancient-starseeds/https://www.newscientist.com/article/2424426-weve-glimpsed-something-that-behaves-like-a-particle-of-gravity/https://www.iflscience.com/to-make-a-human-you-probably-first-need-a-gravitational-wave-73614https://arxiv.org/abs/2402.03593https://www.aip.org/news/2016/origins-we-are-stardusthttps://www.britannica.com/science/gravitonhttps://en.wikipedia.org/wiki/Gravity_wavehttps://www.space.com/gravitational-wave-background-universe-1st-detectionhttps://news.berkeley.edu/2023/06/28/after-15-years-pulsar-timing-yields-evidence-of-cosmic-gravitational-wave-background/https://www.nature.com/articles/d41586-023-02203-6https://theconversation.com/starseeds-psychologists-on-why-some-people-think-theyre-aliens-living-on-earth-197291https://en.wikipedia.org/wiki/Quantum_gravityhttps://forgottenrealms.fandom.com/wiki/Caniahttps://www.starwars.com/news/so-what-the-heck-are-midi-chlorianshttps://en.wikipedia.org/wiki/Denis_of_Paris

In this episode we meet with Matthew McClean, a Sr Manager from AWS's Annapurna Team to talk about Accelerators - the chips that make AI possible. We cover different Accelerators - GPUs, Trainium, Inferentia, Graviton and more.AWS Hosts: Nolan Chen & Malini ChatterjeeEmail Your Feedback: rethinkpodcast@amazon.comLinks for the Show:AWS re:Invent 2023 - Behind-the-scenes look at generative AI infrastructure at Amazon (CMP206)https://www.youtube.com/watch?v=fDk09hms8s8AWS re:Invent 2023 - Behind-the-scenes look at generative AI infrastructure at Amazon (CMP206)https://www.youtube.com/watch?v=VPvguzeWlbUWelcome to AWS Neuronhttps://awsdocs-neuron.readthedocs-hosted.com/en/latest/index.htmlOptimum Neuronhttps://huggingface.co/docs/optimum-neuron/index

Bonjour Denise Epoté, c'est un trio originaire de Côte d'Ivoire qui occupe la première marche de votre podium cette semaine. Issa Berthe, Guillaume Yapi et Mamadou Traoré sont ingénieurs informaticiens, ils ont mis au point IYAKO une innovation qui encourage le civisme et l'intelligence collective en vue de restituer des objets trouvés à leurs légitimes propriétaires. À l'occasion de la CAN 2023, la plateforme a signé une collaboration avec le comité d'organisation. Un second trio d'innovateurs en tête d'affiches, mais cette fois, ils sont originaires du Maroc, et de Tunisie. Les innovations de Mardaoui Rafie, Béchir Benbrika et Saad Ramadan ont été sélectionnées par le programme Launchpad Agritech dont l'objectif est de transformer le paysage agricole africain.

Join AWS Business Innovation leader Ben Schreiner for a recap of re:Invent 2023. We cover major announcements and innovations in infrastructure, data analytics and generative AI. AWS services discussed include S3 Express One Zone, Graviton 4, Bedrock, Amazon Q, Zero ETL and more!AWS Hosts: Nolan Chen & Malini ChatterjeeFurther reference - https://www.aboutamazon.com/news/aws/aws-reinvent-2023-announcementsTop announcements - https://aws.amazon.com/blogs/aws/top-announcements-of-aws-reinvent-2023/Email Your Feedback: rethinkpodcast@amazon.com#awsrethink

What were the major announcements at 2023 AWS re:Invent? What did we learn about their AI strategy? What did we learn about how they continue to evolve the business?SHOW: 778CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotwCHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"SHOW SPONSORS:CloudZero – Cloud Cost Visibility and Savings​​CloudZero provides immediate and ongoing savings with 100% visibility into your total cloud spendReduce the complexities of protecting your workloads and applications in a multi-cloud environment. Panoptica provides comprehensive cloud workload protection integrated with API security to protect the entire application lifecycle.  Learn more about Panoptica at panoptica.appSHOW NOTES:Top announcements from AWS re:Invent 2023AWS re:Invent Keynotes (2023)AWS MANAGES THE TRANSITION FROM ONE CLOUD ERA TO THE NEXT Reviewing AWS' AI strategyNVIDIA DGX Cloud in AWSFurther alignment with AnthropicAWS QCost Optimization HubMemory-optimized Graviton 4 ARM compute nodeszero-ETL integration for a number of database and data-ingestion platformsAurora Limitless DatabaseIBM DB2 comes to AWSProject Kuiper - Satellite InternetFEEDBACK?Email: show at the cloudcast dot netTwitter: @thecloudcastnet

In this episode of Infrastructure Matters, Krista Macomber, Camberley Bates, and Steven Dickens discuss key takeaways from AWS re:Invent 2023, including the cloud juggernaut's pragmatic approach to cloud computing, focusing on AI, hybrid solutions, and cost optimization. It is also investing heavily in new features and services, and partnering with other companies to expand their reach. Key themes include: Gen AI: AWS made a big push towards AI with announcements like Q, a helpful service for developers and cloud admins, custom silicon updates for Graviton and Trainium, and a focus on the AI layered cake. Hybrid is here: AWS acknowledged the hybrid cloud reality with announcements like S3 Express One Zone, an S3 offering for high performance computing, and AWSM2, a managed mainframe migration service. Cost optimization: With the economic headwinds, AWS emphasized cost optimization with announcements like the DB2 offering on AWS, which allows customers to run their legacy workloads in the cloud.

Infomaniak partage les valeurs de Tech Café : éthique, écologie et respect de la vie privée. Découvrez les services de notre partenaire sur Infomaniak.comOn parle des annonces d'Amazon durant l'événement re:Invent 2023, de matos et d'affaires légales... ❤️ Patreon

This week, we review the major announcements from AWS re:Invent and discuss how the hyperscalers are embracing A.I. Plus, a few thoughts on children's chores. Watch the YouTube Live Recording of Episode (https://www.youtube.com/watch?v=q0xwqUis6xA) 443 (https://www.youtube.com/watch?v=q0xwqUis6xA) Runner-up Titles No Slack The Corporate Podcast. Quality of life stop Our roads diverge Eats a bag of llama Nobody wants to do a bake-off AI all the time Rundown AWS re:Invent Top announcements of AWS re:Invent 2023 | Amazon Web Services (https://aws.amazon.com/blogs/aws/top-announcements-of-aws-reinvent-2023/) Salesforce Inks Deal to Sell on Amazon Web Services' Marketplace (https://www.bloomberg.com/news/articles/2023-11-27/salesforce-to-sell-software-on-aws-marketplace-in-self-service-purchase-push#xj4y7vzkg) AWS Unveils Next Generation AWS-Designed Chips (https://press.aboutamazon.com/2023/11/aws-unveils-next-generation-aws-designed-chips) Join the preview for new memory-optimized, AWS Graviton4-powered Amazon EC2 instances (R8g) (https://aws.amazon.com/blogs/aws/join-the-preview-for-new-memory-optimized-aws-graviton4-powered-amazon-ec2-instances-r8g/) Announcing the new Amazon S3 Express One Zone high performance storage class (https://aws.amazon.com/blogs/aws/new-amazon-s3-express-one-zone-high-performance-storage-class/) AWS unveils new Trainium AI chip and Graviton 4, extends Nvidia partnership (https://www.zdnet.com/article/aws-unveils-new-trainium-ai-chip-and-graviton-4-extends-nvidia-partnership/) AI Chip - AWS Inferentia - AWS (https://aws.amazon.com/machine-learning/inferentia/) DGX Platform (https://www.nvidia.com/en-au/data-center/dgx-platform/) Foundational Models - Amazon Bedrock - AWS (https://aws.amazon.com/bedrock/) Supported models in Amazon Bedrock - Amazon Bedrock (https://docs.aws.amazon.com/bedrock/latest/userguide/models-supported.html#models-supported-meta) Agents for Amazon Bedrock is now available with improved control of orchestration and visibility into reasoning (https://aws.amazon.com/blogs/aws/agents-for-amazon-bedrock-is-now-available-with-improved-control-of-orchestration-and-visibility-into-reasoning/) Knowledge Bases now delivers fully managed RAG experience in Amazon Bedrock (https://aws.amazon.com/blogs/aws/knowledge-bases-now-delivers-fully-managed-rag-experience-in-amazon-bedrock/) Customize models in Amazon Bedrock with your own data using fine-tuning and continued pre-training (https://aws.amazon.com/blogs/aws/customize-models-in-amazon-bedrock-with-your-own-data-using-fine-tuning-and-continued-pre-training/) Amazon Q brings generative AI-powered assistance to IT pros and developers (https://aws.amazon.com/blogs/aws/amazon-q-brings-generative-ai-powered-assistance-to-it-pros-and-developers-preview/) Improve developer productivity with generative-AI powered Amazon Q in Amazon CodeCatalyst (https://aws.amazon.com/blogs/aws/improve-developer-productivity-with-generative-ai-powered-amazon-q-in-amazon-codecatalyst-preview/) Upgrade your Java applications with Amazon Q Code Transformation (https://aws.amazon.com/blogs/aws/upgrade-your-java-applications-with-amazon-q-code-transformation-preview/) Introducing Amazon Q, a new generative AI-powered assistant (https://aws.amazon.com/blogs/aws/introducing-amazon-q-a-new-generative-ai-powered-assistant-preview/) New Amazon Q in QuickSight uses generative AI assistance for quicker, easier data insights (https://aws.amazon.com/blogs/aws/new-amazon-q-in-quicksight-uses-generative-ai-assistance-for-quicker-easier-data-insights-preview/) Amazon Managed Service for Prometheus collector provides agentless metric collection for Amazon EKS (https://aws.amazon.com/blogs/aws/amazon-managed-service-for-prometheus-collector-provides-agentless-metric-collection-for-amazon-eks/) Amazon CloudWatch Logs now offers automated pattern analytics and anomaly detection (https://aws.amazon.com/blogs/aws/amazon-cloudwatch-logs-now-offers-automated-pattern-analytics-and-anomaly-detection/) Use Amazon CloudWatch to consolidate hybrid, multicloud, and on-premises metrics (https://aws.amazon.com/blogs/aws/new-use-amazon-cloudwatch-to-consolidate-hybrid-multi-cloud-and-on-premises-metrics/) Amazon EKS Pod Identity simplifies IAM permissions for applications on Amazon EKS clusters (https://aws.amazon.com/blogs/aws/amazon-eks-pod-identity-simplifies-iam-permissions-for-applications-on-amazon-eks-clusters/) Amazon DynamoDB zero-ETL integration with Amazon OpenSearch Service is now available (https://aws.amazon.com/blogs/aws/amazon-dynamodb-zero-etl-integration-with-amazon-opensearch-service-is-now-generally-available/) Amazon says its first Project Kuiper internet satellites were fully successful in testing (https://www.cnbc.com/2023/11/16/amazon-kuiper-internet-satellites-fully-successful-in-testing.html) AWS takes the cheap shots (https://techcrunch.com/2023/11/28/aws-takes-the-cheap-shots/) Here's everything Amazon Web Services announced at AWS re:Invent (https://techcrunch.com/2023/11/28/heres-everything-aws-reinvent-2023-so-far/) Relevant to your Interests Oracle Cloud Made All The Right Moves In 2022 (https://moorinsightsstrategy.com/oracle-cloud-made-all-the-right-moves-in-2022/) Ransomware gang files SEC complaint over victim's undisclosed breach (https://www.bleepingcomputer.com/news/security/ransomware-gang-files-sec-complaint-over-victims-undisclosed-breach/) Keynote Highlights: Satya Nadella at Microsoft Ignite 2023 (https://www.youtube.com/watch?v=QMlUJqxhdoY) Thoma Bravo to sell about $500 million in Dynatrace stock (https://www.marketwatch.com/story/thoma-bravo-to-sell-about-500-million-in-dynatrace-stock-9d7bd0e6) FinOps Open Cost and Usage Specification 1.0-preview Released to Demystify Cloud Billing Data (https://www.prnewswire.com/news-releases/finops-open-cost-and-usage-specification-1-0-preview-released-to-demystify-cloud-billing-data-301990559.html?tc=eml_cleartime) AWS, Microsoft, Google and Oracle partner to make cloud spend more transparent | TechCrunch (https://techcrunch.com/2023/11/16/aws-microsoft-google-and-oracle-partner-to-make-cloud-spend-more-transparent/) Privacy is Priceless, but Signal is Expensive (https://signal.org/blog/signal-is-expensive/) Several popular AI products flagged as unsafe for kids by Common Sense Media | TechCrunch (https://techcrunch.com/2023/11/16/several-popular-ai-products-flagged-as-unsafe-for-kids-by-common-sense-media/) Amazon to sell Hyundai vehicles online starting in 2024 (https://finance.yahoo.com/news/amazon-sell-hyundai-vehicles-online-180500951.html) Amazon to launch car sales next year with Hyundai (https://news.google.com/articles/CBMiP2h0dHBzOi8vd3d3LmF4aW9zLmNvbS8yMDIzLzExLzE2L2FtYXpvbi1oeXVuZGFpLWNhcnMtc2FsZS1hbGV4YdIBAA?hl=en-US&gl=US&ceid=US%3Aen) Canonical Microcloud: Simple, free, on-prem Linux clustering (https://www.theregister.com/2023/11/16/canonical_microcloud/) Introducing the Functional Source License: Freedom without Free-riding (https://blog.sentry.io/introducing-the-functional-source-license-freedom-without-free-riding/) The Problems with Money In (Open Source) Software | Aneel Lakhani | Monktoberfest 2023 (https://www.youtube.com/watch?v=LTCuLyv6SHo) DXC Technology and AWS Take Their Strategic Partnership to the Next Level to Deliver the Future of Cloud for Customers (https://dxc.com/us/en/about-us/newsroom/press-releases/11202023) Broadcom and VMware Intend to Close Transaction on November 22, 2023 (https://www.businesswire.com/news/home/20231121379706/en/Broadcom-and-VMware-Intend-to-Close-Transaction-on-November-22-2023) Broadcom announces successful acquisition of VMware | Hock Tan (https://www.broadcom.com/blog/broadcom-announces-successful-acquisition-of-vmware) Broadcom closes $69 billion VMware deal after China approval (https://finance.yahoo.com/news/broadcom-closes-69-billion-vmware-133704461.html) VMware is now part of Broadcom | VMware by Broadcom (https://www.broadcom.com/info/vmware) Binance CEO Changpeng Zhao Reportedly Quits and Pleads Guilty to Breaking US Law (https://www.wired.com/story/binance-cz-ceo-quits-pleads-guilty-breaking-law/) Congrats To Elon Musk: I Didn't Think You Had It In You To File A Lawsuit This Stupid. But, You Crazy Bastard, You Did It! (https://www.techdirt.com/2023/11/21/congrats-to-elon-musk-i-didnt-think-you-had-it-in-you-to-file-a-lawsuit-this-stupid-but-you-crazy-bastard-you-did-it/) Hackers spent 2+ years looting secrets of chipmaker NXP before being detected (https://arstechnica.com/security/2023/11/hackers-spent-2-years-looting-secrets-of-chipmaker-nxp-before-being-detected/) Meet ‘Anna Boyko': How a Fake Speaker Blew up DevTernity (https://thenewstack.io/meet-anna-boyko-how-a-fake-speaker-blew-up-devternity/) IBM's Db2 database dinosaur comes to AWS (https://go.theregister.com/feed/www.theregister.com/2023/11/29/aws_launch_ibms_db2_database/) Reports of AI ending human labour may be greatly exaggerated (https://www.ecb.europa.eu/pub/economic-research/resbull/2023/html/ecb.rb231128~0a16e73d87.es.html) New Google geothermal electricity project could be a milestone for clean energy (https://apnews.com/article/geothermal-energy-heat-renewable-power-climate-5c97f86e62263d3a63d7c92c40f1330d) VMware's $92bn sale showers cash on Michael Dell and Silver Lake (https://www.ft.com/content/d01901a2-db4b-45df-8ce5-f57ff46d463e) Gartner Says Cloud Will Become a Business Necessity by 2028 (https://www.gartner.com/en/newsroom/press-releases/2023-11-29-gartner-says-cloud-will-become-a-business-necessity-by-2028) IRS starts the bidding for $1.9B IT services recompete (https://www.nextgov.com/acquisition/2023/11/irs-starts-bidding-19b-it-services-recompete/392303/) WSJ News Exclusive | Apple Pulls Plug on Goldman Credit-Card Partnership (https://www.wsj.com/finance/banking/apple-pulls-plug-on-goldman-credit-card-partnership-ca1dfb45) Apple employees most likely to leave to join Google shows LinkedIn (https://9to5mac.com/2023/11/23/apple-employees-next-jobs/) Ranked: Worst Companies for Employee Retention (U.S. and UK) (https://www.visualcapitalist.com/cp/ranked-worst-companies-for-employee-retention-u-s-and-uk/) Apple announces RCS support for iMessage (https://arstechnica.com/gadgets/2023/11/apple-announces-rcs-support-for-imessage/) Apple says iPhones will support RCS in 2024 (https://www.theverge.com/2023/11/16/23964171/apple-iphone-rcs-support) Today on The Vergecast: what Apple really means when it talks about RCS. (https://www.theverge.com/2023/11/17/23965656/today-on-the-vergecast-what-apple-really-means-when-it-talks-about-rcs) **## Nonsense Ikea debuts a trio of affordable smart home sensors (https://www.theverge.com/2023/11/28/23977693/ikea-sensors-door-window-water-motion-price-date-specs) Apple and Spotify have revealed their top podcasts of 2023 (https://www.theverge.com/2023/11/29/23981468/apple-replay-spotify-wrapped-podcasts-rogan-crime-junkie-alex-cooper) Listener Feedback Matt's Trackball: Amazon.com: Kensington Expert Trackball Mouse (K64325), Black Silver, 5"W x 5-3/4"D x 2-1/2"H : Electronics (https://amzn.to/3ujm7ct) Conferences Jan 29, 2024 to Feb 1, 2024 That Conference Texas (https://that.us/events/tx/2024/schedule/) If you want your conference mentioned, let's talk media sponsorships. SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Get a SDT Sticker! Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Follow us: Twitch (https://www.twitch.tv/sdtpodcast), Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/), Mastodon (https://hachyderm.io/@softwaredefinedtalk), BlueSky (https://bsky.app/profile/softwaredefinedtalk.com), LinkedIn (https://www.linkedin.com/company/software-defined-talk/), TikTok (https://www.tiktok.com/@softwaredefinedtalk), Threads (https://www.threads.net/@softwaredefinedtalk) and YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured). Use the code SDT to get $20 off Coté's book, Digital WTF (https://leanpub.com/digitalwtf/c/sdt), so $5 total. Become a sponsor of Software Defined Talk (https://www.softwaredefinedtalk.com/ads)! Recommendations Brandon: The Complete History & Strategy of Visa (https://www.acquired.fm/episodes/visa) Matt: Markdown in Google Docs (https://support.google.com/docs/answer/12014036) Google Docs to Markdown (https://workspace.google.com/marketplace/app/docs_to_markdown/700168918607) Coté: pork chops, preferably thin sliced. Photo Credits Header (https://unsplash.com/photos/bike-on-concrete-floor-j0zlzt40J-0) Artwork (https://unsplash.com/photos/person-holding-black-amazon-echo-dot-qQRrhMIpxPw)

Cette semaine : DOS_deck, une date pour Dragon's Dogma 2, Beyond Good and Evil, un remaster pour les 20 piges, Apps of the Year Apple, Stable Diffusion XL Turbo, Deck.blue pour Bluesky et Phanpy pour Mastodon, les Pixel 8 et 8 Pro de Google ont de l'acné, Graviton 4, le SoC made in Amazon, et le “miracle” du Huawei Kirin 9000S. Lisez plutôt Torréfaction #276 : DOS_deck, les 20 ans de BGE, Stable Diffusion XL Turbo, l'acné des Pixel 8 de Google et bien plus ! avec sa vraie mise en page sur Geekzone. Pensez à vos rétines.

Amazon announced that they will be using Nvidia's NVSwitch to create new rackscale AI platforms. This allows customers to use Nvidia technology like Grace Hopper or build something using AWS Nitro DPUs and Elastic Fabric Adapaters. That last combination doesn't use InfiniBand and moves to Ethernet. Two new chips are coming out from the Amazon labs. The first is Graviton4, the latest generation of Arm processor. Graviton4 has 50% more cores and 75% more memory bandwidth. This version of Graviton is based on the Demeter Neoverse V2 core. On the AI front Amazon also announced the next revision of their AI acceleration chip, Trainium2. This update has a 4x performance increase from the first generation and allows for liquid cooling. Trainium2 is designed to be deployed in clusters of 16 chips. In the data space, AWS made news with the GA of Bedrock, which enables customers to run foundational ML models from companies like Anthropic, Meta, and of course AWS itself. But many companies are worried about hallucination and want to include their own data in these models. That's what AWS is delivering with Guardrails, and what AWS partners are leaning into as well. This and more on this week's Gestalt IT Rundown. 0:00 - Welcome to the Rundown 1:18 - DAOS Foundation Launched for Object Storage 4:57 - Autonomous Purple Team annouced by Skyhawk at AWS re:Invent 8:26 - Couchbase's Capella Columnar Service Revealed 10:59 - Hackers Were Inside NXP For Two Years Before Detection 14:47 - AWS re:Invent Announcements 15:26 - NVSwitch For AI Nodes 20:46 - ARM V2 for Graviton4 and Trainium2 25:22 - AWS Guardrails for Bedrock 30:10 - The Weeks Ahead 33:10 - Thanks for Watching Follow our Hosts on Social Media Tom Hollingsworth: ⁠⁠https://www.twitter.com/NetworkingNerd⁠⁠ Stephen Foskett: ⁠⁠https://www.twitter.com/SFoskett⁠⁠  Follow Gestalt IT Website: ⁠⁠https://www.GestaltIT.com/⁠⁠ Twitter: ⁠⁠https://www.twitter.com/GestaltIT⁠⁠ LinkedIn: ⁠⁠https://www.linkedin.com/company/Gestalt-IT Tags: #Rundown, AI, #AWSreinvent, #AWS, #Storage, @SkyhawkCloudSec, @Couchbase, #Capella, #Data, #Security, #NXP, #China, @AWS, @NVIDIA, #GraceHopper, @Arm, #Graviton4, #Bedrock, @NetworkingNerd, @SFoskett, @GestaltIT,

Amir Szekely, Owner at CloudSnorkel, joins Corey on Screaming in the Cloud to discuss how he got his start in the early days of cloud and his solo project, CloudSnorkel. Throughout this conversation, Corey and Amir discuss the importance of being pragmatic when moving to the cloud, and the different approaches they see in developers from the early days of cloud to now. Amir shares what motivates him to develop open-source projects, and why he finds fulfillment in fixing bugs and operating CloudSnorkel as a one-man show. About AmirAmir Szekely is a cloud consultant specializing in deployment automation, AWS CDK, CloudFormation, and CI/CD. His background includes security, virtualization, and Windows development. Amir enjoys creating open-source projects like cdk-github-runners, cdk-turbo-layers, and NSIS.Links Referenced: CloudSnorkel: https://cloudsnorkel.com/ lasttootinaws.com: https://lasttootinaws.com camelcamelcamel.com: https://camelcamelcamel.com github.com/cloudsnorkel: https://github.com/cloudsnorkel Personal website: https://kichik.com 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, and this is an episode that I have been angling for for longer than you might imagine. My guest today is Amir Szekely, who's the owner at CloudSnorkel. Amir, thank you for joining me.Amir: Thanks for having me, Corey. I love being here.Corey: So, I've been using one of your open-source projects for an embarrassingly long amount of time, and for the longest time, I make the critical mistake of referring to the project itself as CloudSnorkel because that's the word that shows up in the GitHub project that I can actually see that jumps out at me. The actual name of the project within your org is cdk-github-runners if I'm not mistaken.Amir: That's real original, right?Corey: Exactly. It's like, “Oh, good, I'll just mention that, and suddenly everyone will know what I'm talking about.” But ignoring the problems of naming things well, which is a pain that everyone at AWS or who uses it knows far too well, the product is basically magic. Before I wind up basically embarrassing myself by doing a poor job of explaining what it is, how do you think about it?Amir: Well, I mean, it's a pretty simple project, which I think what makes it great as well. It creates GitHub runners with CDK. That's about it. It's in the name, and it just does that. And I really tried to make it as simple as possible and kind of learn from other projects that I've seen that are similar, and basically learn from my pain points in them.I think the reason I started is because I actually deployed CDK runners—sorry, GitHub runners—for one company, and I ended up using the Kubernetes one, right? So, GitHub in themselves, they have two projects they recommend—and not to nudge GitHub, please recommend my project one day as well—they have the Kubernetes controller and they have the Terraform deployer. And the specific client that I worked for, they wanted to use Kubernetes. And I tried to deploy it, and, Corey, I swear, I worked three days; three days to deploy the thing, which was crazy to me. And every single step of the way, I had to go and read some documentation, figure out what I did wrong, and apparently the order the documentation was was incorrect.And I had to—I even opened tickets, and they—you know, they were rightfully like, “It's open-source project. Please contribute and fix the documentation for us.” At that point, I said, “Nah.” [laugh]. Let me create something better with CDK and I decided just to have the simplest setup possible.So usually, right, what you end up doing in these projects, you have to set up either secrets or SSM parameters, and you have to prepare the ground and you have to get your GitHub token and all those things. And that's just annoying. So, I decided to create a—Corey: So much busy work.Amir: Yes, yeah, so much busy work and so much boilerplate and so much figuring out the right way and the right order, and just annoying. So, I decided to create a setup page. I thought, “What if you can actually install it just like you install any app on GitHub,” which is the way it's supposed to be right? So, when you install cdk-github-runners—CloudSnorkel—you get an HTML page and you just click a few buttons and you tell it where to install it and it just installs it for you. And it sets the secrets and everything. And if you want to change the secret, you don't have to redeploy. You can just change the secret, right? You have to roll the token over or whatever. So, it's much, much easier to install.Corey: And I feel like I discovered this project through one of the more surreal approaches—and I had cause to revisit it a few weeks ago when I was redoing my talk for the CDK Community Day, which has since happened and people liked the talk—and I mentioned what CloudSnorkel had been doing and how I was using the runners accordingly. So, that was what I accidentally caused me to pop back up with, “Hey, I've got some issues here.” But we'll get to that. Because once upon a time, I built a Twitter client for creating threads because shitposting is my love language, I would sit and create Twitter threads in the middle of live keynote talks. Threading in the native client was always terrible, and I wanted to build something that would help me do that. So, I did.And it was up for a while. It's not anymore because I'm not paying $42,000 a month in API costs to some jackass, but it still exists in the form of lasttootinaws.com if you want to create threads on Mastodon. But after I put this out, some people complained that it was slow.To which my response was, “What do you mean? It's super fast for me in San Francisco talking to it hosted in Oregon.” But on every round trip from halfway around the world, it became a problem. So, I got it into my head that since this thing was fully stateless, other than a Lambda function being fronted via an API Gateway, that I should deploy it to every region. It didn't quite fit into a Cloudflare Worker or into one of the Edge Lambda functions that AWS has given up on, but okay, how do I deploy something to every region?And the answer is, with great difficulty because it's clear that no one was ever imagining with all those regions that anyone would use all of them. It's imagined that most customers use two or three, but customers are different, so which two or three is going to be widely varied. So, anything halfway sensible about doing deployments like this didn't work out. Again, because this thing was also a Lambda function and an API Gateway, it was dirt cheap, so I didn't really want to start spending stupid amounts of money doing deployment infrastructure and the rest.So okay, how do I do this? Well, GitHub Actions is awesome. It is basically what all of AWS's code offerings wish that they were. CodeBuild is sad and this was kind of great. The problem is, once you're out of the free tier, and if you're a bad developer where you do a deploy on every iteration, suddenly it starts costing for what I was doing in every region, something like a quarter of per deploy, which adds up when you're really, really bad at programming.Amir: [laugh].Corey: So, their matrix jobs are awesome, but I wanted to do some self-hosted runners. How do I do that? And I want to keep it cheap, so how do I do a self-hosted runner inside of a Lambda function? Which led me directly to you. And it was nothing short of astonishing. This was a few years ago. I seem to recall that it used to be a bit less well-architected in terms of its elegance. Did it always use step functions, for example, to wind up orchestrating these things?Amir: Yeah, so I do remember that day. We met pretty much… basically as a joke because the Lambda Runner was a joke that I did, and I posted on Twitter, and I was half-proud of my joke that starts in ten seconds, right? But yeah, no, the—I think it always used functions. I've been kind of in love with the functions for the past two years. They just—they're nice.Corey: Oh, they're magic, and AWS is so bad at telling their story. Both of those things are true.Amir: Yeah. And the API is not amazing. But like, when you get it working—and you know, you have to spend some time to get it working—it's really nice because then you have nothing to manage, ever. And they can call APIs directly now, so you don't have to even create Lambdas. It's pretty cool.Corey: And what I loved is you wind up deploying this thing to whatever account you want it to live within. What is it, the OIDC? I always get those letters in the wrong direction. OIDC, I think, is correct.Amir: I think it's OIDC, yeah.Corey: Yeah, and it winds up doing this through a secure method as opposed to just okay, now anyone with access to the project can deploy into your account, which is not ideal. And it just works. It spins up a whole bunch of these Lambda functions that are using a Docker image as the deployment environment. And yeah, all right, if effectively my CDK deploy—which is what it's doing inside of this thing—doesn't complete within 15 minutes, then it's not going to and the thing is going to break out. We've solved the halting problem. After 15 minutes, the loop will terminate. The end.But that's never been a problem, even with getting ACM certificates spun up. It completes well within that time limit. And its cost to me is effectively nothing. With one key exception: that you made the choice to use Secrets Manager to wind up storing a lot of the things it cares about instead of Parameter Store, so I think you wind up costing me—I think there's two of those different secrets, so that's 80 cents a month. Which I will be demanding in blood one of these days if I ever catch you at re:Invent.Amir: I'll buy you beer [laugh].Corey: There we go. That'll count. That'll buy, like, several months of that. That works—at re:Invent, no. The beers there are, like, $18, so that'll cover me for years. We're set.Amir: We'll split it [laugh].Corey: Exactly. Problem solved. But I like the elegance of it, I like how clever it is, and I want to be very clear, though, it's not just for shitposting. Because it's very configurable where, yes, you can use Lambda functions, you can use Spot Instances, you can use CodeBuild containers, you can use Fargate containers, you can use EC2 instances, and it just automatically orchestrates and adds these self-hosted runners to your account, and every build gets a pristine environment as a result. That is no small thing.Amir: Oh, and I love making things configurable. People really appreciate it I feel, you know, and gives people kind of a sense of power. But as long as you make that configuration simple enough, right, or at least the defaults good defaults, right, then, even with that power, people still don't shoot themselves in the foot and it still works really well. By the way, we just added ECS recently, which people really were asking for because it gives you the, kind of, easy option to have the runner—well, not the runner but at least the runner infrastructure staying up, right? So, you can have auto-scaling group backing ECS and then the runner can start up a lot faster. It was actually very important to other people because Lambda, as fast that it is, it's limited, and Fargate, for whatever reason, still to this day, takes a minute to start up.Corey: Yeah. What's wild to me about this is, start to finish, I hit a deploy to the main branch and it sparks the thing up, runs the deploy. Deploy itself takes a little over two minutes. And every time I do this, within three minutes of me pushing to commit, the deploy is done globally. It is lightning fast.And I know it's easy to lose yourself in the idea of this being a giant shitpost, where, oh, who's going to do deployment jobs in Lambda functions? Well, kind of a lot of us for a variety of reasons, some of which might be better than others. In my case, it was just because I was cheap, but the massive parallelization ability to do 20 simultaneous deploys in a matrix configuration that doesn't wind up smacking into rate limits everywhere, that was kind of great.Amir: Yeah, we have seen people use Lambda a lot. It's mostly for, yeah, like you said, small jobs. And the environment that they give you, it's kind of limited, so you can't actually install packages, right? There is no sudo, and you can't actually install anything unless it's in your temp directory. But still, like, just being able to run a lot of little jobs, it's really great. Yeah.Corey: And you can also make sure that there's a Docker image ready to go with the stuff that you need, just by configuring how the build works in the CDK. I will admit, I did have a couple of bug reports for you. One was kind of useful, where it was not at all clear how to do this on top of a Graviton-based Lambda function—because yeah, that was back when not everything really supported ARM architectures super well—and a couple of other times when the documentation was fairly ambiguous from my perspective, where it wasn't at all clear, what was I doing? I spent four hours trying to beat my way through it, I give up, filed an issue, went to get a cup of coffee, came back, and the answer was sitting there waiting for me because I'm not convinced you sleep.Amir: Well, I am a vampire. My last name is from the Transylvania area [laugh]. So—Corey: Excellent. Excellent.Amir: By the way, not the first time people tell me that. But anyway [laugh].Corey: There's something to be said for getting immediate responsiveness because one of the reasons I'm always so loath to go and do a support ticket anywhere is this is going to take weeks. And then someone's going to come back with a, “I don't get it.” And try and, like, read the support portfolio to you. No, you went right into yeah, it's this. Fix it and your problem goes away. And sure enough, it did.Amir: The escalation process that some companies put you through is very frustrating. I mean, lucky for you, CloudSnorkel is a one-man show and this man loves solving bugs. So [laugh].Corey: Yeah. Do you know of anyone using it for anything that isn't ridiculous and trivial like what I'm using it for?Amir: Yeah, I have to think whether or not I can… I mean, so—okay. We have a bunch of dedicated users, right, the GitHub repo, that keep posting bugs and keep posting even patches, right, so you can tell that they're using it. I even have one sponsor, one recurring sponsor on GitHub that uses it.Corey: It's always nice when people thank you via money.Amir: Yeah. Yeah, it is very validating. I think [BLEEP] is using it, but I also don't think I can actually say it because I got it from the GitHub.Corey: It's always fun. That's the beautiful part about open-source. You don't know who's using this. You see what other things people are working on, and you never know, is one of their—is this someone's side project, is it a skunkworks thing, or God forbid, is this inside of every car going forward and no one bothered to tell me about that. That is the magic and mystery of open-source. And you've been doing open-source for longer than I have and I thought I was old. You were originally named in some of the WinAMP credits, for God's sake, that media player that really whipped the llama's ass.Amir: Oh, yeah, I started real early. I started about when I was 15, I think. I started off with Pascal or something or even Perl, and then I decided I have to learn C and I have to learn Windows API. I don't know what possessed me to do that. Win32 API is… unique [laugh].But once I created those applications for myself, right, I think there was—oh my God, do you know the—what is it called, Sherlock in macOS, right? And these days, for PowerToys, there is the equivalent of it called, I don't know, whatever that—PowerBar? That's exactly—that was that. That's a project I created as a kid. I wanted something where I can go to the Run menu of Windows when you hit Winkey R, and you can just type something and it will start it up, right?I didn't want to go to the Start menu and browse and click things. I wanted to do everything with the keyboard. So, I created something called Blazerun [laugh], which [laugh] helped you really easily create shortcuts that went into your path, right, the Windows path, so you can really easily start them from Winkey R. I don't think that anyone besides me used it, but anyway, that thing needed an installer, right? Because Windows, you got to install things. So, I ended up—Corey: Yeah, these days on Mac OS, I use Alfred for that which is kind of long in the tooth, but there's a launch bar and a bunch of other stuff for it. What I love is that if I—I can double-tap the command key and that just pops up whatever I need it to and tell the computer what to do. It feels like there's an AI play in there somewhere if people can figure out how to spend ten minutes on building AI that does something other than lets them fire their customer service staff.Amir: Oh, my God. Please don't fire customer service staff. AI is so bad.Corey: Yeah, when I reach out to talk to a human, I really needed a human.Amir: Yes. Like, I'm not calling you because I want to talk to a robot. I know there's a website. Leave me alone, just give me a person.Corey: Yeah. Like, you already failed to solve my problem on your website. It's person time.Amir: Exactly. Oh, my God. Anyway [laugh]. So, I had to create an installer, right, and I found it was called NSIS. So, it was a Nullsoft “SuperPiMP” installation system. Or in the future, when Justin, the guy who created Winamp and NSIS, tried to tone down a little bit, Nullsoft Scriptable Installation System. And SuperPiMP is—this is such useless history for you, right, but SuperPiMP is the next generation of PiMP which is Plug-in Mini Packager [laugh].Corey: I remember so many of the—like, these days, no one would ever name any project like that, just because it's so off-putting to people with sensibilities, but back then that was half the stuff that came out. “Oh, you don't like how this thing I built for free in the wee hours when I wasn't working at my fast food job wound up—you know, like, how I chose to name it, well, that's okay. Don't use it. Go build your own. Oh, what you're using it anyway. That's what I thought.”Amir: Yeah. The source code was filled with profanity, too. And like, I didn't care, I really did not care, but some people would complain and open bug reports and patches. And my policy was kind of like, okay if you're complaining, I'm just going to ignore you. If you're opening a patch, fine, I'm going to accept that you're—you guys want to create something that's sensible for everybody, sure.I mean, it's just source code, you know? Whatever. So yeah, I started working on that NSIS. I used it for myself and I joined the forums—and this kind of answers to your question of why I respond to things so fast, just because of the fun—I did the same when I was 15, right? I started going on the forums, you remember forums? You remember that [laugh]?Corey: Oh, yeah, back before they all became terrible and monetized.Amir: Oh, yeah. So, you know, people were using NSIS, too, and they had requests, right? They wanted. Back in the day—what was it—there was only support for 16-bit colors for the icon, so they want 32-bit colors and big colors—32—big icon, sorry, 32 pixels by 32 pixels. Remember, 32 pixels?Corey: Oh, yes. Not well, and not happily, but I remember it.Amir: Yeah. So, I started just, you know, giving people—working on that open-source and creating up a fork. It wasn't even called ‘fork' back then, but yeah, I created, like, a little fork of myself and I started adding all these features. And people were really happy, and kind of created, like, this happy cycle for myself: when people were happy, I was happy coding. And then people were happy by what I was coding. And then they were asking for more and they were getting happier, the more I responded.So, it was kind of like a serotonin cycle that made me happy and made everybody happy. So, it's like a win, win, win, win, win. And that's how I started with open-source. And eventually… NSIS—again, that installation system—got so big, like, my fork got so big, and Justin, the guy who works on WinAMP and NSIS, he had other things to deal with. You know, there's a whole history there with AOL. I'm sure you've heard all the funny stories.Corey: Oh, yes. In fact, one thing that—you want to talk about weird collisions of things crossing, one of the things I picked up from your bio when you finally got tired of telling me no and agreed to be on the show was that you're also one of the team who works on camelcamelcamel.com. And I keep forgetting that's one of those things that most people have no idea exists. But it's very simple: all it does is it tracks Amazon products that you tell it to and alerts you when there's a price drop on the thing that you're looking at.It's something that is useful. I try and use it for things of substance or hobbies because I feel really pathetic when I'm like, get excited emails about a price drop in toilet paper. But you know, it's very handy just to keep an idea for price history, where okay, am I actually being ripped off? Oh, they claim it's their big Amazon Deals day and this is 40% off. Let's see what camelcamelcamel has to say.Oh, surprise. They just jacked the price right beforehand and now knocked 40% off. Genius. I love that. It always felt like something that was going to be blown off the radar by Amazon being displeased, but I discovered you folks in 2010 and here you are now, 13 years later, still here. I will say the website looks a lot better now.Amir: [laugh]. That's a recent change. I actually joined camel, maybe two or three years ago. I wasn't there from the beginning. But I knew the guy who created it—again, as you were saying—from the Winamp days, right? So, we were both working in the free—well, it wasn't freenode. It was not freenode. It was a separate IRC server that, again, Justin created for himself. It was called landoleet.Corey: Mmm. I never encountered that one.Amir: Yeah, no, it was pretty private. The only people that cared about WinAMP and NSIS ended up joining there. But it was a lot of fun. I met a lot of friends there. And yeah, I met Daniel Green there as well, and he's the guy that created, along with some other people in there that I think want to remain anonymous so I'm not going to mention, but they also were on the camel project.And yeah, I was kind of doing my poor version of shitposting on Twitter about AWS, kind of starting to get some traction and maybe some clients and talk about AWS so people can approach me, and Daniel approached me out of the blue and he was like, “Do you just post about AWS on Twitter or do you also do some AWS work?” I was like, “I do some AWS work.”Corey: Yes, as do all of us. It's one of those, well crap, we're getting called out now. “Do you actually know how any of this stuff works?” Like, “Much to my everlasting shame, yes. Why are you asking?”Amir: Oh, my God, no, I cannot fix your printer. Leave me alone.Corey: Mm-hm.Amir: I don't want to fix your Lambdas. No, but I do actually want to fix your Lambdas. And so, [laugh] he approached me and he asked if I can help them move camelcamelcamel from their data center to AWS. So, that was a nice big project. So, we moved, actually, all of camelcamelcamel into AWS. And this is how I found myself not only in the Winamp credits, but also in the camelcamelcamel credits page, which has a great picture of me riding a camel.Corey: Excellent. But one of the things I've always found has been that when you take an application that has been pre-existing for a while in a data center and then move it into the cloud, you suddenly have to care about things that no one sensible pays any attention to in the land of the data center. Because it's like, “What do I care about how much data passes between my application server and the database? Wait, what do you mean that in this configuration, that's a chargeable data transfer? Oh, dear Lord.” And things that you've never had to think about optimizing are suddenly things are very much optimizing.Because let's face it, when it comes to putting things in racks and then running servers, you aren't auto-scaling those things, so everything tends to be running over-provisioned, for very good reasons. It's an interesting education. Anything you picked out from that process that you think it'd be useful for folks to bear in mind if they're staring down the barrel of the same thing?Amir: Yeah, for sure. I think… in general, right, not just here. But in general, you always want to be pragmatic, right? You don't want to take steps are huge, right? So, the thing we did was not necessarily rewrite everything and change everything to AWS and move everything to Lambda and move everything to Docker.Basically, we did a mini lift-and-shift, but not exactly lift-and-shift, right? We didn't take it as is. We moved to RDS, we moved to ElastiCache, right, we obviously made use of security groups and session connect and we dropped SSH Sage and we improved the security a lot and we locked everything down, all the permissions and all that kind of stuff, right? But like you said, there's stuff that you start having to pay attention to. In our case, it was less the data transfer because we have a pretty good CDN. There was more of IOPS. So—and IOPS, specifically for a database.We had a huge database with about one terabyte of data and a lot of it is that price history that you see, right? So, all those nice little graphs that we create in—what do you call them, charts—that we create in camelcamelcamel off the price history. There's a lot of data behind that. And what we always want to do is actually remove that from MySQL, which has been kind of struggling with it even before the move to AWS, but after the move to AWS, where everything was no longer over-provisioned and we couldn't just buy a few more NVMes on Amazon for 100 bucks when they were on sale—back when we had to pay Amazon—Corey: And you know, when they're on sale. That's the best part.Amir: And we know [laugh]. We get good prices on NVMe. But yeah, on Amazon—on AWS, sorry—you have to pay for io1 or something, and that adds up real quick, as you were saying. So, part of that move was also to move to something that was a little better for that data structure. And we actually removed just that data, the price history, the price points from MySQL to DynamoDB, which was a pretty nice little project.Actually, I wrote about it in my blog. There is, kind of, lessons learned from moving one terabyte from MySQL to DynamoDB, and I think the biggest lesson was about hidden price of storage in DynamoDB. But before that, I want to talk about what you asked, which was the way that other people should make that move, right? So again, be pragmatic, right? If you Google, “How do I move stuff from DynamoDB to MySQL,” everybody's always talking about their cool project using Lambda and how you throttle Lambda and how you get throttled from DynamoDB and how you set it up with an SQS, and this and that. You don't need all that.Just fire up an EC2 instance, write some quick code to do it. I used, I think it was Go with some limiter code from Uber, and that was it. And you don't need all those Lambdas and SQS and the complication. That thing was a one-time thing anyway, so it doesn't need to be super… super-duper serverless, you know?Corey: That is almost always the way that it tends to play out. You encounter these weird little things along the way. And you see so many things that are tied to this is how architecture absolutely must be done. And oh you're not a real serverless person if you don't have everything running in Lambda and the rest. There are times where yeah, spin up an EC2 box, write some relatively inefficient code in ten minutes and just do the thing, and then turn it off when you're done. Problem solved. But there's such an aversion to that. It's nice to encounter people who are pragmatists more than they are zealots.Amir: I mostly learned that lesson. And both Daniel Green and me learned that lesson from the Winamp days. Because we both have written plugins for Winamp and we've been around that area and you can… if you took one of those non-pragmatist people, right, and you had them review the Winamp code right now—or even before—they would have a million things to say. That code was—and NSIS, too, by the way—and it was so optimized. It was so not necessarily readable, right? But it worked and it worked amazing. And Justin would—if you think I respond quickly, right, Justin Frankel, the guy who wrote Winamp, he would release versions of NSIS and of Winamp, like, four versions a day, right? That was before [laugh] you had CI/CD systems and GitHub and stuff. That was just CVS. You remember CVS [laugh]?Corey: Oh, I've done multiple CVS migrations. One to Git and a couple to Subversion.Amir: Oh yeah, Subversion. Yep. Done ‘em all. CVS to Subversion to Git. Yep. Yep. That was fun.Corey: And these days, everyone's using Git because it—we're beginning to have a monoculture.Amir: Yeah, yeah. I mean, but Git is nicer than Subversion, for me, at least. I've had more fun with it.Corey: Talk about damning with faint praise.Amir: Faint?Corey: Yeah, anything's better than Subversion, let's be honest here.Amir: Oh [laugh].Corey: I mean, realistically, copying a bunch of files and directories to a.bak folder is better than Subversion.Amir: Well—Corey: At least these days. But back then it was great.Amir: Yeah, I mean, the only thing you had, right [laugh]?Corey: [laugh].Amir: Anyway, achieving great things with not necessarily the right tools, but just sheer power of will, that's what I took from the Winamp days. Just the entire world used Winamp. And by the way, the NSIS project that I was working on, right, I always used to joke that every computer in the world ran my code, every Windows computer in the world when my code, just because—Corey: Yes.Amir: So, many different companies use NSIS. And none of them cared that the code was not very readable, to put it mildly.Corey: So, many companies founder on those shores where they lose sight of the fact that I can point to basically no companies that died because their code was terrible, yeah, had an awful lot that died with great-looking code, but they didn't nail the business problem.Amir: Yeah. I would be lying if I said that I nailed exactly the business problem at NSIS because the most of the time I would spend there and actually shrinking the stub, right, there was appended to your installer data, right? So, there's a little stub that came—the executable, basically, that came before your data that was extracted. I spent, I want to say, years of my life [laugh] just shrinking it down by bytes—by literal bytes—just so it stays under 34, 35 kilobytes. It was kind of a—it was a challenge and something that people appreciated, but not necessarily the thing that people appreciate the most. I think the features—Corey: Well, no I have to do the same thing to make sure something fits into a Lambda deployment package. The scale changes, the problem changes, but somehow everything sort of rhymes with history.Amir: Oh, yeah. I hope you don't have to disassemble code to do that, though because that's uh… I mean, it was fun. It was just a lot.Corey: I have to ask, how much work went into building your cdk-github-runners as far as getting it to a point of just working out the door? Because I look at that and it feels like there's—like, the early versions, yeah, there wasn't a whole bunch of code tied to it, but geez, the iterative, “How exactly does this ridiculous step functions API work or whatnot,” feels like I'm looking at weeks of frustration. At least it would have been for me.Amir: Yeah, yeah. I mean, it wasn't, like, a day or two. It was definitely not—but it was not years, either. I've been working on it I think about a year now. Don't quote me on that. But I've put a lot of time into it. So, you know, like you said, the skeleton code is pretty simple: it's a step function, which as we said, takes a long time to get right. The functions, they are really nice, but their definition language is not very straightforward. But beyond that, right, once that part worked, it worked. Then came all the bug reports and all the little corner cases, right? We—Corey: Hell is other people's use cases. Always is. But that's honestly better than a lot of folks wind up experiencing where they'll put an open-source project up and no one ever knows. So, getting users is often one of the biggest barriers to a lot of this stuff. I've found countless hidden gems lurking around on GitHub with a very particular search for something that no one had ever looked at before, as best I can tell.Amir: Yeah.Corey: Open-source is a tricky thing. There needs to be marketing brought into it, there needs to be storytelling around it, and has to actually—dare I say—solve a problem someone has.Amir: I mean, I have many open-source projects like that, that I find super useful, I created for myself, but no one knows. I think cdk-github-runners, I'm pretty sure people know about it only because you talked about it on Screaming in the Cloud or your newsletter. And by the way, thank you for telling me that you talked about it last week in the conference because now we know why there was a spike [laugh] all of a sudden. People Googled it.Corey: Yeah. I put links to it as well, but it's the, yeah, I use this a lot and it's great. I gave a crappy explanation on how it works, but that's the trick I've found between conference talks and, dare I say, podcast episodes, you gives people a glimpse and a hook and tell them where to go to learn more. Otherwise, you're trying to explain every nuance and every intricacy in 45 minutes. And you can't do that effectively in almost every case. All you're going to do is drive people away. Make it sound exciting, get them to see the value in it, and then let them go.Amir: You have to explain the market for it, right? That's it.Corey: Precisely.Amir: And I got to say, I somewhat disagree with your—or I have a different view when you say that, you know, open-source projects needs marketing and all those things. It depends on what open-source is for you, right? I don't create open-source projects so they are successful, right? It's obviously always nicer when they're successful, but—and I do get that cycle of happiness that, like I was saying, people create bugs and I have to fix them and stuff, right? But not every open-source project needs to be a success. Sometimes it's just fun.Corey: No. When I talk about marketing, I'm talking about exactly what we're doing here. I'm not talking take out an AdWords campaign or something horrifying like that. It's you build something that solved the problem for someone. The big problem that worries me about these things is how do you not lose sleep at night about the fact that solve someone's problem and they don't know that it exists?Because that drives me nuts. I've lost count of the number of times I've been beating my head against a wall and asked someone like, “How would you handle this?” Like, “Oh, well, what's wrong with this project?” “What do you mean?” “Well, this project seems to do exactly what you want it to do.” And no one has it all stuffed in their head. But yeah, then it seems like open-source becomes a little more corporatized and it becomes a lead gen tool for people to wind up selling their SaaS services or managed offerings or the rest.Amir: Yeah.Corey: And that feels like the increasing corporatization of open-source that I'm not a huge fan of.Amir: Yeah. I mean, I'm not going to lie, right? Like, part of why I created this—or I don't know if it was part of it, but like, I had a dream that, you know, I'm going to get, oh, tons of GitHub sponsors, and everybody's going to use it and I can retire on an island and just make money out of this, right? Like, that's always a dream, right? But it's a dream, you know?And I think bottom line open-source is… just a tool, and some people use it for, like you were saying, driving sales into their SaaS, some people, like, may use it just for fun, and some people use it for other things. Or some people use it for politics, even, right? There's a lot of politics around open-source.I got to tell you a story. Back in the NSIS days, right—talking about politics—so this is not even about politics of open-source. People made NSIS a battleground for their politics. We would have translations, right? People could upload their translations. And I, you know, or other people that worked on NSIS, right, we don't speak every language of the world, so there's only so much we can do about figuring out if it's a real translation, if it's good or not.Back in the day, Google Translate didn't exist. Like, these days, we check Google Translate, we kind of ask a few questions to make sure they make sense. But back in the day, we did the best that we could. At some point, we got a patch for Catalan language, I'm probably mispronouncing it—but the separatist people in Spain, I think, and I didn't know anything about that. I was a young kid and… I just didn't know.And I just included it, you know? Someone submitted a patch, they worked hard, they wanted to be part of the open-source project. Why not? Sure I included it. And then a few weeks later, someone from Spain wanted to change Catalan into Spanish to make sure that doesn't exist for whatever reason.And then they just started fighting with each other and started making demands of me. Like, you have to do this, you have to do that, you have to delete that, you have to change the name. And I was just so baffled by why would someone fight so much over a translation of an open-source project. Like, these days, I kind of get what they were getting at, right?Corey: But they were so bad at telling that story that it was just like, so basically, screw, “You for helping,” is how it comes across.Amir: Yeah, screw you for helping. You're a pawn now. Just—you're a pawn unwittingly. Just do what I say and help me in my political cause. I ended up just telling both of them if you guys can agree on anything, I'm just going to remove both translations. And that's what I ended up doing. I just removed both translations. And then a few months later—because we had a release every month basically, I just added both of them back and I've never heard from them again. So sort of problem solved. Peace the Middle East? I don't know.Corey: It's kind of wild just to see how often that sort of thing tends to happen. It's a, I don't necessarily understand why folks are so opposed to other people trying to help. I think they feel like there's this loss of control as things are slipping through their fingers, but it's a really unwelcoming approach. One of the things that got me deep into the open-source ecosystem surprisingly late in my development was when I started pitching in on the SaltStack project right after it was founded, where suddenly everything I threw their way was merged, and then Tom Hatch, the guy who founded the project, would immediately fix all the bugs and stuff I put in and then push something else immediately thereafter. But it was such a welcoming thing.Instead of nitpicking me to death in the pull request, it just got merged in and then silently fixed. And I thought that was a classy way to do it. Of course, it doesn't scale and of course, it causes other problems, but I envy the simplicity of those days and just the ethos behind that.Amir: That's something I've learned the last few years, I would say. Back in the NSIS day, I was not like that. I nitpicked. I nitpicked a lot. And I can guess why, but it just—you create a patch—in my mind, right, like you create a patch, you fix it, right?But these days I get, I've been on the other side as well, right? Like I created patches for open-source projects and I've seen them just wither away and die, and then five years later, someone's like, “Oh, can you fix this line to have one instead of two, and then I'll merge it.” I'm like, “I don't care anymore. It was five years ago. I don't work there anymore. I don't need it. If you want it, do it.”So, I get it these days. And these days, if someone creates a patch—just yesterday, someone created a patch to format cdk-github-runners in VS Code. And they did it just, like, a little bit wrong. So, I just fixed it for them and I approved it and pushed it. You know, it's much better. You don't need to bug people for most of it.Corey: You didn't yell at them for having the temerity to contribute?Amir: My voice is so raw because I've been yelling for five days at them, yeah.Corey: Exactly, exactly. I really want to thank you for taking the time to chat with me about how all this stuff came to be and your own path. If people want to learn more, where's the best place for them to find you?Amir: So, I really appreciate you having me and driving all this traffic to my projects. If people want to learn more, they can always go to cloudsnorkel.com; it has all the projects. github.com/cloudsnorkel has a few more. And then my private blog is kichik.com. So, K-I-C-H-I-K dot com. I don't post there as much as I should, but it has some interesting AWS projects from the past few years that I've done.Corey: And we will, of course, put links to all of that in the show notes. Thank you so much for taking the time. I really appreciate it.Amir: Thank you, Corey. It was really nice meeting you.Corey: Amir Szekely, owner of CloudSnorkel. 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 comment. Heck, put it on all of the podcast platforms with a step function state machine that you somehow can't quite figure out how the API works.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.

Join AWS Go To Market leader Tim Henderson as he introduces us to Amazon's Graviton processor. Learn how Graviton is able to deliver better performance with less cost. We also discuss the types of cloud workloads that are best suited for running on Graviton. We conclude with resources to help you get started with Graviton:https://aws.amazon.com/ec2/graviton/fast-start/https://github.com/aws/porting-advisor-for-gravitonAWS Hosts: Nolan Chen & Malini ChatterjeeEmail Your Feedback: rethinkpodcast@amazon.com

YouTube link https://youtu.be/g12qyToQ4gI Lawrence Krauss dives into dark energy's evolving role, the matter-antimatter conundrum, and the significance of consciousness in our cosmos. - Patreon: https://patreon.com/curtjaimungal (early access to ad-free audio episodes!) - Crypto: https://tinyurl.com/cryptoTOE - PayPal: https://tinyurl.com/paypalTOE - Twitter: https://twitter.com/TOEwithCurt - Discord Invite: https://discord.com/invite/kBcnfNVwqs - iTunes: https://podcasts.apple.com/ca/podcast/better-left-unsaid-with-curt-jaimungal/id1521758802 - Pandora: https://pdora.co/33b9lfP - Spotify: https://open.spotify.com/show/4gL14b92xAErofYQA7bU4e - Subreddit r/TheoriesOfEverything: https://reddit.com/r/theoriesofeverything - TOE Merch: https://tinyurl.com/TOEmerch LINKS MENTIONED: - Edge of Knowledge (Lawrence Krauss): https://amzn.to/3RTsxci - Universe of Nothing (Lawrence Krauss): https://amzn.to/3S9RG2D - The Greatest Story Ever Told So Far (Lawrence Krauss): https://amzn.to/46orPIh - The Physics of Climate Change (Lawrence Krauss): https://amzn.to/46nlVqY - The Black Cloud (Fred Hoyle): https://amzn.to/45qPxm3 - Podcast w/ Brian Keating on TOE: https://youtu.be/AzsZO3_WhDA - Discussion on the detection of gravitational waves - Explanation of CP violation and leptogenesis in the context of neutrinos - Podcast w/ Edward Frenkel on TOE: https://youtu.be/n_oPMcvHbAc TIMESTAMPS: - 00:00:00 Introduction - 00:02:10 Pushing modern physics beyond its frontier - 00:03:00 Writing and the art of asking questions - 00:08:07 Unearthing the roots of consciousness - 00:12:00 Origins of the universe & quantum fluctuations - 00:20:13 Infinite existence (Dyson's arguments) - 00:27:08 Graviton detection impossibility? - 00:30:13 Inflationary models and multiverses - 00:35:05 Neutrinos, leptogenesis, CP violation, and why we're here - 00:46:46 Infinities and renormalization (Feynman's "dippy process") - 00:48:00 Dark matter: particle or modified gravity? - 00:51:58 Higgs field as a Bose-Einstein condensate Learn more about your ad choices. Visit megaphone.fm/adchoices

This week, we discuss paying ransom to cyberattackers, an overview of the "Infrastructure as Code" market, and remote worker productivity. Plus, Matt provides a review of the Raspberry 5 and shares his reasons for refusing to install the Global Entry Mobile App. Watch the YouTube Live Recording of Episode (https://www.youtube.com/live/6vmdE20_Eak?si=qcONahAxeLtl2Fc5) 435 (https://www.youtube.com/live/6vmdE20_Eak?si=qcONahAxeLtl2Fc5) Runner-up Titles All my takes are spicy, once I get enough caffeine We're doing this for science No, just no, Dad No exceeding expectations in that role I will do horrible things with YAML My business is my business They don't have room for purity Rundown Emergency broadcast (https://apnews.com/article/ee3a3039a5cf452a8f307c8f6f8dcbf3) not (https://apnews.com/article/ee3a3039a5cf452a8f307c8f6f8dcbf3) used by Trump (https://apnews.com/article/ee3a3039a5cf452a8f307c8f6f8dcbf3) CBP announces new (https://www.cbp.gov/newsroom/national-media-release/cbp-announces-new-global-entry-mobile-app) MGM, Caesars Cyberattack Responses Required Brutal Choices (https://www.darkreading.com/application-security/mgm-caesars-incident-responses-required-brutal-choices) Creator of Ansible ships "Jetporch" (https://github.com/jetporch/jetporch) Cloud startup Pulumi raises $41M from Madrona, NEA to grow ‘infrastructure as code' platform (https://www.geekwire.com/2023/cloud-startup-pulumi-raises-41m-from-madrona-nea-to-grow-infrastructure-as-code-platform/) Red Hat bins Bugzilla for RHEL issue tracking, jumps on Jira (https://www.theregister.com/2023/09/29/red_hat_bugzilla_jira_migration/) Work From Home Works - Marginal REVOLUTION (https://marginalrevolution.com/marginalrevolution/2023/10/work-from-home-works.html?utm_source=rss&utm_medium=rss&utm_campaign=work-from-home-works) The Raspberry Pi 5 is finally here (https://www.theverge.com/2023/9/28/23889238/raspberry-pi-5-specs-availability-pricing) Relevant to your Interests OpenAI Seeks New Valuation of Up to $90 Billion in Sale of Existing Shares (https://www.wsj.com/tech/ai/openai-seeks-new-valuation-of-up-to-90-billion-in-sale-of-existing-shares-ed6229e0) Epic Games Asks Supreme Court to Hear Apple Case (https://www.macrumors.com/2023/09/27/epic-games-supreme-court/) FCC announces plans to reinstate net neutrality (https://techcrunch.com/2023/09/26/fcc-announces-plans-to-reinstate-net-neutrality/) Mark Zuckerberg reveals Meta AI chatbot, his answer to ChatGPT (https://cointelegraph.com/news/meta-ai-ceo-mark-zuckerberg-unveil-chatbot-rayban-metaverse) Epic Games cuts around 830 jobs (https://www.theverge.com/2023/9/28/23894266/epic-games-layoffs-fortnite-unreal-engine) How Swiggy migrated its k8s workload to Graviton (https://bytes.swiggy.com/how-swiggy-migrated-its-k8s-workload-to-graviton-d2643bbc7871) Passkeys: all the news and updates around passwordless sign-on (https://www.theverge.com/2023/9/29/23895518/passkey-passwordless-login-announcements-news-updates) The potential gap (https://open.substack.com/pub/benn/p/the-potential-gap?r=2d4o&utm_medium=ios&utm_campaign=post) Apple acknowledges hot iPhone 15 Pros, says software fixes are coming (https://www.yahoo.com/news/apple-acknowledges-hot-iphone-15-215031767.html) What's next for VMware? Long-term Virtzilla-watchers opine (https://www.theregister.com/2023/10/02/vmware_broadcom_pundit_predictions/) Bill Ackman reportedly said he would 'absolutely' do a deal with X with his new SPARC funding vehicle (https://www.cnbc.com/2023/10/01/bill-ackman-would-absolutely-do-a-deal-with-x-with-his-new-sparc.html) Open source Datadog rival SigNoz lands on the cloud with $6.5M investment (https://techcrunch.com/2023/09/28/open-source-datadog-rival-signoz-lands-on-the-cloud-with-6-5m-investment/) Okta acquires a16z-backed password manager Uno to develop a personal tier (https://techcrunch.com/2023/10/04/okta-acquires-a16z-backed-password-manager-uno-to-develop-a-personal-tier/) Amazon Used Secret ‘Project Nessie' Algorithm to Raise Prices (https://www.wsj.com/business/retail/amazon-used-secret-project-nessie-algorithm-to-raise-prices-6c593706?st=9ubhqeyjqgu0b2x&reflink=mobilewebshare_permalink) Look what ChatGPT vision can do. (https://twitter.com/_borriss_/status/1707412406048063788) Voice and Video Demos with ChatGPT, How AI Could Redeem Meta's Mixed Reality Bets, OpenAI Explores Hardware (https://overcast.fm/+8XV3Zc4Pg) AI, Hardware, and Virtual Reality (https://stratechery.com/2023/ai-hardware-and-virtual-reality/) The Senate's email system melted down in the face of security test and reply-all chaos. (https://www.politico.com/minutes/congress/09-8-2023/senate-reply-all-mess/) Nonsense Costco is selling gold bars and they are selling out within a few hours (https://www.cnbc.com/2023/09/27/costco-is-selling-gold-bars-and-they-are-selling-out-within-a-few-hours.html) Costco Offers Members $29 Online Health Care Visits (https://www.bloomberg.com/news/articles/2023-09-25/costco-offers-health-care-to-members-in-deal-with-sesame-cost?cmpid=socialflow-twitter-business&utm_source=twitter&utm_content=business&utm_medium=social&utm_campaign=socialflow-organic) Conferences Oct 9th Spring Tour Amsterdam (https://connect.tanzu.vmware.com/EMEA_P7_DG_FE_Q324_Event_S1TourAmsterdam_TanzuLP-AltS1TBanner.html?utm_source=cote&utm_campaign=devrel&utm_medium=newsletter&utm_content=newsletterUpcoming) Oct 10th, 17th, 24th talk series: Building a Path to Production: A Guide for Managers and Leaders in Platform Engineering (https://series.brighttalk.com/series/6011/?utm_source=cote&utm_campaign=devrel&utm_medium=newsletter&utm_content=newsletterUpcoming) November 6-9, 2023, KubeCon NA (https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/), SDT's a sponsor, Matt's there November 6-9, 2023 VMware Explore Barcelona (https://www.vmware.com/explore/eu.html), Coté's attending Jan 29, 2024 to Feb 1, 2024 That Conference Texas (https://that.us/events/tx/2024/schedule/) If you want your conference mentioned, let's talk media sponsorships. SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Get a SDT Sticker! Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Follow us: Twitch (https://www.twitch.tv/sdtpodcast), Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/), Mastodon (https://hachyderm.io/@softwaredefinedtalk), BlueSky (https://bsky.app/profile/softwaredefinedtalk.com), LinkedIn (https://www.linkedin.com/company/software-defined-talk/), TikTok (https://www.tiktok.com/@softwaredefinedtalk), Threads (https://www.threads.net/@softwaredefinedtalk) and YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured). Use the code SDT to get $20 off Coté's book, Digital WTF (https://leanpub.com/digitalwtf/c/sdt), so $5 total. Become a sponsor of Software Defined Talk (https://www.softwaredefinedtalk.com/ads)! Recommendations Brandon: Dental Monitoring (https://dentalmonitoring.com) and Anker Magsafe Battery (https://www.amazon.com/Anker-PowerCore-Magnetic-Slim-B2C/dp/B099284SRR/ref=sr_1_2_sspa?crid=3JIBPD0L930O5&keywords=anker+magsafe+charger&qid=1696440885&sprefix=anker+mag%2Caps%2C170&sr=8-2-spons&sp_csd=d2lkZ2V0TmFtZT1zcF9hdGY&psc=1) Matt: Search Engine podcast: Wait, should I not be drinking airplane coffee? (https://podcasts.apple.com/au/podcast/wait-should-i-not-be-drinking-airplane-coffee/id1614253637?i=1000619792437) Photo Credits Header (https://unsplash.com/photos/GGewLGcQD-I)

Ever wondered what goes on behind the scenes of your favorite video games? Dive into this latest episode as Brooke and Dave team up with Matt Trescot, the mastermind behind AWS Games Solutions Architecture Team. From being the lone ranger handling AWS support on Sundays to leading a team that collaborates with over 2,000 game industry customers, Matt's journey is nothing short of epic! Discover the unique challenges and opportunities that cloud services bring to the gaming world. Get insights on the balance between performance and availability, and the exciting shift towards Graviton processors.

Are we thinking about the fundamentals of the universe wrong? Neil deGrasse Tyson and co-hosts Chuck Nice and Gary O'Reilly answer grab bag questions about aliens, gravitons, and the big unknowns with astrophysicist Charles Liu.NOTE: StarTalk+ Patrons can listen to this entire episode commercial-free here: https://startalkmedia.com/show/cosmic-queries-quantum-aliens-with-charles-liu/Thanks to our Patrons Karim Beydoun, Sture Seljelund, Ken Hays, Kasi Kanniah, Dillon, Mandi McKay, and Phillida Hutcheson for supporting us this week.Photo Credit: NASA Hubble, CC BY 2.0, via Wikimedia Commons

YouTube link: https://youtu.be/NKOd8imBa2s Prof. Jonathan Oppenheim focuses on the stochastic coupling between quantum mechanics and gravity, offering alternative views to loop quantum gravity and string theory. - Patreon: https://patreon.com/curtjaimungal (early access to ad-free audio episodes!) - Crypto: https://tinyurl.com/cryptoTOE - PayPal: https://tinyurl.com/paypalTOE - Twitter: https://twitter.com/TOEwithCurt - Discord Invite: https://discord.com/invite/kBcnfNVwqs - iTunes: https://podcasts.apple.com/ca/podcast/better-left-unsaid-with-curt-jaimungal/id1521758802 - Pandora: https://pdora.co/33b9lfP - Spotify: https://open.spotify.com/show/4gL14b92xAErofYQA7bU4e - Subreddit r/TheoriesOfEverything: https://reddit.com/r/theoriesofeverything - TOE Merch: https://tinyurl.com/TOEmerch LINKS MENTIONED: - Podcast w/ Nicholas Gisin on TOE: https://youtu.be/jcHzgy0I6gk - Jonathan Oppenheim's Quanta video: https://www.youtube.com/watch?v=DkRbNXILroI - Chapel Hill Conference Documentary on Quantum Gravity (Curt Jaimungal): https://youtu.be/eBA3RUxkZdc - The Second Laws of Quantum Thermodynamics: https://arxiv.org/abs/1305.5278 - Podcast w/ Chiara Marletto on TOE: COMING SOON https://youtube.com/TheoriesOfEverything - Podcast with Lue Elizondo on TOE: https://youtu.be/wULw64ZL1Bg - Podcast with Edward Frankel on TOE: https://youtu.be/n_oPMcvHbAc - Podcast w/ Theo Von on TOE: https://youtu.be/1cziCepYeEM?t=4673 - Podcast w/ Joscha Bach on TOE: https://youtu.be/3MNBxfrmfmI - Podcast w/ Noam Chomsky on TOE: https://www.youtube.com/playlist?list=PLZ7ikzmc6zlORiRfcaQe8ZdxKxF-e2BCY - Podcast w/ Stephen Wolfram on TOE: https://youtu.be/1sXrRc3Bhrs - Every TOE Playlist: https://www.youtube.com/@TheoriesofEverything/playlists TIMESTAMPS: - 00:00:00 Introduction - 00:02:37 Integrating general relativity and quantum theory - 00:05:18 The nature of classical mechanics - 00:10:12 Discrete vs continuous space in physics - 00:13:32 Boundary of physics and philosophy - 00:18:44 Post-quantum theory of classical gravity - 00:20:00 Mongrel relativity - 00:24:00 The issue of causal structure in quantum theory of gravity - 00:27:18 Gravity and string theory - 00:34:26 Quantum-classical system coupling (Feynman's position) - 00:45:31 Quantum vs post-quantum noise - 00:58:08 Quantum thermodynamics and the multiple Second Laws - 01:03:35 No-go theorem and classical gravity - 01:06:09 Bohmian mechanics vs many-worlds - 01:08:07 Advice for quantum gravity researchers - 01:13:57 Independent study and learning - 01:15:35 Graviton entanglement testing - 01:20:05 The struggle of podcasting (Theories of Everything's journey) - 01:21:26 Future projects for TOE - 01:24:52 Gratitude for support Learn more about your ad choices. Visit megaphone.fm/adchoices

Steve Tuck, Co-Founder & CEO of Oxide Computer Company, joins Corey on Screaming in the Cloud to discuss his work to make modern computers cloud-friendly. Steve describes what it was like going through early investment rounds, and the difficult but important decision he and his co-founder made to build their own switch. Corey and Steve discuss the demand for on-prem computers that are built for cloud capability, and Steve reveals how Oxide approaches their product builds to ensure the masses can adopt their technology wherever they are. About SteveSteve is the Co-founder & CEO of Oxide Computer Company.  He previously was President & COO of Joyent, a cloud computing company acquired by Samsung.  Before that, he spent 10 years at Dell in a number of different roles. Links Referenced: Oxide Computer Company: https://oxide.computer/ On The Metal Podcast: https://oxide.computer/podcasts/on-the-metal 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 in part by our friends at RedHat. As your organization grows, so does the complexity of your IT resources. You need a flexible solution that lets you deploy, manage, and scale workloads throughout your entire ecosystem. The Red Hat Ansible Automation Platform simplifies the management of applications and services across your hybrid infrastructure with one platform. Look for it on the AWS Marketplace.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. You know, I often say it—but not usually on the show—that Screaming in the Cloud is a podcast about the business of cloud, which is intentionally overbroad so that I can talk about basically whatever the hell I want to with whoever the hell I'd like. Today's guest is, in some ways of thinking, about as far in the opposite direction from Cloud as it's possible to go and still be involved in the digital world. Steve Tuck is the CEO at Oxide Computer Company. You know, computers, the things we all pretend aren't underpinning those clouds out there that we all use and pay by the hour, gigabyte, second-month-pound or whatever it works out to. Steve, thank you for agreeing to come back on the show after a couple years, and once again suffer my slings and arrows.Steve: Much appreciated. Great to be here. It has been a while. I was looking back, I think three years. This was like, pre-pandemic, pre-interest rates, pre… Twitter going totally sideways.Corey: And I have to ask to start with that, it feels, on some level, like toward the start of the pandemic, when everything was flying high and we'd had low interest rates for a decade, that there was a lot of… well, lunacy lurking around in the industry, my own business saw it, too. It turns out that not giving a shit about the AWS bill is in fact a zero interest rate phenomenon. And with all that money or concentrated capital sloshing around, people decided to do ridiculous things with it. I would have thought, on some level, that, “We're going to start a computer company in the Bay Area making computers,” would have been one of those, but given that we are a year into the correction, and things seem to be heading up into the right for you folks, that take was wrong. How'd I get it wrong?Steve: Well, I mean, first of all, you got part of it right, which is there were just a litany of ridiculous companies and projects and money being thrown in all directions at that time.Corey: An NFT of a computer. We're going to have one of those. That's what you're selling, right? Then you had to actually hard pivot to making the real thing.Steve: That's it. So, we might as well cut right to it, you know. This is—we went through the crypto phase. But you know, our—when we started the company, it was yes, a computer company. It's on the tin. It's definitely kind of the foundation of what we're building. But you know, we think about what a modern computer looks like through the lens of cloud.I was at a cloud computing company for ten years prior to us founding Oxide, so was Bryan Cantrill, CTO, co-founder. And, you know, we are huge, huge fans of cloud computing, which was an interesting kind of dichotomy. Instead of conversations when we were raising for Oxide—because of course, Sand Hill is terrified of hardware. And when we think about what modern computers need to look like, they need to be in support of the characteristics of cloud, and cloud computing being not that you're renting someone else's computers, but that you have fully programmable infrastructure that allows you to slice and dice, you know, compute and storage and networking however software needs. And so, what we set out to go build was a way for the companies that are running on-premises infrastructure—which, by the way, is almost everyone and will continue to be so for a very long time—access to the benefits of cloud computing. And to do that, you need to build a different kind of computing infrastructure and architecture, and you need to plumb the whole thing with software.Corey: There are a number of different ways to view cloud computing. And I think that a lot of the, shall we say, incumbent vendors over in the computer manufacturing world tend to sound kind of like dinosaurs, on some level, where they're always talking in terms of, you're a giant company and you already have a whole bunch of data centers out there. But one of the magical pieces of cloud is you can have a ridiculous idea at nine o'clock tonight and by morning, you'll have a prototype, if you're of that bent. And if it turns out it doesn't work, you're out, you know, 27 cents. And if it does work, you can keep going and not have to stop and rebuild on something enterprise-grade.So, for the small-scale stuff and rapid iteration, cloud providers are terrific. Conversely, when you wind up in the giant fleets of millions of computers, in some cases, there begin to be economic factors that weigh in, and for some on workloads—yes, I know it's true—going to a data center is the economical choice. But my question is, is starting a new company in the direction of building these things, is it purely about economics or is there a capability story tied in there somewhere, too?Steve: Yeah, it's actually economics ends up being a distant third, fourth, in the list of needs and priorities from the companies that we're working with. When we talk about—and just to be clear we're—our demographic, that kind of the part of the market that we are focused on are large enterprises, like, folks that are spending, you know, half a billion, billion dollars a year in IT infrastructure, they, over the last five years, have moved a lot of the use cases that are great for public cloud out to the public cloud, and who still have this very, very large need, be it for latency reasons or cost reasons, security reasons, regulatory reasons, where they need on-premises infrastructure in their own data centers and colo facilities, et cetera. And it is for those workloads in that part of their infrastructure that they are forced to live with enterprise technologies that are 10, 20, 30 years old, you know, that haven't evolved much since I left Dell in 2009. And, you know, when you think about, like, what are the capabilities that are so compelling about cloud computing, one of them is yes, what you mentioned, which is you have an idea at nine o'clock at night and swipe a credit card, and you're off and running. And that is not the case for an idea that someone has who is going to use the on-premises infrastructure of their company. And this is where you get shadow IT and 16 digits to freedom and all the like.Corey: Yeah, everyone with a corporate credit card winds up being a shadow IT source in many cases. If your processes as a company don't make it easier to proceed rather than doing it the wrong way, people are going to be fighting against you every step of the way. Sometimes the only stick you've got is that of regulation, which in some industries, great, but in other cases, no, you get to play Whack-a-Mole. I've talked to too many companies that have specific scanners built into their mail system every month looking for things that look like AWS invoices.Steve: [laugh]. Right, exactly. And so, you know, but if you flip it around, and you say, well, what if the experience for all of my infrastructure that I am running, or that I want to provide to my software development teams, be it rented through AWS, GCP, Azure, or owned for economic reasons or latency reasons, I had a similar set of characteristics where my development team could hit an API endpoint and provision instances in a matter of seconds when they had an idea and only pay for what they use, back to kind of corporate IT. And what if they were able to use the same kind of developer tools they've become accustomed to using, be it Terraform scripts and the kinds of access that they are accustomed to using? How do you make those developers just as productive across the business, instead of just through public cloud infrastructure?At that point, then you are in a much stronger position where you can say, you know, for a portion of things that are, as you pointed out, you know, more unpredictable, and where I want to leverage a bunch of additional services that a particular cloud provider has, I can rent that. And where I've got more persistent workloads or where I want a different economic profile or I need to have something in a very low latency manner to another set of services, I can own it. And that's where I think the real chasm is because today, you just don't—we take for granted the basic plumbing of cloud computing, you know? Elastic Compute, Elastic Storage, you know, networking and security services. And us in the cloud industry end up wanting to talk a lot more about exotic services and, sort of, higher-up stack capabilities. None of that basic plumbing is accessible on-prem.Corey: I also am curious as to where exactly Oxide lives in the stack because I used to build computers for myself in 2000, and it seems like having gone down that path a bit recently, yeah, that process hasn't really improved all that much. The same off-the-shelf components still exist and that's great. We always used to disparagingly call spinning hard drives as spinning rust in racks. You named the company Oxide; you're talking an awful lot about the Rust programming language in public a fair bit of the time, and I'm starting to wonder if maybe words don't mean what I thought they meant anymore. Where do you folks start and stop, exactly?Steve: Yeah, that's a good question. And when we started, we sort of thought the scope of what we were going to do and then what we were going to leverage was smaller than it has turned out to be. And by that I mean, man, over the last three years, we have hit a bunch of forks in the road where we had questions about do we take something off the shelf or do we build it ourselves. And we did not try to build everything ourselves. So, to give you a sense of kind of where the dotted line is, around the Oxide product, what we're delivering to customers is a rack-level computer. So, the minimum size comes in rack form. And I think your listeners are probably pretty familiar with this. But, you know, a rack is—Corey: You would be surprised. It's basically, what are they about seven feet tall?Steve: Yeah, about eight feet tall.Corey: Yeah, yeah. Seven, eight feet, weighs a couple 1000 pounds, you know, make an insulting joke about—Steve: Two feet wide.Corey: —NBA players here. Yeah, all kinds of these things.Steve: Yeah. And big hunk of metal. And in the cases of on-premises infrastructure, it's kind of a big hunk of metal hole, and then a bunch of 1U and 2U boxes crammed into it. What the hyperscalers have done is something very different. They started looking at, you know, at the rack level, how can you get much more dense, power-efficient designs, doing things like using a DC bus bar down the back, instead of having 64 power supplies with cables hanging all over the place in a rack, which I'm sure is what you're more familiar with.Corey: Tremendous amount of weight as well because you have the metal chassis for all of those 1U things, which in some cases, you wind up with, what, 46U in a rack, assuming you can even handle the cooling needs of all that.Steve: That's right.Corey: You have so much duplication, and so much of the weight is just metal separating one thing from the next thing down below it. And there are opportunities for massive improvement, but you need to be at a certain point of scale to get there.Steve: You do. You do. And you also have to be taking on the entire problem. You can't pick at parts of these things. And that's really what we found. So, we started at this sort of—the rack level as sort of the design principle for the product itself and found that that gave us the ability to get to the right geometry, to get as much CPU horsepower and storage and throughput and networking into that kind of chassis for the least amount of wattage required, kind of the most power-efficient design possible.So, it ships at the rack level and it ships complete with both our server sled systems in Oxide, a pair of Oxide switches. This is—when I talk about, like, design decisions, you know, do we build our own switch, it was a big, big, big question early on. We were fortunate even though we were leaning towards thinking we needed to go do that, we had this prospective early investor who was early at AWS and he had asked a very tough question that none of our other investors had asked to this point, which is, “What are you going to do about the switch?”And we knew that the right answer to an investor is like, “No. We're already taking on too much.” We're redesigning a server from scratch in, kind of, the mold of what some of the hyperscalers have learned, doing our own Root of Trust, we're doing our own operating system, hypervisor control plane, et cetera. Taking on the switch could be seen as too much, but we told them, you know, we think that to be able to pull through all of the value of the security benefits and the performance and observability benefits, we can't have then this [laugh], like, obscure third-party switch rammed into this rack.Corey: It's one of those things that people don't think about, but it's the magic of cloud with AWS's network, for example, it's magic. You can get line rate—or damn near it—between any two points, sustained.Steve: That's right.Corey: Try that in the data center, you wind into massive congestion with top-of-rack switches, where, okay, we're going to parallelize this stuff out over, you know, two dozen racks and we're all going to have them seamlessly transfer information between each other at line rate. It's like, “[laugh] no, you're not because those top-of-rack switches will melt and become side-of-rack switches, and then bottom-puddle-of-rack switches. It doesn't work that way.”Steve: That's right.Corey: And you have to put a lot of thought and planning into it. That is something that I've not heard a traditional networking vendor addressing because everyone loves to hand-wave over it.Steve: Well so, and this particular prospective investor, we told him, “We think we have to go build our own switch.” And he said, “Great.” And we said, “You know, we think we're going to lose you as an investor as a result, but this is what we're doing.” And he said, “If you're building your own switch, I want to invest.” And his comment really stuck with us, which is AWS did not stand on their own two feet until they threw out their proprietary switch vendor and built their own.And that really unlocked, like you've just mentioned, like, their ability, both in hardware and software to tune and optimize to deliver that kind of line rate capability. And that is one of the big findings for us as we got into it. Yes, it was really, really hard, but based on a couple of design decisions, P4 being the programming language that we are using as the surround for our silicon, tons of opportunities opened up for us to be able to do similar kinds of optimization and observability. And that has been a big, big win.But to your question of, like, where does it stop? So, we are delivering this complete with a baked-in operating system, hypervisor, control plane. And so, the endpoint of the system, where the customer meets is either hitting an API or a CLI or a console that delivers and kind of gives you the ability to spin up projects. And, you know, if one is familiar with EC2 and EBS and VPC, that VM level of abstraction is where we stop.Corey: That, I think, is a fair way of thinking about it. And a lot of cloud folks are going to pooh-pooh it as far as saying, “Oh well, just virtual machines. That's old cloud. That just treats the cloud like a data center.” And in many cases, yes, it does because there are ways to build modern architectures that are event-driven on top of things like Lambda, and API Gateway, and the rest, but you take a look at what my customers are doing and what drives the spend, it is invariably virtual machines that are largely persistent.Sometimes they scale up, sometimes they scale down, but there's always a baseline level of load that people like to hand-wave away the fact that what they're fundamentally doing in a lot of these cases, is paying the cloud provider to handle the care and feeding of those systems, which can be expensive, yes, but also delivers significant innovation beyond what almost any company is going to be able to deliver in-house. There is no way around it. AWS is better than you are—whoever you happen to—be at replacing failed hard drives. That is a simple fact. They have teams of people who are the best in the world of replacing failed hard drives. You generally do not. They are going to be better at that than you. But that's not the only axis. There's not one calculus that leads to, is cloud a scam or is cloud a great value proposition for us? The answer is always a deeply nuanced, “It depends.”Steve: Yeah, I mean, I think cloud is a great value proposition for most and a growing amount of software that's being developed and deployed and operated. And I think, you know, one of the myths that is out there is, hey, turn over your IT to AWS because we have or you know, a cloud provider—because we have such higher caliber personnel that are really good at swapping hard drives and dealing with networks and operationally keeping this thing running in a highly available manner that delivers good performance. That is certainly true, but a lot of the operational value in an AWS is been delivered via software, the automation, the observability, and not actual people putting hands on things. And it's an important point because that's been a big part of what we're building into the product. You know, just because you're running infrastructure in your own data center, it does not mean that you should have to spend, you know, 1000 hours a month across a big team to maintain and operate it. And so, part of that, kind of, cloud, hyperscaler innovation that we're baking into this product is so that it is easier to operate with much, much, much lower overhead in a highly available, resilient manner.Corey: So, I've worked in a number of data center facilities, but the companies I was working with, were always at a scale where these were co-locations, where they would, in some cases, rent out a rack or two, in other cases, they'd rent out a cage and fill it with their own racks. They didn't own the facilities themselves. Those were always handled by other companies. So, my question for you is, if I want to get a pile of Oxide racks into my environment in a data center, what has to change? What are the expectations?I mean, yes, there's obviously going to be power and requirements at the data center colocation is very conversant with, but Open Compute, for example, had very specific requirements—to my understanding—around things like the airflow construction of the environment that they're placed within. How prescriptive is what you've built, in terms of doing a building retrofit to start using you folks?Steve: Yeah, definitely not. And this was one of the tensions that we had to balance as we were designing the product. For all of the benefits of hyperscaler computing, some of the design center for you know, the kinds of racks that run in Google and Amazon and elsewhere are hyperscaler-focused, which is unlimited power, in some cases, data centers designed around the equipment itself. And where we were headed, which was basically making hyperscaler infrastructure available to, kind of, the masses, the rest of the market, these folks don't have unlimited power and they aren't going to go be able to go redesign data centers. And so no, the experience should be—with exceptions for folks maybe that have very, very limited access to power—that you roll this rack into your existing data center. It's on standard floor tile, that you give it power, and give it networking and go.And we've spent a lot of time thinking about how we can operate in the wide-ranging environmental characteristics that are commonplace in data centers that focus on themselves, colo facilities, and the like. So, that's really on us so that the customer is not having to go to much work at all to kind of prepare and be ready for it.Corey: One of the challenges I have is how to think about what you've done because you are rack-sized. But what that means is that my own experimentation at home recently with on-prem stuff for smart home stuff involves a bunch of Raspberries Pi and a [unintelligible 00:19:42], but I tend to more or less categorize you the same way that I do AWS Outposts, as well as mythical creatures, like unicorns or giraffes, where I don't believe that all these things actually exist because I haven't seen them. And in fact, to get them in my house, all four of those things would theoretically require a loading dock if they existed, and that's a hard thing to fake on a demo signup form, as it turns out. How vaporware is what you've built? Is this all on paper and you're telling amazing stories or do they exist in the wild?Steve: So, last time we were on, it was all vaporware. It was a couple of napkin drawings and a seed round of funding.Corey: I do recall you not using that description at the time, for what it's worth. Good job.Steve: [laugh]. Yeah, well, at least we were transparent where we were going through the race. We had some napkin drawings and we had some good ideas—we thought—and—Corey: You formalize those and that's called Microsoft PowerPoint.Steve: That's it. A hundred percent.Corey: The next generative AI play is take the scrunched-up, stained napkin drawing, take a picture of it, and convert it to a slide.Steve: Google Docs, you know, one of those. But no, it's got a lot of scars from the build and it is real. In fact, next week, we are going to be shipping our first commercial systems. So, we have got a line of racks out in our manufacturing facility in lovely Rochester, Minnesota. Fun fact: Rochester, Minnesota, is where the IBM AS/400s were built.Corey: I used to work in that market, of all things.Steve: Really?Corey: Selling tape drives in the AS/400. I mean, I still maintain there's no real mainframe migration to the cloud play because there's no AWS/400. A joke that tends to sail over an awful lot of people's heads because, you know, most people aren't as miserable in their career choices as I am.Steve: Okay, that reminds me. So, when we were originally pitching Oxide and we were fundraising, we [laugh]—in a particular investor meeting, they asked, you know, “What would be a good comp? Like how should we think about what you are doing?” And fortunately, we had about 20 investor meetings to go through, so burning one on this was probably okay, but we may have used the AS/400 as a comp, talking about how [laugh] mainframe systems did such a good job of building hardware and software together. And as you can imagine, there were some blank stares in that room.But you know, there are some good analogs to historically in the computing industry, when you know, the industry, the major players in the industry, were thinking about how to deliver holistic systems to support end customers. And, you know, we see this in the what Apple has done with the iPhone, and you're seeing this as a lot of stuff in the automotive industry is being pulled in-house. I was listening to a good podcast. Jim Farley from Ford was talking about how the automotive industry historically outsourced all of the software that controls cars, right? So, like, Bosch would write the software for the controls for your seats.And they had all these suppliers that were writing the software, and what it meant was that innovation was not possible because you'd have to go out to suppliers to get software changes for any little change you wanted to make. And in the computing industry, in the 80s, you saw this blow apart where, like, firmware got outsourced. In the IBM and the clones, kind of, race, everyone started outsourcing firmware and outsourcing software. Microsoft started taking over operating systems. And then VMware emerged and was doing a virtualization layer.And this, kind of, fragmented ecosystem is the landscape today that every single on-premises infrastructure operator has to struggle with. It's a kit car. And so, pulling it back together, designing things in a vertically integrated manner is what the hyperscalers have done. And so, you mentioned Outposts. And, like, it's a good example of—I mean, the most public cloud of public cloud companies created a way for folks to get their system on-prem.I mean, if you need anything to underscore the draw and the demand for cloud computing-like, infrastructure on-prem, just the fact that that emerged at all tells you that there is this big need. Because you've got, you know, I don't know, a trillion dollars worth of IT infrastructure out there and you have maybe 10% of it in the public cloud. And that's up from 5% when Jassy was on stage in '21, talking about 95% of stuff living outside of AWS, but there's going to be a giant market of customers that need to own and operate infrastructure. And again, things have not improved much in the last 10 or 20 years for them.Corey: They have taken a tone onstage about how, “Oh, those workloads that aren't in the cloud, yet, yeah, those people are legacy idiots.” And I don't buy that for a second because believe it or not—I know that this cuts against what people commonly believe in public—but company execs are generally not morons, and they make decisions with context and constraints that we don't see. Things are the way they are for a reason. And I promise that 90% of corporate IT workloads that still live on-prem are not being managed or run by people who've never heard of the cloud. There was a decision made when some other things were migrating of, do we move this thing to the cloud or don't we? And the answer at the time was no, we're going to keep this thing on-prem where it is now for a variety of reasons of varying validity. But I don't view that as a bug. I also, frankly, don't want to live in a world where all the computers are basically run by three different companies.Steve: You're spot on, which is, like, it does a total disservice to these smart and forward-thinking teams in every one of the Fortune 1000-plus companies who are taking the constraints that they have—and some of those constraints are not monetary or entirely workload-based. If you want to flip it around, we were talking to a large cloud SaaS company and their reason for wanting to extend it beyond the public cloud is because they want to improve latency for their e-commerce platform. And navigating their way through the complex layers of the networking stack at GCP to get to where the customer assets are that are in colo facilities, adds lag time on the platform that can cost them hundreds of millions of dollars. And so, we need to think behind this notion of, like, “Oh, well, the dark ages are for software that can't run in the cloud, and that's on-prem. And it's just a matter of time until everything moves to the cloud.”In the forward-thinking models of public cloud, it should be both. I mean, you should have a consistent experience, from a certain level of the stack down, everywhere. And then it's like, do I want to rent or do I want to own for this particular use case? In my vast set of infrastructure needs, do I want this to run in a data center that Amazon runs or do I want this to run in a facility that is close to this other provider of mine? And I think that's best for all. And then it's not this kind of false dichotomy of quality infrastructure or ownership.Corey: I find that there are also workloads where people will come to me and say, “Well, we don't think this is going to be economical in the cloud”—because again, I focus on AWS bills. That is the lens I view things through, and—“The AWS sales rep says it will be. What do you think?” And I look at what they're doing and especially if involves high volumes of data transfer, I laugh a good hearty laugh and say, “Yeah, keep that thing in the data center where it is right now. You will thank me for it later.”It's, “Well, can we run this in an economical way in AWS?” As long as you're okay with economical meaning six times what you're paying a year right now for the same thing, yeah, you can. I wouldn't recommend it. And the numbers sort of speak for themselves. But it's not just an economic play.There's also the story of, does this increase their capability? Does it let them move faster toward their business goals? And in a lot of cases, the answer is no, it doesn't. It's one of those business process things that has to exist for a variety of reasons. You don't get to reimagine it for funsies and even if you did, it doesn't advance the company in what they're trying to do any, so focus on something that differentiates as opposed to this thing that you're stuck on.Steve: That's right. And what we see today is, it is easy to be in that mindset of running things on-premises is kind of backwards-facing because the experience of it is today still very, very difficult. I mean, talking to folks and they're sharing with us that it takes a hundred days from the time all the different boxes land in their warehouse to actually having usable infrastructure that developers can use. And our goal and what we intend to go hit with Oxide as you can roll in this complete rack-level system, plug it in, within an hour, you have developers that are accessing cloud-like services out of the infrastructure. And that—God, countless stories of firmware bugs that would send all the fans in the data center nonlinear and soak up 100 kW of power.Corey: Oh, God. And the problems that you had with the out-of-band management systems. For a long time, I thought Drax stood for, “Dell, RMA Another Computer.” It was awful having to deal with those things. There was so much room for innovation in that space, which no one really grabbed onto.Steve: There was a really, really interesting talk at DEFCON that we just stumbled upon yesterday. The NVIDIA folks are giving a talk on BMC exploits… and like, a very, very serious BMC exploit. And again, it's what most people don't know is, like, first of all, the BMC, the Baseboard Management Controller, is like the brainstem of the computer. It has access to—it's a backdoor into all of your infrastructure. It's a computer inside a computer and it's got software and hardware that your server OEM didn't build and doesn't understand very well.And firmware is even worse because you know, firmware written by you know, an American Megatrends or other is a big blob of software that gets loaded into these systems that is very hard to audit and very hard to ascertain what's happening. And it's no surprise when, you know, back when we were running all the data centers at a cloud computing company, that you'd run into these issues, and you'd go to the server OEM and they'd kind of throw their hands up. Well, first they'd gaslight you and say, “We've never seen this problem before,” but when you thought you've root-caused something down to firmware, it was anyone's guess. And this is kind of the current condition today. And back to, like, the journey to get here, we kind of realized that you had to blow away that old extant firmware layer, and we rewrote our own firmware in Rust. Yes [laugh], I've done a lot in Rust.Corey: No, it was in Rust, but, on some level, that's what Nitro is, as best I can tell, on the AWS side. But it turns out that you don't tend to have the same resources as a one-and-a-quarter—at the moment—trillion-dollar company. That keeps [valuing 00:30:53]. At one point, they lost a comma and that was sad and broke all my logic for that and I haven't fixed it since. Unfortunate stuff.Steve: Totally. I think that was another, kind of, question early on from certainly a lot of investors was like, “Hey, how are you going to pull this off with a smaller team and there's a lot of surface area here?” Certainly a reasonable question. Definitely was hard. The one advantage—among others—is, when you are designing something kind of in a vertical holistic manner, those design integration points are narrowed down to just your equipment.And when someone's writing firmware, when AMI is writing firmware, they're trying to do it to cover hundreds and hundreds of components across dozens and dozens of vendors. And we have the advantage of having this, like, purpose-built system, kind of, end-to-end from the lowest level from first boot instruction, all the way up through the control plane and from rack to switch to server. That definitely helped narrow the scope.Corey: This episode has been fake sponsored by our friends at AWS with the following message: Graviton Graviton, Graviton, Graviton, Graviton, Graviton, Graviton, Graviton, Graviton. Thank you for your l-, lack of support for this show. Now, AWS has been talking about Graviton an awful lot, which is their custom in-house ARM processor. Apple moved over to ARM and instead of talking about benchmarks they won't publish and marketing campaigns with words that don't mean anything, they've let the results speak for themselves. In time, I found that almost all of my workloads have moved over to ARM architecture for a variety of reason, and my laptop now gets 15 hours of battery life when all is said and done. You're building these things on top of x86. What is the deal there? I do not accept that if that you hadn't heard of ARM until just now because, as mentioned, Graviton, Graviton, Graviton.Steve: That's right. Well, so why x86, to start? And I say to start because we have just launched our first generation products. And our first-generation or second-generation products that we are now underway working on are going to be x86 as well. We've built this system on AMD Milan silicon; we are going to be launching a Genoa sled.But when you're thinking about what silicon to use, obviously, there's a bunch of parts that go into the decision. You're looking at the kind of applicability to workload, performance, power management, for sure, and if you carve up what you are trying to achieve, x86 is still a terrific fit for the broadest set of workloads that our customers are trying to solve for. And choosing which x86 architecture was certainly an easier choice, come 2019. At this point, AMD had made a bunch of improvements in performance and energy efficiency in the chip itself. We've looked at other architectures and I think as we are incorporating those in the future roadmap, it's just going to be a question of what are you trying to solve for.You mentioned power management, and that is kind of commonly been a, you know, low power systems is where folks have gone beyond x86. Is we're looking forward to hardware acceleration products and future products, we'll certainly look beyond x86, but x86 has a long, long road to go. It still is kind of the foundation for what, again, is a general-purpose cloud infrastructure for being able to slice and dice for a variety of workloads.Corey: True. I have to look around my environment and realize that Intel is not going anywhere. And that's not just an insult to their lack of progress on committed roadmaps that they consistently miss. But—Steve: [sigh].Corey: Enough on that particular topic because we want to keep this, you know, polite.Steve: Intel has definitely had some struggles for sure. They're very public ones, I think. We were really excited and continue to be very excited about their Tofino silicon line. And this came by way of the Barefoot networks acquisition. I don't know how much you had paid attention to Tofino, but what was really, really compelling about Tofino is the focus on both hardware and software and programmability.So, great chip. And P4 is the programming language that surrounds that. And we have gotten very, very deep on P4, and that is some of the best tech to come out of Intel lately. But from a core silicon perspective for the rack, we went with AMD. And again, that was a pretty straightforward decision at the time. And we're planning on having this anchored around AMD silicon for a while now.Corey: One last question I have before we wind up calling it an episode, it seems—at least as of this recording, it's still embargoed, but we're not releasing this until that winds up changing—you folks have just raised another round, which means that your napkin doodles have apparently drawn more folks in, and now that you're shipping, you're also not just bringing in customers, but also additional investor money. Tell me about that.Steve: Yes, we just completed our Series A. So, when we last spoke three years ago, we had just raised our seed and had raised $20 million at the time, and we had expected that it was going to take about that to be able to build the team and build the product and be able to get to market, and [unintelligible 00:36:14] tons of technical risk along the way. I mean, there was technical risk up and down the stack around this [De Novo 00:36:21] server design, this the switch design. And software is still the kind of disproportionate majority of what this product is, from hypervisor up through kind of control plane, the cloud services, et cetera. So—Corey: We just view it as software with a really, really confusing hardware dongle.Steve: [laugh]. Yeah. Yes.Corey: Super heavy. We're talking enterprise and government-grade here.Steve: That's right. There's a lot of software to write. And so, we had a bunch of milestones that as we got through them, one of the big ones was getting Milan silicon booting on our firmware. It was funny it was—this was the thing that clearly, like, the industry was most suspicious of, us doing our own firmware, and you could see it when we demonstrated booting this, like, a year-and-a-half ago, and AMD all of a sudden just lit up, from kind of arm's length to, like, “How can we help? This is amazing.” You know? And they could start to see the benefits of when you can tie low-level silicon intelligence up through a hypervisor there's just—Corey: No I love the existing firmware I have. Looks like it was written in 1984 and winds up having terrible user ergonomics that hasn't been updated at all, and every time something comes through, it's a 50/50 shot as whether it fries the box or not. Yeah. No, I want that.Steve: That's right. And you look at these hyperscale data centers, and it's like, no. I mean, you've got intelligence from that first boot instruction through a Root of Trust, up through the software of the hyperscaler, and up to the user level. And so, as we were going through and kind of knocking down each one of these layers of the stack, doing our own firmware, doing our own hardware Root of Trust, getting that all the way plumbed up into the hypervisor and the control plane, number one on the customer side, folks moved from, “This is really interesting. We need to figure out how we can bring cloud capabilities to our data centers. Talk to us when you have something,” to, “Okay. We actually”—back to the earlier question on vaporware, you know, it was great having customers out here to Emeryville where they can put their hands on the rack and they can, you know, put your hands on software, but being able to, like, look at real running software and that end cloud experience.And that led to getting our first couple of commercial contracts. So, we've got some great first customers, including a large department of the government, of the federal government, and a leading firm on Wall Street that we're going to be shipping systems to in a matter of weeks. And as you can imagine, along with that, that drew a bunch of renewed interest from the investor community. Certainly, a different climate today than it was back in 2019, but what was great to see is, you still have great investors that understand the importance of making bets in the hard tech space and in companies that are looking to reinvent certain industries. And so, we added—our existing investors all participated. We added a bunch of terrific new investors, both strategic and institutional.And you know, this capital is going to be super important now that we are headed into market and we are beginning to scale up the business and make sure that we have a long road to go. And of course, maybe as importantly, this was a real confidence boost for our customers. They're excited to see that Oxide is going to be around for a long time and that they can invest in this technology as an important part of their infrastructure strategy.Corey: I really want to thank you for taking the time to speak with me about, well, how far you've come in a few years. If people want to learn more and have the requisite loading dock, where should they go to find you?Steve: So, we try to put everything up on the site. So, oxidecomputer.com or oxide.computer. We also, if you remember, we did [On the Metal 00:40:07]. So, we had a Tales from the Hardware-Software Interface podcast that we did when we started. We have shifted that to Oxide and Friends, which the shift there is we're spending a little bit more time talking about the guts of what we built and why. So, if folks are interested in, like, why the heck did you build a switch and what does it look like to build a switch, we actually go to depth on that. And you know, what does bring-up on a new server motherboard look like? And it's got some episodes out there that might be worth checking out.Corey: We will definitely include a link to that in the [show notes 00:40:36]. Thank you so much for your time. I really appreciate it.Steve: Yeah, Corey. Thanks for having me on.Corey: Steve Tuck, CEO at Oxide Computer Company. 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 episode, please leave a five-star review on your podcast platform of choice, along with an angry ranting comment because you are in fact a zoology major, and you're telling me that some animals do in fact exist. But I'm pretty sure of the two of them, it's the unicorn.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.

Marvel Tales Ep #40: West Coast Avengers #1-#4 Welcome back to Marvel Tales! In this episode, Phil and Justin review the original West Coast Avengers miniseries (September-December 1984) featuring Hawkeye and Mockingbird putting together a new team of Avengers to face any and all threats “west of the rocky mountains”. Iron Man, Wonder Man and Tigra help them defeat threats from The Blank and Graviton.   Tune in today and don't forget to review the show on Apple Podcasts, Spotify, YouTube, and anywhere else you can!     Marvel Tales Links  → Twitter http://www.twitter.com/MarvelTalesPod → Instagram https://www.instagram.com/capeslunatics/ → Facebook facebook.com/MarvelTalesPod → YouTube https://www.youtube.com/c/CapesandLunatics   ==================  

Want to help define the AI Engineer stack? Have opinions on the top tools, communities and builders? We're collaborating with friends at Amplify to launch the first State of AI Engineering survey! Please fill it out (and tell your friends)!If AI is so important, why is its software so bad?This was the motivating question for Chris Lattner as he reconnected with his product counterpart on Tensorflow, Tim Davis, and started working on a modular solution to the problem of sprawling, monolithic, fragmented platforms in AI development. They announced a $30m seed in 2022 and, following their successful double launch of Modular/Mojo

Learn more about the recently launched I4g AWS Nitro SSDs. AWS Nitro SSDs build on the AWS silicon innovation with the AWS Nitro System and are custom-designed to deliver the best storage performance for your I/O intensive workloads running in Amazon EC2. I4g instances offer similar memory and storage ratios to existing I4i instances and are optimized for workloads with small to medium sized datasets that perform a high mix of random read/write and require very low I/O latency, such as databases and real-time analytics. I4g instances deliver the best compute price performance for a storage optimized instance, and best storage performance per TB for a Graviton-based storage instance. Amazon EC2 I4g instances deliver up to 15% better compute performance compared to similar storage-optimized instances. Amazon l4g instances website: https://go.aws/3YxI3vr Blog: Amazon EC2 I4g storage-optimized instances: https://go.aws/3OoKbRK

Welcome episode 222 of The Cloud Pod Podcast - where the forecast is always cloudy! This week we take an in depth look at the latest earnings reports from all the major players, changes to IPv4 costs (inflation), Healthscribe, and all the news (in cybersecurity) that's fit to print.  Titles we almost went with this week:

Silicon chips are the foundation of modern computing. AWS custom-designs its silicon chips to be more efficient and sustainable, which helps you maximize performance and save money. On June 21, 2023 AWS hosted our first Silicon Innovation Day with 20 different deep dives into how these innovations can improve your workflows, impact your business, and power your networking developments. Learn more about everything that was discussed in our roundup podcast and the videos on demand linked in our show notes! All sessions are available here: https://www.youtube.com/@AWSEventsChannel & https://www.youtube.com/playlist?list=PL2yQDdvlhXf9i-4AsyOdlgVFDpBjgwNYw Learn more about Graviton: https://go.aws/42MJ4Ao Learn more about Inferentia: https://go.aws/3N7pM2M Learn more about Trainium: https://go.aws/3N7q0qE Learn more about Nitro: https://go.aws/3CDpCM2

What is the universe made of? Will we ever have a complete list of all the particles that make up existence? To find out, Dr. Charles Liu and co-host Allen Liu welcome Dr. Lesya Horyn, PhD, a Fermilab researcher working at the Large Hadron Collider (LHC) at CERN in Switzerland.   As always, though, we start off with the day's joyfully cool cosmic thing, which takes us to Brookhaven National Laboratory in Long Island, NY, where scientists have figured out how to make matter from energy. They smashed 2 photons together to produce a matter/anti-matter particle pair. It happens naturally in the universe, and we convert matter into energy all the time, but we've never before turned energy into matter using photons, which have no mass.   Next up, a quantum mechanics question from Lindsey in Massachusetts: “Do you believe that there is an elementary particle responsible for gravity?” Dr. Horyn explains how the standard model (the “periodic table” of subatomic particles) “makes a nice picture” but is “missing stuff” like dark matter and gravity, neither of which are in the standard model. One of these missing pieces is the graviton, a theorized elementary particle that would be responsible for gravitational force in the same way that the photon is responsible for the electromagnetic force, which Dr. Horyn and Charles both believe exists but has not yet been discovered. (Honorable mention: Our geek-in-chief Chuck mentions the Marvel Comics supervillain Graviton, who has the comic book superpower of gravity.)   Dr. Horyn explains her research at CERN, and how the LHC actually is used for experiments. You'll learn more about the LHC, a 17-mile-circumfrence underground ring used to smash particles into each other at specific speeds, and the Compact Muon Solenoid (CMS) detector, which Lesya is using for her research now. You'll also hear about the much larger A Toroidal LHC Apparatus (ATLAS), which she used previously for her primary research, both of which were used in the discovery of the Higgs boson ten years ago.   As Charles and Lesya take us down the particle physics rabbit hole, we end up talking about the Muon g-2 experiments eventually conducted by Fermilab. Find out why the gyromagnetic moment is important to particle physics – and yes, we go deep into the physics weeds in this episode! (Make sure to catch the story about moving a giant magnet from Brookhaven National Laboratory in New York by boat and truck to Fermilab in Illinois!)   Moving on, the crew tackles a question from Walter T. on Patreon, who asks, “Could the many worlds theory still be deterministic?” Charles explains the many worlds model, but because our existing experiments cannot distinguish between the many different models of quantum mechanics, Lesya defaults to the infamous Richard Feynman quote, “Anybody who claims to understand quantum mechanics is either crazy or lying.”   If you'd like to know more about Dr. Horyn, you can follow her on Twitter at @lesyaah. And be sure to follow @CERN, @ATLASexperiment, and @CMSexperiment to keep up with some of the developments we've discussed in this episode.   We hope you enjoy this episode of The LIUniverse, and, if you do, please support us on Patreon.    Credits for Images Used in this Episode: Brookhaven National Laboratory – Credit: Energy.gov, public domain Particles in the Standard Model – Credit: Cush via Wikimedia, public domain The CMS detector – Credit: Evenkolder, CC-BY 2.0 The g-2 experiment magnet in transit – Credit: Energy.gov, public domain MuonG-2 Predicted – Credit: Allen Liu, for the LIUniverse MuonG-2 Observed – Credit: Allen Liu, for the LIUniverse  

Silicon chips are the foundation of modern computing. AWS custom-designs its silicon chips to be more efficient and sustainable, which helps you maximize performance and save money. To learn how AWS custom-designed silicon chips can help your business, tune in to AWS Silicon Innovation Day on June 21, at 9 a.m. Pacific Time at twitch.tv/awsonair or LinkedIn. Register at Splash That: https://bit.ly/3PkzMZd Learn more about Graviton: https://go.aws/42MJ4Ao Learn more about Inferentia: https://go.aws/3N7pM2M Learn more about Trainium: https://go.aws/3N7q0qE Learn more about Nitro: https://go.aws/3CDpCM2

Everett Berry, Growth and Open Source at Vantage, joins Corey at Screaming in the Cloud to discuss the complex world of cloud costs. Everett describes how Vantage takes a broad approach to understanding and cutting cloud costs across a number of different providers, and reveals which providers he feels generate large costs quickly. Everett also explains some of his best practices for cutting costs on cloud providers, and explores what he feels the impact of AI will be on cloud providers. Corey and Everett also discuss the pros and cons of AWS savings plans, why AWS can't be counted out when it comes to AI, and why there seems to be such a delay in upgrading instances despite the cost savings. About EverettEverett is the maintainer of ec2instances.info at Vantage. He also writes about cloud infrastructure and analyzes cloud spend. Prior to Vantage Everett was a developer advocate at Arctype, a collaborative SQL client acquired by ClickHouse. Before that, Everett was cofounder and CTO of Perceive, a computer vision company. In his spare time he enjoys playing golf, reading sci-fi, and scrolling Twitter.Links Referenced: Vantage: https://www.vantage.sh/ Vantage Cloud Cost Report: https://www.vantage.sh/cloud-cost-report Everett Berry Twitter: https://twitter.com/retttx Vantage Twitter: https://twitter.com/JoinVantage 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:  LANs of the late 90's and early 2000's were a magical place to learn about computers, hang out with your friends, and do cool stuff like share files, run websites & game servers, and occasionally bring the whole thing down with some ill-conceived software or network configuration. That's not how things are done anymore, but what if we could have a 90's style LAN experience along with the best parts of the 21st century internet? (Most of which are very hard to find these days.) Tailscale thinks we can, and I'm inclined to agree. With Tailscale I can use trusted identity providers like Google, or Okta, or GitHub to authenticate users, and automatically generate & rotate keys to authenticate devices I've added to my network. I can also share access to those devices with friends and teammates, or tag devices to give my team broader access. And that's the magic of it, your data is protected by the simple yet powerful social dynamics of small groups that you trust.Try now - it's free forever for personal use. I've been using it for almost two years personally, and am moderately annoyed that they haven't attempted to charge me for what's become an essential-to-my-workflow service.Corey: Have you listened to the new season of Traceroute yet? Traceroute is a tech podcast that peels back the layers of the stack to tell the real, human stories about how the inner workings of our digital world affect our lives in ways you may have never thought of before. Listen and follow Traceroute on your favorite platform, or learn more about Traceroute at origins.dev. My thanks to them for sponsoring this ridiculous podcast. Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. This seems like an opportune moment to take a step back and look at the overall trend in cloud—specifically AWS—spending. And who better to do that than this week, my guest is Everett Berry who is growth in open-source over at Vantage. And they've just released the Vantage Cloud Cost Report for Q1 of 2023. Everett, thank you for joining me.Everett: Thanks for having me, Corey.Corey: I enjoy playing slap and tickle with AWS bills because I am broken in exactly that kind of way where this is the thing I'm going to do with my time and energy and career. It's rare to find people who are, I guess, similarly afflicted. So, it's great to wind up talking to you, first off.Everett: Yeah, great to be with you as well. Last Week in AWS and in particular, your Twitter account, are things that we follow religiously at Vantage.Corey: Uh-oh [laugh]. So, I want to be clear because I'm sure someone's thinking it out there, that, wait, Vantage does cloud cost optimization as a service? Isn't that what I do? Aren't we competitors? And the answer that I have to that is not by any definition that I've ever seen that was even halfway sensible.If SaaS could do the kind of bespoke consulting engagements that I do, we would not sell bespoke consulting engagements because it's easier to click button: receive software. And I also will point out that we tend to work once customers are at a certain point at scale that in many cases is a bit prohibitive for folks who are just now trying to understand what the heck's going on the first time finance has some very pointed questions about the AWS bill. That's how I see it from my perspective, anyway. Agree? Disagree?Everett: Yeah, I agree with that. I think the product solution, the system of record that companies need when they're dealing with Cloud costs ends up being a different service than the one that you guys provide. And I think actually the to work in concert very well, where you establish a cloud cost optimization practice, and then you keep it in place via software and via sort of the various reporting tools that the Vantage provide. So, I completely agree with you. In fact, in the hundreds of customers and deals that Vantage has worked on, I don't think we have ever come up against Duckbill Group. So, that tells you everything you need to know in that regard.Corey: Yeah. And what's interesting about this is that you have a different scale of visibility into the environment. We wind up dealing with a certain profile, or a couple of profiles, in our customer base. We work with dozens of companies a year; you work with hundreds. And that's bigger numbers, of course, but also in many cases at different segments of the industry.I also am somewhat fond of saying that Vantage is more focused on going broad in ways where we tend to focus on going exclusively deep. We do AWS; the end. You folks do a number of different cloud providers, you do Datadog cost visibility. I've lost track of all the different services that you wind up tracking costs for.Everett: Yeah, that's right. We just launched our 11th provider, which was OpenAI and for the first time in this report, we're actually breaking out data among the different clouds and we're comparing services across AWS, Google, and Azure. And I think it's a bit of a milestone for us because we started on AWS, where I think the cost problem is the most acute, if you will, and we've hit a point now across Azure and Google where we actually have enough data to say some interesting things about how those clouds work. But in general, we have this term, single pane of glass, which is the idea that you use 5, 6, 7 services, and you want to bundle all those costs into one report.Corey: Yeah. And that is something that we see in many cases where customers are taking a more holistic look at things. But, on some level, when people ask me, “Oh, do you focus on Google bills, too,” or Azure bills in the early days, it was, “Well, not yet. Let's take a look.” And what I was seeing was, they're spending, you know, millions or hundreds of millions, in some cases, on AWS, and oh, yeah, here's, like, a $300,000 thing we're running over on GCP is a proof-of-concept or some bizdev thing. And it's… yeah, why don't we focus on the big numbers first? The true secret of cloud economics is, you know, big numbers first rather than alphabetical, but don't tell anyone I told you that.Everett: It's pretty interesting you say that because, you know, in this graph where we break down costs across providers, you can really see that effect on Google and Azure. So, for example, the number three spending category on Google is BigQuery and I think many people would say BigQuery is kind of the jewel of the Google Cloud empire. Similarly for Azure, we actually found Databricks showing up as a top-ten service. Compare that to AWS where you just see a very routine, you know, compute, database, storage, monitoring, bandwidth, down the line. AWS still is the king of costs, if you will, in terms of, like, just running classic compute workloads. And the other services are a little bit more bespoke, which has been something interesting to see play out in our data.Corey: One thing that I've heard that's fascinating to me is that I've now heard from multiple Fortune 500 companies where the Datadog bill is now a board-level concern, given the size and scale of it. And for fun, once I modeled out all the instance-based pricing models that they have for the suite of services they offer, and at the time was three or $400 a month, per instance to run everything that they've got, which, you know, when you look at the instances that I have, costing, you know, 15, 20 bucks a month, in some cases, hmm, seems a little out of whack. And I can absolutely see that turning into an unbounded growth problem in kind of the same way. I just… I don't need to conquer the world. I'm not VC-backed. I am perfectly content at the scale that I'm at—Everett: [laugh].Corey: —with the focus on the problems that I'm focused on.Everett: Yeah, Datadog has been fascinating. It's been one of our fastest-growing providers of sort of the ‘others' category that we've launched. And I think the thing with Datadog that is interesting is you have this phrase cloud costs are all about cloud architecture and I think that's more true on Datadog than a lot of other services because if you have a model where you have, you know, thousands of hosts, and then you add-on one of Datadogs 20 services, which charges per host, suddenly your cloud bill has grown exponentially compared to probably the thing that you were after. And a similar thing happens—actually, my favorite Datadog cost recommendation is, when you have multiple endpoints, and you have sort of multiple query parameters for those endpoints, you end up in this cardinality situation where suddenly Datadog is tracking, again, like, exponentially increasing number of data points, which it's then charging to you on a usage-based model. And so, Datadog is great partners with AWS and I think it's no surprise because the two of them actually sort of go hand-in-hand in terms of the way that they… I don't want to say take ad—Corey: Extract revenue?Everett: Yeah, extract revenue. That's a good term. And, you know, you might say a similar thing about Snowflake, possibly, and the way that they do things. Like oh, the, you know, warehouse has to be on for one minute, minimum, no matter how long the query runs, and various architectural decisions that these folks make that if you were building a cost-optimized version of the service, you would probably go in the other direction.Corey: One thing that I'm also seeing, too, is that I can look at the AWS bill—and just billing data alone—and then say, “Okay, you're using Datadog, aren't you?” Like, “How did you know that?” Like, well, first, most people are secondly, CloudWatch is your number two largest service spend right now. And it's the downstream effect of hammering all the endpoints with all of the systems. And is that data you're actually using? Probably not, in some cases. It's, everyone turns on all the Datadog integrations the first time and then goes back and resets and never does it again.Everett: Yeah, I think we have this set of advice that we give Datadog folks and a lot of it is just, like, turn down the ingestion volume on your logs. Most likely, logs from 30 days ago that are correlated with some new services that you spun up—like you just talked about—are potentially not relevant anymore, for the kind of day-to-day cadence that you want to get into with your cloud spending. So yeah, I mean, I imagine when you're talking to customers, they're bringing up sort of like this interesting distinction where you may end up in a meeting room with the actual engineering team looking at the actual YAML configuration of the Datadog script, just to get a sense of like, well, what are the buttons I can press here? And so, that's… yeah, I mean, that's one reason cloud costs are a pretty interesting world is, on the surface level, you may end up buying some RIs or savings plans, but then when you really get into saving money, you end up actually changing the knobs on the services that you're talking about.Corey: That's always a fun thing when we talk to people in our sales process. It's been sord—“Are you just going to come in and tell us to buy savings plans or reserved instances?” Because the answer to that used to be, “No, that's ridiculous. That's not what we do.” But then we get into environments and find they haven't bought any of those things in 18 months.Everett: [laugh].Corey: —and it's well… okay, that's step two. Step one is what are you using you shouldn't be? Like, basically measure first then cut as opposed to going the other direction and then having to back your way into stuff. Doesn't go well.Everett: Yeah. One of the things that you were discussing last year that I thought was pretty interesting was the gp3 volumes that are now available for RDS and how those volumes, while they offer a nice discount and a nice bump in price-to-performance on EC2, actually don't offer any of that on RDS except for specific workloads. And so, I think that's the kind of thing where, as you're working with folks, as Vantage is working with people, the discussion ends up in these sort of nuanced niche areas, and that's why I think, like, these reports, hopefully, are helping people get a sense of, like, well, what's normal in my architecture or where am I sort of out of bounds? Oh, the fact that I'm spending most of my bill on NAT gateways and bandwidth egress? Well, that's not normal. That would be something that would be not typical of what your normal AWS user is doing.Corey: Right. There's always a question of, “Am I normal?” is one of the first things people love to ask. And it comes in different forms. But it's benchmarking. It's, okay, how much should it cost us to service a thousand monthly active users? It's like, there's no good way to say that across the board for everyone.Everett: Yeah. I like the model of getting into the actual unit costs. I have this sort of vision in my head of, you know, if I'm Uber and I'm reporting metrics to the public stock market, I'm actually reporting a cost to serve a rider, a cost to deliver an Uber Eats meal, in terms of my cloud spend. And that sort of data is just ridiculously hard to get to today. I think it's what we're working towards with Vantage and I think it's something that with these Cloud Cost Reports, we're hoping to get into over time, where we're actually helping companies think about well, okay, within my cloud spend, it's not just what I'm spending on these different services, there's also an idea of how much of my cost to deliver my service should be realized by my cloud spending.Corey: And then people have the uncomfortable realization that wait, my bill is less a function of number of customers I have but more the number of engineers I've hired. What's going on with that?Everett: [laugh]. Yeah, it is interesting to me just how many people end up being involved in this problem at the company. But to your earlier point, the cloud spending discussion has really ramped up over the past year. And I think, hopefully, we are going to be able to converge on a place where we are realizing the promise of the cloud, if you will, which is that it's actually cheaper. And I think what these reports show so far is, like, we've still got a long ways to go for that.Corey: One thing that I think is opportune about the timing of this recording is that as of last week, Amazon wound up announcing their earnings. And Andy Jassy has started getting on the earnings calls, which is how you know it's bad because the CEO of Amazon never deigned to show up on those things before. And he said that a lot of AWS employees are focused and spending their time on helping customers lower their AWS bills. And I'm listening to this going, “Oh, they must be talking to different customers than the ones that I'm talking to.” Are you seeing a lot of Amazonian involvement in reducing AWS bills? Because I'm not and I'm wondering where these people are hiding.Everett: So, we do see one thing, which is reps pushing savings plans on customers, which in general, is great. It's kind of good for everybody, it locks people into longer-term spend on Amazon, it gets them a lower rate, savings plans have some interesting functionality where they can be automatically applied to the area where they offer the most discount. And so, those things are all positive. I will say with Vantage, we're a cloud cost optimization company, of course, and so when folks talk to us, they often already have talked to their AWS rep. And the classic scenario is, that the rep passes over a large spreadsheet of options and ways to reduce costs, but for the company, that spreadsheet may end up being quite a ways away from the point where they actually realize cost savings.And ultimately, the people that are working on cloud cost optimization for Amazon are account reps who are comped by how much cloud spending their accounts are using on Amazon. And so, at the end of the day, some of the, I would say, most hard-hitting optimizations that you work on that we work on, end up hitting areas where they do actually reduce the bill which ends up being not in the account manager's favor. And so, it's a real chicken-and-egg game, except for savings plans is one area where I think everybody can kind of work together.Corey: I have found that… in fairness, there is some defense for Amazon in this but their cost-cutting approach has been rightsizing instances, buy some savings plans, and we are completely out of ideas. Wait, can you switch to Graviton and/or move to serverless? And I used to make fun of them for this but honestly that is some of the only advice that works across the board, irrespective in most cases, of what a customer is doing. Everything else is nuanced and it depends.That's why in some cases, I find that I'm advising customers to spend more money on certain things. Like, the reason that I don't charge percentage of savings in part is because otherwise I'm incentivized to say things like, “Backups? What are you, some kind of coward? Get rid of them.” And that doesn't seem like it's going to be in the customer's interest every time. And as soon as you start down that path, it starts getting a little weird.But people have asked me, what if my customers reach out to their account teams instead of talking to us? And it's, we do bespoke consulting engagements; I do not believe that we have ever had a client who did not first reach out to their account team. If the account teams were capable of doing this at the level that worked for customers, I would have to be doing something else with my business. It is not something that we are seeing hit customers in a way that is effective, and certainly not at scale. You said—as you were right on this—that there's an element here of account managers doing this stuff, there's an [unintelligible 00:15:54] incentive issue in part, but it's also, quality is extraordinarily uneven when it comes to these things because it is its own niche and a lot of people focus in different areas in different ways.Everett: Yeah. And to the areas that you brought up in terms of general advice that's given, we actually have some data on this in this report. In particular Graviton, this is something we've been tracking the whole time we've been doing these reports, which is the past three quarters and we actually are seeing Graviton adoption start to increase more rapidly than it was before. And so, for this last quarter Q1, we're seeing 5% of our costs that we're measuring on EC2 coming from Graviton, which is up from, I want to say 2% the previous quarter, and, like, less than 1% the quarter before. The previous quarter, we also reported that Lambda costs are now majority on ARM among the Vantage customer base.And that one makes some sense to me just because in most cases with Lambda, it's a flip of a switch. And then to your archival point on backups, this is something that we report in this one is that intelligent tiering, which we saw, like, really make an impact for folks towards the end of last year, the numbers for that were flat quarter over quarter. And so, what I mean by that is, we reported that I think, like, two-thirds of our S3 costs are still in the standard storage tier, which is the most expensive tier. And folks have enabled S3 intelligent tiering, which moves your data to progressively cheaper tiers, but we haven't seen that increase this quarter. So, it's the same number as it was last quarter.And I think speaks to what you're talking about with a ceiling on some cost optimization techniques, where it's like, you're not just going to get rid of all your backups; you're not just going to get rid of your, you know, Amazon WorkSpaces archived desktop snapshots that you need for some HIPAA compliance reason. Those things have an upper limit and so that's where, when the AWS rep comes in, it's like, as they go through the list of top spending categories, the recommendations they can give start to provide diminishing returns.Corey: I also think this is sort of a law of large numbers issue. When you start seeing a drop off in the growth rate of large cloud providers, like, there's a problem, in that there are only so many exabyte scale workloads that can be moved inside of a given quarter into the cloud. You're not going to see the same unbounded infinite growth that you would expect mathematically. And people lose their minds when they start to see those things pointed out, but the blame that oh, that's caused by cost optimization efforts, with respect, bullshit it is. I have seen customers devote significant efforts to reducing their AWS bills and it takes massive amounts of work and even then they don't always succeed in getting there.It gets better, but they still wind up a year later, having spent more on a month-by-month basis than they did when they started. Sure they understand it better and it's organic growth that's driving it and they've solved the low hanging fruit problem, but there is a challenge in acting as a boundary for what is, in effect, an unbounded growth problem.Everett: Yeah. And speaking to growth, I thought Microsoft had the most interesting take on where things could happen next quarter, and that, of course, is AI. And so, they attributed, I think it was, 1% of their guidance regarding 26 or 27% growth for Q2 Cloud revenue and it attributed 1% of that to AI. And I think Amazon is really trying to be in the room for those discussions when a large enterprise is talking about AI workloads because it's one of the few remaining cloud workloads that if it's not in the cloud already, is generating potentially massive amounts of growth for these guys.And so, I'm not really sure if I believe the 1% number. I think Microsoft may be having some fun with the fact that, of course, OpenAI is paying them for acting as a cloud provider for ChatGPT and further API, but I do think that AWS, although they were maybe a little slow to the game, they did, to their credit, launch a number of AI services that I'm excited to see if that contributes to the cost that we're measuring next quarter. We did measure, for the first time, a sudden increase on those new [Inf1 00:20:17] EC2 instances, which are optimized for machine learning. And I think if AWS can have success moving customers to those the way they have with Graviton, then that's going to be a very healthy area of growth for them.Corey: I'll also say that it's pretty clear to me that Amazon does not know what it's doing in its world of machine-learning-powered services. I use Azure for the [unintelligible 00:20:44] clients I built originally for Twitter, then for Mastodon—I'm sure Bluesky is coming—but the problem that I'm seeing there is across the board, start to finish, that there is no cohesive story from the AWS side of here's a picture tell me what's in it and if it's words, describe it to me. That's a single API call when we go to Azure. And the more that Amazon talks about something, I find, the less effective they're being in that space. And they will not stop talking about machine learning. Yes, they have instances that are powered by GPUs; that's awesome. But they're an infrastructure provider and moving up the stack is not in their DNA. But that's where all the interest and excitement and discussion is going to be increasingly in the AI space. Good luck.Everett: I think it might be something similar to what you've talked about before with all the options to run containers on AWS. I think they today have a bit of a grab bag of services and they may actually be looking forward to the fact that they're these truly foundational models which let you do a number of tasks, and so they may not need to rely so much on you know, Amazon Polly and Amazon Rekognition and sort of these task-specific services, which to date, I'm not really sure of the takeoff rates on those. We have this cloud costs leaderboard and I don't think you would find them in the top 50 of AWS services. But we'll see what happens with that.AWS I think, ends up being surprisingly good at sticking with it. I think our view is that they probably have the most customer spend on Kubernetes of any major cloud, even though you might say Google at first had the lead on Kubernetes and maybe should have done more with GKE. But to date, I would kind of agree with your take on AI services and I think Azure is… it's Azure's to lose for the moment.Corey: I would agree. I think the future of the cloud is largely Azure's to lose and it has been for a while, just because they get user experience, they get how to talk to enterprises. I just… I wish they would get security a little bit more effectively, and if failing that, communicating with their customers about security more effectively. But it's hard for a leopard to change its spots. Microsoft though has demonstrated an ability to change their nature multiple times, in ways that I would have bet were impossible. So, I just want to see them do it again. It's about time.Everett: Yeah, it's been interesting building on Azure for the past year or so. I wrote a post recently about, kind of, accessing billing data across the different providers and it's interesting in that every cloud provider is unique in the way that it simply provides an external endpoint for downloading your billing data, but Azure is probably one of the easiest integrations; it's just a REST API. However, behind that REST API are, like, years and years of different ways to pay Microsoft: are you on a pay-as-you-go plan, are you on an Azure enterprise plan? So, there's all this sort of organizational complexity hidden behind Azure and I think sometimes it rears its ugly head in a way that stringing together services on Amazon may not, even if that's still a bear in and of itself, if you will.Corey: Any other surprises that you found in the Cloud Cost Report? I mean, looking through it, it seems directionally aligned with what I see in my environments with customers. Like for example, you're not going to see Kubernetes showing up as a line item on any of these things just because—Everett: Yeah.Corey: That is indistinguishable from a billing perspective when we're looking at EC2 spend versus control plane spend. I don't tend to [find 00:24:04] too much that's shocking me. My numbers are of course, different percentage-wise, but surprise, surprise, different companies doing different things doing different percentages, I'm sure only AWS knows for sure.Everett: Yeah, I think the biggest surprise was just the—and, this could very well just be kind of measurement method, but I really expected to see AI services driving more costs, whether it was GPU instances, or AI-specific services—which we actually didn't report on at all, just because they weren't material—or just any indication that AI was a real driver of cloud spending. But I think what you see instead is sort of the same old folks at the top, and if you look at the breakdown of services across providers, that's, you know, compute, database, storage, bandwidth, monitoring. And if you look at our percentage of AI costs as a percentage of EC2 costs, it's relatively flat, quarter over quarter. So, I would have thought that would have shown up in some way in our data and we really didn't see it.Corey: It feels like there's a law of large numbers things. Everyone's talking about it. It's very hype right now—Everett: Yeah.Corey: But it's also—you talk to these companies, like, “Okay, we have four exabytes of data that we're storing and we have a couple 100,000 instances at any given point in time, so yeah, we're going to start spending $100,000 a month on our AI adventures and experiments.” It's like, that's just noise and froth in the bill, comparatively.Everett: Exactly, yeah. And so, that's why I think Microsoft's thought about AI driving a lot of growth in the coming quarters is, we'll see how that plays out, basically. The one other thing I would point to is—and this is probably not surprising, maybe, for you having been in the infrastructure world and seeing a lot of this, but for me, just seeing the length of time it takes companies to upgrade their instance cycles. We're clocking in at almost three years since the C6 series instances have been released and for just now seeing C6 and R6 start to edge above 10% of our compute usage. I actually wonder if that's just the stranglehold that Intel has on cloud computing workloads because it was only last year around re:Invent that the C6in and the Intel version of the C6 series instances had been released. So, I do think in general, there's supposed to be a price-to-performance benefit of upgrading your instances, and so sometimes it surprises me to see how long it takes companies to get around to doing that.Corey: Generation 6 to 7 is also 6% more expensive in my sampling.Everett: Right. That's right. I think Amazon has some work to do to actually make that price-to-performance argument, sort of the way that we were discussing with gp2 versus gp3 volumes. But yeah, I mean, other than that, I think, in general, my view is that we're past the worst of it, if you will, for cloud spending. Q4 was sort of a real letdown, I think, in terms of the data we had and the earnings that these cloud providers had and I think Q1 is actually everyone looking forward to perhaps what we call out at the beginning of the report, which is a return to normal spend patterns across the cloud.Corey: I think that it's going to be an interesting case. One thing that I'm seeing that might very well explain some of the reluctance to upgrade EC2 instances has been that a lot of those EC2 instances are databases. And once those things are up and running and working, people are hesitant to do too much with them. One of the [unintelligible 00:27:29] roads that I've seen of their savings plan approach is that you can migrate EC2 spend to Fargate to Lambda—and that's great—but not RDS. You're effectively leaving a giant pile of money on the table if you've made a three-year purchase commitment on these things. So, all right, we're not going to be in any rush to migrate to those things, which I think is AWS getting in its own way.Everett: That's exactly right. When we encounter customers that have a large amount of database spend, the most cost-effective option is almost always basically bare-metal EC2 even with the overhead of managing the backup-restore scalability of those things. So, in some ways, that's a good thing because it means that you can then take advantage of the, kind of, heavy committed use options on EC2, but of course, in other ways, it's a bit of a letdown because, in the ideal case, RDS would scale with the level of workloads and the economics would make more sense, but it seems that is really not the case.Corey: I really want to thank you for taking the time to come on the show and talk to me. I'll include a link in the [show notes 00:28:37] to the Cost Report. One thing I appreciate is the fact that it doesn't have one of those gates in front of it of, your email address, and what country you're in, and how can our salespeople best bother you. It's just, here's a link to the PDF. The end. So, thanks for that; it's appreciated. Where else can people go to find you?Everett: So, I'm on Twitter talking about cloud infrastructure and AI. I'm at@retttx, that's R-E-T-T-T-X. And then of course, Vantage also did quick hot-takes on this report with a series of graphs and explainers in a Twitter thread and that's @JoinVantage.Corey: And we will, of course, put links to that in the [show notes 00:29:15]. Thank you so much for your time. I appreciate it.Everett: Thanks, Corey. Great to chat.Corey: Everett Berry, growth in open-source at Vantage. I'm Cloud Economist Corey Quinn and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice along with an angry, insulting comment that will increase its vitriol generation over generation, by approximately 6%.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.

What if the solar system had two suns? Neil deGrasse Tyson and Chuck Nice give a sneak peek into our patron-only Q&As with questions about the three body problem, galaxy formation, the alpha centauri system, and more. NOTE: StarTalk+ Patrons can listen to this entire episode commercial-free here: https://startalkmedia.com/show/moonmoons-gravitons-and-more/Thanks to our Patrons Donald Jones, Mohammed Taha Faridi, Jon Barnett, Harmon Dhaliwal, and Sean Griffen for supporting us this week.Photo Credit: Elmi1966, CC BY-SA 4.0, via Wikimedia Commons