Podcasts about Werner Vogels

With only nine months to launch Max, Tom Leaman, VP of Site Reliability Engineering at Warner Bros. Discovery had to move fast to keep millions of viewers streaming smoothly. Learn about their innovative approach to measuring efficiency, managing global operations, and building resilient systems at massive scale with your hosts Simon Elisha and Dr. Werner Vogels. Learn More: http://thefrugalarchitect.com/architects/tom-leaman-warner-bros-discovery.html

What started as CEO and founder John Mill's need for better wildfire information grew into tech that supported 9 million users during the LA fires. Learn how the founders of Watch Duty grew through constraints to scale mission-critical software as Amazon CTO Werner Vogels and your host Simon Elisha chat with John Mills and CTO Dave Merritt of Watch Duty about the early days of this startup with a mission to save lives. Learn More: https://bit.ly/43OLliG

En este episodio especial del podcast de Charlas Técnicas AWS, cerramos oficialmente la Temporada 5 con el esperado re:Cap de re:Invent 2024. Y para hacerlo aún más especial, nos acompaña Marcia Villalba, co-host original del podcast.Hablamos de todo lo que dejó este re:Invent: los nuevos chips Graviton4, avances en inteligencia artificial con Amazon Q Developer y los nuevos modelos NOVA, mejoras en infraestructura como la fibra óptica de núcleo hueco, y la evolución de bases de datos con Aurora DSQL. Todo esto, mezclado con reflexiones sobre cómo AWS sigue apostando por la simplicidad sin perder su esencia.Si te perdiste el evento o quieres repasar los anuncios más importantes, este episodio es para ti.Temas destacados:[00:00] Introducción y regreso de Marcia Villalba.[01:35] Balance general de re:Invent 2024 y tendencias.[05:30] 10 años de AWS Lambda [08:20] Infraestructura avanzada: Hollow-Core Fiber y relojes atómicos.[09:45] Innovaciones en bases de datos: Aurora DSQL y DynamoDB Strong Consistency.[15:40] Mejoras en Amazon S3: S3 Metadata Search y S3 Tables.[17:20] Lanzamiento de Graviton4, Systolic Arrays y Neuron Kernel Interface (NKI).[21:07] Amazon Bedrock, agentes y novedades[26:17] Amazon Q Developer: integración con GitHub, .Net, VMware y Mainframe.[27:40] Amazon NOVA, nuevos modelos de IA Generativa[32:07] Herramientas para IA Generativa, prompt caching, inteligent routing.[38:20] Reflexiones sobre la keynote de Werner Vogels y la simplicidad en AWS.[44:30] Próximos pasos y sorpresas para la Temporada 6.[46:04] El regalo de Marcia.Nos vemos en la Temporada 6 con más contenido, historias de la comunidad y sorpresas. ¡Gracias por acompañarnos este año!

Le premier episode 'Quoi de neuf ?' de cette année revient sur les prédictions technologiques pour 2025 et au delà de Werner Vogels, CTO d'Amazon. Nous parlons aussi des nouveautés des dernières semaines: Amazon bedorck et Sagemake acceuillent Les nouveaux modèles de Meta (Llama 3.3) et de Stability.ai (Stable Diffusion 3.5). On parle aussi d'un nouveau connecteur open source pour Apache Flink et Amazon Kinesis Data Stream, de Amazon Workspaces qui est désormais accessible via AWS Global Accelerator. Enfin nous abordons des nouvelles fonctions de Resources Explorer et dans la console de gestion des factures et des coûts (AWS Billing and Costs Management).

It is the end of re:Invent 2024! Simon gives you a quick look at Werner's keynote, reveals the t-shirt choice, shares some tips for making the most of re:Invent content, and even drops an "easter egg" in as well!

In 1969, Mr. Rogers went before the US Senate Commerce Committee to request funds to support the growth of Public Broadcasting. His heartwarming request is often remembered as a pivotal moment in American television history, highlighting the importance of educational programming that serves the public good. Today, that mission endures, and Mike Norton and his team at PBS continue to honor it in their own way -- by stretching every public dollar as far as it can go. In a world where resources are finite but the demand for quality, accessible content is ever-growing, these engineers work behind the scenes to maximize efficiency, leverage innovative technologies, and make every penny count... for viewers like you. Fred Rogers' Testimony: https://www.youtube.com/watch?v=fKy7ljRr0AA Blog Post: https://www.thefrugalarchitect.com/architects/mike-norton-pbs.html

Join Simon Elisha and Dr. Werner Vogels, as they kick off a new mini-series, "The Frugal Architect," with Dan Conti, whose journey from the constrained world of embedded systems to WeTransfer's cloud architecture is a masterclass in frugal innovation. In his early career, Dan wrestled with MP3 players where 48K of RAM was a luxury. This experience cultivated a deep appreciation for efficiency that would prove crucial at WeTransfer. As CTO, Dan applied this resourceful mindset to cloud computing, where easy scaling often masked hidden waste. His team's efforts to optimize storage, improve observability, and align technology with environmental values showcased that in the cloud, frugality isn't about penny-pinching—it's about squeezing every ounce of value from your architecture -- and doing it sustainably. Blog Post Link: https://www.thefrugalarchitect.com/architects/dan-conti-wetransfer.html

We sit down this week with Werner Vogels, the Amazon chief technology officer, at Amazon headquarters in Seattle. We talked about the evolution of artificial intelligence, the promise of AI in healthcare and the environment, his broader tech predictions for the year, and one of his most iconic traditions at the company's annual cloud conference. Werner Vogels - All Things Distributed Archive of Now Go Build episodes AWS re:Invent 2023 - Keynote with Dr. Werner Vogels Tech Predictions for 2024 and beyond @Werner on X. With GeekWire co-founder Todd Bishop; Edited by Curt Milton.See omnystudio.com/listener for privacy information.

In this episode of IT Talks, Sebastian Jansson will help you unravel the concepts of synchronous and asynchronous. The IT world in its natural form is mostly synchronous (tasks performed in a coordinated order), while the world we live in is mostly asynchronous (not bound to a specific order or pace). Based on these concepts, what happens in today's society as the IT world and the physical world become increasingly interconnected? And how does one need to think when building adaptive systems capable of handling future changes? Deepen your understanding of the topic by listening to this episode!  Link to YouTube: AWS re:Invent 2022 - Keynote with Dr. Werner Vogels: https://www.youtube.com/watch?v=RfvL_423a-I

Ethan Evans is a writer, career coach, course instructor, and retired VP at Amazon. During his 15 years at Amazon, he helped invent Prime Video, Amazon Video, the Amazon Appstore, Prime Gaming (formerly Twitch Prime), and Twitch Commerce. Prior to Amazon, Ethan spent 12 years in technical leadership roles at several East Coast startups. He writes a newsletter, Level Up, which publishes candid career advice and has a growing community of ambitious professionals to connect with. Ethan also offers a range of Leadership Development Courses via live online classes and on-demand courses. In this episode, we discuss:• The Magic Loop framework: a five-step process to grow your career• A handful of reasons why people get stuck in their career growth• Advice on how to break out of a career plateau• How to cultivate inventiveness in your work• How to stand out in interviews• A personal story of failing Jeff Bezos and lessons learned• Contrarian opinions on the return-to-office movement and doing business on a handshake—Brought to you by Sidebar—Accelerate your career by surrounding yourself with extraordinary peers | Sprig—Build a product people love | Arcade Software—Create effortlessly beautiful demos in minutes—Find the full transcript at: https://www.lennyspodcast.com/taking-control-of-your-career-ethan-evans-amazon/—Where to find Ethan Evans:• LinkedIn: https://www.linkedin.com/in/ethanevansvp/• Substack: https://levelupwithethanevans.substack.com/—Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• X: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/—In this episode, we cover:(00:00) Ethan's background(04:25) The Magic Loop(08:31) The goal of the Magic Loop(10:59) Clarifications on the framework(12:46) Success stories(17:22) The importance and effectiveness of the Magic Loop(19:01) A quick summary of the steps in the Magic Loop(21:46) What if you're not pursuing a promotion?(23:09) How to break out of a career plateau(28:52) How to become systematically inventive(36:04) Interview advice and how to stand out(40:43) A story of failing Jeff Bezos(50:31) Lessons learned from that failure(57:30) What Ethan would have done differently(01:00:35) Amazon's leadership principles(01:08:52) Contrarian corner: Returning to the office vs. staying remote(01:10:39) Contrarian corner: Doing business on a handshake(01:11:52) Lightning round—Referenced:• The Magic Loop: https://www.lennysnewsletter.com/p/the-magic-loop• SDE levels: https://www.masaischool.com/blog/understanding-sde-levels-sde-1-vs-sde-2-vs-sde-3-differences/• What Got You Here Won't Get You There: How Successful People Become Even More Successful: https://www.amazon.com/What-Got-Here-Wont-There/dp/1401301304• Thomas Edison's quote: https://www.brainyquote.com/quotes/thomas_a_edison_109928• Jeff Bezos: Amazon and Blue Origin | Lex Fridman Podcast: https://www.youtube.com/watch?v=DcWqzZ3I2cY• Unpacking Amazon's unique ways of working | Bill Carr (author of Working Backwards): https://www.lennyspodcast.com/unpacking-amazons-unique-ways-of-working-bill-carr-author-of-working-backwards/• Working Backwards: Insights, Stories, and Secrets from Inside Amazon: https://www.amazon.com/Working-Backwards-Insights-Stories-Secrets/dp/1250267595• Jeff Wilke on X: https://twitter.com/jeffawilke• Andy Jassy on LinkedIn: https://www.linkedin.com/in/andy-jassy-8b1615/• Werner Vogels on LinkedIn: https://www.linkedin.com/in/wernervogels/• Amazon's Silk browser explained: https://www.androidpolice.com/amazon-silk-browser-explainer/• Chickens and pigs: https://www.scrum.org/resources/chickens-and-pigs• 58% of tech employees experience imposter syndrome. Here's how to overcome it: https://medium.com/wearefutureworks/58-of-tech-employees-experience-imposter-syndrome-heres-how-to-overcome-it-78172d8a2258• Jeff Bezos to exec after product totally flopped: ‘You can't, for one minute, feel bad': https://www.cnbc.com/2020/05/22/jeff-bezos-why-you-cant-feel-bad-about-failure.html• Amazon's leadership principles: https://www.amazon.jobs/content/en/our-workplace/leadership-principles• Sam Altman on X: https://twitter.com/sama• Decisive: How to Make Better Choices in Life and Work: https://www.amazon.com/Decisive-Make-Better-Choices-Life/dp/0307956393• Leadership and Self-Deception: Getting Out of the Box: https://www.amazon.com/Leadership-Self-Deception-Getting-Out-Box/dp/1523097809• The Almanack of Naval Ravikant: A Guide to Wealth and Happiness: https://www.amazon.com/Almanack-Naval-Ravikant-Wealth-Happiness/dp/1544514212/• Angel list: https://venture.angellist.com/naval/syndicate• Naval Ravikant on X: https://twitter.com/naval• 1923 on Paramount+: https://www.paramountplus.com/shows/1923/• Yellowstone on Paramount+: https://www.paramountnetwork.com/shows/yellowstone• Chuckit! dog toys: https://www.chuckit-toys.co.uk/• Luke 12:48: https://law.utk.edu/2016/05/10/to-whom-much-is-given-much-will-be-required• The Challenger space shuttle disaster: https://en.wikipedia.org/wiki/Space_Shuttle_Challenger_disaster• Ethan's popular course on Maven: https://maven.com/ethan-evans/break-through-to-executive—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com.—Lenny may be an investor in the companies discussed. Get full access to Lenny's Newsletter at www.lennysnewsletter.com/subscribe

Strap in for a discussion on the big reveals from the AWS re:Invent conference, where AI stole the limelight. We, your hosts - Chris Miles, Alex Perkins, and Tim McConnaughy, dissect the announcements and how this tech giant is embedding AI in their cloud operations. And it's not just about the big names - we also delve into the AI-powered Amazon Q,  a promising tool that might just revolutionize network troubleshooting.But wait, there's more! Picture a constellation of satellites granting private access to AWS. Now imagine AWS outposts on the moon. Sounds like science fiction, right? Well, we're here to tell you it's closer to reality than you think. We're excited to share our thoughts on these trail-blazing developments in satellite connectivity and the latest updates to CloudWatch. This episode is a must-listen for anyone keen on staying ahead in the rapidly evolving world of cloud computing.As we wrap up, we'll take a nostalgic trip down memory lane. Remember the early days of online shopping and the excitement surrounding limited product releases? We'll chat about how that frenzy has evolved, influenced by innovations in cloud technology. We'll also discuss the keynotes from the AWS re:Invent conference, focusing on Adam Selipsky's opening speech and Werner Vogels' emphasis on cost in functional design. Don't miss out on our take on these industry-shaping keynotes and what they signal for the future of cloud computing. Buckle up for a thrilling journey through the universe of AI and cloud technology!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

In our final re:Invent recap episode, Simon shares news and announcements from Dr. Werner Vogels' keynote. We'll cover why artificial intelligence (AI) is something every builder must consider when developing systems and its tremendous impact on our world. Also, stay tuned for episodes in the next few weeks where we'll dive deep into some of our favorite re:Invent launches. Be sure to tune in!

#235: In the mid-2000s, Werner Vogels introduced the idea of "you build it, you run it". This concept suggested that the same team responsible for building a product should also be responsible for running and maintaining it. However, despite the initial enthusiasm, we have yet to see this phrase truly materialize in practice. The industry has faced challenges in fully realizing the "build it, run it" philosophy. In this episode, we speak with Kaspar von Grünberg, founder & CEO at Humanitec, about why "shifting left" to the developers really isn't all it's cracked up to be and how instead cleaner abstractions can bridge the gap in understanding between non-technical managers and the developers in the trenches.   Kaspar's contact information: Twitter: https://twitter.com/kaspar_official LinkedIn: https://www.linkedin.com/in/kvgruenberg/   YouTube channel: https://youtube.com/devopsparadox   Books and Courses:  Catalog, Patterns, And Blueprints https://www.devopstoolkitseries.com/posts/catalog/   Review the podcast on Apple Podcasts: https://www.devopsparadox.com/review-podcast/   Slack: https://www.devopsparadox.com/slack/   Connect with us at: https://www.devopsparadox.com/contact/

Dr. Werner Vogels is Vice President & Chief Technology Officer at Amazon where he is responsible for driving the company's customer-centric technology vision. He is a pioneer in cloud computing and has been instrumental in shaping the modern cloud infrastructure.    In this episode of Vietsuccess Business, he shares his expert insights on the latest trends and advancements in cloud computing and their implications for businesses. He also offers practical strategies for organizations looking to stay ahead of the curve and take advantage of the latest advancements in cloud computing.   Big thanks Amazon Web Services for making this episode possible.   Tiến sĩ Werner Vogels là Phó Chủ tịch kiêm Giám đốc Công nghệ tại Amazon, nơi ông chịu trách nhiệm thúc đẩy tầm nhìn công nghệ lấy khách hàng làm trung tâm của công ty. Ông là người tiên phong trong lĩnh vực điện toán đám mây và đóng góp nhiều công sức trong việc định hình cơ sở hạ tầng đám mây hiện đại.   Trong tập mới nhất của Vietsuccess Business, ông sẽ chia sẻ những hiểu biết mang tính chuyên môn về các xu hướng, tiến bộ mới nhất trong điện toán đám mây cũng như ý nghĩa của chúng đối với các doanh nghiệp. Ông cũng đưa ra các chiến lược thiết thực giúp các tổ chức nắm bắt và dẫn đầu trong việc áp dụng những tiến bộ mới nhất của điện toán đám mây. Hãy cùng đón xem!   Cảm ơn Amazon Web Services đã đồng hành cùng chúng tôi trong tập Podcast này của Vietsuccess Business.   Dẫn chuyện - Host | Quốc Khánh Kịch bản - Scriptwriting | Quốc Khánh, Thu Bình Biên Tập – Editor | Thu Bình Truyền thông - Social team | Phương Dung, Cẩm Vân Sản Xuất -  Producer | Anneliese Mai Nguyen  Quay Phim - Cameraman | Khanh Trần, Hải Long, Thanh Quang, Nhật Trường Âm Thanh - Sound | Khanh Trần  Hậu Kì – Post Production | Khanh Trần Thiết kế - Design | Nghi Nghi Makeup Artist | Ngọc Nga    #Vietsuccess #VietsuccessBusiness #dientoandammay #Cloudcomputing #cloudcomputingtrends #AWS #DrWernerVogels

Welcome to the newest episode of The Cloud Pod podcast! Justin, Ryan, Jonathan, Matthew and Peter are your hosts this week as we discuss all things cloud and AI,  Titles we almost went with this week: The Cloud Pod is better than Bob's Used Books The Cloud Pod sets up AWS notifications for all The Cloud Pod is non-differential about privacy in BigQuery The Cloud Pod finds Windows Bob The Cloud Pod starts preparing for its Azure Emergency today A big thanks to this week's sponsor: Foghorn Consulting, provides top-notch cloud and DevOps engineers to the world's most innovative companies. Initiatives stalled because you have trouble hiring?  Foghorn can be burning down your DevOps and Cloud backlogs as soon as next week.

Jeremy Howard thinks Mojo might be the biggest programming language advance in decades, Amelia Wattenberger is not impressed by AI chatbots, a leaked Google memo admits big tech has no AI moats & Werner Vogels reminds us that monoliths are not dinosaurs.

Jeremy Howard thinks Mojo might be the biggest programming language advance in decades, Amelia Wattenberger is not impressed by AI chatbots, a leaked Google memo admits big tech has no AI moats & Werner Vogels reminds us that monoliths are not dinosaurs.

Jeremy Howard thinks Mojo might be the biggest programming language advance in decades, Amelia Wattenberger is not impressed by AI chatbots, a leaked Google memo admits big tech has no AI moats & Werner Vogels reminds us that monoliths are not dinosaurs.

#205: At the end of 2022, Werner Vogels, CTO at Amazon, published a blog post about the tech predictions for 2023 and (more importantly) beyond. In this episode, Darin and Viktor dig into a couple of those predictions, namely simulated worlds (digital twins) and custom silicon.   Tech predictions for 2023 and beyond https://www.allthingsdistributed.com/2022/12/tech-predictions-for-2023-and-beyond.html   YouTube channel: https://youtube.com/devopsparadox/   Books and Courses: Catalog, Patterns, And Blueprints https://www.devopstoolkitseries.com/posts/catalog/   Review the podcast on Apple Podcasts: https://www.devopsparadox.com/review-podcast/   Slack: https://www.devopsparadox.com/slack/   Connect with us at: https://www.devopsparadox.com/contact/

Platform engineering “is the art of designing and binding all of the different tech and tools that you have inside of an organization into a golden path that enables self service for developers and reduces cognitive load,” said Kaspar Von Grünberg, founder and CEO of Humanitec, in this episode of The New Stack Makers podcast.  This is structure is important for individual contributors, Grünberg said, as well as backend engineers: “if you look at the operation teams, it reduces their burden to do repetitive things. And so platform engineers build and design internal developer platforms, and help and serve users. “ This conversation, hosted by Heather Joslyn, TNS features editor, dove into platform engineering: what it is, how it works, the problems it is intended to solve, and how to get started in building a platform engineering operation in your organization. It also debunks some key fallacies around the concept. This episode was sponsored by Humanitec.The Limits of ‘You Build It, You Run It'The notion of “you build it, you run it” — first coined by Werner Vogels, chief technology officer of [sponsor_inline_mention slug="amazon-web-services-aws" ]Amazon,[/sponsor_inline_mention] in a 2006 interview — established that developers should “own” their applications throughout their entire lifecycle. But, Grünberg said, that may not be realistic in an age of rapidly proliferating microservices and multiple, distributed deployment environments. “The scale that we're operating today is just totally different,” he said. “The applications are much more complex.” End-to-end ownership, he added, is “a noble dream, but unfair towards the individual contributor. We're asking developers to do so much at once. And then we're always complaining that the output isn't there or not delivering fast enough. But we're not making it easy for them to deliver.” Creating a “golden path” — though the creation by platform teams of internal developer platforms (IDPs) — can not only free developers from unnecessary cognitive load, Grünberg said, but also help make their code more secure and standardized. For Ops engineers, he said, the adoption of platform engineering can also help free them from doing the same tasks over and over. “If you want to know whether it's a good idea to look at platform engineering, I recommend go to your service desk and look at the tickets that you're receiving,”  Grünberg said. “And if you have things like, ‘Hey, can you debug that deployment?' and ‘Can you spin up in a moment all these repetitive requests?' that's probably a good time to take a step back and ask yourself, ‘Should the operations people actually spend time doing these manual things?'”The Biggest Fallacies about Platform EngineeringFor organizations that are interested in adopting platform engineering, the Humanitec CEO attacked some of the biggest misconceptions about the practice. Chief among them: failing to treat their platform as a product, in the same way a company would begin creating any product, by starting with research into customer needs. “If you think about how we would develop a software feature, we wouldn't be sitting in a room and taking some assumptions and then building something,” he said. “We would go out to the user, and then actually interview them and say, ‘Hey, what's your problem? What's the most pressing problem?'” Other fallacies embraced by platform engineering newbies, he said, are “visualization” — the belief that all devs need is another snazzy new dashboard or portal to look at — and believing the platform team has to go all-in right from the start, scaling up a big effort immediately. Such an effort, he said is “doomed to fail.” Instead, Grünberg said, “I'm always advocating for starting really small, come up with what's the most lowest common tech denominator. Is that containerization with EKS? Perfect, then focus on that." And don't forget to give special attention to those early adopters, so they can become evangelists for the product. “make them fans, prioritize the right way, and then show that to other teams as a, ‘Hey, you want to join in? OK, what's the next cool thing we could build?'” Check out the entire episode for much more detail about platform engineering and how to get started with it.

Mitä tapahtuu atk:n, IT:n ja teknologian maailmassa vuonna 2023? Vikasietotila on ruopannut listan erilaisten tahojen julkaisemia ennusteita ja valikoi niistä omat suosikkinsa, yhteensä 9 kappaletta. Varoitus: on hyvin todennäköistä, että näiden osumatarkkuus on luokkaa 0–1%.  Mikäli pidät podcastista ja haluat tukea sen tekijöitä rahallisesti, suuntaa Supporting Cast -sivullemme. Vinkit Panun softavinkki on Tails Karin lukuvinkki on Spotify Content and Advertising Chief Dawn Ostroff Talks Joe Rogan, Meghan Markle, Podcast Cancelations and More Materiaalit Netflix will be next on Microsoft's shopping list What Is The Roku Channel? Roku's Streaming Service Explained Microsoft responds to FTC case seeking to block Activision Blizzard deal, saying it wouldn't hurt competition Soundtrack the World (Audio) Free Ad-Supported TV (FAST) Is the Future, and the Future Is Now The latest study by IEEE reveals the most important tech areas in 2023 13 predictions for tech platforms in 2023 (The Verge / Casey Newton) A meta-analysis of 2023 tech trends & predictions Gartner Top 10 Strategic Predictions for 2023 and Beyond AWS's Werner Vogels' Tech Predictions for 2023 and Beyond Tech in 2023: Here's what is going to really matter (ZDNetin kooste) Deloitte: TMT Predictions 2023 Big Ideas in Tech for 2023: An a16z Omnibus Koneviestin huoltovisa Web3 is Going Just Great LastPassin tietovuodon kommentaaria 2023 Trending What is a passkey? Music Player Daemon

Mitä tapahtuu atk:n, IT:n ja teknologian maailmassa vuonna 2023? Vikasietotila on ruopannut listan erilaisten tahojen julkaisemia ennusteita ja valikoi niistä omat suosikkinsa, yhteensä 9 kappaletta. Varoitus: on hyvin todennäköistä, että näiden osumatarkkuus on luokkaa 0–1%. Mikäli pidät podcastista ja haluat tukea sen tekijöitä rahallisesti, suuntaa Supporting Cast -sivullemme.VinkitPanun softavinkki on TailsKarin lukuvinkki on Spotify Content and Advertising Chief Dawn Ostroff Talks Joe Rogan, Meghan Markle, Podcast Cancelations and MoreMateriaalitNetflix will be next on Microsoft's shopping listWhat Is The Roku Channel? Roku's Streaming Service ExplainedMicrosoft responds to FTC case seeking to block Activision Blizzard deal, saying it wouldn't hurt competitionSoundtrack the World (Audio)Free Ad-Supported TV (FAST) Is the Future, and the Future Is NowThe latest study by IEEE reveals the most important tech areas in 202313 predictions for tech platforms in 2023 (The Verge / Casey Newton)A meta-analysis of 2023 tech trends & predictionsGartner Top 10 Strategic Predictions for 2023 and BeyondAWS's Werner Vogels' Tech Predictions for 2023 and BeyondTech in 2023: Here's what is going to really matter (ZDNetin kooste)Deloitte: TMT Predictions 2023Big Ideas in Tech for 2023: An a16z OmnibusKoneviestin huoltovisaWeb3 is Going Just GreatLastPassin tietovuodon kommentaaria2023 TrendingWhat is a passkey?Music Player DaemonLearn more about your ad choices. Visit megaphone.fm/adchoices

Listen in podcast app* Market update* Last Fed Meeting Until February 23'* Navigating the Canadian Economy in 23'* Top 10 Innovations of 2022* What to get your husband for Christmas in this year* Recommendations and PredictionsListen on Apple, Spotify, or Google Podcasts.If you aren't in the Reformed Millennials Facebook Group join us for daily updates, discussions, and deep dives into the investable trends Millennials should be paying attention to.

The Cloud Pod recaps all of the positives and negatives of Amazon ReInvent 2022, the annual conference in Las Vegas, bringing together 50,000 cloud computing professionals.  This year's keynote speakers include Adam Selpisky, CEO of Amazon Web Services, Swami Sivasubramanian, Vice President of Data and Machine Learning at AWS and Werner Vogels, Amazon's CTO.  Attendees and web viewers were treated to new features and products, such as AWS Lambda Snapstart for Java Functions, New Quicksight capabilities and quality-of-life improvements to hundreds of services.  Justin, Jonathan, Ryan, Peter and Special guest Joe Daly from the Finops foundation talk about the show and the announcements. Thank you to our sponsor, Foghorn Consulting, which provides top notch cloud and DevOps engineers to the world's most innovative companies. Initiatives stalled because you're having trouble hiring? Foghorn can be burning down your DevOps and Cloud backlogs as soon as next week. Episode Highlights ⏰ AWS Pricing Calculator now supports modernization cost estimates for Microsoft workloads. ⏰ AWS Re:Invent 2022 announcements and keynote updates. Top Quote

Recapitulación del Keynote del VP y CTO de amazon.com Werner Vogels quien describe como los clientes y AWS estan utilizando patrones de arquitecturas originales para construir aplicacaciones escalables, resilientes y tolerantes a fallos, ademas se mencionan innovaciones y tecnologias emergentes para crear sistemas que no se podian imaginar en el pasado y describe como la nube es el centro de esta nueva era de innovacion. Material Adicional: https://www.allthingsdistributed.com/2022/11/amazon-1998-distributed-computing-manifesto.html

This week we discuss Werner's AWS Keynote, Event-Based Architectures and the potential of ChatGPT. Plus, some thoughts on International Condiments. Watch the YouTube Live Recording of Episode 390 (https://www.youtube.com/watch?v=CRy69wGMROM) Runner-up Titles It's never stopped us before. Ranch dressing divine/Before the Big Bang, it was/Eternal condiment Three kinds of mayonnaise An aspirational architectural pattern. There's not a lot of architectural thought out there. I don't have a computer science degree. Mid-Code It's just a bunch of programming, how hard could it be? Is it a utopian Wall-E or not? Rundown AWS re:Invent 2022 - Keynote with Dr. Werner Vogels (https://www.youtube.com/watch?v=RfvL_423a-I) Amazon announces Eventbridge Pipes, a simpler way to connect events (https://techcrunch.com/2022/12/01/amazon-announces-eventbridge-pipes-a-simpler-way-to-connect-events-from-multiple-services/) Design Patterns (https://www.amazon.com/gp/product/0201633612/) book ChatGPT: Optimizing Language Models for Dialogue (https://openai.com/blog/chatgpt/) ChatGPT will replace StackOverflow? (https://twitter.com/anildash/status/1599655544486187009) Automating bullshit - OpenAI ChatGPT removes office worker toil (https://buttondown.email/cote/archive/automating-bullshit-openai-chatgpt-removes-office/) Coté doesn't need to write those survey analysis blogs anymore (https://beta.openai.com/playground/p/w2tNHzzV7DXsz63ZWQfKGpD4?model=text-davinci-003). Relevant to your Interests Elastic Earnings (https://twitter.com/jaminball/status/1598068640137428992?s=46&t=eFF6wBlhOCFaLPPQf7nSLQ) Snowflake Earnings (https://twitter.com/jaminball/status/1598348082839977984?s=20&t=3ZTOl6JnPJu8vtcP7YUC4Q) IBM and Maersk Abandon Ship on TradeLens Logistics Blockchain (https://www.coindesk.com/business/2022/11/30/ibm-and-maersk-abandon-ship-on-tradelens-logistics-blockchain/) OpenStack cloud sees explosive growth (https://www.zdnet.com/article/openstack-cloud-sees-explosive-growth/) Amazon EC2 Instance Types - Amazon Web Services (https://aws.amazon.com/ec2/instance-types/?trk=3478554f-e06b-44d5-8171-41d0ea80c8c9&sc_channel=ps&s_kwcid=AL!4422!3!544066093425!p!!g!!graviton%20processor&ef_id=Cj0KCQiAvqGcBhCJARIsAFQ5ke48NKL5fH2ETDPdMavKJxSfxS6luQdG2ZGGW51UzVtV8ev8GSxc2ucaAqoCEALw_wcB:G:s&s_kwcid=AL!4422!3!544066093425!p!!g!!graviton%20processor) HYPR, the Leader in Phishing-Resistant MFA, Raises $25M (https://blog.hypr.com/press-releases/hypr-the-leader-in-phishing-resistant-mfa-raises-25m?_ga=2.20718968.1905140386.1669908801-1738015730.1669908801) Future is quietly shutting down (https://twitter.com/robaeprice/status/1598393044503502860) Andreessen Horowitz's buzzy tech publication Future is shutting down (https://www.businessinsider.com/a16z-future-closes-staff-exit-2022-11?international=true&r=US&IR=T) AWS launches Application Composer, a low-code tool for building serverless apps (https://techcrunch.com/2022/12/01/aws-launches-application-composer-a-low-code-tool-for-building-serverless-apps/) No one seemed to see Bret Taylor stepping away from Salesforce (even Marc Benioff) (https://techcrunch.com/2022/12/01/no-one-seemed-to-see-bret-taylor-stepping-away-from-salesforce-even-marc-benioff/) Major password manager LastPass suffered a breach — again (https://www.npr.org/2022/12/01/1140076375/major-password-manager-lastpass-suffered-a-breach-again) Here's everything AWS announced in its re:Invent data keynote (https://techcrunch.com/2022/11/30/heres-everything-aws-announced-today/) Cloudflare hikes prices by a quarter (https://www.theregister.com/2022/12/01/cloudflare_price_rises_annual_exemptions/) Twitter lawsuit (https://twitter.com/AkivaMCohen/status/1598487532764798983) the only cheat sheet you need (https://github.com/chubin/cheat.sh) Google Plans to Lay Off 10,000 'Poor Performing' Employees. Why That's a Big Lie, According to Harvard Professor (https://www.inc.com/nick-hobson/googles-plan-to-lay-off-10000-poor-performing-employees-is-based-on-a-big-lie-according-toharvard-professor.html) Broadcom again tries to quash VMware price rise rumors (https://www.theregister.com/2022/12/01/vmware_broadcom_prices_nutanix_q123/) Rackspace email outage continues as migrations prove hard (https://www.theregister.com/2022/12/05/rackspace_hosted_exchange_security_update/) If Rowy has its way, if you can use Excel, you can build software (https://techcrunch.com/2022/12/05/rowy-pre-seed/) Axiom launches its automated identity and access management platform (https://techcrunch.com/2022/12/06/axiom-launches-its-automated-identity-and-access-management-platform/) The E-Mail Newsletter for the Mogul Set (https://www.newyorker.com/news/annals-of-communications/the-e-mail-newsletter-for-the-mogul-set) The EU hosted a 24-hour party in its $400,000 metaverse to appeal to young people, but pretty much no one showed up (https://www.businessinsider.com/eu-hosts-400000-metaverse-party-barely-anyone-shows-up-2022-12) mIRC ended its lifetime license agreement with all who purchased its software 10 years out (https://www.pocnetwork.net/internet-news/mirc-ended-its-lifetime-license-agreement-with-all-who-purchased-its-software-10-years-out/) Security compliance and automation platform Drata nabs $200M at $2B valuation (https://techcrunch.com/2022/12/07/security-compliance-and-automation-platform-drata-nabs-200m-at-2b-valuation/) 9 insights on real world container use (https://www.datadoghq.com/container-report/) Bret Taylor to step down as Salesforce co-CEO (https://www.axios.com/2022/11/30/bret-taylor-salesforce-ceo-step-down?utm_source=newsletter&utm_medium=email&utm_campaign=newsletter_axioslogin&stream=top) Tableau Software CEO Mark Nelson steps down (https://www.geekwire.com/2022/tableau-software-ceo-mark-nelson-steps-down/) Confirmed: Slack CEO Stewart Butterfield stepping down in January (https://techcrunch.com/2022/12/05/report-slack-ceo-stewart-butterfield-stepping-down-in-january/) Microsoft Teams adds free communities feature to take on Facebook and Discord (https://www.theverge.com/2022/12/7/23497938/microsoft-teams-communities-feature) Nonsense Advent of Code (https://adventofcode.com/2022) The difference between a snafu, a shitshow, and a clusterfuck (https://qz.com/work/1225213/the-difference-between-a-snafu-a-shitshow-and-a-clusterfuck/) Dangerously Advanced Git (https://twitter.com/QuinnyPig/status/1598382103829544961?s=20&t=3ZTOl6JnPJu8vtcP7YUC4Q) Conferences THAT Conference Texas Speakers and Schedule (https://that.us/events/tx/2023/schedule/), Round Rock, TX Jan 15th-18th Use code SDT for 5% off New State of Open Con 2023, (https://stateofopencon.com/sponsors/) London, UK, February 7th-8th 2023 CloudNativeSecurityCon North America (https://events.linuxfoundation.org/cloudnativesecuritycon-north-america/), Seattle, Feb 1 – 2, 2023 DevOpsDays Birmingham, AL 2023 (https://devopsdays.org/events/2023-birmingham-al/welcome/), April 20 - 21, 2023 Listener Feedback Send “End of Year” listener questions to questions@softwaredefinedtalk.com (mailto:questions@softwaredefinedtalk.com). Tim recommends Stratechery (with Ben Thompson) | Acquired Podcast (https://www.acquired.fm/episodes/stratechery-with-ben-thompson) 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 on Twitch (https://www.twitch.tv/sdtpodcast), Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/), LinkedIn (https://www.linkedin.com/company/software-defined-talk/) 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: Large Mouse Pad (https://www.amazon.com/dp/B0788LMLZL?psc=1&ref=ppx_yo2ov_dt_b_product_details) Matt: Ze Frank's True Facts: Tarantulas (https://www.youtube.com/watch?v=EhJYtmZuhV4) Sriracha History (https://www.vice.com/en/article/zmj4ae/the-story-of-sriracha-is-the-story-of-america) Coté: CleanShot X (https://cleanshot.com/) Photo Credits Header (https://unsplash.com/photos/LOHduxdd73s) CoverArt (https://unsplash.com/photos/tGBXiHcPKrM)

In our final re:Invent recap episode of the year, Simon shares the news and announcements from Dr. Werner Vogels's keynote. We'll cover innovations and emerging technologies that are enabling builders to create scalable, resilient, and fault-tolerant applications. And don't worry, we'll be sharing more episodes diving deep on a handful of our favorite re:Invent launches over the next few weeks, so be sure to tune in! Check out the AWS News Blog for AWS Chief Evangelist Jeff Barr's picks for this year's top announcements: https://go.aws/3XFrxZv Take The Official AWS Podcast audience survey through 4/11/2023: https://bit.ly/3G9hrK4

Dr. Werner Vogels is Chief Technology Officer at Amazon.com where he is responsible for driving the company's customer-centric technology vision.As one of the forces behind Amazon's approach to cloud computing, he is passionate about helping young businesses reach global scale, and transforming enterprises into fast-moving digital organizations.Vogels joined Amazon in 2004 from Cornell University where he was a distributed systems researcher. He has held technology leadership positions in companies that handle the transition of academic technology into industry. Vogels holds a PhD from the Vrije Universiteit in Amsterdam and has authored many articles on distributed systems technologies for enterprise computing.Twitter: https://twitter.com/WernerLinkedIn: https://www.linkedin.com/in/wernervogels/Blog: https://www.allthingsdistributed.com/AWS: https://aws.amazon.com

About LynnCloud Architect who codes, Angel InvestorLinks: Lynn Langit Consulting: https://lynnlangit.com/ Groove Capital: https://www.groovecap.com/groove-capital-minnesotas-first-check-fund Twitter: https://twitter.com/lynnlangit GitHub: https://github.com/lynnlangit 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: Today's episode is brought to you in part by our friends at MinIO the high-performance Kubernetes native object store that's built for the multi-cloud, creating a consistent data storage layer for your public cloud instances, your private cloud instances, and even your edge instances, depending upon what the heck you're defining those as, which depends probably on where you work. It's getting that unified is one of the greatest challenges facing developers and architects today. It requires S3 compatibility, enterprise-grade security and resiliency, the speed to run any workload, and the footprint to run anywhere, and that's exactly what MinIO offers. With superb read speeds in excess of 360 gigs and 100 megabyte binary that doesn't eat all the data you've gotten on the system, it's exactly what you've been looking for. Check it out today at min.io/download, and see for yourself. That's min.io/download, and be sure to tell them that I sent you.Corey: This episode is sponsored by our friends at Oracle HeatWave is a new high-performance query accelerator for the Oracle MySQL Database Service, although I insist on calling it “my squirrel.” While MySQL has long been the worlds most popular open source database, shifting from transacting to analytics required way too much overhead and, ya know, work. With HeatWave you can run your OLAP and OLTP—don't ask me to pronounce those acronyms again—workloads directly from your MySQL database and eliminate the time-consuming data movement and integration work, while also performing 1100X faster than Amazon Aurora and 2.5X faster than Amazon Redshift, at a third of the cost. My thanks again to Oracle Cloud for sponsoring this ridiculous nonsense.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. So, I've been doing this podcast for a little while now—by my understanding, this is episode 300 and something—but back when the very first episode aired, I had pre-recorded the first twelve episodes. Episode number ten was with Lynn Langit who is, among many other things, the CEO of Lynn Langit Consulting, she is also the first person to achieve the AWS Community Hero and equivalent designations at all three of the primary tier-one hyperscale cloud providers, which I can't even wrap my head around what it takes to get that at one of those companies. Lynn, thank you so much for agreeing to come back now that I'm no longer scared of the microphone.Lynn: Well, thank you for having me. It's great to be back, Corey.Corey: So, it's been a few years now since we really sat down and caught up. And what an interesting few years it's been. There's been a whole minor global pandemic thing that wound up hitting us from unexpected and unpleasant places. There's been a significant, I would say, not revolution but evolution in how adoption of cloud services has been proceeding. The types of problems that customers are encountering, the conversational discourse has moved significantly away from, “Should we be using cloud?” Into, “Okay, we obviously should be using Cloud. How should we be using it?” And the industry keeps on churning. Sure there's still rough parts, there are still ridiculous aspects of it, but what have you been up to?Lynn: Well, as you might remember, I have an independent consultancy where I do really what my customers need. I work across different clouds, which keeps it interesting and fun, but I've had a focus over the past few years in supporting bioinformatics research. Before the pandemic, it was mostly cancer research. Since the pandemic, it's been all Covid, all the time.Corey: All Covid, all the time sort of has been the unofficial theme of this. And it's weird. I know, we're in 2022, now, but it still feels like on some level, it's like, “Man, this is March 2020; it's still dragging on, on some level.” There have been a number of stories in the world that is, let's say medicine-adjacent, more so than—we're all sort of medicine adjacent these days, but there's been a lot of refocusing away from things like cancer research into Covid and similar pandemic respiratory diseases. Do you think that there's a longer-term story where we're going to start seeing progress stall on things that were previously areas of focus—in your case cancer—in favor of reducing infectious disease, or is it really one of those ‘rising tide lifts all boats' type of scenarios?Lynn: Yeah, it's the latter. It's been really interesting. Without getting too much into the details, you know, you think of genomic research for drug discovery, you know, we started with this idea of different DNA sequencing cohorts. So, like people from the—you know, that started from the United States, people that started from Africa, you know, different cohort as a normative to evaluate the effectiveness of diseases, what was an area of research already was to go down to the level of what's called single-cell RNA. So, look at the expression of the genomics by cell area, so by the different parts of your body.Well, this is similar to what has been done to understand the impact and the efficacy of potential Covid drugs. So, this whole single-cell RNA mapping cohorts of what is normal for different types of populations has resulted in this data explosion that I've never seen before. And I see it as positive for the impact of human health. However, it really drives the need for adoption to the cloud. These research facilities are running out of space if they're still working on-prem.Corey: I spend an awful lot of time thinking about data and its storage from a primarily cost-focused perspective, for obvious reasons, and that is nuanced and intricate and requires, sort of, an end-to-end lifecycle policy. There's this idea of, ideally, you would delete old data you don't need anymore, but failing that you, maybe aspirationally, don't need 500 copies of the same thing lying around. Maybe there are ways to fix that. And that's all within one cloud ecosystem. You work across all of the clouds. How do you keep it all straight in your head trying to figure out things around lifecycles, things around just understanding the capabilities of the various platforms? Because I got to say, from my perspective, it's challenging enough only bounding it to one.Lynn: Yeah, it's the constant problem. The big clients I had over this past year were not on Amazon, they were on other platforms. So, it seems like it sort of goes in cycles. And what I'll sometimes need to do is hire subcontractors that have been working on those platforms because you can't, I mean, you can't even know one platform, much less all of them to the level of complexity in order to implement. One thing that is kind of interesting though, in bioinformatics is—and different than the other domains—is when you talk about data, it's a function of time first and cost second.So, they will run on less computational resources, so that they can, for example, not overspend their research grant, and wait longer for the results. And this has been really an interesting shift in my work because I used to work with FinTech and ad tech, where it's all about, get it out there fast. And we don't really care how much it costs, we just want it super fast. So, this continuum of time or money shifts by vertical. And that's been something that—I don't know, it's kind of obvious, in hindsight, but I didn't really expect until I got into the different domains.Corey: It's always been fascinating to me watching how different organizations and different organization types wind up have interacting with cost. I mean, I've been saying for a while now that cost and architecture are the same thing when it comes to cloud. What are your trade-offs? What are your constraints? In many venture-backed companies, it's when you have a giant pile of other people's money raring to go, and it's a spend it and hit your milestone if you want to get another round of funding, or this has been an incredible journey Medium post in the making, then, yeah, okay, go ahead and make the result happen faster. Save money is not the first, second or third order of business as far as what you're trying to achieve.In academia, where everything's grant powered. And it's a question of, we need to be able to deliver, and we need to be able to show results and be able to go and play the game and understand the cultural context we're operating in, and ideally get another grant next year, it completely shifts the balance of what needs to be prioritized and when. And I don't think there's been a lot of discussion around that because most cloud cost discussions inherently center around industry.Lynn: They do and they focus on the industries where they're willing to spend most. So, most of the reference examples are, they always prioritize for time and money is sort of unlimited. I'll give you an example—this was from a few years back—some work I did with a research group in Australia, and again, it was a genomics example. They were running on-prem, and to do a single query, it took them 500 hours. And I was just like, “Are you kidding me?”And they're like, “Hey, cloud lady, what can you do?” Right? So, we gave two solutions, and the first solution was kind of a more of a lift-and-shift kind of a solution because they didn't know anything about cloud. And it took a few hours. The second solution was what was in our opinion, super elegant, it was one of the earliest data lakes, it took minutes.Well, it was a big hit to the ego that they adopted… the easier solution. But again, it's a learning because another dimension about cloud architecture is usability. The FinTechs are like, “We're going to get it really done fast; we'll hire who we need to hire.” The biotechs, they can't afford to hire who they need to hire because there all being hired by the FinTechs. So, you have these different dimensions you need to optimize for that aren't really obvious if you just work in the industries that optimize for time.Corey: And the thing that always gets overlooked is that in most environments, the people working on things are more expensive than the infrastructure themselves. And back when Lambda and all the serverless joy came out, my first iteration of lastweekinaws.com website was powered entirely by Lambda functions, S3, and other assorted bits of nonsense. Today, it's on WordPress.And it's not because I think that is somehow the superior architecture from a purely technologist point of view, but because I have to find other people who aren't me or one of the other six people in the world at the time who could stuff all that into their head and work on it effectively, should be able to make changes to the website. That is not something I need to be focusing on. There's something to be said for going to where there's a significant talent pool, rather than pushing the frontiers of innovation in areas that don't directly benefit whatever it is your organization is targeting.Lynn: Yeah, it's really interesting, when Covid hit back in 2020—kind of an interesting little story here—one of my clients is the Broad Institute at MIT and Harvard—they're a well-known research organization for, you know, cancer genomic datasets—they were tasked with pivoting their labs so that they could provide Covid testing capability. And I was a long-term contractor with them, so they brought me in for an architectural cloud consultant. I said, “This clearly is a serverless. I know you guys haven't done this before, but this is going to be burstable, you don't know how big this is going to need to go.” And then just to make life interesting, in the middle of the build of that, I was one of the first people in Minnesota to get Covid, so I actually wasn't able to go and complete it, nor was I able to get a test because there weren't tests.I mean, you know, I can't make this stuff up. I was in the ER saying, “Okay, is this the end of me, or can I go back and get you some tests?” [laugh]. So, it's really kind of two things—kind of a weird story. And also, life situations will cause change, and so the Broad did launch that pipeline, and it was serving up to 10% of the Covid tests in the United States.But they had never done anything serverlessly or had considered it before because they didn't need to have that amount of change. It was really, again, a big thing when I came into human health. Prior to that, I was doing all serverless all the time. You know, I came into human health, and they were saying, “Okay, we're going to have massive VMs.” And I was like, “No…” but you know, you have to meet the client where they are.Corey: I think it's the easiest thing in the world, particularly as a junior consultant—because you do not see senior consultants doing this ever, you know, after the first time—to walk into an environment, look around and have zero context into what's going on—because you're a consultant; you haven't been there and say, “This is ridiculous. What fool built this?” Invariably, to said fool. Now, most people don't show up in the morning hoping to do a terrible job at work today, so there are constraints that you are certainly not seeing. And maybe it was an offering wasn't available that maybe they weren't aware of it. Maybe there was a constraint that you're not seeing.But the best case is you're right and you just made them feel terrible, which is not generally a great way to land more consulting projects. It's always frustrating to me because even looking at a bill and having a pretty good idea of what's going on, I always frame it as, “Can you help me understand why this is the case? Had you considered this, or is that not an option?” As opposed to categorically saying, well, this is not the way to do it. Because once you're wrong when you're delivering expertise, it takes a lot to build that back, if it's even possible.Lynn: Well, again, from human health because, you know, they were consuming the vendor information, they thought they wanted to learn how to use Kubernetes, but what they really needed to learn was how to do archiving to reduce their storage costs.Corey: Yes. Kubernetes is a terrific solution for a bunch of problems and create several orders of magnitude more somewhere along the way. My somewhat accurate, somewhat snarky observation is that Kubernetes is great if your primary problem is you want to pretend you work at Google but didn't pass their technical screen. I don't really want to cosplay as a cloud provider myself, most days. That said, there are use cases for which it makes sense, but context is everything, and generally speaking, I don't tend to follow a hype trend to figure out whether or not it's going to solve my particular problem.Lynn: Well, here's the soundbite: “Kubernetes is today's Hadoop.”Corey: Oh, there are people who are not going to like that. I made a tweet, I think—Lynn: Tough.Corey: —three years ago now—Lynn: It's true. [laugh].Corey: Oh, yeah. Tweet three years ago or so that said, “Hot take: In five years, nobody's going to care about Kubernetes.” And I think I have a year or two left on that prediction. And what I said at the time was that not that it's going to go away and not be anywhere—because enterprises do not move that quickly—but it's no longer going to be the sort of thing that everyone is concerned about at a very high level. The Linux kernel has a bunch of aspects to it that we used to have to care about a fair bit. Now, a few people really, really need to care about those things; because of those folks' hard work, the rest of us don't have to think about it at all. And that is the nature of technology, in the fullness of time.Lynn: Well, another way to think about it is Kubernetes is a C++. Certain people are going to be experts in it and need to, and that's valid, right, but what percentage of developers code in C++. Like, ten? Five? You know, it's kind of analogous, right?So, it's one of the signatures of my consultancy. You know, I'm this pragmatic midwesterner, and I love to say, “Look,”—like you said—“If you think you need this, you really need to understand the actual cost of it because it's non-trivial on all clouds.” And I get to say that because I'm independent. You know, they're doing solid work to abstract it into a higher-level implementation, but when I hear a customer say, “I need Kubernetes,” the burden of proof is on them [laugh] before I'm going to build that.Corey: Speaking of hype-driven emerging technologies, you are arguably one of the few people on the planet I can have this conversation with, and I do not mean that as an insult other people operating in this space. For context, a couple of years ago, AWS launched Brakets—which they spelled Braket without a C because it's Amazon and spelling is hard, presumably; I know, I know, there's a reason behind it—and it is their service that enables you to get access to quantum computers the same way we get access to any other AWS service: Through a somewhat janky console and some APIs. And, okay, quantum computing. We've heard a lot about it forever; it always seemed a bit like science fiction and it was never really clearly articulated what kind of value it can solve for us.So, “Aha, now it's here. I don't need to go and build or buy a quantum computer somewhere else.” And I tried using the Quickstart, and it turns out that the Hello World tutorial for quantum computing—at least to my mind—is basically an application for a PhD program at Berkeley. And I am not that type of academic for better or worse, so I kept smacking my head off of that and realizing, okay, whatever this is, is clearly not for me. You have been doing some deep dives in the quantum computing space, but as we've just mentioned, your day job is not, to my understanding, a college professor. You are a consultant, you run your own consultancy, solving data problems, particularly towards bioinformatics. What is the deal—to the layperson—of quantum computing these days?Lynn: Well, yeah, like you, I was introduced years ago and tried to read the books, and I didn't have the math and just, you know, saw it as a curiosity. Last year, I picked up a book from O'Reilly called Practical Quantum Computing, which of course, because the name was attractive to me. I read it, felt like I was getting a little bit more knowledge, implemented a learning JavaScript library with a browser-based editor—so zero-install—and it was a simulator, you couldn't run it on actual QPUs. So, I decided to see if there's any other interest in my tech community, and I got about five other developers and we ran a 15-week long book club because we all just wanted to move forward with our knowledge. Because there is this fundamental difference in the information you can get from a qubit versus a bit because a qubit can basically be, like, a globe, and so it has a superposition, and so you can have all the different mathematical points on the globe, versus a bit is on or off.I mean, that's intuitive, like, “Hey, I could get more information out of that.” So, the potential usages—it's always been tech that leads the way—is on figuring out of what are called NP-hard or computationally complex problems, and, again, this is at the edge of my knowledge, but this is where bioinformatics is. I think of it in an oversimplified way, as [N by N by N by N, all by all by all 00:16:49]. We want to see all possible combinations of all possible inputs. So, for example, we can figure out which Covid drug we should try—which set of drugs we should try—and we want that as fast as possible.So, I wanted to see, okay, you know, where's this at? Plus, like you said, Amazon introduced Braket; when Amazon introduces something, then there's some customers somewhere that are using it. I mean, that's—you know, kind of pay attention to it now. So, as I was doing this book club, I investigated all the different cloud vendors and captured all that learning in a GitHub, and just recently recorded a LinkedIn Learning course. Which again, in the learning ladder is, if this is, you know, Hello World and this is actual implementation, it's like right here.But right here doesn't exist. Like, there's nothing there, so I tried to make something to say, okay, the Amazon Braket example, how does that actually work? What is a Hadamard Gate? Why do you care? What is amplification? How do you measure it? Like, what would you do with that? And so, you know, I tried to interpret some academic papers and do that learning layer in the middle to help move people towards productivity. Am I fully there? No. Did I move further? I hope so. Do you want to come along with me? Great.Corey: You've done something, though, that I don't think anyone else yet has when I had conversations with them about quantum computing, which is we all are shaped by our own needs and our own experiences when we interact with a cloud provider. To me, I, perhaps foolishly, took Amazon seriously when they called it Amazon Web Services. “Oh, okay. Clearly, this is going to be things to help me build websites and website accessories, more or less.” So, it's always odd to me when I'll see something like oh, and here's our IoT solution that winds up powering a fleet of 10,000 robots, and I'm looking around my website going, “I don't really have a problem that could be solved by the 10,000 robots. I have a bunch that could be made a lot worse.”But it feels like it's this orthogonal thing that is removed. But some areas, it's okay. I can see the points of commonality and how you get there from here, and if I think really hard, I can do that with IoT stuff. For example, iRobot is a cloud-connected robot that talks to something that looks like a website and vacuums my house. Whereas with quantum computing, it always felt very isolated, very much an island as far as being connected to anything else that I can recognize. Bioinformatics research, as you describe it, well, yeah, I can see you get the bioinformatics research from web services. And now I can see how you can get to quantum computing through the bioinformatics side of things.Lynn: Well, the other thing that really was useful for me, I am doing TensorFlow, finally. Took me a few years, but for neural networks. And so I am using, with some of my bioinformatics clients, acceleration with GPUs and TPUs, if I happen to be on Google because it's a known thing that when you're training a neural network, again, similar you have complexity, so you have a specialized chip, where you can offload some of the linear algebra onto that chip. So, you split the classic and the tensor portion, if you will, and you do computation on both sides. And so it's not a huge leap to say, “Well, I'm not going to use a GPU, I'm going to use a QPU,” because you split. And that's the way it actually works.There's actually a really interesting paper I put in my GitHub. It is a QCNN, and it is—that's a Quantum Convolutional Neural Network that is used to analyze images of breast cancer. Because again, on the image, you can think of the pixels as what's called a tensor, which is just vectors in multiple dimensions, you need the [all by all by all 00:20:17] again; that's really how it goes in my head. You know, you have the globe of the qubit and you want to get the all possible combinations faster, so that you can analyze all combinations in the, in this case, the image. And they found, not only was it faster, it was more accurate. And that's why I am interested in this.Corey: Couchbase Capella Database-as-a-Service is flexible, full-featured and fully managed with built in access via key-value, SQL, and full-text search. Flexible JSON documents aligned to your applications and workloads. Build faster with blazing fast in-memory performance and automated replication and scaling while reducing cost. Capella has the best price performance of any fully managed document database. Visit couchbase.com/screaminginthecloud to try Capella today for free and be up and running in three minutes with no credit card required. Couchbase Capella: make your data sing.Corey: The neat part is that this might be one of the first clear-cut stories where, “What could I use a quantum computer for?” And the answer isn't something that's forward-looking or theoretical. I mean, the obvious gag when you said reading about Practical Quantum Computing is that book is probably in pre-release, I would assume.Lynn: [laugh].Corey: But it's a hard thing to solve for, and I do have the awareness that I am not an academic, academia has never been my friend, so I bias heavily for, “Well, can we use this to solve real-world problems slash make money?”—because industry—and academia focuses, ideally and aspirationally on the expansion of the limits of human knowledge. And sometimes it's okay to do those things without an immediate, “Well, how can I turn a profit on it next quarter?” What a dismal, bleak society we have if that's all that we wind up focusing on any given point in time.Lynn: Yeah, that's for sure.Corey: Which, of course, sets us up for one other thing that's a relatively recent change for you. You now have mentioned in your bio, which I believe is new since the last time we spoke, that you are an angel investor. And that is something that I recently found being applied to me as well after I made an investment in a startup that I was very excited about. I talked about in the show previously; it's called Byte Check. But honestly, I didn't realize that what I was doing was called angel investing until I read the press release because ‘strategic angel' are two words that no one ever applies to me, particularly in that order. What happened? What are you doing these days?Lynn: Well, I live in Minneapolis. So—and I moved there in 2019, so you know, my 2020 story is first I had Covid, got over that, and then I was there during the tragedy of George Floyd. So, I wanted to understand more about what were the root causes, and what I could do to make an impact in the recovery of my city. And I was really surprised to find that Minnesota is one of the most charitable states in the United States, it ranks one or two, but yet we have in the Twin Cities of Minneapolis and St. Paul, we have really unacceptable income inequality and poverty. So, something's not working.I'm a pretty charitable person; I always allocate a certain percentage of my money to charity, but I said, “I want to accelerate this.” So, at the same time, there was a new angel investment fund launched, it's called Groove Capital, that was going to focus on women-owned and BIPOC businesses. And I thought, “Hmm, this seems good.”Now, I was super intimidated because I lived in California for so many years, and check sizes in California, you just add a zero. And I thought, you know, “I don't have generational wealth. This is my own money.” You know, I'm well-compensated, but I'm not loaded.Corey: Yeah there's a common trope right now that oh, angel investor is a polite way of saying I am rich—Lynn: Right.Corey: —but I rent my home at this point, living in San Francisco. It is, I am not exactly sitting here diving into a money bin out back, Scrooge McDuck-style either.Lynn: Right. Well, I mean, you know, I'll just be transparent about it. Like everybody else, or many people, I moved out of California because of the cost of doing business there and reduced my cost of living by 40% move into the Midwest, which is awesome. So anyway, I joined this fund, and it's been just fantastic because I've listened to deals on my own and felt just like a complete, like, I don't know what I'm doing. But I'm taking advantage—Corey: How do you evaluate an idea that someone has that's early-stage, barely better in some cases than back-of-an-envelope scrawlings?Lynn: For sure, right. But what I found through the fund is I can contribute both money and time because, you know, I did this cloud expertise, and in addition to writing checks for a couple companies that I really believe in, for example, I got all these companies on the X cloud company for startups program. Because that wasn't just a known thing in my ecosystem. I was like, “Why are you paying a cloud bill? You could be on the startup program for the first year.”So, I'm impacting these new businesses with both my experience and my dollars, and I just really love it. I just really, really love it. And you know, the reasons I want to talk about it is because more people who have expertise in tech should do this because you can really, really be impactful. One of the companies that I invested in is called TurnSignl. They are coming to Los Angeles.It was three attorneys and one of their brothers is a police officer. They wanted to de-escalate situations that happen with traffic stops. So, it's a mobile app, where you push a button and you're connected to an attorney. And they do training for the community and police officers, and the idea to record the conversation and to get an attorney involved to de-escalate and get everybody home safely. And that was my first investment and I'm—it's going national, and I'm like, really, really—the kind of things I want to do you know.Corey: It is simultaneously such a terrific idea and such a stunning indictment of the society that makes something like that necessary.Lynn: Well, you know, we have to find practical solutions. We have to find ways forward.Corey: Oh, please. Don't interpret anything I'm saying a shade on that. It's like, “Well, I wish the world were differently.” Yeah, I think most people do. But you have to deal for better or worse with the hand that you're dealt, and this is, for better or worse, at the time of recording this, the society that we have, and finding the best path forward is often not easy.But it beats just sitting here complaining about everything every day, and not doing anything to be part of that change. The surprising thing I learned as I went through it was that in many cases, the value of individual angel investors is not the check that they're writing, that's basically just almost a formality, on some level. It is the expertise, it is the insight into particular markets, and the rest. The part of what you're saying that surprises me that I hadn't really considered, but of course, it must exist, is the idea of angel funds. Is this generally run by an existing VC firm? Is it a group of like-minded friends who decide, ah, we're going to just basically do the investing equivalent of a giving circle where everyone puts some money in the pot and then that decides where to go? How is it structured?Lynn: Yeah, the way ours worked is you do pay a fee—it's a small fee—to be part of it, and then they have people who vet deals for you. And then what I really like about it is the community aspect because just like in tech, when you're learning something new in tech, you have community, same thing here. We have a Slack, we have a website for each deal, we have in-person meetups when Covid situation allows, and we have chosen to start by investing in Minnesota, although we're going to, in fund two we're going to invest in Upper Midwest. And for example, here's something I would have never known. There's an angel tax credit Minnesota, that for certain businesses, you can get a 25% tax credit. Which hey, do good, be good, get good. I would have never known about that, I would have never known how to do it. All my investments so far have qualified. Fantastic. My money goes further.Corey: Yeah, it's about well, what are you talking about worrying about taxes? That there's about to be doing something good? Yeah, great. If you believe in a cause, take advantage of the tax code as written—I am not advocating tax fraud; pay every cent that you owe, let's be serious here. They have no sense of humor about that—Lynn: [laugh].Corey: —and take advantage of that. That means you have additional money to do good with. I wish that more people had an awareness around that particular school of thought.Lynn: Well, make your money go further, make your money effective.Corey: Oh yes.Lynn: Because like it or not, we run on money. We run on money. And so be smart, from everything where you shop to how you spend. That's how we're going to make change.Corey: One last area I want to explore with you is that for a long time you've been working on, effectively, data pipelines and similar things in that space, tied to your consulting work. You are clearly skilled across all of the various cloud providers and even tieing into the expertise side of what you're doing as an angel investor, you've always been a staunch advocate for, I guess we'll call it doing security the right way. And I've always been tangentially related to security throughout the course of my career. And somewhat recently, I launched another day of my newsletter focused on security within AWS, for folks who are not themselves in the security space of what do you need to know. But so much of it comes down to the do the easy thing now, the right way to do it before you wind up having to do a whole bunch of damage control. And you've been advocating for that since before it was trendy to do so. I imagine you're still somewhat passionate about that perspective.Lynn: Well, I always like to say, you know, Werner Vogels doesn't talk anything about tech; he just talks about, “Please use our security.” And I don't blame him. I mean, you know, I joke that I am an AWS Community Hero because I made a bunch of YouTube videos about securing buckets. And that was, like, seven years ago and I just had a financial client, literally in November, and their buckets, you know, was made public because it was easy for the developer. I'm like, “Ugh, can we just do our foundations?”I don't know why it is not seen as a valuable skill. I mean, I've made craploads of money because people come after they have an incident, but you know, I wish we would be better. And I'm worried because as we start to get more and more of our health information in these big repositories—granted, we have some laws; yay, good—but it's just not valued like coding up a new feature with node or something. And why not? I don't understand.So, I make all these educational resources: I make courses, I have GitHub repos, I have videos. You know, just do it. Plus the people who learned security. I mean, we are always in demand. I'm not a security professional, but I always do security kind of like as a courtesy. And people are like, “Oh, you know, you're great. Oh, my friend needs you.” Dah-dah-dah… I mean, you'll be working forever.Corey: It feels like it's aligned with cost in that it is almost a reactive function. You can spend all your time on it, but it's not going to advance the state of your org further toward its stated goals. You've got to do it, but there's also never really any ‘done' there. It's just easier for me on the cost side because I can very easily quantify the return on investment, whereas with security, it's much more nebulous. And, of course, you wind up with the vendor—I'm going to call it what it is, in some cases—nonsense that is in this space, where, “Oh, you're completely doomed, unless you buy their particular product.” You know, walk up or down the aisle at RSA a few times and your shopping cart is full. And great, are you more secure? You're a lot more complex, but does this get you to a better outcome?And it's, I am so continually frustrated by all of these fancy whiz-bang solutions that are sort of going around the easy stuff—not easy, but it's the baseline level of things: Secure your S3 buckets, or—for users themselves—it's use a password manager that has a strong password on it, use it for everything, use MFA for the important things that you need to use, make sure your email is secure, don't click random nonsense. There's a whole separate pile of things. If I can click the wrong link in an email and it destroys my company, maybe it's not me clicking that link in the email that's the root problem here. Maybe there's an entire security model revisitation that's due. But I'm sorry, I will rant like a loon about the dismal state of security these days, if you let me, and you absolutely should not.Lynn: Well, I would just entreat the audience, basic threat modeling is not complicated. It's like cost modeling. It's just a basic of having successful business on the cloud.Corey: [sigh]. I wish the world work differently than it does, and yet here we are. Lynne, I really want to thank you for taking the time to come on the show a second time. If people want to learn more about what you're up to and talk to you about anything we've discussed, what's the best way to find you?Lynn: So, if you can't find me, you're not looking. I have an internet-easy name. But two places that I'm pretty active: Twitter—just my name, @lynnlangit—and go to my GitHub. In particular, I have a learning cloud kind of meta-repository that has over 100 links to mostly free things on every cloud and just use them. Have at it, learn, be a practitioner, use the cloud more effectively.Corey: And we will, of course, put links to that in the [show notes 00:32:25]. Thanks so much for coming back on. I really appreciate it.Lynn: Thanks for having me. It's been fun.Corey: Lynn Langit, CEO of Lynn Langit Consulting, and oh so much more. 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 comment talking about how security really isn't that important, and right before you submit that comment accidentally type your banking password into the form, too.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

DevOps is defined as, “Everything you do to overcome the friction created by silos … All the rest is plain engineering” Why is it so difficult to implement, but so easy to make up so many job titles surrounding it?SHOW: 593CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotwCHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"SHOW SPONSORS:CloudZero - Cloud Cost Intelligence for Engineering TeamsDatadog Monitoring: Modern Monitoring and AnalyticsStart monitoring your infrastructure, applications, logs and security in one place with a free 14 day Datadog trial. Listeners of The Cloudcast will also receive a free Datadog T-shirt.Teleport is the easiest, most secure way to access all your infrastructure Get started with Teleport SHOW NOTES:Shades of DevOps Roles (Patrick Dubois) IF EVERYTHING IS DEVOPS, THEN WHAT IS DEVOPS?Patrick Dubois, one of the original creators of the DevOps concept, recently published a framework to think about all the job titles that have emerged out of the original DevOps concept. Is this a good progression, or is it just hiding the cultural and organizational complexities that DevOps is trying to address?THE CHALLENGES OF TRYING TO ELIMINATE SILOED TECHNOLOGY FUNCTIONSIt seems like it all began when AWS' CTO Werner Vogels said, “You build it, you run it.” That was such a foreign concept in the IT world, and ever since, we've been trying to invent ways to apply existing organization paradigms to the byproduct of that concept. Previous applications were rarely changed. Now applications (microservices, etc.) are designed from Day 1 to frequently change. Once again, the existing organization paradigms have to change. And the public cloud introduces a level of financial transparency and complexity (e.g. here's a bill every month) that is creating new roles (or newer concepts) that are trying to optimize that information. Lots of companies say that they can't support multiple operational models (hence why they try to retrofit old models into new names), but the reality is that they are always supporting multiple process or platform models. Resume-driven-development has become a real thing, so it's not unusual to see title-washing happen at various companies. It can also be valuable for recruiting as well, at least in the short-term. I wish there was some better measurement model for progress along these DevOps paths, instead of just the tiering of the State of DevOps report. It's too easy to get frustrated, when many companies are just striving to get to a mid-level of DevOps efficiency. FEEDBACK?Email: show at the cloudcast dot netTwitter: @thecloudcastnet

In this Episode Mark and Mike chat to Dave 'live from Vegas' at AWS re:Invent 2021. Watch to find out their take on Matt Coulter's speech as part of Werner Vogels keynote, how Serverless and CDK is becoming part of the mainstream as well as the announcement on CDK Patterns Version 2. Sustainability has been the hot ticket item at AWS re:Invent - you saw that prediction from The Serverless Edge first!  AWS have announced their Carbon Calculator.  And sustainability is now another pillar in the Well Architected framework. There was more news on AWS Amplify and great dialogue on the Data Driven Enterprise as well as the Goldman Sachs Financial Cloud for Data.  Some of the new pieces were incremental and the team were spotting how machine learning is being integrated in many of the developer tools. Don't miss out on Serverless Craic's unique insight and perspectives as well as hints on the best talks from AWS re:Invent 2021. Serverless Craic from The Serverless Edge theserverlessedge.com @ServerlessEdge

In this Episode, Dave, Mark and Mike welcome guest and former Liberty Mutual colleague, Matt Coulter @NI Developer, who received the 'Now Go Build' award from Werner Vogels at AWS re:Invent 2021.  As well as all having previously worked together at Liberty Mutual, Matt is founder of CDK Patterns and published author of the CDK Book available on thecdkbook.com.  He is an Architect for Liberty Mutual, an AWS DevTools Hero and Serverless Architect sharing reusable, well architected, serverless patterns over at cdkpatterns.com or behind the scenes bringing his flagship event: 'CDK Day' to life. Matt Coulter and the Serverless Edge guys reminisce about bringing serverless to life at Liberty Mutual and how CDK patterns was a key part of the journey.  They talk about the challenges they encountered and the approaches that brought them success such as gaining external validation from the pioneers of serverless to enable them to get the internal support needed to start serverless at a 100 year old global insurer. You can learn from these experts on how to get started on your severless journey using tools such as Wardley mapping to get your situational awareness and find your next best thing to do.  Find out about the importance of building a developer community to maximise the fast flow efficiencies from CDK patterns.  And how combining that with well architected and serverless first principles will build momentum into a self sustaining Value Flywheel.  This unlocks your clarity of purpose and gives your org long term value. Listen to Dave, Mark, Mike and Matt talk about their experiences of removing cognitive burden from developers to allow them to experiment and collaborate in the wider community leading to even greater efficiencies for their teams and organisations. Notes: Matt Coulter: @NIDeveloper CDKpatterns.com https://github.com/cdk-patterns thecdkbook.com Serverless Craic from The Serverless Edge theserverlessedge.com @ServerlessEdge

本次的 AWS re:Invent 2021 特輯也來到了尾聲，最後為大家帶來的是 Werner Vogels 的 Keynote。在最後一場 Keynote 中，Dr. Werner 帶來更多元、完善的基礎設施服務，像是 AWS Cloud WAN 可以創建及管理個人網路環境，甚至還把範圍擴及到了太空，推出了 AWS Ground Station 透過衛星來傳送資訊！另外，也為開發者們帶來 AWS Amplify Studio 的開發相關服務，提供視覺化的開發介面，還能直接匯入 Figma 的元件，縮短 UI/UX Designer 與開發者們的距離，進而變成一個良好的溝通工具，讓 Designer 設計的介面能真正 fit in 開發者所建構的系統！ AWS 以客戶為中心的 Day 1 精神，不間斷地推陳出新及優化各項服務，而這些更新也會一同推動架構及開發等各種面向的改變，並激發各式各樣的創新！Dr. Werner 鼓勵大家勇於使用自己的方式來建構系統，且強調「沒有做不到，只有想不到」，只有透過實際動手打造，才能造就價值！ 一起來聽聽 Tina 對於這場 Keynote 的分享吧！ 我有話要說：想聽什麼或建議，都可以偷偷跟我們說喔 Facebook｜Instagram｜Spotify｜Apple Podcast ｜Google Podcast ｜KKBOX Podcast

In this extended episode, Eoin and Luciano talk about Amplify with a particular focus on Amplify Studio, a new visual way to manage Amplify applications announced at the recent re:Invent event during Werner Vogels' keynote. In this episode we mentioned the following: - Amplify Studio: https://aws.amazon.com/amplify/studio/ - Figma: https://www.figma.com/ - The 2021 AWS re:Invent Werner Vogels keynote segment on Amplify Studio: https://youtu.be/8_Xs8Ik0h1w?t=3346 - Ali Spittel: https://www.youtube.com/watch?v=7MKVCmNKT1c This episode is also available on YouTube: https://www.youtube.com/AWSBites You can listen to AWS Bites wherever you get your podcasts: - Apple Podcasts: https://podcasts.apple.com/us/podcast/aws-bites/id1585489017 - Spotify: https://open.spotify.com/show/3Lh7PzqBFV6yt5WsTAmO5q - Google: https://podcasts.google.com/feed/aHR0cHM6Ly9hbmNob3IuZm0vcy82YTMzMTJhMC9wb2RjYXN0L3Jzcw== - Breaker: https://www.breaker.audio/aws-bites - RSS: https://anchor.fm/s/6a3312a0/podcast/rss Do you have any AWS questions you would like us to address? Leave a comment here or connect with us on Twitter: - https://twitter.com/eoins - https://twitter.com/loige

This is the final day of our coverage of re:Invent 2021! Check out all the announcements here: https://aws.amazon.com/blogs/aws/top-announcements-of-aws-reinvent-2021/ Extended Shownotes: https://d29iemol7wxagg.cloudfront.net/489ExtendedShownotes.html

4.00" Keavy Ryan, partner at law firm A&L Goodbody and an Irish Proshare Association (IPSA) board member joins Dalata Hotels company secretary, Sean McKeon to discuss why the withdrawal of Ulster Bank from the Irish market may throw current Save As You Earn Schemes (SAYE) into disarray. They join co-host Susan Spence (founder Softco) in discussing talent attraction and retention problems due to an inadequate share option scheme that does not match a similar UK scheme, available to companies in Northern Ireland.22.00" Geraldine Jones, founder Skin Formulas, talks about her brand that is sold in Dunnes Stores, Shaws (almost nationwide), Meaghers Pharmacies etc. She has bootstrapped the business herself and she's now hoping to head for the UK market without further investment - unless 'smart money' wants to join her. So how do you take on the might of the big brands (her products are not make up, but nutraceuticals, an important differentiator. Her 'hire in a heartbeat'? Well she chose two (wise woman!). She wants the sectoral knowledge of TeamGBS alumna, Aimee Connolly, as well as the unstinting encouragement of her uncle, also a TeamGBS alumnus, Peter Byrne, CEO of FRS.39.00" Glimpse software founders Oran Mulvey and Shane O'Sullivan (both 26) entertained us with their youthful enthusiasm as well intriguing us with what could be world beating software to help small and large retailers find out who's shopping with them, in store (they compare their software to Google Analytices for bricks and mortar stores). They're currently raising €2m to help with their assault on the UK market and when (not if!) that's successful, they're heading for the US of A. Just listen to their exuberance. It'll lift your day. Their 'hire in a heartbeat', Werner Vogels, CTO and VP at Amazon.59.00" Roisin Carroll, Sales and Marketing Manager, Carroll Estates tells us how she works with her dad, her sister, her brother-in-law, and how they keep the peace. Her real reason to be on That Great Business Show was to try to tell the world about their houses for sale in Malahide, Dublin, but they're already selling like hot cakes so we chatted to her about the family business, Japanese toilets and the TV show, Grand Designs. As we say, we do business differently. Roisin's 'hire in a heartbeat'? Helena Morrissey, mother of nine, former boss of Newton Investments and campaigner for greater female presentations on company boards. Hosted on Acast. See acast.com/privacy for more information.

The Fix This team sat down with Dr. Werner Vogels, Chief Technology Officer of Amazon and host of Now Go Build. 2021 marks the 15-year anniversary of Amazon Web Services (AWS). In this time, Dr. Vogels has traveled the world to meet with customers using AWS to solve hard, human problems. Tune in to hear Dr. Vogels discuss the customer stories that most inspire him, what they are creating, and what makes him optimistic for the future of entrepreneurs who are building with sustainability top of mind.

On The Cloud Pod this week, everyone's favorite guessing game is back, with the team making their predictions for AWS Summit and re:Inforce — which were not canceled, as they led us to believe last week.                   A big thanks to this week's sponsors: Foghorn Consulting, which provides full-stack cloud solutions with a focus on strategy, planning and execution for enterprises seeking to take advantage of the transformative capabilities of AWS, Google Cloud and Azure. JumpCloud, which offers a complete platform for identity, access, and device management — no matter where your users and devices are located.  This week's highlights

Antonio, Guillaume et Emmanuel discutent de pleins de choses dont des analyses de l'écosystème de la JVM, de la generation de code via intelligence Artificielle avec CoPilot, mais pas que. Enregistré le 16 juillet 2021 Téléchargement de l'épisode LesCastCodeurs-Episode–999.mp3 News Langages Les prédictions d'Adam Bien pour la seconde moitié de 2021 Kube a gagné la guerre. Les cloud providers fournissent des solutions dérivées plus simplifiées. La compatibilité kubernetes devient moins cruciale FaaS est utilise pour son usage listener et point d'intégration et plus en général purpose tool Prix du cloud et repatriation. Bouger une app existante dans le cloud n'amène pas d'avantage. Le monolith devient une best pratice Coût du cloud pousse a merger des microsercices dans un cadre de cloud cost driven development Cloud deviennent intéressant pour les services unique (text to speech, image recognition, etc). En parallèle la sécurité des cloud providers est reconnu. Donc boring load on prem, projects innovants dans le cloud. Serverless va être le trend de 2021 (fonction mais aussi db, workflow, event streams etc) idée est scale down to zero La montée des frameworks next gen Micronaut et Quarkus est indisputable. Build time deployment. La popularité de quarkus a explosé, difficile de trouver un développeur Java qui n'a pas expérimenté. Le cocktail GraalVM api familières Jakarta ee et micro profile, sa do so mémoire et temps de démarrage lui donne un avantage. Mais la compétition ne dors pas (Helidon et micronaut) Moins de langages alternatifs parce que l'innovation dans Java a accéléré Lombok moins populaire parce que Java Records. Kafka sera plus un data store immuable et source de vérité que un remplacement pour JMS Kafka et réactive en combo va rendre la programmation réactive populaire Le projet Loom eliminera la programmation reactive pour les resources non-reactives ARM sur le serveur GraalVM pour remplacer OpenJDK car rapide et multi langage. Et competitor a GraalVM qui arrive Visual studio code et ses features pour Java pas forcément connu et donc va croître encore. Payara cloud serverless server ou l'app server est un opérateur Kube et on déploie un thin jar. GraalVM offre des plugins Gradle et Maven pour la compilation native Tester les libraires en natif avec les tests junit 5 qui tournent en natif Après tourne les tests en JVM, ils sont loggués et ajoutés en réflection et complication native. Et un binaire de test est créé plugin Gradle License Oracle Universal Permissive probablement un dérivé de Universal Permissive License Le rapport sur l'écosystème JVM par Snyk Sondage effectué durant six semaines (entre février et mars 2021) au prêt de 2000 developeurs et comparé à GitHub et Google Trends Mon (Emmanuel) intuition c'est qu'il y un biais dans les gens mesurés 44% des Dev Java utilisent adoptopenjdk en prod. Oracle openjdk 28 et Oracle JDG 23 60% utilisent Java 11 en prod. Et 12 la dernière mais encore 60% de 8 en prod Java 91% kotlin 18% groovy 13 et scala 10 IntelliJ 70% eclipse 25 et vscode 23. 50% sont bi IDE Maven 76% gradle 38% ant 12W yah Spring Boot 58% Spring MVC 29% Jakarta ee 13% Quarkus 11% JDK 17 en ramp down phase 2 Schedule 2021/07/15 Rampdown Phase Two 2021/08/05 Initial Release Candidate 2021/08/19 Final Release Candidate 2021/09/14 General Availability Features integrated in JDK 17: JEP 306: Restore Always-Strict Floating-Point Semantics JEP 356: Enhanced Pseudo-Random Number Generators JEP 382: New macOS Rendering Pipeline JEP 391: macOS/AArch64 Port */ JEP 398: Deprecate the Applet API for Removal JEP 403: Strongly Encapsulate JDK Internals (sauf pour sun.misc.Unsafe) JEP 406: Pattern Matching for switch (Preview) JEP 407: Remove RMI Activation JEP 409: Sealed Classes JEP 410: Remove the Experimental AOT and JIT Compiler JEP 411: Deprecate the Security Manager for Removal JEP 412: Foreign Function & Memory API (Incubator) JEP 414: Vector API (Second Incubator) JEP 415: Context-Specific Deserialization Filters Librairies Spring Native 0.10.0 Utilise Native testing de GraalVM Passe au plugin Gradle de l'équipe GraalVM Ahead of time proxies pour les classes Quarkus 2.0 est sorti Guide de migration mais les applis devraient essentiellement fonctionner (extensions ont plus de taf) JDK 11+ GraalVM 21.1 Vert.x 4 Microprofile 4 Continuous testing : les tests impactes tournent automatiquement en Dev mode. Les tests qui cassent sur un changement sont visible tout de suite et en continu. Comme infinitest mais sans plugin IDE. Quarkus a une CLI pour simplifier l'interaction vs les plugins maven ou gradle. Notamment création de projetas. JDK 11+ GraalVM 21.1 Vert.x 4 Microprofile 4 GraphQL client (smallrye), CDI decorators supportés, transaction pour MongoDB avec Panache, Support kotlin grandement amélioré : resteasy rezctive, rest client, reactive messaging extensions supportent tous les coroutines Support d'Amazon services system manager Crafting rolling releases for a Quarkus CLI application Y'a encore du chemin pour faire simplement des CLI avec graalVM en comparaison de go JReleaser outils permettant de livrer automatiquement des projets Java vers différentes plateforme (Homebrew, Snapcraft, Scoop) Inspiré de GoReleaser et jbang Le blog package l'outil kcctl créé par Gunnar avec JReleaser Pas mal de conf (Windows vs Linux/MacOS) mais à la fin il y arrive Infrastructure Amazon sort son OpenSearch 1.0 et OpenSearch Dashboard, leur fork d'Elastic Search et Kibana 1.0 sortie de OpenSearch (GitHub) Suppression du code propriétaire Upgrading: mise a jour d'ElasticSearch et Kibana vers OpenSearch et OpenSearch Dashboard aussi simple qu'une mise a jour de version Compatibility: travaux de reflexion autour de la compatibilité avec les outils existants Testing: infrastructure de test moderne et flexible Supporte les architecture for Linux ARM64 Minimal artifacts for embedding of OpenSearch and OpenSearch Dashboards into existing products and services, Data stream support for OpenSearch Dashboards, Span attribute visibility and filtering in the Trace Analytics plugin, Scheduling and tenant support in the Reporting plugin. Aussi mentionne la roadmap Kubernetes 1.22 enlève le support des vieilles versions de ressource Faites le ménage en continu pas des grosses migrations tous les 3 ans Release prévue en aout Il vont supprimer des APIs qui étaient en beta Cloud Un tweet lance un faux service AWS InfiniDash qui a été repris par des devs et des boîtes La théorie est que la plupart des devs n'entendront parler de technologie que via les tweets et les articles. Aussi le métier de devrel c'est de surfer la vague du social media. Les dev rels AWS ont continué la farce (je crois) Werner Vogels, oui pour sur. gros effet boulle de neige Outillage GitHub copilot itellisense boosté par les projets visible et hostés dans GitHub et autre données publiques via l'intelligence artificelle, essaie de comprendre l'intention via le contexte uniquement le fichier édité en contxte pour l'instant VSCode extension donc tourne partout où les plugins VSCode tournent 0,1% de copie exacte le code nous appartient en tant qu'utilisateur le code contexte est transmis a GitHub qui l'utilise pour ses telemetries et améliorer les modèles ML pas toujours du code de qualité des secrets valides sont générés (du corpus originali e.g. SendGrid) propose du code GPL (derivation?) attaque de sécurité vont venir :) Audacity 3 spyware ou pas après le rachat la communauté “niveau 2” s'est emballée, a crée une dizaine de forks. C'était déjà annoncé et discuté avec la communauté Audacity. OS, pays, cpu, erreurs, reports de crash Protection légale « law enforcement ». Les 13 ans, juste pour éviter des restrictions légales us 3.0.2 n'a pas le code des collections de données Avec feedback initial passe de Google analytics à un hébergement propre. Quand compile le project c'est off par défaut (donc seuls les binaires distribués l'ont par défaut) donc pas dans les distros linux Sécurité LinkedIn la brèche qui donne des infos de 92% de ses utilisateurs y compris les salaires inférés API LinkedIn abusée. Email, noms, telephone, adresse physique, de 700M d'utilisateurs Presque interessé de fouiller pour voir mon salaire théorique :) Dispo sur le dark web Loi, société et organisation Lettre à ceux qui veulent faire tourner la France sur l'ordinateur de quelqu'un d'autre par Tariq Krim Télécharger l'ebook au format PDF. Très documenté et référencé Coulisses et manoeuvres pour installer les GAFAM au coeur de l'État 17 mai 2021, Bercy présente la nouvelle stratégie Cloud du Gouvernement GAM (Googla Amazon Microsoft) À part OVH Cloud, aucun des acteurs français n'a été mentionné par les Ministres Les lois américaines dites FISA et Cloud Act permettent d'obliger les grandes sociétés US à fournir à la justice américaine les données situées sur leurs serveurs européens Si l'on met de côté les questions de souveraineté, les services de sociétés comme Amazon, Microsoft et Google sont très ergonomiques Les Américains offrent des services clé en main, les services “made in France” demandent de combiner plusieurs produits issus de sociétés différentes Apple, Google, Facebook, Amazon ont embauché des dizaines de milliers d'ingénieurs, dont de très talentueux Français Les clouds GAM pourraient décrocher le label SecNum Cloud (le plus haut niveau de sécurisation de l'État) Après avoir délocalisé notre industrie (le fameux “Fabless” de Serge Tchuruk ancien patron d'Alcatel), l'État et les grandes entreprises ont délocalisé leur informatique vers les grandes SSII qui se sont mises à produire des projets à la chaîne Nous contacter Soutenez Les Cast Codeurs sur Patreon https://www.patreon.com/LesCastCodeurs Faire un crowdcast ou une crowdquestion Contactez-nous via twitter https://twitter.com/lescastcodeurs sur le groupe Google https://groups.google.com/group/lescastcodeurs ou sur le site web https://lescastcodeurs.com/

Antonio, Guillaume et Emmanuel discutent de pleins de choses dont des analyses de l'écosystème de la JVM, de la generation de code via intelligence Artificielle avec CoPilot, mais pas que. Enregistré le 16 juillet 2021 Téléchargement de l'épisode [LesCastCodeurs-Episode-999.mp3](https://traffic.libsyn.com/lescastcodeurs/LesCastCodeurs-Episode-999.mp3) ## News ### Langages [Les prédictions d'Adam Bien pour la seconde moitié de 2021](https://adambien.blog/roller/abien/entry/mid_year_2021_observations_and) * Kube a gagné la guerre. Les cloud providers fournissent des solutions dérivées plus simplifiées. La compatibilité kubernetes devient moins cruciale * FaaS est utilise pour son usage listener et point d'intégration et plus en général purpose tool * Prix du cloud et repatriation. Bouger une app existante dans le cloud n'amène pas d'avantage. Le monolith devient une best pratice * Coût du cloud pousse a merger des microsercices dans un cadre de cloud cost driven development * Cloud deviennent intéressant pour les services unique (text to speech, image recognition, etc). En parallèle la sécurité des cloud providers est reconnu. Donc boring load on prem, projects innovants dans le cloud. * Serverless va être le trend de 2021 (fonction mais aussi db, workflow, event streams etc) idée est scale down to zero * La montée des frameworks next gen Micronaut et Quarkus est indisputable. Build time deployment. * La popularité de quarkus a explosé, difficile de trouver un développeur Java qui n'a pas expérimenté. Le cocktail GraalVM api familières Jakarta ee et micro profile, sa do so mémoire et temps de démarrage lui donne un avantage. Mais la compétition ne dors pas (Helidon et micronaut) * Moins de langages alternatifs parce que l'innovation dans Java a accéléré * Lombok moins populaire parce que Java Records. * Kafka sera plus un data store immuable et source de vérité que un remplacement pour JMS * Kafka et réactive en combo va rendre la programmation réactive populaire * Le projet Loom eliminera la programmation reactive pour les resources non-reactives * ARM sur le serveur * GraalVM pour remplacer OpenJDK car rapide et multi langage. Et competitor a GraalVM qui arrive * Visual studio code et ses features pour Java pas forcément connu et donc va croître encore. * Payara cloud serverless server ou l'app server est un opérateur Kube et on déploie un thin jar. [GraalVM offre des plugins Gradle et Maven pour la compilation native](https://medium.com/graalvm/gradle-and-maven-plugins-for-native-image-with-initial-junit-testing-support-dde00a8caf0b) * Tester les libraires en natif avec les tests junit 5 qui tournent en natif * Après tourne les tests en JVM, ils sont loggués et ajoutés en réflection et complication native. * Et un binaire de test est créé * plugin Gradle * License Oracle Universal Permissive * probablement un dérivé de [Universal Permissive License](https://opensource.org/licenses/UPL) [Le rapport sur l'écosystème JVM](https://snyk.io/jvm-ecosystem-report-2021) par Snyk * Sondage effectué durant six semaines (entre février et mars 2021) au prêt de 2000 developeurs et comparé à GitHub et Google Trends * Mon (Emmanuel) intuition c'est qu'il y un biais dans les gens mesurés * 44% des Dev Java utilisent adoptopenjdk en prod. Oracle openjdk 28 et Oracle JDG 23 * 60% utilisent Java 11 en prod. Et 12 la dernière mais encore 60% de 8 en prod * Java 91% kotlin 18% groovy 13 et scala 10 * IntelliJ 70% eclipse 25 et vscode 23. 50% sont bi IDE * Maven 76% gradle 38% ant 12W yah * Spring Boot 58% Spring MVC 29% Jakarta ee 13% Quarkus 11% [JDK 17 en ramp down phase 2](https://mail.openjdk.java.net/pipermail/jdk-dev/2021-March/005266.html) Schedule * 2021/07/15 Rampdown Phase Two * 2021/08/05 Initial Release Candidate * 2021/08/19 Final Release Candidate * 2021/09/14 General Availability Features integrated in JDK 17: * [JEP 306: Restore Always-Strict Floating-Point Semantics](https://openjdk.java.net/jeps/306) * [JEP 356: Enhanced Pseudo-Random Number Generators](https://openjdk.java.net/jeps/356) * [JEP 382: New macOS Rendering Pipeline](https://openjdk.java.net/jeps/382) * [JEP 391: macOS/AArch64 Port ](https:/*openjdk.java.net/jeps/391)*/ * [JEP 398: Deprecate the Applet API for Removal](https://openjdk.java.net/jeps/398) * [JEP 403: Strongly Encapsulate JDK Internals](https://openjdk.java.net/jeps/403) (sauf pour `sun.misc.Unsafe`) * [JEP 406: Pattern Matching for switch (Preview)](https://openjdk.java.net/jeps/406) * [JEP 407: Remove RMI Activation ](https://openjdk.java.net/jeps/407) * [JEP 409: Sealed Classes ](https://openjdk.java.net/jeps/409) * [JEP 410: Remove the Experimental AOT and JIT Compiler](https://openjdk.java.net/jeps/410) * [JEP 411: Deprecate the Security Manager for Removal](https://openjdk.java.net/jeps/411) * [JEP 412: Foreign Function & Memory API (Incubator)](https://openjdk.java.net/jeps/412) * [JEP 414: Vector API (Second Incubator)](https://openjdk.java.net/jeps/414) * [JEP 415: Context-Specific Deserialization Filters](https://openjdk.java.net/jeps/415) ### Librairies [Spring Native 0.10.0](https://spring.io/blog/2021/06/14/spring-native-0-10-0-available-now) * Utilise Native testing de GraalVM * Passe au plugin Gradle de l'équipe GraalVM * Ahead of time proxies pour les classes [Quarkus 2.0 est sorti](https://quarkus.io/blog/quarkus-2-0-0-final-released/) * Guide de migration mais les applis devraient essentiellement fonctionner (extensions ont plus de taf) * JDK 11+ GraalVM 21.1 * Vert.x 4 * Microprofile 4 * Continuous testing : les tests impactes tournent automatiquement en Dev mode. Les tests qui cassent sur un changement sont visible tout de suite et en continu. Comme infinitest mais sans plugin IDE. * Quarkus a une CLI pour simplifier l'interaction vs les plugins maven ou gradle. Notamment création de projetas. * JDK 11+ GraalVM 21.1 * Vert.x 4 * Microprofile 4 * GraphQL client (smallrye), CDI decorators supportés, transaction pour MongoDB avec Panache, * Support kotlin grandement amélioré : resteasy rezctive, rest client, reactive messaging extensions supportent tous les coroutines * Support d'Amazon services system manager [Crafting rolling releases for a Quarkus CLI application](https://andresalmiray.com/crafting-rolling-releases-for-a-quarkus-cli-application/) * Y'a encore du chemin pour faire simplement des CLI avec graalVM en comparaison de go * [JReleaser](https://jreleaser.org) outils permettant de livrer automatiquement des projets Java vers différentes plateforme (Homebrew, Snapcraft, Scoop) * Inspiré de GoReleaser et jbang * Le blog package l'outil `kcctl` créé par Gunnar avec JReleaser * Pas mal de conf (Windows vs Linux/MacOS) mais à la fin il y arrive ### Infrastructure [Amazon sort son OpenSearch 1.0 et OpenSearch Dashboard, leur fork d'Elastic Search et Kibana](https://opensearch.org/blog/updates/2021/07/opensearch-general-availability-announcement/) * 1.0 sortie de [OpenSearch](https://opensearch.org) ([GitHub](https://github.com/opensearch-project)) * Suppression du code propriétaire * Upgrading: mise a jour d'ElasticSearch et Kibana vers OpenSearch et OpenSearch Dashboard aussi simple qu'une mise a jour de version * Compatibility: travaux de reflexion autour de la compatibilité avec les outils existants * Testing: infrastructure de test moderne et flexible * Supporte les architecture for Linux ARM64 * Minimal artifacts for embedding of OpenSearch and OpenSearch Dashboards into existing products and services, * Data stream support for OpenSearch Dashboards, * Span attribute visibility and filtering in the Trace Analytics plugin, * Scheduling and tenant support in the Reporting plugin. * Aussi mentionne la roadmap [Kubernetes 1.22 enlève le support des vieilles versions de ressource](https://kubernetes.io/blog/2021/07/14/upcoming-changes-in-kubernetes-1-22/#api-changes) * Faites le ménage en continu pas des grosses migrations tous les 3 ans * Release prévue en aout * Il vont supprimer des APIs qui étaient en beta ### Cloud [Un tweet lance un faux service AWS InfiniDash qui a été repris par des devs et des boîtes](https://siliconangle.com/2021/07/05/fake-amazon-cloud-service-aws-infinidash-quickly-goes-viral/) * La théorie est que la plupart des devs n'entendront parler de technologie que via les tweets et les articles. * Aussi le métier de devrel c'est de surfer la vague du social media. Les dev rels AWS ont continué la farce (je crois) * Werner Vogels, oui pour sur. * gros effet boulle de neige ### Outillage [GitHub copilot](https://copilot.github.com/) * itellisense boosté par les projets visible et hostés dans GitHub et autre données publiques * via l'intelligence artificelle, essaie de comprendre l'intention via le contexte * uniquement le fichier édité en contxte pour l'instant * VSCode extension donc tourne partout où les plugins VSCode tournent * 0,1% de copie exacte * le code nous appartient en tant qu'utilisateur * le code contexte est transmis a GitHub qui l'utilise pour ses telemetries et améliorer les modèles ML * pas toujours du code de qualité * [des secrets valides sont générés](https://twitter.com/alexjc/status/1411966249437995010) (du corpus originali e.g. SendGrid) * [propose du code GPL (derivation?)](https://drewdevault.com/2021/07/04/Is-GitHub-a-derivative-work.html) * attaque de sécurité vont venir :) [Audacity 3 spyware ou pas après le rachat](https://arstechnica.com/gadgets/2021/07/no-open-source-audacity-audio-editor-is-not-spyware/) * la communauté "niveau 2" s'est emballée, a crée une dizaine de forks. * C'était déjà annoncé et discuté avec la communauté Audacity. * OS, pays, cpu, erreurs, reports de crash * Protection légale « law enforcement ». Les 13 ans, juste pour éviter des restrictions légales us * 3.0.2 n'a pas le code des collections de données * Avec feedback initial passe de Google analytics à un hébergement propre. * Quand compile le project c'est off par défaut (donc seuls les binaires distribués l'ont par défaut) donc pas dans les distros linux ### Sécurité [LinkedIn la brèche qui donne des infos de 92% de ses utilisateurs y compris les salaires inférés](https://9to5mac.com/2021/06/29/linkedin-breach/amp/?__twitter_impression=true) * API LinkedIn abusée. * Email, noms, telephone, adresse physique, de 700M d'utilisateurs * Presque interessé de fouiller pour voir mon salaire théorique :) * Dispo sur le dark web ### Loi, société et organisation [Lettre à ceux qui veulent faire tourner la France sur l'ordinateur de quelqu'un d'autre](https://www.codeforfrance.fr/publications) par [Tariq Krim](https://twitter.com/tariqkrim) * [Télécharger l'ebook au format PDF](https://www.codeforfrance.fr/assets/ebook/cloud_14Juillet2021.pdf). Très documenté et référencé * Coulisses et manoeuvres pour installer les GAFAM au coeur de l'État * 17 mai 2021, Bercy présente la nouvelle stratégie Cloud du Gouvernement * GAM (Googla Amazon Microsoft) * À part OVH Cloud, aucun des acteurs français n'a été mentionné par les Ministres * Les lois américaines dites FISA et Cloud Act permettent d'obliger les grandes sociétés US à fournir à la justice américaine les données situées sur leurs serveurs européens * Si l'on met de côté les questions de souveraineté, les services de sociétés comme Amazon, Microsoft et Google sont très ergonomiques * Les Américains offrent des services clé en main, les services “made in France” demandent de combiner plusieurs produits issus de sociétés différentes * Apple, Google, Facebook, Amazon ont embauché des dizaines de milliers d'ingénieurs, dont de très talentueux Français * Les clouds GAM pourraient décrocher le label SecNum Cloud (le plus haut niveau de sécurisation de l'État) * Après avoir délocalisé notre industrie (le fameux “Fabless” de Serge Tchuruk ancien patron d'Alcatel), l'État et les grandes entreprises ont délocalisé leur informatique vers les grandes SSII qui se sont mises à produire des projets à la chaîne ## Nous contacter Soutenez Les Cast Codeurs sur Patreon [Faire un crowdcast ou une crowdquestion](https://lescastcodeurs.com/crowdcasting/) Contactez-nous via twitter sur le groupe Google ou sur le site web

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

Episodio dedicado a comentar el estupendo artículo de Werner Vogels, CTO y vicepresidente de Amazon, titulado 8 predicciones sobre como la tecnología continuará cambiando nuestras vidas en el 2021. Este artículo publicado en su blog personal All Things Distributed, es un análisis de gran interés para comprender los cambios que la tecnología producirá no sólo en el 2021, sino también la próxima década. Werner Vogels demuestra un conocimiento global del impacto de la tecnología y cómo las tecnologías de Amazon Web Services están a la vanguardia de muchas tendencias tecnológicas. Otro punto muy destacable es la absoluta confianza en la capacidad de la tecnología para mejorar nuestras vidas. Al contrario que la visión pesimista de otras personas con respecto a la tecnología, Werner desborda optimismo y un total convencimiento de que el acceso asequible a la tecnología ayudará a que muchas regiones del planeta mejoren su calidad de vida. Las 8 predicciones de Werner Vogels para el 2021 y más adelante son: Predicción 1. La nube estará en todas partes. Predicción 2. La internet del aprendizaje automático Predicción 3: En el 2021 imágenes, video y audio hablarán más que las palabras. Predicción 4: La tecnología transformará nuestros mundos físicos tanto como los mundos digitales. Predicción 5. El aprendizaje en remoto se gana su sitio en la educación. Predicción 6. Los negocios pequeños se lanzarán a la nube y Sudeste asiático y el áfrica subsahariana liderarán el camino. Predicción 7. La computación cuántica comenzará a florecer. Predicción 8. La frontera final… Sin duda se trata de un artículo de gran interés y que por su extensión y profundidad merece una lectura sosegada. En definitiva una visión muy completa del futuro de la tecnología, de la mano de unos de los líderes tecnológicos más influyentes del mundo.

Escucha a Ivan Salazar y Hernan Garcia resumir la sesión de Werner Vogels en re:Invent 2020. Cómo amazon está resolviendo los problemas tecnológicos más difíciles de la actualidad, qué conocimientos compartió el CTO de Amazon sobre la construcción de arquitecturas verdaderamente resilientes y lo que eso significa para el futuro del desarrollo de software. Material Adicional: https://virtual.awsevents.com/media/t/1_nzjikk5i/

Episodio dedicado a comentar el estupendo artículo de Werner Vogels, CTO y vicepresidente de Amazon, titulado 8 predicciones sobre como la tecnología continuará cambiando nuestras vidas en el 2021. Este artículo publicado en su blog personal All Things Distributed, es un análisis de gran interés para comprender los cambios que la tecnología producirá no sólo en el 2021, sino también la próxima década. Werner Vogels demuestra un conocimiento global del impacto de la tecnología y cómo las tecnologías de Amazon Web Services están a la vanguardia de muchas tendencias tecnológicas. Otro punto muy destacable es la absoluta confianza en la capacidad de la tecnología para mejorar nuestras vidas. Al contrario que la visión pesimista de otras personas con respecto a la tecnología, Werner desborda optimismo y un total convencimiento de que el acceso asequible a la tecnología ayudará a que muchas regiones del planeta mejoren su calidad de vida. Las 8 predicciones de Werner Vogels para el 2021 y más adelante son: - Predicción 1. La nube estará en todas partes. - Predicción 2. La internet del aprendizaje automático - Predicción 3: En el 2021 imágenes, video y audio hablarán más que las palabras. - Predicción 4: La tecnología transformará nuestros mundos físicos tanto como los mundos digitales. - Predicción 5. El aprendizaje en remoto se gana su sitio en la educación. - Predicción 6. Los negocios pequeños se lanzarán a la nube y Sudeste asiático y el África Subsahariana liderarán el camino. - Predicción 7. La computación cuántica comenzará a florecer. - Predicción 8. La frontera final… Sin duda se trata de un artículo de gran interés y que por su extensión y profundidad merece una lectura sosegada. En definitiva una visión muy completa del futuro de la tecnología, de la mano de unos de los líderes tecnológicos más influyentes del mundo. Enlaces del episodio: https://republicaweb.es/podcast/8-predicciones-sobre-como-la-tecnologia-continuara-cambiando-nuestras-vidas-en-el-2021/

Episodio dedicado a comentar el estupendo artículo de Werner Vogels, CTO y vicepresidente de Amazon, titulado 8 predicciones sobre como la tecnología continuará cambiando nuestras vidas en el 2021. Este artículo publicado en su blog personal All Things Distributed, es un análisis de gran interés para comprender los cambios que la tecnología producirá no sólo en el 2021, sino también la próxima década. Werner Vogels demuestra un conocimiento global del impacto de la tecnología y cómo las tecnologías de Amazon Web Services están a la vanguardia de muchas tendencias tecnológicas. Otro punto muy destacable es la absoluta confianza en la capacidad de la tecnología para mejorar nuestras vidas. Al contrario que la visión pesimista de otras personas con respecto a la tecnología, Werner desborda optimismo y un total convencimiento de que el acceso asequible a la tecnología ayudará a que muchas regiones del planeta mejoren su calidad de vida. Las 8 predicciones de Werner Vogels para el 2021 y más adelante son: - Predicción 1. La nube estará en todas partes. - Predicción 2. La internet del aprendizaje automático - Predicción 3: En el 2021 imágenes, video y audio hablarán más que las palabras. - Predicción 4: La tecnología transformará nuestros mundos físicos tanto como los mundos digitales. - Predicción 5. El aprendizaje en remoto se gana su sitio en la educación. - Predicción 6. Los negocios pequeños se lanzarán a la nube y Sudeste asiático y el África Subsahariana liderarán el camino. - Predicción 7. La computación cuántica comenzará a florecer. - Predicción 8. La frontera final… Sin duda se trata de un artículo de gran interés y que por su extensión y profundidad merece una lectura sosegada. En definitiva una visión muy completa del futuro de la tecnología, de la mano de unos de los líderes tecnológicos más influyentes del mundo. Enlaces del episodio: https://republicaweb.es/podcast/8-predicciones-sobre-como-la-tecnologia-continuara-cambiando-nuestras-vidas-en-el-2021/

Interviews November 10, 2020Volume 18, issue 5 PDF The Amazon CTO sits with Tom Killalea to discuss designing for evolution at scale. When I joined Am... https://queue.acm.org/detail.cfm?id=3434573 The September/October 2020 issue of acmqueue is out nowSubscribers and ACM Professional members login hereInterviewsVolume 18, issue 5 From the March 14, 2006, press release for the S3 (Simple Storage Service) launchhttps://aws.amazon.com/builders-library/https://press.aboutamazon.com/news-releases/news-release-details/amazon-web-services-launches-amazon-s3-simple-storage-servicehttps://aws.amazon.com/architecture/well-architected/https://dl.acm.org/doi/10.1145/1294261.1294281https://jamesdixon.wordpress.com/2010/10/14/pentaho-hadoop-and-data-lakes/https://queue.acm.org/detail.cfm?id=1142065ACM Digital LibraryMetrics That MatterTracking and Controlling Microservice DependenciesDesigning Cluster Schedulers for Internet-Scale ServicesCanary Analysis Service

En este es el episodio #17 del Podcast de AWS en Español.En este episodio te hacemos un resumen de los lanzamientos que hubo en la tercera semana de AWS re:Invent 2020. Hablamos de los lanzamientos de la keynote de Werner Vogels y todo lo que paso en esta semana.00:00 - Qué pasó esta semana en reinvent?03:40 - Resumen de la keynote de Werner Vogels28:59 - Más anuncios de esta semana48:22 - Top 3 de anuncios de Isa y Marcia 54:37 - Fin de temporada 1

Dans cet épisode, nous résumons les annonces faites par Peter DeSantis, VP Infrastructure de AWS et Werner Vogels, CTO Amazon.com. Nous parlons énergie renouvelable, chaos engineering, un coquillage dans la console, de Prometheus et Grafana et d'un nouveau service Amazon Location Service pour ne pas perdre le nord.

Dans cet épisode, nous résumons les annonces faites par Peter DeSantis, VP Infrastructure de AWS et Werner Vogels, CTO Amazon.com. Nous parlons énergie renouvelable, chaos engineering, un coquillage dans la console, de Prometheus et Grafana et d'un nouveau service Amazon Location Service pour ne pas perdre le nord.

Werner Vogels's keynote was a blast and definitely the highlight of re:Invent 2020. Michael and I are going through the announced features and services. As usual, we also take a look at the technical details.

חדש! ביום רביעי 16 בדצמבר נקיים ״הכה את המומחה״ או ״שאל אותי כל דבר״ AMA עם דותן, אלון ואני בדיסקורד פה https://discord.gg/cJYX7f2j, מוזמנים להאזין, להצטרף ולתחיל כבר לשאול שאלות מראש. פרק מספר 399 (!) של רברס עם פלטפורמה - באמפרס מספר 70 (!!).באולפן (הוירטואלי) רן, דותן נחום ואלון נתיב - בוקר טוב, מלא זמן שלא הקלטנו, ובדרך עוד היה לנו כנס: Reversim Summit 2020, שאליו נרשמו מלא אנשים וצפו בוידאו מלא אנשים - מקווה שהייתם שם, וגם אם לא אז אתם מוזמנים ללכת ולצפות, כל ההרצאות זמינות עכשיו ב-YouTube, פשוט לכו ל-Reversim Summit 2020 וחפשו את ההקלטות או פשוט חפשו ב-YouTube את ה-Playlist, זה גם פורסם ברשתות השונות וכל זה, בקיצור - קל למצוא.נגיד בהזדמנות זו תודה לכל המודרטורים (Moderators), כולל דותן שלקח חלק במאמץ הזה, וזהו:היה בסך הכל מאוד מוצלח, פעם ראשונה בעצם שאנחנו עושים כנס וירטואלי - היו בסך הכל משהו כמו 12 הרצאות בשישה טרקים (Tracks) שוניםעשינו את זה במשך שלושה ימים ברצףה-Q&A היה מאוד צפוף ומעניין, היו הרבה מאוד אנשים שהגיעו ופתחנו את זה ככה גם לשיחה פתוחה באחד הימים שפשוט לא נגמרה . . . היה כיף.מקווה שבפעם הבאה ניפגש פנים אל פנים, אבל עד אז - נמשיך במסורת ה-Zoom.[וזה באמפרס - סדרה של קצרצרים שבה כל אחד מאיתנו מספר על הדברים המעניינים שהוא נתקל בהם בחודש (או קצת יותר) האחרון - בלוג-פוסטים מעניינים, Repos מעניינים ב-GitHub, כתבות מעניינות וכו’].רן - ואולי ככה מעניין לעניין באותו עניין - קצת עדכונים מהרשת על עבודה מרחוק בחברות השונות, שני עדכונים קטנים שיצא לי לתפוס בחודש-חודשיים האחרונים - הראשון - Dropbox מכריזה שהם עוברים למדיניות של Remote Work - לתמידמה שהם עושים בעצם זה הופכים את כל חללי העבודה שלהם לסוג של חלל עבודה משותף, זאת אומרת - לא יהיו שולחנות קבועים, לפחות לפי ההכרזה או הכתבה ב-Business Insider.סוג של WeWork (כביטוי): מרחבי עבודה שאתה יכול להגיע אליהם - אבל אתה לא מחוייב להגיע אליהם - במשרדים השונים, כשאתה יכול לעבוד מהבית מתי שאתה רוצה.האמת היא שלהרבה חברות יש חדשות בתחום הזה, ממש הבאתי מקבץ מאוד קטן - חדשה נוספת מחברה גדולה אחרת כמו Microsoft, שגם הם מכריזים על Policy רשמי של Remote workבו הם אומרים “אתם יכולים לעבוד עד 50% מהזמן מהבית - ובאישור מנהל אפילו ב-100% מהזמן מהבית.יכול להיות, דרך אגב, שזה כבר השתנה, אני יודע שדברים משתנים כל הזמן - אבל בגדול רק רציתי לבוא ולהראות את המגמה, שחברות נפתחות יותר ויותר לסיפור של Remote Work, ולא רק בהקשר של הקורונה.זאת אומרת, מן הסתם עכשיו יש אילו-שהם אילוצים - אבל הם גם מדברים על העתיד, לא מדברים רק על הקורונה אלא מדברים גם על העתיד.דרך אגב, יצא לי לדבר עם חבר שנמצא עכשיו בסאן-פרנסיסקו, והוא אומר שהעיר ממש “מתה” - הכל סגור: מסעדות סגורות, חנויות סגורות, כל האנשים עובדים מרחוק - לא רק עובדים מהבית אלא ממש נסעו למקום אחרהשכירות בעיר ירדה ב30% - לפי מה שהוא אומר, לא באמת בדקתי את הנתונים סטטיסטית - אבל בהחלט מרגישים את השינוי: העיר הפכה לכמעט “עיר רפאים”.זה מעניין - אני מניח שזה לא ישאר ככה לתמיד, אבל אני חושב שזה טרנד מעניין והוא בהחלט מורגש.האמריקאים כנראה תמיד מגיבים מהר, ואולי לפעמים מגיבים, ככה, “בתגובת יתר”; הישראלים מגיבים קצת יותר לאט, אז אצלם אולי הדברים ילכו קצת יותר לאט - אבל בכל אופן, אני חושב שזה שינוי משמעותי שאני חושב שאי אפשר להתעלם ממנו.(דותן) יש לכם מושג מה עושים עובדי Microsoft, שצריכים להתעסק עם חומרה? בדיוק אני חושב על זה . . .(אלון) אני שמעתי על אינטל . . . אני יכול להגיד לך שבאינטל, מה שקרה הוא שבנו להם “מעבדה בבית” . . .(דותן) באמת?(אלון) אנשים הפכו את המטבח למעבדה, עם כל “הציוד המכאני הכבד”, ציוד לפעמים באיזה $100K שיושב להם בבית, לבדיקות . . . אני לא יודע איך Microsoft, אבל אני יודע שבאינטל, חלקם לפחות, עושים בבית.(דותן) גם פה יש איזשהו סימן שאלה של . . . תכל’ס, בית זה שטח פרטי, ועכשיו לקחת לי חדר מהבית, שזה יכול להיות מאוד יקר לאנשים . . .(רן) אני שמעתי, אני חושב שבהולנד או מדינה אירופאית אחרת כלשהי . . . אולי זה היה גרמניה? מציעים למסות את המעבידים ב-5%, או משהו כזה, על כל עובד מהבית - זאת אומרת: לא למסות את העובדים עצמם, אבל למסות את המעביד, כאילו הוא “מרוויח” נדל”ן, אז בוא תשלם על זה איפשהו במקום אחר.זה מעניין - מעניין איזו חקיקה או איזה מיסוי חדש הולך להיות על כל הסיפור הזה . . .(דותן) זה כאילו פותח לי איזושהי תיבת פנדורה . . . נגיד שיש לך ציוד כזה בבית - מה קורה אם הילדים נוגעים בציוד הזה, או חס וחלילה תאונה - מה קורה עם הביטוחים? אם אתה Apple, ומישהו פורץ לך לבית ולוקח את הדגם של ה-iPhone הבא . . . וואו, זה מטורף.(אלון) אני מאמין ש-Apple לא . . . במדיניות שלהם הם לא יעשו את זה מהבית . . . זה אני מאמין שלא יהיהאתה יודע - לא כל החברות עברו לעבוד מהבית, נגיד - וזו דוגמא לזה שהם דווקא יכולים לעבוד מהבית - אבל המנכ”ל של Netflix אמר שהעבודה מהבית זה הדבר הכי גרוע שקרה, וביום הראשון שאפשר לחזור הוא מחזיר את כולם . . .אז הוא הפוך מהמגמה, ואני לא אתפלא אם Netflix קנו לעובדים שלהם חיסונים, אפילו ברמה הזו, כי הוא אמר . . . הוא אפילו הצהיר על זה איזשהו משהו מעורפל, שלעובדים שלו - הם הראשונים שיתחסנו, אני לא יודע אם הוא באמת רכש חיסונים או לא, אבל זה יהיה מעניין.(רן) Amazon השקיעו, בזמנו, כבר ממש בתחילת המשבר, הם השקיעו הרבה מאוד בסניטזציה (Sanitization) של (בשביל) העובדים שלהם - אז עדיין לא דובר על חיסונים, אבל הם הכריזו על סכום, אני לא זוכר מה היה הסכום אבל זה היה סכום מאוד גדול, משהו כמו $100M או אפילו יותר מזה - בבריאות של עובדים ושמירה על הבטחון שלהם וכו’.ומעניין לעניין באותו עניין (II) - אם כבר דיברנו קצת על Microsoft, אז Guido van Rossum, הידוע לנו מתהילתו כיוצר של Python וה”דיקטטור-לעד” - איך אומרים את זה? ה - Benevolent Dictator For Life של Python? - שכזכור לכם מפרקים קודמים של העלילה (לפני 20 באמפרים) התפטר מהתפקיד שלו כ”הדיקטטור-לעד-של-Python” ואמר “אוקיי חבר’ה, הספיק לי - אני יוצא לחופשה”אז מסתבר שהספיק לו מהחופשה הזאת ועכשיו הוא חזר לעבוד - והוא חזר לעבוד ב-Microsoft.הוא למעשה הודיע שהוא התגייס לעבוד בשורות Microsoft, הוא הולך להמשיך לעבוד על Python ולשפר את השפה ואת הכלים של השפה, תחת המטרייה של Python (של Microsoft)וזהו - חדשות מעניינות, יכול להיות שפשוט היה משמעם לו לעשות בטן-גב, או שהוא החליט שהספיק לו, והוא חייב עכשיו לבוא ולהשפיע . . . מעניין איך הקהילה תגיב לכל הסיפור הזה, אני עוד לא ראיתי תגובות מהקהילה, רק ראיתי את ההכרזה שלו ושל Microsoftאתה זוכר בטח שבפרקים קודמים יצא לנו לדבר על “אוקיי - מה עושים עכשיו, אחרי שהוא פרש?”’ וכבר קמו מנהיגים לקהילה - אז מה יקרה עכשיו כשהוא חזר? מעניין, נראה מה יהיה.(דותן) אפשר לעשות מזה סדרה . . . זה נראה מהטוויט שלו, שעכשיו אני קורא את זה בתוך המאמר שבלינק, שהוא אמר פשוט שמשעמם לו . . .(רן) כן - הוא אמר שמשעמם לו, “בואו תנו לי כסף ואני אעבוד” או משהו כזה . . .(אלון) לא, הוא אמר משהו יותר מעניין - הוא לא בדיוק אמר . . הוא אמר “אני לא יודע מה אני אעשה, אבל זה יהיה קשור ל- Python” - הוא לא בדיוק אמר “אני חוזר להנהיג את השפה”.(רן) נכון(אלון) “אני אעשה משהו כדי לקדם את הקהילה של Python”, אבל זה היה די מעורפל כזה של “אני לא בהכרח חוזר להוביל את הקהילה”.(דותן) הנה - הוא עושה ממש עכשיו Twit מעניין - azure.pythonlabs.com - ואז הוא כתב “למדתי לעשות משהו ב-Azure” . . .(אלון) דותן - הפרק של 1 באפריל? אז בדרך כלל אנחנו מקליטים אותו ב-1 באפריל . . . נשמע לי שצריך לחתוך את זה . . .(דותן) אה, נכון . . . נשמור את זה.ד”ש ל-Werner Vogels.(רן) נושא אחר לחלוטין הפעם - Application Load Balancers for gRPCבעצם AWS מכריזים על תמיכה ב-HTTP2 וב-gRPC, תחת ה-Load balancer שלהם, שזה בעצם Feature שאני חושב שהרבה זמן חיכינו לו.בעצם gRPC עובד מעל פרוטוקול שנקרא HTTP2, שזו הגרסא המתקדמת יותר של HTTP, עם פיצ’רים שונים - יש הרבה דברים שונים בין HTTP ו-HTTP2, ועד עכשיו ה-Load Balancers של AWS תמכו ב-TCP וב-HTTP1 או ב-HTTP1.1, אבל לא ב-HTTP2עכשיו הם למעשה תומכים ב-HTTP2 וב-gRPC שרוכב עליו - וזה נחמד, למי שצריך . . . לא תמיד צריך - אם זה gRPC שנמצא בתוך ה-Datacenter, ואתם לא בהכרח רוצים להכניס Load Balancer בפנים,אבל אם זה משהו שמגיע מבחוץ, או לפעמים, במקרים מסויימים, בתוך ה-Data Center - אז זה Feature מעניין שאני חושב שנמצא לו שימוש.ובעניין אחר לגמרי: תורים ישראליים - כולם מכירים את המושג הזה של “תור ישראלי”, כזה שאם אתה מוצא חבר בתור אז אתה מקודם אוטומטית קדימה?אז מסתבר שזו לא רק אנקדוטה ישראלית, אלא שממש יש מבנה נתונים כזה שנקרא “תורים ישראליים”נתנו לזה אולי שם קצת יותר פוליטיקלי-קורקט, אבל השם החביב הוא “תורים ישראליים”, ופה אני מצרף איזשהו מאמר, שמסביר את המוטיבציה למתי נצטרך “תורים ישראליים” כאלה - כשאתם רוצים לצוות כמה Work Items ביחד, כשזמן ה-Setup של כל אחד ארוך . . .אז הוא בא ואומר “אוקיי, יש תורים, ויש גם Priority Queues - אבל לפעמים יש Work Items שהסוג שלהם דומה” - נגיד שאתם רוצים לעשות איזשהו Setup ל-Web Scrapper, או לאיזשהו עיבוד של Data שהוא מאסיבי, ואתם רוצים לעשות Setup מיוחד, אז עדיף לכם לצמד כמה Work Items מאותו סוג ולעבוד עליהם ביחד - ובשביל זה תורים ישראליים, תורים שבהם אתם מצמדים את ה-Work Items לפי הסוגים שלהם, כשהסוגים הם לכאורה “חברים” - תורים כאלה יכולים להיות מאוד יעילים.אז זהו - מאמר נחמד, עם הרבה תרשימים, ובעיקר שם חמוד - “תורים ישראליים”.(אלון) אגב - זה ממש לא חדש. . . (רן) לא, זה לא חדש - רק ההצגה של זה כמדע פופלארי והשם היפה הזה של “תורים ישראליים” - זה כן נחמד.(דותן) אני פשוט רואה פה מאמר של שני חבר’ה ישראליים - ניר פרל ואורי יחיאלי, מאוניברסיטת תל אביב - שנקרא The Israeli Queue with Priorities, שהוא עושה לו רפרנס זה המאמר שכאילו נתן את השם, או שזה בא אחרי שכבר יש את הדבר הזה?(רן) אני לא יודע היסטורית, פשוט נתקלתי בבלוג-פוסט הזה, ואני מסכים שזאת לא עבודה חדשה ולא קונספט חדש, זה נכון, אבל פשוט בלוג-פוסט שמסביר את זה בצורה נחמדה, קצת הומוריסטית וקל לקריאה.(דותן) מעניין(רן) ובעניין אחר - הפעם איזושהי כתבה שפורסמה ב-Geektime, קצת משעשעת, על מהנדס בריטי שהחליט לפתוח חברת ייעוץ ולקרוא לה בשם, שימו לב - “”> LTD”בקיצור - ניסה לעשות Cross sites Script Injection באמצעות השם של החברה . . .(דותן) מדהים . . .(רן) . . . מתוך מחשבה שאם מישהו . . .אולי רשם החברות הבריטי לא יפול בפח, אבל בכל מקום אחר שהדבר הזה יוצג, יכול להיות שהוא ייצר Cross Site Script Attack.אבל זה לא הלך לו . . . אז קודם כל היה לו אחלה חוש הומור, אבל רשם החברות הבריטי כנראה היה מספיק עירני ועצר אותו - אבל הרעיון נחמד.בסופו של דבר הוא שינה את השם פשוט לשם של “החברה שהיה לה Script HTML ורשם החברות סירב” - וזה השם של החברה, פחות או יותר.סתם, סיפור ככה משעשע, וזה כמובן מזכיר לנו את הסיפור על Little Bobby DROP TABLE (כמובן עם קישור ל-xkcd)אחזור על זה, כיוון שזה משעשע - מנהל בית הספר מתקשר לאמא ושואל “הי! זו אמא של בובי? הייתה בעיה קטנה במחשב . . . ““מה בובי שוב שבר?”מנהל בית הספר עונה “זה לא שהוא באמת שבר משהו, אבל . . . האם באמת קראת לבן שלך Robert’); DROP TABLE Students;-- ? . . .”אז היא אומרת “כן, כן - אנחנו קוראים לו Little Bobby Tables” . . . המנהל אומר “רק שתדעי- כל טבלת הסטודנטים של השנה האחרונה נמחקה, אני מקווה שזה ילמד אותך לא לקרוא לילדים שלך בשמות כאלה”אז היא עונה לו בחזרה - “אני מקווה שזה ילמד אותך לקח, לפעם הבאה לסנן את ה-Inputs שלך” . . .כן, אז זהו - xkcd משעשע . . .(אלון) היה אגב, באותו הקשר, מישהו שהשם משפחה שלו NULL, או . . . וב-SOA, מה שהיה עם ה-Web Services, היו מעבירים XML, והייצוג של NULL היה פשוט לרשום String NULL . . .(רן) זה היה ב-SOAP לדעתי . . .(אלון) כן, נכון, ב-SAOP - ואז כאילו אני זוכר שזה לא עבד באיזה משרד ממשלתי או איזו שטות כזאת . . .(רן) כן, אז הייתה שאלה כזאת ב - Stack Overflow - מה עושים אם השדה באמת NULL, והיו כל כך הרבה הצעות שם . . . זה היה Thread, אה, מאוד ממצא, ב-Stack Overflow.אז הנה - עוברים אליך - דותן - קח את זה:דותן - טוב - אז האייטם הראשון שלי הוא Repository שנקרא code-serverבא מחברה בשם Coder, שאני יודע שהם עושים . . . יש להם פתרון של “בוא תפתח לא במחשב שלך, אלא בסביבה, כזאת, וירטואלית”. “בעצם לא באמת צריך את המחשב שלך וכל ה-IDE והכלים כולם אצלנו, והכל יהיה יותר קל” - זה הפתרון שלהם.מה שמגניב פה זה שהם לקחו את VS Code וגרמו לו לרוץ על Browser בשלמותו.תמיד ידעתי של-VS Code יש איזשהו פוטנציאל להיות הרבה יותר ממה שהוא, במיוחד שאני די מת על ה-Vim Mode שלו - מרשים.אני לא יודע אם אפשר לעשות עם זה משהו כרגע פיזית או האם אני ממליץ לעבור ל-VS Code ב- Browser, אבל די מרשים לראות את VS Code בשלמותו עובד ב-Browser.(רן) נזכיר, דרך אגב, שזה לא ה-IDE הראשון שרץ ב-Browser, אמאזון אפילו קנו חברה שעושה את זה, ויש לא מעט חברות אחרות . . .(דותן) כן, Cloud 9 . . .(רן) Cloud 9 . . . יש לא מעט חברות כאלה, אבל אתה אומר שמבחינת ביצוע, יש כאן ביצוע טוב במיוחד?(דותן) כן, יש Editor שהוא כולו על טהרת הנקרא-לזה-Frontend, שנארז ב-Electron, שזה VS Code - ותמיד אתה שואל את עצמך “האם אני יכול לקרוא את הדבר הזה ולדחוף אותו ל-Browser, ושזה עדיין יעבוד?”, האם יש פה איזושהי הפגנת יכולות טכנית מאוד מרשימה?והתשובה היא “כן” - הם עשו את זה.ועוד פעם, ב-VS Code ה-Editor, לפחות החלק של ה-Editing, מבוסס על טכנולוגיה של Microsoft, תעזרו לי אם איך קראו לה - Monaco? משהו כזה? כבר לא זוכר . . .(רן) Monaco זה Front, אבל יכול להיות שיש גם טכנולוגיה כזאת, אני לא מכיר . . .(דותן) בכל מקרה, שם-של-עיר כלשהי שמתחיל ב-”מ” . . . אבל נחמד לראות את זה קורה ממש במציאות, ואני מניח שהם, אותה החברה - יש להם אינטרס שזה יעבוד והם משתמשים בזה בצורה כזו.(אלון) הוספתי פה לינק ל - StackBlitz - האמת היא שכבר דיברנו עליו פעם בעבר, אבל אם תראה אותו עכשיו, אז זה השתפר מאודעכשיו אתה ממש . . פשוט זה “VS Code online” - האמת שבראיונות האחרונים - אני מוכרח כאן גילוי נאות שאנחנו מראיינים - פשוט רצינו שיעשו איזה משהו Frontend ב-React - פשוט תגישו דרך זה, זה הדבר הכי נוח, כאילו . . . תלחץ על React ויש לך Editor, יש לך הכל בפנים . . .(רן) אבל זה רק Frontend, נכון? . . . (אלון) כן, אבל זה מדהים, פשוט מדהים - כי זה עובד: אתה יכול להוסיף Dependencies בקליק, הכלי הזה ניהיה פשוט מפלצתהאמת היא שרציתי לדבר עליו אח”כ, אבל דותן עקף אותי . . .אז זה ממש מגניב: לוחצים בקליק ויש לך אפליקציה עובדת והכל מתעדכן - וזה VS Codeאפילו יש את ה-Extensions . . . אני לא יודע אם כל ה-Extensions של VS Code נתמכים בזה או לא, אבל אתה ממש יכול להעשיר את זה, אם חסר לך איזה Extension של VS Code אז אתה יכול להוסיף אותו.מומלץ בחום, אפילו אם אתם לא צריכים כלום, סתם לשחק עם זה, כי זה באמת פותח את הראש וזה ממש מגניב.(דותן) אני מניח שה-Use case העיקרי, או לפחות המיידי, הוא לכל מיני חברות שיש להן פלטרפורמות לראיונות ב-Real time וכל מיני דברים כאלה - Cloud 9 היה מאוד מוקדםזאת אומרת - יש את התופעה של חברות שמקדימות את זמנן וכל מיני דברים כאלה, אני זוכר את Cloud 9 ממש לפני המון שנים, ואז AWS קנו אותם - אני עדיין לא יודע בדיוק למה . . .(רן) הם משתמשים בהם, נגיד - אתה יכול לערוך פונקציות Lambda ב-Cloud 9, לערוך את הטקסט שלהן . . .(אלון) זה יותר מזה - זה נותן לך Ecosystem - הרעיון שם הוא שזה נותן לך Ecosystem ל-Cloud, שאתה יכול בקליק לעשות Deploy ך-Cloud ואז לשנות - ואז אתה כאילו אומר . . . ה-Editor שלך מחובר ל-AWS, ואנשים נורא נקשרים גם ל-Editor, אז אם מחר אני אעביר אותך אז אתה גם לא תרצה לעבור Editor - ואז אתה גם לא תעבור Cloud . . .(דותן) בדיוק . . .(אלון) זה כאילו הפוך . . .(דותן) זה היה מאוד מעניין, שעוד לא ראיתי אותם אומרים את זה - זה קורה “בשקט בשקט”, אבל . . .(רן) אני משתמש המון ב-Jupyter בזמן האחרון, וזה גם סביבת עבודה . . עכשיו - זה לא באותה רמה של Visual Studio, אבל זה כן . . .זאת אומרת, יש הרבה אנשים שכל החיים שלהם רק חיים בתוך Jupyter, עם כל המגבלות של הכלי הזה, אבל זהו - זה כמובן בתוך הדפדפן, ה-Jupyter.(אלון) יש גם אנשים שחיים בתוך Emacs, זה לא הופך את זה לכלי ממש טוב . . רק אומר.(רן) כמעט אמרת VI, טוב שעצרת את עצמך . . . (דותן) ולאייטם הבא - יש פרויקט שנקרא urlhunter - בעצם זה סוג של כלי, נקרא לזה “כלי להאקרים”, לכל מיני חבר’ה “שמנסים את מזלם”.מה שזה עושה זה שולף קבצים שמכילים של Short URLs ל-URL המלאנגיד - Bitly זה שירות שעושה Shortening ל-URLsיש איזושהי חברה אחרת שעושה את ה-Scanning וה-Crawling וכל זה - והכלי הזה פשוט לוקח ומאנדקס (Index) אותם.בעצם נולד לך סוג של כלי שאתה יכול לחפש איזשהו Regular Expression - נגיד לינק יחסית-רגיש, שהוחבא פעם תחת Short Link - ולקבל אותו.הדוגמא שהם נותנים שם זה נגיד ב Google Docs Link, שאתה יכול ליפול על כל מיני מסמכים פומבייםו-Long Story Short, אתה יכול לייצר לעצמך איזושהי . . . אם אתה האקר שעושה את זה למחייתו אז לייצר איזושהי הכנסה, ואם אתה אתי, אז זה לייצר מאמר ב-TechCrunch על חברה שדלפה כל מיני דברים מעניינים . . .אז קחו, שחקו - ונסו את מזלכם.אייטם הבא - ספריה בשם rich, ב-Python, ולפחות מהתקופה שעשיתי המון ב-Python - היום אני עושה הרבה פחות - חיפשתי ספרייה שהיא דומה מאוד לספריות הפופלאריות ב-Node.js, שצובעת טקסט בטרמינל, שעושה Text-highlighting בטרמינל, שעושה מסגרות, טבלאות, כל מיני דברים נחמדים, נקרא לזה “Developer Experience” מאוד נחמד - ולא היה. ממש ממש לא היה, ודי התבאסתי מזה.והנה סוף סוף יוצאת ספרייה, שנראה שהיא עושה את זה בצורה טובה, שזה ממש ממש מגניב.(רן) דרך אגב, דותן - אתה אומר שהיום אתה כמעט שלא כותב ב-Python - איך נראה ה - Stack הטכנולוגי שלכם היום בחברה?(דותן) Rust ו-TypeScript.(רן) אוקיי . . .(דותן) יש גם Data Science שזה Python - אבל בתקופה הקודמת הייתי עושה פשוט Full-time, כמעט 100% Python - גם Frontend ו-Backend והכל.האייטם הבא נקרא Maddy - למי שזוכר את Caddy, אז יש כזה שרת HTTP שנקרא Caddy, שה-Value שלו כלפינו זה פשוט כשרת HTTP שאפשר להרים, והקונפיגורציה (Configuration) שלו היא מאוד אנושית ומאוד קלילה, והכל מרגיש כמו פלסטלינה.בניגוד, נגיד, ל-NGINX עכשיו ו-Apache וכאלהובא מישהו ואמר - “טוב, אני אחליף את האות הראשונה מ-C ל-N” - יצא לו Maddy - וזה אותו הרעיון, רק Mail Server . . .כלומר - זה עכשיו מחליף את ה Post-fix-ים וכל החבר’ה האלה של העולם.אם אתה במצב שאתה רוצה לבנות לעצמך איזשהו Mail Server in-House, אז האמת שזו אחלה אופציהבאילו מקרים תרצה לעשות את זה? אז אני יכול להגיד, שמהנסיון שלי, הרבה פעמים הייתי מקים מערכות שהמטרה שלהן זה לקבל מיילים, To process them ולעשות איזושהי אוטומציה - נגיד שאתה שולח מייל לאיזשהו בוט - “שלום, מחר תזכיר לי לקנות חלב”, ואז ב-Calendar שלך אתה פתאום רואה Invite לעצמך “לקנות חלב” , או משהו בסגנון.היום, נגיד, אם ניקח את Rails - הם כבר הקימו תשתית, הקימו Framework שעושה את ה Inbound email processing, יש SaaS-ים שעושים את זה, שאתה יכול לזרוק שם איזושהי פונקציהאבל עדיין לפעמים יש מצבים שאתה רוצה ממש Mail Server בכוחות עצמך, שרץ אצלך וכו’.(רן) אני חושב, אגב, שההבדל המשמעותי בין זה לבין ה-Mail Servers היותר מסורתיים ומוכרים זה שה-Mail Servers האלה אולי מממשים את הפרוטוקולים הבסיסיים של SMTP ו-POP3, אבל יש הרבה הרבה מאוד Extensions, בעיקר בתחום של Security ו Anti-Spam וכאלה, כמו DKIM ו-SPF וכאלה, שזה כאב ראש להוסיף ל Mail Server המסורתיים.ו-Maddy - ככה קראנו לו? - Maddy מגיע עם כל אלה Built-in, אז נחמד, זה חוסך לך הרבה מאוד עבודה ב-Setup.(דותן) כן, וכמובן גם Caddy וגם Maddy טובים ב-Go (השפה, לא זה), שזה אומר שאפשר לשחק איתם, לשנות אותם, לעשות Import לחלקים מהם . . . וזה נחמד, מה שאי אפשר תמיד לעשות עם NGINX ו-Apache וכו’.אייטם אחר, של Microsoft - פרוייקט שנקרא . . . אין לזה באמת שם, אבל ה-Repository נקרא Bringing-Old-Photos-Back-to-Lifeהפרויקט עצמו הוא פרויקט Data Science שנקרא Old Photo Restoration ובעצם, מה שהם עשו זה... יש פה איזשהו פרויקט Deep Learning שנותן לך את היכולת לקחת תמונה - “מעופשת, מקומטת וקצת דהויה” - ופשוט להעביר את זה דרך המנוע הזה, ואתה מקבל תמונה שהיא נראית חדשה, “בלי קמטים”, בלי טשטושים - מדהים.עברתי ממש על כל הדוגמאות שיש להם פה.(אלון) בדיוק רציתי להגיד שזה מדהים - אם אתה ב-2010 . . . כי בכל פלאפון (זה ממש 2001. . .) יש את ה-Auto-fix הזה של התמונות, וזה עושה את אותו אפקט . . . (דותן) אני אגיד לך למה זה מדהים - כי לפחות בתקופת הקורונה, כבר נתקלתי בכמה וכמה מופעים שאנשים סביב פשוט שולפים כל מיני תמונות מהבוידעם . . . אתה יודע, הסגר גורם לדברים האלה לקרות, אתה מנסה להוציא את הארגזים ולשלוף את התמונות הישנות ולהיזכר וכל מיני דברים כאלה.ולכן זה מדהים - זה אחלה כלי לבוא עכשיו לסרוק את התמונה - אתה יכול לסרוק או לצלם את התמונה או מה שבא לך.אבל אם יש לך תמונה באמת מיושנת, שבאמת הוצאת אותה מלפני 70 שנה, ששייכת לדורות אחורה - אז זה מאוד מעניין לבוא ולהעביר אותה דרך המנוע הזה, ולראות מה אתה מקבל.(אלון) מה שרציתי להגיד זה רק שב-Google Photos יש לך את ה-Magic Pen הזה, וגם ב-iPhone Photos . . . זה בול אותו אפקט, כאילו . . . (דותן) וואלה . . .(אלון) אז מגניב ש-Microsoft הגיעו לזה עכשיו, אבל . . . היה את זה ב-2010. אולי בלי Machine Learning, אבל . . .(דותן) רגע - אבל זה כולל קמטים? (זה לא קרם, כן?) - זאת אומרת, אם יש לך תמונה עם קמטים כאלה וחתכים . . זה מאחה לך את הכל?(אלון) יש לך Sharpen, שעושה אפקט כזה . . . יש כאן רק איזה אפקט אחד שאני חושב שהוא לא מטפל בו, האפקט של הפסים הלבנים האלה, שאני לא בטוח . . . אבל כל שאר האפקטים . . .(דותן) כן, פס לבן זה קמט או משהו, כשתמונה מתעקמת אז זה נשבר.(אלון) כן, אבל כל שאר האפקטים פה - זה לגמרי ה-Magic Fix עושה לבד, אז . . . לא יודע.(דותן) מה אתה אומר . . .(רן) באותה הזדמנות - יש פרויקט נחמד של My Heritage של צביעת תמונות, בעצם שירות שהחברה נותנת בחינם, למיטב זכרוניאתם יכולים להעלות תמונות בשחור-לבן ובאמצעות - עם גרשיים באוויר “Deep Learning” - או דברים אחרים, לא יודע בדיוק איך, אבל הם צובעים, בצורה אינטליגנטית, מבינים מה אמור להיות הצבע של כל חלק בתמונה, צובעים אותו, וזה נחמד.זה אולי לא מתקן קמטים או דברים כאלה, אבל כל מה שאתם רוצים זה לצבוע תמונות, אז זה נחמד.(דותן) אז זהו . . . כאן אין צביעה של התמונות בפרויקט הזה(אלון) יש על זה פטנט, אגב . . . על הצביעת תמונות יש פטנט, אני חושב של Facebook, שאתה לוקח תמונה בשחור-לבן, אבל נגיד שיש שם פחית קולה, ואתה יודע בדיוק מה הצבע של הפחית קולה ואז לפי זה אתה יכול לצבע את התמונה בצבעים האמיתיים שלה . .. אתה מוצא כמה Anchors על חפצים, נגיד עם Brand - שקית דוריטוס או אני לא יודע מה - ומתחיל לצבוע ככה את התמונה, ואז אתה מגיע באמת לצבעים האמיתיים , שם עובד בצורה אחרת, אני חושב, מהשיטה של . . .(דותן) כן, זה תחום אחר - למי שאוהב Netflix ואת מלחמת העולם השנייה, אז יש כזה מן סרט דוקומנטרי על מלחמת העולם השנייה בצבעים, שעשו Re-coloration לכל הדברים האלה - למי שאוהב את שני הדברים האלה אז זה שילוב מעניין.יש מישהו שנקרא 3Blue1Brown - זה הכינוי שלו בכלל ב-YouTube, ככה אני הכרתי אותו, ועם הזמן הייתי מקשיב לפרקים שלו בנושא מתימטיקה באוטו, במקום פודקאסט הייתי פשוט מקשיב לזה, ומדי פעם חוזר על חומרים בצורה ויזואלית.האיכות שלו . . . הוא לוקח נושא כמו הכפלת מטריצות או כל מיני דברים כאלה ומראה את זה בצורה אנימטיבית (Animated) מאוד מאוד אינטואיטיבית.אז אני Fan שלו - של הערוץ שלו בכלל ושל הוידאו שלו שם, שהם משהו כמו 5 דקות כל אחד אז זה גם טוב, נחמד שזה לא מעיק מדי.מה שהוא עשה - בוידאו שלו יש אנימציות, שהוא לוקח נגיד צירים ועושה להם סיבוב ועושה להם איזושהי טרנספורמציה, ואת כל הדברים האלה הוא לא בנה באיזושהי דרך מלאכותית, אלא הוא כתב קוד שעשה את האנימציות האלה.והוא פשוט משחרר את ה-Code Base שבעזרתו הוא בנה את האנימציות לווידאו שלו, ובעיני זה לא פחות ממדהים.ראיתי קצת קטעי קוד שבונים אנימציות, יש Tutorials ב-Repository למטה - וזה פשוט מדהים.אם אתה רוצה להבהיר רעיון מתימטי - זה ממש השאיר אותי ב”וואו” . . .אז נחמד, ומי שרוצה . . . לא יודע, אולי ברמה האינדיבידואלית קצת ללמד, נגיד - אם רוצים ללמד ילדים ככה, נגיד באיזור התיכון או טיפה לפני, ורוצים לתת אינטואיציה, ולהמחיש באמצעות ויזואליזציה ואנימציה אז זה ממש מעולה.(אלון) בלי קשר, הערוץ פשוט מדהים . . . הפרויקט הזה מגניב גם כן, אבל ה . . .(דותן) זה לגמרי משהו שהיה נחמד לראות בזמן האוניברסיטה, כי זה נותן את האינטואיציה שמאחורי כל התיאוריה - כשגם התיאוריה היא חשובה, אבל גם האינטואיציה.יש פרויקט נוסף שנקרא EUL - לא יודע אם אפשר לבטא את זה - וזה כמו בתקופה של Windows, כשהייתי, אז היו מלא Utilities כאלה מגניבים שמראים לך את ה-Performance של המערכת, וגם ב-Linux . . יש את זה קצת פחות ב-Mac.אז הוא מוציא Utility כזה מאוד מגניב, כשתחת כל Performance שאתה מוציא על המחשב שלך יש בטריה, Volts, מאווררים, מה שבא לך . . .לפריקים של Performance וחומרה ל-Mac בעצם.כמובן יש את הקוד - זה בנוי ב-Swift, והכל נורא מגניב.פרויקט נוסף ,גם באיזור הזה של Mac - למי שמתעסק בויזטואליזציה (Virtualization) של Mac, וצריך עכשיו “להקים Mac-ים מאפס” כזה, מה שיצא לי גם להתעסק איתו - לפעמים צריך “סביבה ריקה” לגמרי, נקייה.אז יש פה פרויקט שפשוט שולף את כל ה . . . אני לא יודע עד כמה זה רשמי, במובן של חוקי, אבל הפרויקט הזה הוא Open-source ומה שהוא עושה זה די יודע איך ה-Installer של Mac עובד, ונותן לך את זה בצורת Scripts של Pythonהוא פשוט . . . אתה אומר לו מה אתה רוצה, מהחבילות שיש ל Mac OS, והוא פשוט מביא לך את ה-Zip-ים ואת Tarball-ים ישירות, ואז אתה יכול פשוט לעשות אם זה מה שאתה רוצה, אם אתה בונה אוטומציות.אז לאנשי אוטומציה או אנשים שרוצים לעשות טסטים וכל מיני דברים כאלה, נראה לי שזה יכול מאוד מאוד להועיל, שזה מגניב.(אלון) עם ה-Mac החדש זה גם עובד?(דותן) וואלה - לא יודע . . . עם ה-CPU של ARM? (אלון) כן, סתם שאלה . . .(דותן) שאלה . . . האם אתה היית קונה את המחשב הראשון שיוצא עם CPU חדש? (אלון) תשמע . . . תראה . . . המחשב הספציפי, הדגם שיש לי של ה-Mac - לרדת מפה הם לא יצליחו, אז כן.(דותן) לא יודע, תראה - זה מעניין, כי אתה יכול לחשוב על זה שה-iPads שיש עכשיו עובדים עם ARM, ובעצם כל מה שצריך זה לקחת את אותו ה-CPU ורק לתת לו עוד קצת בשר, ולחבר לו מקלדת ועכבר ויש לך את אותה המערכת.אבל, מה שנקרא - אני באופן אישי, במיוחד כשזה קשור לכלים האישיים שלי, מה שעובד לי טוב אני לא כל כך רוצה להחליף, במיוחד כשזה קשור לחומרה.אבל בוא נראה איך זה יקרה, כאילו - יכול להיות שזה יקרה כמו שתמיד: הם תמיד מחליפים את ה-Macbook Air, לפחות זה מה שאני זוכר מהפעם שעברה, מהמרים על ה Macbook Airs של העולם, ואחרי זה הם ממשיכים לתוך ה-Pro, לתוך כל ה-Mac-ים שהם באמת למקצוענים שצריכים את זה בשביל היום יום שלהם לעבודה.האייטמים הבאים הם בנושא Rust - אחת הכתבות שהתפרסמו לאחרונה, שקצת יותר תפסו כותרת, היא על AWS, שקצת פרסמה “מאמרי אהבה ל-Rust”, אבל הם היו לטענתי קצת חלשים, כי האחרון שבהם היה “אנחנו תומכים ב-Rust, ונתנו להם אחסון S3 חינם” . . .אז עכשיו הם יוצאים עם מאמר הרבה יותר חזק - הם אומרים ש-Rust זה בעצם חלק מה-Core שלהם, והם חייבים - בצורה אסטרטגית, כמו ש-AWS יודעים לעשות - להשקיע ב-Rust.מה שמעניין פה זה Tokio, שזו בעצם תשתית Networking, הדור הבא בכל מובן ולדעתי גם בכל שפה, שמבוססת ושייכת ל-Rust.וזה חשוב להם - זה בעצם Runtime ל- async Programming.הם הולכים להשקיע בזה - הם לקחו, לפחות עשו Hiring למישהו שהיה ב-Core של Rust, ואני חושב שגם לעוד אנשים.הם בעצם מכריזים - “חבר’ה, אנחנו הולכים להיכנס ממש עמוק לתוך Rust” - שזה ממש טוב.ובלי קשר, באופן כללי, כבר לא מעט חברות, במיוחד מהסוג הזה, שצריך Performance וטכנולוגיה Hardcore עמוק בתוך התשתיות - הן כבר מושקעות ב-Rust, שזה ממש טוב.היה איזשהו Milestone לפני שבוע, ש-Rust הגיעה ל 50,000 Crates, שזה Libraries או Gens או npm Modules או מה שזה לא יהיה.זה לא הרבה במונחים של Ruby ו-Node.js, שם המספרים זה מאות אלפים ואולי מיליונים, אבל מה שאני יכול להגיד מניסיון אישי זה שכמעט כל אחד מ-50,000 האלה הם מאוד איכותיים, לפחות בשלב הזה.אין לי 8 ספריות של Logging . . .(אלון) הבעיה עם הכמות הזו . . הכמות, מה לעשות, מורידה את האיכות - והיה משהו טוב ב-Rust, שהיה לך בקושי ספריות מצד אחד, ומצד שני כל אחת הייתה, וואלה - חלק מהשפה.(דותן) בדיוק - אין לי 8 ספריות של Logging, אין לי חמש ספריות של . . . לא יודע, מה שלא תבחר - וזה לא מבלבל, אתה פשוט לוקח מתוך שניים, אחד.והשניים, שעושים ספריות של Logging, הם ממש שונים, בצורה כזאת שבאמת אתה צריך לבחור מה שמתאים לך, ולא “מה שטעים לך”, מה שהטעם שלך . . . פשוט מה שמתאים לסיטואציה.זה ממש נחמד, ונותן למח שלך לנוח, כי אתה יודע שאתה בוחר באופציה הטובה ביותר שאפשר לבחור.יצא גם ספר - The Rust Performance Book - למי שמכיר Rust, אז יש לו Performance מטורף, וגם יוצא ספר שקצת מדבר על Performance, שזה 3=1+1 כזה, קצת . . .וקצת למי שמתעניין, אז הוספתי גם שני פרויקטים ב-Rust - אחד גדול ואחד קטן:אחד מהם זה פרויקט שעושה משהו כמו 1password - זאת אומרת, עם UI, רק עם Linux, לצערי, GTK-based - מישהו לקח Rust ו-GTK ומימש משהו כמו 1password או LastPass, מה שאתם לא משתמשים בוהשני הוא אולי קצת יותר מעניין, גם בגלל שהוא קטן - נקרא simples, ואני אגיב את זה בצורה בוטה: זה כמו Kafka קטן שמישהו מימש ב-Rust . . .או באופן רשמי - event sourcing databaseזאת אומרת - זה לא באמת Kafka, בואו לא נשלה את עצמנו - אבל זה ממש אחלה פרויקט כדי לקרוא את הקוד שלוהם אומרים שאתה יכול לקחת את זה ל-Raspberry Pi . . . אני לא יודע אם מישהו משתמש במשהו כמו Kafka על Raspberry Pi, אולי ארגונים מחקריים או מישהו שרוצה לבדוק Distributed Systems וכאלהאבל זה באמת אחלה פרויקט בשביל לקרוא את הקוד שלו, לקמפל (Compile) אותו, לשנות אולי טיפה את הקוד, להריץ עוד טיפה וכאלה - למי שרוצה “ללמוד דרך הידיים”, מה שנקרא.זהו - אליך אלון!אלון - (“!Alon is on the Mike”) [דמיינו אפקט סאונד לבחירתכם]אתה (דותן) דיברת על כלי UI חמוד, אז אני אלך על כלי Terminal-י חמוד - DUFשלך היה EUL? - אז חמוד, שלוש אותיות גם כן, אולי דיברנו עליו פעם.למי שאוהב Terminal וגרפים ב-Terminal אז זה הכלי שלכם - אתם עושים ורואים את כל ה-Folders, גרפים, אחוזים, בארים - הכל בגרפיקת Terminal יפה.אז לגיקי-הטרמינל (להקה חדשה?) בקהל, שאוהבים סטטיסטיקות . . .(רן) זה בעצם בא להחליף את du, נכון? כאילו - du, אבל עם קצת יותר ויזואליזציה ושיטה? קצת Norton Commander ל-du.(אלון) ממש . . האמת, נכון. אבל זה יותר יפה, Norton Commander היה כחול, וזה עם צבעים יותר יפים, נעימים, למה . . קצת לכלכת . . .(דותן) Norton Commander זה עם הצבע הנעים . . .(אלון) זה היה עם . . . היה כחול, והיה לו את הפונט הצהוב הזוהר הזה, שאתה צריך משקפי שמש . . .(דותן) כן . . . תקשיב, זה כחול-בורלנד (Borland-Blue), נקרא . . . (רן) “ב-DUF אתה תמצא לא פחות מ-256 צבעים שונים (!)” . . . אוקיי, יפה ונחמד.יש איזה כלי של Google שנקרא ko - זה כלי ל-Go, אז הם כנראה החליפו רק אות אחת ויצא להם ko . . .זה כלי לבנייה ו-Deploy של Go על Kubernetesאז אם Kubernetes זו אבסטרקציה, פתאום ניהיה עוד אבסטרקציה על האבסטרקציה . . . הרעיון הוא שאתה רק נותן Mode מעיין YAML-י כזה, של מה שצריך לעשות, והוא בונה לך כבר את ה-Image, ואתה יכול לעשות איתו Deployment.אז זה נראה מאוד מעניין, האמת - אז אם יש לכם איזה Kubernetes ו-Go ביחד, זה יכול להיות מעניין(רן) יש עוד איזה Framework של Functions-as-a-Service מעל Kubernetes, שכחתי איך קוראים לזה . . . אני זוכר שראיתי משהו בעבר . . .אולי זה יתפתח פשוט ל-ko בסוף?(אלון) יכול להיות . . . זה כאילו . . . לפי מה שרשום פה, זה מה שהם ממליצים או משתמשים או לא יודע.יש גם איזשהו כלי ב-Cloud, שהוא מבוסס על זה . . . של לבנות Image-ים, אז אני חושב שזה מבוסס על זה.(דותן) אני רואה שאחד ה-Highlights פה הוא שאתה כאילו לא נותן . . . כשאתה בונה את ה-YAML-ים הנהדרים של Kubernetes, אתה לא שם Docker Image בצד ובלה-בלה-בלה, אלא אתה פשוט נותן איזשהו Prefix מיוחד שמתחיל ב //:ko, כמו פרוטוקול כזה שלהם - ובעצם כל מה שקורא אחר כך זה פשוט ה-url ל-Package שלך ב-Go אני מניח שמה שהם עושים זה בונים את הפרויקט ב-Go ודוחפים את זה לאיזה Minimal Image ב-Alpine או משהו כזה, והופ! נולד לך Image . . .שזה, האמת, ממש משכנע . . .(אלון) זה חמוד - כי אתה לא צריך Docker . . . זה מוריד לך את ה-Docker, אתה רק מגדיר ב-YAML את מה שאתה רוצה, שהם כבר אומרים “אוקיי, זה ה-Repo שלך? אני בונה לך אותו” . . . (דותן) מעניין!(אלון) למה אני צריך לבנות לבד Docker? תמיד אני עושה בדיוק את אותם הדברים . . . בונה, לוקח את ה-Dependencies שלי, זורק עליהם . . . הרי אין פה איזה משהו מיוחדאלא אם כן יש לך איזה משהו ספציפי, אבל ב-90% מהמקרים אתה הרי סתם אומר “מה אני צריך?” - ודוחף את זה פנימה וזהו.אז חסכו לך את כל זה - וזה מעניין.(רן) אני אגב לא רואה מניעה שזה יהיה גם בשפות אחרות - אולי הגרסא הראשונה זה ב-Go, אבל לא נראה שיש פה משהו שהוא מאוד ספציפי ל-Go.(דותן) כן . . .קצת מזכיר לי את Buildpacks של Heroku(רן) כן, נכון(אלון) כן . . .אז Netlix הוציאו איזה מאמר, על הStreaming . . . על כל האבולוציה של השימוש שלהם ב-Node.js ב-Netlix - הוציאו על זה וידאו נחמד.אז מי שאוהב Node.js ומתעסק עם Performance יכול למצוא את זה מעניין.האמת שזה קצת מוזר, כי כולם לאחרונה רשמו שהם יורדים מ-Node.js ופתאום Netflix, שהם די גדולים ומשמעותיים . . . די מעניין, האמת, כי זו חברה מעניינת והכלים שלהם מעניינים והם פותרים דברים בצורה מעניינת - בגלל זה זה לא איזה מאמר צדדי כזה, שאתה אומר “עוד מישהו הצליח לעשות איזה משהו”, אז אני חושב שיש פה משהו נחמד, ומי שבעולם ה-Node.js ומחפש Performance אז זהנראה לי נחמד מאוד.ו-“Neflix הוציאו וידאו” זה אכן חדשות מטורפות(רן) ועוד Netflix?(אלון) עוד Netflix! איזה חיבור מדהים, הרצף! סתם . . . למי שרוצה לבדוק Speed-Test, אז גיליתי את זה לא מזמן - יש את Fast.comזה ממש נחמד, ואחד הדברים היפים הם שלא צריך ללחוץ על כלום - תמיד כשאתה רוצה לעשות Speed test, אתה ננכס לאתר ועושה “Start!” - למה? בוא תתחיל לבדוק . . . אז זה של Netflix - זה Fast.com, וזה בודק Performance נחמד.(רן) אז כמה מילים על זה - קודם כל הוא בודק רק Download, כי זה הדבר היחיד שמעניין את Netflix, רק כמה Download, ממש לא מעניין אותם Uploadוגם לא Ping - רק מראה לך Download.דבר שני - אני זוכר שכשהאתר הזה הוקם - Fast.com - זה הוקם בעקבות של הסיפור של Net Neutrality בארה”ב, לפני כמה שנים - אתם זוכרים את הסיפור הזה, שהיו כמה חברות גדולות שבאו ואמרו “מה זה? כל חברות ה-Streaming האלה שוברות לנו את האינטרנט! שימו להם מגבלות” וכל זה.ואז Netflix באו ואמרו “רגע, חבר’ה - Net Neutrality! אתם לא יכולים לשים מגבלות רק על חברה אחת ולא על חברה אחרת”.והם גילו באמת שהיו הרבה ISP שהגבילו את ה-Traffic ל-Netflix ולא הגבילו את ה-Traffic למקומות אחרים.אז הם החליטו לבנות את Fast.com ואמרו - “תקשיבו, אתם בעצמכם תמדדו את היכולת של ה-ISP שלכם, ואם אתם לא מרוצים ממנו, אז תעברו ל-ISP אחר” - וזה התחיל אז.אבל אני מסכים שזה אחלה כלי - כלי נורא פשוט למדידה של Download.מה שכן - הוא לא מישראל - אתה לא עושה Download מישראל - אולי זה לא מה שאתה רוצה למדוד, אבל כשאתה עושה Speed Test, הוא בדר”כ מחפש את ה-Download הקרוב ביותר, והרבה פעמים זה קורה בישראל.ו-Fast.com הולך, כנראה, ל-Netflix, באיזשהו מקום בעולם.(דותן) אני יכול לשלוח להם מייל, תלונה או משהו? כי אני רואה רק 960Mb . . . ולא 1000 גדול.(רן) אני לא רוצה להגיד לך מה יש לי על המסך . . . (אלון) בביטים . . .עוד משהו על זה - כן יש שם Upload, אני אתקן - יש שם איזה חץ כזה . . . זה לא ב-Default, כי זה פחות מעניין אותם, אבל אתה יכול לראות גם Upload, אז זה . . .רק שלא יתבעו אותך דיבה, אתה יודע . . .(רן) !I stand corrected, סבבה . . .עוד אתר נחמד, אם אנחנו כבר בבדיקות מהירות - האמת שהוא יותר חמוד - הוא של Cloudflare - ו-Cloudflare, עש להם גם אתר - Speed.Cloudflare.Com - שהם מראים לך Dashboard, שחוץ מזה שהוא יפה ומהיר ונחמד, הוא גם עובד מיד ועם Upload והכלוהוא גם נותן לך את הסטטיסטיקות של ה-Jitter וה-Latency ודברים כאלה, וגם מראה לך מאיפה הוא בודקאת ה-End-point הקרוב לביתינו הוא - לפחות מהבית שלי - הוא גרמניה . . . אולי לכם יש משהו בארץ, אבל אולי בחור השחור של פתח-תקווה זה הדבר הכי קרוב שהוא מוצא.(רן) אני הגעתי ל-TLV . . .(אלון) אני הגעתי לגרמניה . . . זה מה שיש אצלי. אני פרנקפורט . . . למרות שיש להם גם Nodes בארץ, אני לא יודע למה הוא . . .(רן) באמת Dashboard יפה, מראה כל מיני סטטיסטיקות ממש נחמדות.(אלון) כן, והוא גם נותן מידע שאין לך לפעמים - לפעמים אתה אומר שהאינטרנט שלך מהיר אבל הדברים לא זזים בגלל ה-Jitter, אז אתם יכולים להסתכל פה ולהבין אם יש לכם בעיה במחשב, ב-Router, וכו’((דותן) אני גם גרמניה . . . אלון, נראה לי שאני ואתה יוצאים ישר לאוקיאנוס, ישירות . . .(אלון) אנחנו על המהיר! נכון, הוא עובר ועוצר בחנייה פה, שכחתי את אינטרנט שלו . . .(רן) ככה זה באופטי, כן . . .(אלון) כן, אנחנו באופטי . . .(רן) אבל הי - קיבלתי יותר מ-Fast.com . . . (אלון) זה אומר שחוסמים לך את Netflix. . . (רן) לגמרי . . .(אלון) ראית מה זה?ול-NET.! אז NET 5.0 יצאה(דותן) וואו!(אלון) ומדברים פה על . . . זה NET Core 3.1. - מדברים פה על שיפורי Performance די מרשימים שיש בגרסא הזאת.באופן כללי, NET. - אם לא היה לא את העוול של פעם עם ה-Windows, נראה לי שהיום זה היה By-far אמור להיות ה-Framework הכי מצליחאין שום סיבה - יש לו את כל הנתונים להצליח: יש לו את #C, שזהכנראה שפה הכי מתקדמת ונחמדה וה-Framework פסיכי, ולדעתי זה סתם PR רע שהיה לו לכמה שנים כשהם היו באמת לא-להיט ומאז קשה לו להתרומם.אבל באמת - ה-Framework הזה מדהים, ה-NET. - הוא משתפר מרגע לרגע ו . . . לא יודע, אולי ב-NET. 7-8 זה כבר יהיה Framework פופולארי בחזרה(דותן) רגע, אני אשפוך שנייה מים קרים(דותן) לא, לא עכשיו . . .(דותן) זה נראה, לפחות מה-Screenshot, שהשיפורים הם סביב SQL ו-Caching של SQL וכל מיני דברים כאלה . . . אבל אני מקווה שיש יותר מזה.אני תמיד הייתי בעד ה-NET. - מהצד . . . כלומר, אני כבר לא בפנים, אבל מהצד.(אלון) אז קודם כל כן - הם מדברים פה שה-Output, שזה Caching sample, איזה Fusion’s “Caching” sample של איזה רכיב שהוסיפו פה.אני לא יודע אם זה ספציפית רק על הרכיב הזה או עוד דברים - אבל באופן כללי . . . יש שם גם איזה לינק למאמר יותר רחב ובפירוט . . .(דותן) אני רואה שזה באמת . . .זה Across the board - המאמר הבא הוא ממש וואו - GC ו-Jit ומלא מלא דברים יש לו פה . . .(אלון) כן - זה גם חופר פסיכי, כאילו במספרים, למי שזה מעניין אותו, זה חופר, יורד פה לפרטים ולכל המספרים, וזה נראנה פסיכי - מספיק להסתכל פה על הגרפים ולראות את השיפורי Performance . . .כמובן שזה “בדיקות מעבדה” - Disclaimer וכל הבלה-בלה-בלה - אבל ה-Framework הזה פשוט מתקדם מדהים.(דותן) אני אגיד לך מה - כשאני משווה את שני “ה-VM-ים הדינוזאורים” - Java ו-NET. - אז כש - NET. מפרסמים “שידרגנו גרסא ויש שיפורי Performance”, אז המאמר, שעכשיו אני מסתכל עליו ועומד מולו, הוא ממש כייפי לקריאהכלומר - יושב בנאדם, בנה פה מאמר ש . . . לא יודע, עם ה-Scroll-bar אני יכול להגיד שיש פה 50, אולי 70 עמודים - והוא כתב אותו טוב מלמעלה עד למטה, ואני ככה “צד” כל מיני תכנים בעיניים - וזה נראה אחלה חומר קריאה גם לללמידה, ככה בכיףהוא מלמד על לקחים שהם למדו, מה עבד ומה לא עבד - איך בונים שפה, בקיצור.בעיני זה סוג של הבדל, נגיד, בין לחיות בתוך ה-Ecosystem של Java לבין NET., שפעם היום מתחרים גדולים, אני לא יודע עד כמה זה נכון עכשיו.(אלון) אני לא יודע אם הם באמת היו מתחרים, כי תמיד היה להם את הבעיה של “רק Windows”, והעולם היה תמיד Linux, אז הם . . . אני לא יודע מתי הם באמת הובילו.(דותן) פעם שדה הקרב היה הרבה יותר מיושר - אם אתה מסתכל על 2008, נגיד עד 2010, אז הקרב היה . . . היה שם פייט רציני.היום הם כבר בטח לא.(אלון) כן, למרות ששוב, כמו שאמרתי - אני חש שזה Marketing issue - ומן הסתם הקהילה לא שם, אז זה הבעיה . . . רוב הקהילה ב-Java אז הכלים נכתבים שם.(דותן) כן, Windows Server היה משהו פעם . . . (אלון) כן, היום אף אחד כבר לא יודע מה זה . . . בסדר, לא יודע אם יש עוד דבר כזה בכלל(רן) בוא נבדוק אם יצאה גרסא חדשה ל-IIS, יכול להיות שיצא IIS 6 או 7 או 8, לא זוכר . . .(אלון) יו . . לא, היה 7(רן) היה 7?(אלון) היה עוד משהו, 7 אני זוכר שהיה, אחרי זה אני לא יודע.מי שעבד עם IIS יותר מתקדם מ-7 - 8 ומעלה - אנא שלחו לנו גלויה, ואנחנו נפתח אותה בפרק הבא, ונגיב!אז תודה למגיבים.אז נמשיך . . .כלי חמוד - דיברנו על UI ב-Terminal, אז progressbar ב-Goלמי שרוצה לעשות Progress Bar חמודים ב-Terminal, איזה יש פה ספריה חמודה ב-Goקחו, אמצו, השתמשו.ואגב, דרך פה יש את הפרויקט הזה, שאני לא זוכר, אני חושב שדברנו עליו, שנקרא crocדיברנו - ב-Bumpers הקודם . . .זה Client-to-Client, לשלוח קבצים - אז הוא פשוט משתמש בספרייה הזאת כדי לעשות את ה-Bar-ים החמודים שלו, אז זה כל מה שרציתי לציין פה.(רן) חמוד, באמת נראה נחמד(רן) אז אלון - תגיד לי: איך עובד DNS? אתה יכול להסביר לי איך עובד DNS?(אלון) או - טוב ששאלת! אני שמח . . . במקרה הכינותי מראש: יש אתר ממש חמוד בשם How DNS works (זה HowDNS.Works - זה הדומיין . . .)ואז יש Episode I, וזה ממש מסביר בצורה ציורית-קומיקסית כל שלב שקורה ב-DNS - מה קורה כשמקלידים ב-Browser, ואז ה-Browser עושה “עצור! מה זה הכתובת הזאת?”, הולך למערכת הפעלה, שואל את עצמו האם יש לו ב-Cache, שואל את המערכת הפעלה - שניהם מחפשים ב-Cacheלא מוצאים - הולכים ל-DNSוהכל בקומיקס ממש חמוד - אז מי שרוצה להבין DNS לעומק, יכול לראות את הקומיקס הזה, ואשכרה לדעת DNS לעומק.(רן) ואם זה קל לך מדי - אפשר לעשות את זה שוב, בספרדית. יש את זה גם באנגלית וגם בספרדית.(אלון) זה המבחן - במבחן אחרי זה אתה צריך להשלים . . . אתה מתרגם את הספרדית לאנגלית כדי לראות אם הצלחת . . .(רן) כמו שהיה בבית ספר “מפה עיוורת” - היית צריך להגיד איפה הישובים.(אלון) נכון, היה משהו כזה פעם (בית ספר?)היה בצבא גם . . במבחן בקורס קצינים פעם היה משהו כזה, לא יודע.(רן) כן . . . תגיד - מה מצב רשתות ה-GAN בזמן האחרון? הייתה התקדמות עם Generation של פרצופים?(אלון) שמע, זה נושא מעניין שאני רוצה בדיוק לדבר עליו . . . אז היה פעם את האתר הזה, שמייצר את הפרצופים הזה . . שכחתי את שמו - שהיה מייצר פרצופים רדנומליים?הכוונה ל-This Person Does Not Exist?אז עכשיו יש את זה ב-New York Times ,ממש יפה - זה קצת התקדם, ועכשיו הוא ייצר מלא פרצופים דמיוניים . . .המערכות האלה ב-AI, ואפשר לשחק באתר של ה-New York Times, בגלל זה הוא כל כך יפה . . . אתה יכול לשחק עם הגיל של הפרצופים שם, ועם העיניים . . .אתה מקבל אינסוף פרצופים, על אותו פרצוף אפילו . . .לסובב אותו, לחייך, אם אתה רוצה שהפרצוף יחייך או יהיה עצוב - זה ממש Gamification קלאפילו אפשר לשנות Race, מאדם שחור ללבן, או Gender, מאישה לגבר - על ידי sliderאז . . . ממש מגניב.(רן) למי שלא היה פה בפרקים האחרונים, מדובר על רשתות GAN, רשתות שבעצם מג’נרטות (Generates) תמונות של אנשים שהם לא אמיתיים - אבל התמונות נראות לחלוטין אמיתיותאתם תראו את התמונה ותגידו - “וואלה, זה בנאדם”, נראה כמו תצלום של בנאדםאף אחד מהאנשים שמופעים פה בתמונות לא באמת קיים - הכל מג’ונרט (Generated)ומה שיפה זה שהם עשו בכתבה הזו של ה-NYT זה שבאמצעות Scroll פשוט של העכבר אתם יכולים לעבור בהדרגה מפרצוף אחד לפרצוף שני, או כמו שאלון אמר קודם - לשנות Gender, לשנות Race, לשנות הבעת פנים וכו’.והכל נראה ממש טבעי - זה נראה כמו איזשהו סרטון של בנאדם שמתחיל לחייך, והכל נראה מאוד אמיתי ויפה, זה מגניב.נכון שהטכנולוגיה עצמה לא חדשה, והיא באמת מאוד השתפרה - והתצוגה של ה-NYT פשוט מאוד יפה.(אלון) אני חושב שהם באמת עשו פה מהלך יפה עם התצוגה - היו כל מיני אתרים, אבל זה באמת הכי מרשים שראיתי.(רן) ואנחנו לקראת סיום - נעבור למצחיקולים שלנו: יש לנו פה כמה פריטים קטנים - אז האייטם הראשון - בעצם שני האייטמים הראשונים - הם מאת מחבר בשם מיכאל ציון - Michael Zion - חבר שעובד איתי (רן) ב-Appsflyer - בחור מאוד יצרתי, והוא יצר כמה פרויקטים בקוד פתוח, הראשון שבהם נקרא okify - זה פרויקט ב-Go, קטן, שנותן לכם להרגיש טוב עם עצמכםלמה להרגיש רע כשאפשר להרגיש טוב? יותר חשוב . . .השורה שלו היא “הרגשות שלכם יותר חשובים מ-Production” - קודם כל תרגיעו, הכל בסדר.אפילו אם זה 404 - הכל בסדר, עשיתם הכל נכון, אין לכם מה לדאוגגם אם ה-CI נכשל - זה לא אשמתכם! אתם עשיתם כל מה שצריך!כל מה שאתם צריכים זה לקחת את ה-Output, להכניס אותו לתוך okify - והוא כבר יתן לכם איזושהי תפיכה נעימה על השכם.כמו שהוא אמר - “יותר חשובים הרגשות שלכם מאשר ה-Production או ה-CI או אחרים” . . .כלי מאוד נחמד - והוא אחר כך גם הולך ועושה בו קצת שימוש בכלים אחרים שהוא כותבוהכלי הבא נקרא singload - וזה למעשה Load Balancer שמפשט מאוד את הענייניםלמה לעשות Load Balancing להרבה מאוד Server-ים שונים, אם אפשר לפשט את הסיפור הזה, ותמיד לעשות Load Balancing לאותו Server, לאותו Backend Server?הוא אומר “Load Balancing זה קונספט נורא מורכב- בואו תקימו Cluster, שהוא Single-load, וכל ה-Cluster בסופו של דבר ינתב את כל ה-Traffic ל-Server אחד, ויהיה לכם מאוד ברור איזה Server הולך לקבל Traffic, בלי כל הסיבוך הזה של Load Balancing”.(אלון) נורא קל ל-Debugging . . . למי שמכיר את הבעיה עם Load Balancer - נורא ק

Even as most of us are trudging through our days within the boundaries of our homes, our digital lives are roaming farther and faster out there in the world than ever before. Simon sits down with Amazon CTO, Dr. Werner Vogels, to hear where his digital life has roamed recently, and what he has seen along the way. That includes everything from people with almost no coding skills quickly building applications to help their communities get through this hard period, to the notion of customers dialing-in “cost aware architectures,” and startups tackling the world’s toughest problems on Vogels’ show “Now Go Build.” Running through every example Vogels gives is the idea that, especially now, we have the ability and the need to build digital systems that address our very human needs. Oh, and music to listen to when you are coding until 4 a.m. Now Go Build YouTube Playlist: https://www.youtube.com/playlist?list=PLhr1KZpdzukdIpgzSSCkNsnRAwDz6Xx5B Now Go Build on Prime Video: https://www.amazon.com/gp/video/detail/B08GQLV5NK/ref=atv_dp_season_select_s2

S05E10 - Automatiseer je levenOp een verloren avond dook Alexander de wereld in van Zapier. Dat is een tool die je helpt verschillende diensten aan elkaar te knopen. Zo kun je Philips-lichten laten knipperen als je een LinkedIn endorsement krijgt. Ja, gek voorbeeld, maar het kán dus wel. Ernst-Jan bouwde ondertussen een persoonlijk financieel systeem, waarmee al zijn belangrijke geldbeslissingen automatisch voor hem worden genomen. Wat volgt is een uur praktische tips uitwisselen rond dit soort trucjes. Maar, met een duidelijke grens, we gaan allebei nooit aan een smart home beginnen. Shownotes:

Deze week geen gast, vakantie of een verkocht bedrijf, maar een ouderwetse lijstjes-aflevering. We bespreken aan de hand van een kunstwerk hoe E-ink niet alleen onze levens maar ook de maatschappij gaat verbeteren. Alexander kwam een openklappende telefoon tegen die daadwerkelijk iets oplost. En Ernst-Jan zit de toekomst van het uitgeven en de journalistiek in een kinderboekenuitgeverij. Alleen een echte POM-luisteraar ziet de samenhang in deze onderwerpen. Veel luisterplezier! En vergeet niet de extralange shownotes te bekijken.

On this episode of The Six Five - Insiders Edition hosts Patrick Moorhead and Daniel Newman welcome Jeff Barr, Vice President and Chief Evangelist at AWS to discuss AWS’ response to COVID-19 and exciting new product announcements.   AWS’ Response to COVID-19   During this COVID-19 pandemic, AWS has been focused on helping customers continue to operate as efficiently as possible. One of the first things the company did was make it easier for businesses to get access to Amazon Workspaces, a virtual desktop in the cloud. They also had special offers for Amazon Chime and Amazon WorkDocs to help companies facilitate collaboration.   In addition to helping customers, AWS launched the Diagnostic Development Initiative (DDI) to provide support for innovation around both testing and development of different kinds of solutions. They’ve also made AWS compute power more available to researchers who are studying different possible solutions and vaccines.   Finally, AWS launched a public data lake with curated data sets so experiments could actually run queries on real data which will hopefully allow scientists and researchers to find a cure faster.   AWS Virtual Summit   Traditionally, AWS hosts Global Summits throughout the year, but given the current stay-at-home orders still in place, they’ve had to pivot to a virtual summit the first of which was Wednesday, May 13.   The summit is free, online and anyone interested can join. The event is designed to bring the cloud computing community together to connect, collaborate, and learn about AWS. Attendees will hear from CTO Werner Vogels, CEO Andy Jassy, and several other AWS employees who are subject matter experts in various AWS categories.   Breaking Down AWS Announcements   Jeff, Patrick and Daniel spent time discussing several of the new AWS announcements from the last few months that are making a difference for customers all over the world.   Amazon Macie   Macie is a security service that uses machine learning to automatically discover and protect sensitive data in AWS. This service has been around for about a year, but AWS has recently made some great additions including updating the machine learning models so customers can scan for even more types of private information. They’ve also added some customizability if customers have special data types that might have different kinds of proprietary or sensitive data inside. The best part is AWS has lowered the price down to a fifth of what it previously cost so more customers are able to benefit from the different services.   Amazon Elasticsearch Service   Data is growing exponentially in quantity and size and Amazon Elasticsearch Service customers are needing new ways to store and access data as efficiently as possible, specifically data that was collected for the long-term. The current storage tier was called Hot for quickly accessed storage. AWS just introduced a new tier — Ultra Warm — that will hold the more historic data that customers don’t need as often and it will take slightly longer to access.   Amazon AppFlow   SaaS applications have been highly functional, but the data created and collected across these many applications has effectively been in a silo. Amazon AppFlow is a service that allows customers to securely transfer data between SaaS applications. Customers can unlock the access to that data, making it easier for data to flow from the SaaS app into AWS as well as the other way around. and the other way around as well. Customers can run data flows on a schedule, in response to an event, or on demand — basically whenever they need it.   Amazon Kendra   AWS’ enterprise search tool Kendra gives customers powerful natural language search capabilities across websites and applications so users can easily find information in the data spread across the enterprise.   While most search tools use keyword queries, Kendra is able to use natural language questions to search through portals, wikis, databases, and document repositories to find whatever is needed. It not only captures the data, but also the access permissions for the data too.   Amazon Augmented AI (A2I)   Many current machine learning applications require humans to review predictions to ensure results are correct. Amazon Augmented AI or A2I makes it easy to build the workflows required for these reviews and provides a built-in review system for common machine learning use cases.   Customers are able to choose three different categories of human reviewers. They can use the 500,000 global workers that make use of Mechanical Turk. There's a set of third party organizations that have a base of pre-authorized workers, or organizations can make use of a private pool or workers.   AWS Snow Family   The Snow Family devices are physical devices that have both storage and local compute power making it easy to migrate data into and out of AWS. Recently AWS launched an improved version of the Snowball Edge Storage Optimized devices. These devices provide both block storage and Amazon S3-compatible object storage.   AWS did a hardware refresh, added additional processing power, and added some additional SSD storage inside. Now if you launch EC2 instances on the Snowball Edge those instances have access to this SSD powered storage.   You can use these devices for data collection, machine learning and processing, and storage in environments with limited connectivity giving customers the ability to use them basically anywhere.   Finally, AWS also made it easier for our customers to set up and manage the Snowball Family devices with AWS OpsHub, a graphical user interface where customers can unlock, configure, copy data to and from the device via drag and drop even if they're not connected to the Internet.   If you’d like to learn more about any of these announcements, be sure to visit the AWS website. Make sure to listen to the entire episode below and while you’re at it, be sure to hit subscribe so you never miss an episode.

스탠다드아웃 81번째 로그에서는 AWS 새소식들, 당근마켓 쇼핑앱 2위, #MayThe4th 해시태그 등에 대해 이야기를 나눴습니다. 참가자: @nacyo_t, @raccoony, @seapy 정기 후원 - stdout.fm are creating 프로그래머들의 팟캐스트 | Patreon 쇼노트 AWS 새 리전 소식 새 AWS 아프리카(케이프타운) 리전 소개 새로운 AWS EU(밀라노) 리전 발표 Reaffirming our commitment to Italy: Introducing the AWS Europe (Milan) Region - All Things Distributed Werner Vogels 블로그에 긴 글로 소개 Miserlou/Zappa: Serverless Python In the Works – AWS Region in Indonesia | AWS News Blog 세종에 세계 최대 규모 네이버 데이터센터…2022년 준공 | 연합뉴스 아마존 제프 베조스의 2019년 연례 주주 서한 (번역) – 이바닥늬우스 AWS 이미지 빌더, 우분트 등 주요 리눅스 지원 EC2 이미지 빌더, Ubuntu, RHEL, CentOS 및 SLES에 대한 지원 추가 Packer by HashiCorp AWS의 신 서비스들 AWS Chatbot 정식 출시 AWS Chatbot과 슬랙(Slack)을 연.. : 네이버블로그 Amazon AppFlow 소개 Amazon EventBridge 통합 Amazon CloudWatch Synthetics 정식 출시 Companies everywhere are powered by Statuspage | Statuspage GitHub Status GitHub과 GitLab 이야기 GitLab Infrastructure Team · GitLab Features • GitHub Actions Bitbucket | The Git solution for professional teams Mercurial SCM eunjeon / seunjeon — Bitbucket 당근마켓, 안드로이드 쇼핑앱 MAU 2위 ‘당근마켓’ 일 사용자, 11번가·위메프 넘어섰다 | Bloter.net 유랑마켓 | 프로그램 | JTBC #MayThe4th 해시태그 Disney+ on Twitter: “By sharing your message with us using #MayThe4th… https://t.co/G0AyToufQ5” / Twitter lunamoth on Twitter: “https://t.co/CywDAouwGH Chris Messina on Twitter: “By using any hashtag, in digital or physical media,… 시피의 부동산 이야기 ‘진짜 부자는 강남아파트 안 살아’…회장님 줄줄이 모여사는 이곳 단독 김범수 카카오 의장, 147억 분당 초호화 주택 최초 공개 - 한국비즈 다운튼 애비 | 다음영화 유비쿼티 유니파이(Ubiquiti Unifi) 제품 기반 홈 네트워크 구축기 | 44BITS 담장 없애랬더니 집 요새화…판교의 ‘중정형’ 단독주택 - 중앙일보

רן, אלון, ודותן (ואורח מיוחד!)  בפרק מספר 66 של באמפרס (387 למניין רברס עם פלטפורמה, קורונה + 20 בגימטריה) - עם קצרצרים וסקירה של טכנלוגיות ודברים מעניינים האחרון, נכון ל-1 באפריל 2020. כנס חדש בישראל! (בהנחה שבזמן שאתם מאזינים העולם עדיין קיים ולא נסגר לרגל הקורונה) - כנס מתָחזקים ומִתְחזקיםהוועדה המארגנת כוללת אחד בשם דותן נחום והוא חושף פרטים - קודם כל הכנס בעל שם עם ניקוד, אחרת לא תבינו - מדובר בכנס לאנשים שמתחזקים קוד, ויודעים לקחת את כל מי שסביבם ולחזק אותם, כי לתחזק קוד זה לא דבר פשוט.יש כמובן גם אתרבין ההרצאות המתוכננות (מחפשים דוברים - הגישו  מועמדות!) - “קוד לגסי (Code Legacy) - בעד ונגד” (האם נכון להכניס קוד Legacy חדש או לא?)“איך להגיד ״לא״ לטסטים” (הרי כולנו מעבירים את רוב היום על הדילמה הזו)עצה ממומחה“סורס קונטרול (Source Control) מודרני ו SVN”או - Git מול SVN, שחוזר בגדול עכשיו עם כל בעיות ה-Security של Git.ולמהדרין - אם אתה כבר פותח חברה, קח ארון ושים שם את כל השרתים שלך. הכי טוב.“תנועת האג׳ייל ולמה זה טוב”כן, זה דו-משמעי. לא צריך ניקוד.“סטנדאפ (Stand-up meetings) - אפשר יותר מפעם אחת ביום”(אלון) ואפילו מומלץ! עד אחה”צ אתה הרי כבר שוכח על מה דיברו בבוקר.יש כבר מאמר שמראה שבגלל שזה קצר אז יש ארגון שמנסה ארבע פעמים ביום. קריאה מהנה.קלוג׳ר (Clojure) בארגון צומח - לעוד 5 שנים מוצלחות”“לכל כלי יש אתר - למה הכי טוב לפרמט קבצי קונפיגורציה וקוד באתר פומבי ברשת”הרי יש כל מיני כלים, והרעיון הוא שהכי נוח לקחת את כל קבצי הקונפיגורציה, להעלות לרשת, לפרמט (Formatting), להעתיק בחזרה ולהחזיר לקוד - לא צריך להתקין כלים חדשים.(אלון) סוג של HTML-based configuration? לא - למשל אם יש לך קובץ json, רק להעלות לרשת, לקבל פורמט ולהחזירזה לא שיש מה להסתיר, חבל להכביד עם עוד כלי בינארי - יש כבר הכל בחוץ“הצפנה בעד ונגד”יש עכשיו טרנד של להצפין כמה שפחות, כי זה ממש יקרבעידן של Quantum computing גם ככה הכל הולך להישבר אז למה זה טוב?“איך עברנו לססמאות קצרות וחסכנו 5GB בשנה על אחסון”חברה שמציגה חסכון אדיר על ידי מעבר לסיסמאות קצרותנכון, יש עקרונות של סיסמאות ארוכות, אבל האם מישהו אי פעם עצר לחשוב כמה מקום זה תופס ב-Database?!טרק מיוחד של Design & UXחביב במיוחד על רן - תמיד אפשר ללמוד מההיסטוריהבין הרצאות גאוסיטיס (GeoCities) - המיטב: כל ה Best Practices וה - UX שהאתר הזה גילה ויצר - ומה אפשר לעשות איתם היוםבטרק של Work-Life Balance: ל”ראות את הילדים בערב - בעד ונגד”יש כאלה שעברו לשבוע-שבוע . . .ועוד יותר רלוונטי עם כל עניין הקורונה - יש כאלה שמעדיפים לראות את הילדים רק עם Zoom.מוזמנים להציע נושאים נוספיםולאורח המיוחד - ארני (ארנון) פוגל (Arnie (Arnon) Fogel) שמבקר בישראל והצטרף להקלטה! כבוד גדול שמח לגלות שהטכנולוגיה הזו של הפודקאסט תפסה גם בעבריתלא הרבה יודעים אבל אח שלי הוא Werner Vogels - התחלנו את הקריירה יחד בגיל 12 עם אפליקציה למשחת שנים עבור בן-דודמפה לשם זה גדל, עד שחצי North-Minnesota הייתה אצלנומשם עברנו לתוכנה לחוט דנטלי . . .באיזה שלב אחיך עבר ממכירת אמצעים דנטליים למכירת ספרים דיגיטליים ב-Amazon?המעבר היה פשוט - יום אחד הוא ישב ב-Subway וראה מישהי שיושבת וקוראת את הדף הראשון בספר (זה שריק לגמרי), ואז מגלגלת אותו והופכת אותו לקיסם שיניים.זה בא במקביל לגל ה”Combo” - מדפסת-סורק, מצלמה-טלפון, כל אלהמפה לשם - ספרים שמנקים איתם שיניים? מהפכני!ומכל זה נולד כל העניין של Cloud-Computing - והיום Werner Vogels הוא ה-CTO של AWS - והתפוח לא נפל רחוק: היום ארני נמצא ממש בחזית הטכנולוגיה. עדיין מוכר קיסמי שיניים?לא - יש לי אתר ב Etsy, של קיסמי שיניים מעוצבים אישית עם ברכה“שלא תדע עששת”? זה שלימשווק יחד עם Beyond Meatועכשיו אתה עוסק בשיווק קורונה?למה ככה?! מדדו לי חום בשדה והייתי בבידוד 11 ימים עד אתמול . . . ויתרתי על היומיים האחרונים כדי לבוא להקליט איתכם.אם סופרים ב- Hexadecimal זה יוצא בסדר.עברנו על חשבון ה-Twitter שלך ומצאנו כמה דברים מעניינים שנשמח אם תוכל להתייחס אליהם, למשל - Space Computing vs. Cloud Computing - האם זה באמת הולך להיות השלב הבא?אם נחזור רגע לניסוי הזה של אח שלי - הוא התחיל עם זה שהיו להם מלא מחשבים שלא עושים כלום, ואז הוא הגיע לבזוס, שהוא כל כך קמצן  שאפילו את התחתונים הוא לפעמים משכיר בתור ממחטה.הוא הציע לו להשכיר את המחשבים בינתיים - ובזוס הסכים.אז אני (ארני) הלכתי ל-Elon ואמרתי לו: “אתה העלת לשמיים מלא לוויינים בגודל של קרטון חלב, ולאף אחד אין מושג מה עושים עם הדבר הזה - בוא נריץ עליהם עבודות ונראה מה יקרה, אולי יצא מזה business”.באיזה שלב זה נמצא? יש כבר לקוחות Beta ל-Space Computing? אפשר לקחת CPU בחלל ולהשתמש בו?כבר היום משרד הבריאות הישראלי משתמש בזה לחיזוי התפשטות הקורונה, בגלל זה אתם כאן top of the line עם זה(בהנחה שעד מועד השידור האנושות תתקיים והשמש תזרח).גם המערכת הזו שאומרת מתי מגיע אוטובוס בישראל, שעבור האינטגרציה שלה הגעתי לכאן היום - המערכת הזו מחשבת את תנועת האוטובוסים תוך שימוש ב Space Computingוכל זה קורה ממש מתחת לאף שלנו . . . מדהים.נושא אחר שעלית עליו הוא ההבדל בין HL ל - ML, כלומר - Human Learning לעומת Machine Learning.ספר לנו קצת על זה  . . .אני חושב שאנחנו עומדים מול טרנד חדש של “כמות מול איכות” - מחשבים לומדים בסך הכל מאז שנות ה-70, והם לומדים טוב בסך הכל ב 5-10 שנים האחרונות - אבל אנשים לומדים כבר 25,000 שנים, וזה הרבה יותר זמן ללמוד.הרבה יותר למידה התבצעה פה, וזה חבל לא לנצל את זה . . (רן) אני באמת זוכר מהקורס שלי בבינה מלאכותית - רשתות נוירונים מדהימות קיימות כבר במוח האנושי, אז למה בעצם אנחנו מנסים להמציא מחדש את הגלגל עם רשתות נוירונים ממוחשבות, מה הטעם?מעולה - הרמנו בדיוק שירות מעל Human Learning: אם אתה רוצה לנסוע ממקום למקום, למשל בניו יורק (שם הרצנו פיילוט), אז במקום להתקשר ל-Waze ולבזבז חשמל ולאבד את המגע האנושי, לנו יש סט של נהגי מוניות שאיבדו את העבודה שלהם בגלל Uber - והם פשוט עונים לך בטלפון ומכווינים אותך (“אח שלי קח ימינה, ואז שמאלה”, “אל תקשיב לאין כניסה, זה רק 2 מטרים ותגיד לשוטר שעשית רוורס” וכו’).ככה משתמשים ב Human Learning במקום Machine Learning.אתה מדבר כאן בעצם על פיצ’ר שלא קיים ב - Machine Learning: היכולת לאלתר, למשל לדבר עם שוטר ולהמציא סיפורים. זה ה - Holy Grail של Machine Learning ואתה משיג את זה בדרכים הרבה יותר אפקטיביות עם Human Learning.כן, באנגלית זה נקרא “cutting corners”, לא יודע אם יש לזה מילה בעברית. באמת אין ביטוי כזה (פה לא חותכים - מעגלים…), אבל שווה לבדוק. אנחנו מאוד Strict בישראל ולא חשבנו על זה.מה שכן מאוד חשוב לנו כאן זה העניין של הכשרות - הרבה פעמים יוצא שאני מגיע לאתר ואני לא כל כך בטוח לגבי הכשרות שלו. האם יש בשורות חדשות בנושא לדעתך?אנחנו ישבנו על נתוני תעבורה של אתר שנקרא B&H, מכיר? ודאי שם קניתי את המצלמה הדיגיטלית הראשונה שלי . . .מסתבר שאתה לא לבד . . . הרצנו על זה מודל של Big Data, וגילינו שהם סגורים בשבת וגם עושים המון כסף. זו קורלציה מאוד חזקה, אז אנחנו הולכים לשווק סגירה בשבת גם לאתרים של חילונים וגויים, כדי שיהיו מצליחים גם הם כמו B&H.וזה עובד ממש מעולה - כל בתי הספר ב - Washington DC עכשיו סוגרים את האתר שלהם בשבת.ממילא אין לימודים אז למה צריך אתר? אתה יכול לחסוך כ-20% מהוצאות הקירור, חשמל וכו’, חיסכון אדיר.אם אתה לא צריך לקרר בשבת - ויכול להשתמש בשרתים בתור פלטה של שבת אז אתה ממש במקום טוב.אנחנו מתחילים עכשיו לשווק קיגל מה-Data Centers שלנו - ה - Cloud Kugel, או CK.אלון מתרגש כי בבית סבא היו עושים קיגל . . . בטח זוכר את הקיגל הראשון שהוא עשה על ה Sinclair Spectrum שלו.זה מאוד מעניין - כל האספקט הכלכלי של זה . . . תמיד חשבנו על מנוחת הנפש, אבל יש כאן גם אספקט כלכלי טהור, ונראה שממש תפסת אותו בביצים והשתמשת לטובתך . . .התייחסת קודם לנושא של הצפנות ו-Quantum Computing, וראיתי בטוויטר שלך שזה גם נושא שמעניין אותך, כולל לא מעט בלוגים.לאיפה כל הנושא של הצפנות ו-Quantum Computing הולך לדעתך?במילה אחת? פאקקט. אין הצפנות יותר ב-Quantum Computing, אנחנו פרצנו הכל. אני יודע עכשיו להגיד לך שהארבע ספרות האחרונות של כרטיס האשראי שלך הן 1234, וגם את השם של הכלב הראשון שלך, בוני. והחיה הראשונה שלך הייתה דג זהב.אמור לרדת בעריכה . . . בכל זאת גם לנו יש מגבלות של Security, אבל הרעיון מובן.אם ראית במקרה את הסרט Avengers: End Game, אתה יודע שיש הרבה מקבילים ליקום.אם אני רוצה לפרוץ ב Quantum Computing לסיסמא שלך, אני יכול פשוט לגשת ליקום שבו הסיסמא שלך היא 1234 (כי אתה טמבל שם), ולהביא את האיזור הזה של היקום האחר לפה, וככה אני יודע כאן מה הסיסמא שלך.מדהים. ו -By far לא החלק העלילתי הכי הזוי בסרט.איך זה עובד? יש לזה Docker?ב-Quantum Computing לא קוראים לזה Docker אלא Loop Worm: אלו תולעים מחורי תולעת שמאפשרות לעבור את מהירות האור, אם אתה יודע קצת פיסיקה מודרנית.הקוונטים לא עוברים - ה-Docker הוא לוויתן ויש לו מסננת בגרון, אז הקוונטים לא עוברים.לעומת זאת ב-Loop Worm זה הרבה יותר חזק.ממש מעניין - זה אומר שבכל היקומים המקבילים שבהם אני לא טמבל, אתה לא תצליח לפרוץ?רגע, בודק את כל הסיכויים שזה קרה . . . יש 45 מיליון אפשרויות ורק באחת מהן אתה לא טמבל.זה בהחלט מציג פרספקטיבה חדשה לכל עולם המחשוב, זה לא פחות ממהפכה.

# Podcast S01-E16: Más data breaches - Microsoft y Jeff Bezos Hackeados! - Conducido por @_marKox, @domix ## Revisión de las noticias - [Microsoft data breach exposes 250 million customer service and support records](https://www.grahamcluley.com/microsoft-data-breach/) - [Amazon EKS Price Reduction](https://aws.amazon.com/blogs/aws/eks-price-reduction/) - [Lightbend Telemetry](https://www.lightbend.com/blog/lightbend-telemetry-2.13-released) - [Octarine Adds 2 Open Source Projects To Secure Kubernetes](https://www.linux.com/news/octarine-adds-2-open-source-projects-to-secure-kubernetes/) ## Twitter! - [Jeff Bezos,dueño de Amazon y hombre más rico del mundo hackeado.](https://twitter.com/unsrdebarcelona/status/1220807420278202368) - [SQLite Is Serverless](https://twitter.com/alexellisuk/status/1221355007318151170) - [Thread sobre Microservices VS Monoliths](https://twitter.com/allenholub/status/1220118174739374081) - [CNCF projs are Go & all this OSS used to be Java (Thread)](https://twitter.com/kellabyte/status/1220045189554765825) - [announce Secret Manager - a secure and convenient method for storing API keys, passwords, certificates, and other sensitive data on GCP](https://twitter.com/sethvargo/status/1220035296018018310) - [Cornelia Davis the new WeaveWorks CTO](https://twitter.com/cdavisafc/status/1220017566267203585) - [I hope SMI gets adopted into CNCF](https://twitter.com/ibuildthecloud/status/1219688502276677632) - [¿Por qué es tan fácil escalar con Elixir?](https://twitter.com/commitconf/status/1210560970877100037) - [Conway Law por el mismisimo Werner Vogels](https://twitter.com/werner/status/1207993978223841280) - [Vagrant cumple 10 años!](https://twitter.com/mitchellh/status/1219656867783139329) ## Referencias y Recursos - [Kubernetes made my latency 10x higher](https://srvaroa.github.io/kubernetes/migration/latency/dns/java/aws/microservices/2019/10/22/kubernetes-added-a-0-to-my-latency.html) - [Scaling Kubernetes Monitoring without Blind Spots or Operations Burden](https://www.influxdata.com/blog/scaling-kubernetes-monitoring-without-blind-spots-or-operations-burden/?utm_source=twitter&utm_medium=social) - [The Service Mesh Era: Architecting, Securing and Managing Microservices with Istio](https://inthecloud.withgoogle.com/ebook-19/service-mesh-era-architecting-securing-and-managing-microsecives-with-istio.html) - [Building containers without Docker](https://blog.alexellis.io/building-containers-without-docker/) - [Is Your Kubernetes Cluster Healthy? Here are 5 Ways to Find Out](https://thenewstack.io/is-your-kubernetes-cluster-healthy-here-are-5-ways-to-find-out/) - [WhitePaper - Elements of Scheduling](https://arxiv.org/abs/2001.06005) - [3 reasons why your Big Bang legacy replacement will most likely fail miserably!](https://blog.trifork.com/2019/02/20/3-reasons-why-your-big-bang-legacy-replacement-will-most-likely-fail-miserably/) ## Repos chingones de código - [Kiam](https://github.com/uswitch/kiam) - [Permission Manager](https://github.com/sighupio/permission-manager) - [inlets-operator](https://github.com/inlets/inlets-operator)

An airhacks.fm conversation with Bela Ban belaban.blogspot.com about: C64 wasn't real, Atari was the way to go, Atari ST vs. Amiga wars, Pascal, Modula-2 and Modula 3, Atari had a nice IDE with 1MB RAM, War Games movie, contact list application as "hello, world", fixing Epson printer hexcodes, chess and tennis over programming, learning C was a step down from Modula, system programming and the fascination with immediate feedback, writing CORBA to CMIP bridges in GDMO, C++ templates are an own language, "C++ is crap", Java at the first World Wide Web conference in 1995 in ...Darmstadt, starting with oak, applets and NCSA Mosaic, Netscape server, extracting data from mainsframes with Java over JNI, Cornell University research with Sun's Java 1.0, working with Ken Birman, Robbert van Renesse, Werner Vogels, Ensemble in Ocaml, replacing Ocaml with Java the "Java Groups", Jim Waldo was leading the JINI project, Sun Microsystems and Cornell worked together to make Java Intelligent Network Infrastructure (JINI) reliable using Java Groups, leasing JINI was revolutionary, JINI message was changed several times, there was no elevator pitch for JINI, Sun tried to keep the JINI / Java Groups cooperation secret, A Note on Distributed computing by Jim Waldo, the Eight Fallacies of Distributed Computing, JGroups on Sourceforge in 2000 (and still on available), revival of JGroups at Fujitsus's Network Management System, the Sacha Labourey and Marc Fleury contact, writing JBoss Cache on unpaid vacation in 6 weeks, the Blue and Red Papers from Mark Fleury, the EJB Open Source System, Mark Fleury and paratroopers, JBoss Cache started as tree and became a distributed map, meeting Manik Surtani in a Taxi, JBoss Cache became Infinispan, JGroups is the communication layer of Infinispan, the CP of CAP interests resulted in RAFT, JGroups RAFT is used in production, there are many Paxos implementations Raff is a Paxos simplification, RAFT for kids in JBoss Distributed Singletons, useless but consistent systems, vector clocks is an inconvenient reconciliation system, JGroups is using RocksDB and MapDB, JGroups makes UDP and other protocols like RDMA reliable, JGroups is particularly efficient with many nodes, JGroups and Sun Cluster Lab in Switzerland, running JGroups on 2000+ nodes at Gcloud, Project Loom and Fibers, mini sabaticals for hype chasing, back to easy request response to Project Java's Loom and Fibers, injecting JChannel in Quarkus, JGroups runs on Quarkus in native mode, KISS and JGroups - No Dependencies in JGroups, Bela's blog: belaban.blogspot.com

Support Mobycast-> https://glow.fm/mobycast

Werner Vogels, CTO of Amazon.com, delivers his AWS re:Invent 2019 keynote. Watch as pulls back the covers to talk about the innovations behind AWS Nitro, Firecracker, AWS Fargate, Amazon EBS and more. This year's featured guests include Clare Liguori, Principal Software Engineer at AWS - who goes deep on AWS Fargate and how we've built this to give customers a truly unique customer experience – as well as Jeff Dowds, IT Executive at Vanguard, Sebastien de Halleux, COO of Saildrone and Dr. Martin Hofmann, Group CIO of Volkswagen automotive group.In this keynote you'll also hear more about the launch of the Amazon Builders' Library: https://aws.amazon.com/builders-library/And Werner's video series, 'Now Go Build': https://aws.amazon.com/startups/NowGoBuild/01:10:26 A special thanks for the satellite imagery provided by AWS customer Maxar: https://bit.ly/33VJG8i

In this episode of AWS TechChat we cover the Thursday keynote of re:Invent 2019 by Dr Werner Vogels, CTO of Amazon. We start the show introducing Amazon Nitro System, look at it from a software lens and share with you the why and how we built this. As virtualization is at the core of the AWS Cloud we went back to the drawing board and built our own hypervisor to provide performance almost in-distinguishable of bare metal whilst providing a security demarcation for our platform. Nitro has allowed us to innovate faster, we have released 4x more instances since we have moved to Nitro. We then take a refresher and look at Firecracker. You can launch lightweight micro-virtual machines (microVMs) in non-virtualized environments in a fraction of a second. Given we use Firecracker under the hood for AWS Lambda and AWS Fargate, it provides faster, tighter more seamless scaling than other platforms such as Amazon Elastic Compute Cloud (EC2), Amazon Elastic Container Service (ECS) and Amazon Elastic Kubernetes Service (EKS). To wrap up the show, we touch on the importance of “evolvable architectures” looking through the lens of Amazon Simple Storage Service (S3) before introducing you to Amazon Builders’ Library that has papers and topics on how Amazon builds our own distributed systems. Speakers: Shane Baldacchino - Solutions Architect, ANZ, AWS Gabe Hollombe, Senior Technical Evangelist, AWS Resources: AWS Nitro System https://aws.amazon.com/ec2/nitro/ AWS Nitro Enclaves https://aws.amazon.com/ec2/nitro/nitro-enclaves/ Firecracker – Lightweight Virtualization for Serverless Computing https://aws.amazon.com/blogs/aws/firecracker-lightweight-virtualization-for-serverless-computing/ Amazon EKS on AWS Fargate Now Generally Available https://aws.amazon.com/blogs/aws/amazon-eks-on-aws-fargate-now-generally-available/ Shuffle Sharding: Massive and Magical Fault Isolation https://aws.amazon.com/blogs/architecture/shuffle-sharding-massive-and-magical-fault-isolation/ The Amazon Builders' Library https://aws.amazon.com/builders-library/ AWS Events: AWS Builders Online Series https://aws.amazon.com/events/builders-online-series/ AWS Modern Application Development on-demand https://aws.amazon.com/events/application/modern-app-development/ AWS Innovate on-demand https://aws.amazon.com/events/aws-innovate/ AWS Events and Webinars https://aws.amazon.com/events/

פודקאסט מספר 376 של רברס עם פלטפורמה - אורי ורן מארחים בכרכור (עדיין חם, עדיין אוגוסט, עדיין חופש גדול, עדיין מטפסים על הקירות עד החופש בספטמבר) את רם רחום לשיחה על (בעיקר) פרויקט פופולארי בשם PySnooper (כן, זה קשור ל Python), וגם על צבים בערב הסעודית, דגים ועל לחשוב כמו ילדים (לא בהכרח קשור ל Python).רם -אנשים בעיקר מכירים אותי כמתכנת Python, עבדתי בכל מיני חברות שונות ותמיד הקפדתי לעבוד עם Python - להיכנס מאוד לעומק ולהכיר את השפהפעיל בקהילת הקוד הפתוח - מארגן כנס (Meetup) שנקרא PyWeb-IL - מתעסק ב Python וב - Web ועוד כל מיני נושאים (נפגשים פעם בחודשיים בתל אביב).הגרסא הגדולה של זה היא PyCon . . . מתכנת מאז שאני ילד, עברתי בתעשייה בכל מיני חברות - גם כפרילאנסר וגם בחברות גדולות יותר, כבר 10 שניםבהתחלה הייתי עובד יותר מהבית (סטארטאפים וכל מיני כאלה)לפני כ-4 שנים התחלתי לעבוד בחברה גדולה (סטארטאפ ישראלי שנקנה ע”י אחת החברות הגדולות - Google it אם ממש בא לכם לבדוק) - זו הייתה “החברה הגדולה הראשונה שלי”סיימתי שם לפני כמה חודשים ומאז עשיתי כל מיני עבודות Freelance והדרכות - ועכשיו התחלתי לעבוד ב - BlueVine - חברת FinTech בתל אביב.שתי מילים על BlueVine אז BlueVine עוסקת במתן הלוואות לעסקים באמריקה (ארה”ב) - עסקים קטנים מבקשים הלוואה וצריך מישהו שיעריך את הסיכון, סיכוי להחזר הלוואה ובהתאם - איזו ריבית אפשר להציע להםומי הלקוחות - בנקים או מלווים שונים?יש כל מיני 3rd-parties שמציעים את ההלוואת בשם BlueVineמה שהפתיע אותי (לעומת מה שחשבתי כשבאתי להתראיין, שזה בגדול שנותנים שירות לאיזשהו בנק) זה ש-BlueVine זה הבנק - עשו Debt Financing, יש “כמות עצומה של כסף” ונותנים את ההלוואות מהכסף של החברה (של המשקיעים). בגדול - אני עובד בבנק.יש לא מעט חברות Fin-Tech בסגנון - מגייסות קרן אחת “אופרטיבית” וקרן נוספת שהיא, ובכן - “הקרן” (המשקיעה)יש מודל דומה(?) ב - Lemonade למשל, זה מודל שהוא יחסית מקובל.אז אנחנו מניחים שעל מנת לתת הלוואת בחוכמה צריך הרבה Data - וצריך לדעת איך לנתח אותו, אז בטח משתמשים ב  -Python גם שם.שנייה לפני - האם זה באמת “הרבה דאטה”? יש הרבה מאוד עסקים קטנים אבל זה עדיין . . .לא מכיר עד הסוף את החברה עדיין, לא יודעמה שכן אני יודע - אנחנו מגייסים!בפיתוח, QA, פרודקט, Data Science, ועודרוצים לעזור לרם להרוויח מענק חבר-מביא-חבר? תהיו חברים :-). אפשר לשלוח קו”ח ל-ram@rachum.comהחברה ממוקמת בתל אביב, בניין אלון 1 (על רחוב יגאל אלון)ולסיפור העיקרי - לפני חודשיים-שלושה הוצאת כלי Open Source שהגיע להיות מספר 1 גם ב - GitHub Tending וגם ב - Hacker News - שזה משהו שלא קורה הרבה, חייבים להגיד: די נדיר שכלי מגיע להיות מספר 1 בשני המקומות, ובטח שאין הרבה ישראלים שלהם זה קרה.בוא תעביר אותנו סביב הסיפור וסביב החוויה - מה זה הכלי הזה? איך היה לך כזה “פוקס”? :-)“חצי מזה זה באמת מזל”  . . . ב-10 שנים שבהן אני מפתח (כמקצוע) עשיתי הרבה פעמים פרוייקטים בקוד פתוח (אפשר לראות אסופה של פרוייקטים שעשיתי בפרופיל שלי בגיטהאב) - ורובם לא הגיעו לשום מקום.היה עוד אחד שהגיע למשהו מרשים - PythonTurtle - נדבר עליו אחר כך.ועכשיו ל PySnooper - מה הוא נותן?אני מאוד אוהב להשתמש ב - Debuggers. כשאתה מתכנת - בחצי מהזמן אתה בכלל מנסה להבין מה הקוד עושה לעומת מה שהוא אמור היה (לדעתך) לעשות - נראה שהוא אמור לעשות את “הדבר הנכון” אבל במקום זה יש Bug ואתה רוצה להבין מה קורה שם.אני מתכנת מאז שאני ילד, ותמיד נראה לי הגיוני להשתמש ב - Debugger: אתה מוסיף Break Point באיזו שורה, והקוד עוצר שם - ואתה יכול לשאול מה קורה שם (מה הערך של המשתנים, להריץ פונקציה וכו’). זה כלי שאני רואה אותו כחלק אינטגלי מתכנות.ואז התחלתי לעבוד בתעשייה - וראיתי שאנשים פשוט לא משתמשים ב - Debugger . . . זה מאוד הפתיע אותי - מתכנתים מקצועיים, שמקבלים הרבה כסף (!) ועובדים על דברים מאוד חשובים (!!), פשוט “תוקעים שורות Print” כשהם רוצים לדעת מה קורה, ואין להם את היכולת “לעשות Pause” בנקודה כלשהי, פשוט כאשר רוצים לדעת מה הערך של משתנה בנקודה מסויימת הם מוסיפים Print ולאחר מכן קוראים את הלוג.אז הקושי שראית הוא שבמקום לפתוח Debugger פשוט מוסיפים פקודות Print . . . אבל Debuggers זה משהו שיש (קיים), אז למה זה קורה?בוא נגיד שאתה עובד בבית על הפרויקט החמוד שלך - אתה כן פותח את ה - Debugger, יוצר קובץ, כותב קוד, Break-points וכו’ - אבל אתה בדר”כ לא בבית אלא בחברה, והקוד לא רץ על המכונה שלך אלא על איזשהו שרת חיצוני או ב - Docker או Vagrant או כל Setup מורכב אחר - ומסובך לחבר את ה - Debugger שלך לזה . . .ה - Debugger הוא כלי אינטראקטיבי, שצריך “לתקשר עם הקוד” - מתי לעצור, מתי להמשיך, מתי אני רוצה משהו אחר - צריך לקנפג אותו, ורוב האנשים לא עושים את העבודה הזו.זה די טכני, ואולי זה סוג של קוצר-רואי אבל עדיין לא עושים את זה - מבזבזים כל כך הרבה זמן כי לא רוצים להשקיע את המאמץ בלקנפג את זה, ומשתמשים בשיטה “החוראנית”.אז אמרתי - “אוקיי, בוא נראה אם אני יכול לעשות משהו שהוא “חוראני+” - משהו באמצע שבין השיטה החוראנית לבין Debugger.משהו שיותר “מפנק” מה - Prints ,אבל שלא צריך לקנפג - כי שיטת ה Prints מאוד מתסכלת: צריך להחליט איפה לשים את ה - Print בקוד ולהחליט מה אתה רוצה לראות מראש - ואז צריך לעשות Build (שלוקח זמן), ואחרי שאתה רואה את הפלט עדיין צריך לנחש ממנו מה קרה, ולפעמים להבין שאולי צריך לשים את ה - Print  במקום אחר או להראות משתנה אחר - Back & Forth נוראי (הנה אחד לא נוראי).מה שעשיתי זה פרויקט בשם PySnooper - מוסיף Decorator לפונקציה, שורה בקוד שאומרת ל-Python “שים לב! בפונקציה הזו על כל שורה שרצה תכתוב ללוג שעכשיו השורה הזו רצה, המשתנה X=7 והמשתנה y=14” וכו’ - מעיין לוג אוטומטי של כל מה שקרה בפונקציה, קצת כמו לשים אוטומטית שורות Print בכל מקום.ולגבי Decorator ב-Python למי שלא מכיר -  זו בעצם “פונקציה שעוטפת פונקציה”האמת שאני לא חושב על זה ככה (אני גם מלמד Python, אז יש לי הרבה ניסיון בלהסביר לאנשים מה זה) - אני חושב על זה יותר כעל דרך “לשפצר” פונקציה: מעיין שורת הדרכה שאתה מוסיף ואומרת ל-Python “שים לב - תן לפונקציה הזו טיפול מיוחד, כמו שאני מבקש”.ברמה הסמנטית זה בא “לעטר” את הפונקציה (“לעשות לה Decorate”, לא כזה); ברמה הטכנית זה ממש פונקציה שעוטפת פונקציה, ויכולה לקבל אותה כרפרנס ולהריץ אותו - וזה מה שמאפשר לעשות את כל הדברים האלה.זה לא יוצר לוג ענק?כן . . . זאת אומרת - תלוי כמה שורות יש בפונקציה: זה עובר רק על הפונקציה “שעיטרת”.רן שמע בבוקר פודקאסטים על תנ”ך אז צפי לעוד כמה מושגים בהמשך (או ל-Follow up ב-1 באפריל על המשך עלילות Werner Vogels והחזרה בתשובה).אתה רואה שורות לוג רק על הקוד שבפונקציה “שעיטרת” - אם הפונקציה הזו קראה לפונקציה אחרת, לא תראה שורות לוג עליה (אלא אם תשתמש ב Argument הידוע Depth = 2 …)ואם הפונקציה שלי גדולה, ויש בה כמה לולאות . . .אתה עלול לראות כמה אלפי שורות קוד ב - Log.אוקיי - אז יש לך מלא לוגים. מה אתה עושה עם כל הטוב הזה?

„Wird das was?“ Diese Frage stellen sich Nutzerinnen und Nutzer ja bei vielen digitalen Entwicklungen. Plötzlich reden alle über irgendein technologisches Thema im Alltag, und eigentlich weiß man gar nicht so genau, was das soll oder dahintersteckt. Zeit, darüber zu reden. Genau das machen wir bei ZEIT ONLINE alle zwei Wochen in unserem Digitalpodcast. In der fünften Folge spricht Kulturredakteur Dirk Peitz mit dem Amazon-Technikchef Werner Vogels vor allem über die Cloud – das heißt die IT-Dienste, welche die Amazon-Tochterfirma AWS anderen Unternehmen anbietet. Denn was viele Menschen nicht wissen: Egal worauf sie im Netz klicken, die Wahrscheinlichkeit ist relativ hoch, dass sie dadurch einen Server von Amazon Web Services (eben AWS) anwerfen. So lagern etwa alle Filme und Serien, die auf der Streaming-Plattform Netflix verfügbar sind, auf AWS-Rechnern. Ebenso läuft das Videospiel „Fortnite“ über das Cloud-Computing von Amazon, und wenn man auf der Website von Zalando ein neues T-Shirt bestellt, geschieht das ebenfalls über AWS. Was bedeutet es, wenn derart viele verschiedene Online-Dienste keine eigene IT-Infrastruktur besitzen, sondern die Rechenkapazitäten eines einzigen Cloud-Anbieters wie AWS nutzen, der in dem Bereich Weltmarktführer ist? Sind unsere Daten dort wirklich sicher, auch sicher voneinander getrennt? Und wirft Amazon wirklich keinen Blick auf all das, was da in den AWS-Rechenzentren überall auf der Welt gespeichert ist und dort prozessiert wird? Nein, sagt Werner Vogels, der Chief Technology Officer (CTO) von Amazon. Vogels arbeitet seit 2004 bei dem Tech-Konzern und ist der Schöpfer dessen Cloud-Dienstes. Ein Hinweis noch: Das Interview mit dem Niederländer Vogels wurde auf Englisch geführt. Wir hoffen, dass das Gespräch dennoch für die meisten Zuhörerinnen und Zuhörer gut verständlich ist.

In this Special episode Alex and Sai host two AWS Specialist Architects at Rackspace Steve Drew and Malcolm North and Dan White, special guest from AWS Architect team. Tune in find out what happened at the biggest AWS event of the year, apart from new announcements, you will also find out what happened in Vegas and what was on the menu! Show notes links: 1. Racker Blockchain Intro at AWSUG UK - https://www.youtube.com/watch?v=f99TwDZUG0A 2. AWS re:Invent 2018 - Keynote with Werner Vogels -https://www.youtube.com/watch?v=femopq3JWJg

Watch Werner Vogels deliver his AWS re:Invent 2018 keynote. Learn more about AWS at https://amzn.to/2FKc7zk. This year's keynote includes featured guests, Yuri Misnik, Executive General Manager, National Australia Bank (NAB), Ethan Kaplan, Chief Product Officer, Fender Musical Instruments, Mai Lan Tomsen Bukovec, AWS VP + General Manager of S3, and Holly Mesrobian, Director of Engineering, AWS Lambda. In the keynote, hear about new AWS launch announcements and get a preview of Werner's new video series, "Now Go Build" - https://youtu.be/a42kxHSX4Xw. Keynote speakers: 00:00:00 Dr Werner Vogels, Amazon CTO 00:32:30 Mai Lan Tomsen Bukovec, AWS VP + General Manager of S3 00:50:30 Ethan Kaplan, Chief Product Officer, Fender Musical Instruments 01:02:50 Holly Mesrobian, Director of Engineering, AWS Lambda. 01:33:10 Yuri Misnik, Executive General Manager, National Australia Bank (NAB) New AWS launch announcements: 01:15:20 AWS Tool Kits for popular IDEs 01:17:00 Custom Runtimes for Lambda 01:18:50 Lambda Layers 01:20:40 Nested Applications using Serverless Application Repository 01:23:10 Step Functions service integrations 01:24:25 WebSocket support for API Gateway 01:47:15 AWS Well - Architected Tool

Werner Vogels, CTO of Amazon, joins YC Software Engineer Kyle Corbitt to share his experience and insights on technology and startups.Video LinkVideo Transcript

IBM is buying Red Hat. Topic acquired. Sponsored by DataDog This episode is sponsored by Datadog and this week Datadog wants you to know about Watchdog. Watchdog automatically detects performance problems in your applications without any manual setup or configuration. By continuously examining application performance data, it identifies anomalies, like a sudden spike in hit rate, that could otherwise have remained invisible. Once an anomaly is detected, Watchdog provides you with all the relevant information you need to get to the root cause faster, such as stack traces, error messages, and related issues from the same timeframe. Sign up for a free trial (https://www.datadog.com/softwaredefinedtalk) today at https://www.datadog.com/softwaredefinedtalk and tell them your friends at Software Defined Talk sent you. IBM and Red Hat Acquisition IBM Nears Deal to Acquire Software Maker Red Hat (https://www.bloomberg.com/news/articles/2018-10-28/ibm-is-said-to-near-deal-to-acquire-software-maker-red-hat) IBM To Acquire Red Hat, Completely Changing The Cloud Landscape And Becoming World's #1 Hybrid Cloud Provider (https://newsroom.ibm.com/2018-10-28-IBM-To-Acquire-Red-Hat-Completely-Changing-The-Cloud-Landscape-And-Becoming-Worlds-1-Hybrid-Cloud-Provider) Banks could reap as much as $115 million for orchestrating the IBM-Red Hat deal (https://www.thisisinsider.com/ibm-red-hat-largest-software-bank-fees-2018-10) Cloud Wars Forcing Irrational Open Source Takeovers (https://medium.com/futuresin/cloud-wars-forcing-irrational-open-source-takeovers-1ce096c53b19) Red Hat and IBM: Elephants Can Dance (https://www.aniszczyk.org/2018/10/29/red-hat-and-ibm-elephants-can-dance/) Armed with Red Hat, IBM launches a cloud war against Amazon, Microsoft and Google | ZDNet (https://www.zdnet.com/article/armed-with-red-hat-ibm-launches-a-cloud-war-against-amazon-microsoft-and-google/) Analysis: Red Hat’s continued independence is key to success of IBM’s $34B acquisition (https://www.geekwire.com/2018/analysis-red-hats-continued-independence-key-success-ibms-34b-acquisition/) IBM Acquires Red Hat — What This Means for Open Source (https://blog.usejournal.com/ibm-acquires-red-hat-what-this-means-for-open-source-d236d680da5b) Statement on the IBM acquisition of Red Hat from Ubuntu (https://blog.ubuntu.com/2018/10/30/statement-on-ibm-acquisition-of-red-hat) Big Blue Puts on a Red Hat: IBM Acquires Red Hat (https://redmonk.com/sogrady/2018/10/30/ibm-red-hat/) Big Blue’s takeover of Red Hat could produce an über-cloud (https://www.economist.com/business/2018/10/30/big-blues-takeover-of-red-hat-could-produce-an-uber-cloud) Blockbuster IBM-Red Hat Deal Draws Support – and Concerns for the ‘Spirit of Linux’ (https://www.enterprisetech.com/2018/10/29/blockbuster-ibm-red-hat-deal-draws-support-and-concerns-about-the-spirit-of-linux/?utm_source=rss&utm_medium=rss&utm_campaign=blockbuster-ibm-red-hat-deal-draws-support-and-concerns-about-the-spirit-of-linux) “I like the ones where you prepare.” (Coté ed.) Look, Red Hat and IBM are Pivotal competitors, good ones: we wish them success in this complex integration, it’s good they’re finally trying to fix their cloud portfolio, we’re hiring, etc., etc.. Let’s take it for mature-granted that we’d prefer enterprises be Pivotal customers than IBM/Red Hat customers. Now, let’s put that aside. This is an exquisite slide from their deck (https://www.ibm.com/investor/att/pdf/IBM-RED-HAT-Charts-10-2018.pdf): https://d2mxuefqeaa7sj.cloudfront.net/s_F8186D6801E202DEB03199A6D1F610BAB9CB91A2CFD988A2666F991EBC2E6CC0_1541067546607_image.png Easily the best corporate deck slide of 2018. First, this is a bold, good move. Acquiring Red Hat has always been a hill too high and it’s kind of mind-blowing that someone actually did it. The valuation here is sort of besides the point of anything impressive. In contrast, the GitHub valuation was impressive because GitHub is a one product company (please don’t email me about “community” as a separate product - sure thing, I agree). Red Hat is kind of everything IBM has missing…except public cloud. To be, I guess, contrarian and annoyingly not Pivotal-biased, I think it’ll be hard for IBM to fuck this up. On that last point, Ben Thompson (https://stratechery.com/2018/ibms-old-playbook/): “The company has spent the years since then claiming it is committed to catching up in the public cloud, but the truth is that Palmisano sealed the company’s cloud fate when he failed to invest a decade ago; indeed, one of the most important takeaways from the Red Hat acquisition is the admission that IBM’s public cloud efforts are effectively dead.” In other word, IBM is too late to catch-up to public cloud co.’s, it’d need to spend lots of capex to get close. Related, sick nerd burn: “Meanwhile, [IBM’s] aforementioned commitment to the cloud has mostly been an accounting fiction derived from re-classifying existing businesses” Fixing IBM’s cloud business. What was wrong in the first place? Things Red Hat has: RHEL revenue, JBoss developer presence, product/developer know-how, support know-how, OSS good-will, OpenShift as a k8s distribution: RHEL & IBM has a foot-print in most all enterprise stacks, but not public cloud(?) IBM knows how to eek out OS revenue, so does Red Hat. JBoss + WebSphere. At some point, IBM had a huge developer community. They likely do among enterprise developers (but even there, it’s been fading). Red Hat has developers - I assume. People do like kubernetes. The know-how and good will are interesting - added to IBM’s OSS equivalent (they still have that?) you have, potentially, the biggest OSS people around…? I’m not sure which standards bodies this allows them more control over, no which projects. Google and Microsoft are contenders here too. “Lock-in”: From the press release: “research shows that 80 percent of business workloads have yet to move to the cloud, held back by the proprietary nature of today’s cloud market.” (No citation provided. I will assume it’s from the Anonymous Galactic Research Board Whose IP Licensing Policy Prohibits Your From Citing Us By Name Because We Prefer to Peacefully Float In Space Like Those Rasta Dudes in William Gibson Books But The Good Early Ones Not The Weird In The Present Ones Except For the Blue Color of Bigend’s Suit Which Was Actually Pretty Cool - But Cuban Parkour Ninja Cults? Boy.) See also: Turns out Pareto was some kind of every single study ever genius. Shut it down, boys, turns out every survey result ends up in an 80/20 split. As ever, this topic vexes me. I take lock-in to mean: I don’t want to keep paying this rent-seeker, aka, “maintenance contracts - AMIRIGHT?.” I’m just interested in paying less. If you gave me a closed source offering that was free, I’d be just as happy. I don’t want to get trapped in an aging stack that isn’t evolving (e.g., I want to use node.js on UNIVACs, or something), so I need “the freedom to leave” to get the benefits of new technologies. I like having the source code for transparency, to make my own forks, and/or because rainbows and sandals. Like, seriously, what options do you have to move to? DIY stack - you’re going to take the IBM/Red Hat stack and run it all on your own, merging in new releases and patches, even forking and evolving it yourself. Will all the IBM stuff be available? What if you run on VMware or Azure or Softlayer? How do you rebuild that entire stack? So you just want to rebuild a little bit of it? If you throw OpenStack with KVM in there, plus whatever SDN and storage stuff you could get in open source, throw in some OSS network routing…you could get away with the only proprietary thing being chips and other rando hardware things. You’ll need some bare-metel BIOS/firmware update things. Begged question: how far (and up!) the stack do you want to be un-proprietary? Only use OSS Android on jail-broken phones? No iPhones, clearly, and toss out Safari, macOS, and Windows - maybe you can cruise in with some HTML5 stuff through Firefox and Chrome on the desktop and mobile, then on some Eclipse for GUIs? AWS, Azure, Google Cloud, AzureStack, Pivotal ready stack with VMware - perhaps you could take the thin k8s and PaaS layer from the Red Hat IBM stack and move it to those clouds? Will that work? Is it better, economically and innovation roadmap-ally than just sticking with IBM/Red Hat Alibaba and the other non-Western clouds. Same. MSPs like Rackspace. Maybe - the Rackspace people could just run whatever you want. See concerns of #1, plus the premium paid for “fanatical.” Maybe Rackspace has some SRE magic that allows them to do what you’d be doing at 80% of the cost, or something. I don’t understand this reasoning. How is IBM + Red Hat lack of “proprietary nature”? If I’m running an IBM/RedHat stack, can I just move off all my workloads over night, paying nothing to move and then run my workloads, like, perfectly? If I’m running on that stack, and then I want to move to Google Cloud, does that work? Where-else would I go? Can I just take my pods and throw them onto Azure? Also, if any of these are practically true - it’s a shitty business for IBM/Red Hat to be in, at least a huge risk for them to carry. Any time a customer cashes in on freedom to leave, that’s lost revenue to IBM/Red Hat. My point is: I wish we’d stop talking about lock-in and focus on more practical matters, namely, does the technology work, does it work in a good ecosystem/community (I can find and make it work with other stuff), does it evolve/innovate at a pace I like, and am I happy with the initial and ongoing costs. If the answer to all of those is yes, I don’t think people care about OSS versus closed. But what do I know, I don’t know such stuff, I just do slides. What really matters is getting the two sales forces to sell each other’s stuff, esp. accelerating OpenShift. The IBM sales force has to sell moving away from their traditional offerings (WebSphere, 3 tier, etc.) and instead sell modernizing to OpenShift. That’s fine, but a lot to ask. Also, the comp. plans might get dicey. Part of the point of modernizing is to reduce costs, implying a lower up-front deal-size and smaller ongoing deal-size. So, you’re asking the IBM rep to sell cheaper products, potentially. And if you’re not, see lock-in screed above on pricing. There’s not much upside to sales people here, aside from maybe holding onto an eroding market, but that’s years out, sales people are short-term focused by design. Red Hat sales people might fare better because they’re used to that deal size and can sell more; however, IBM sales people will resist these Red Hat people getting into their account and snatching their paper. All of this is not a killer, but likely the bulk of work that needs to be nailed to synergize maximally (my favorite type of synergizing). Brandon’s winners/looses, also O’Grady’s (https://redmonk.com/sogrady/2018/10/30/ibm-red-hat/). Cloud Earnings Amazon says AWS revenue jumped 46 percent in third quarter (https://www.cnbc.com/2018/10/25/aws-q3-results.html) Microsoft’s commercial cloud revenue jumped 47 percent in its fiscal Q1, but Azure growth slows (https://www.geekwire.com/2018/microsofts-commercial-cloud-revenue-jumped-47-percent-fiscal-q1-azure-growth-slows/) Google Cloud Revenue Boosts Alphabet’s Earnings - SDxCentral (https://www.sdxcentral.com/articles/news/google-cloud-revenue-boosts-alphabets-earnings-but-wall-streets-not-impressed/2018/10/) Relevant to your interests Oracle Open World 2018: CEO Mark Hurd says SAP ERP customers will defect (https://www.computerweekly.com/news/252451138/Oracle-Open-World-2018-CEO-Mark-Hurd-says-SAP-ERP-customers-will-defect) Atlassian reimagines Jira to herd cats, a.k.a. developer teams (https://diginomica.com/2018/10/24/atlassian-reimagines-jira-herd-cats-developer-teams/amp/) Serverless Architecture Market Size, Share & Trends Analysis (https://www.researchandmarkets.com/reports/4661572/serverless-architecture-market-size-share-and) Werner Vogels responds to CNBC story about Amazon Outage (https://twitter.com/Werner/status/1054901529478459392) Conferences, et. al. Nov 3rd to Nov 12th - SpringOne Tour (https://springonetour.io/) - all over the earth! Coté will be MC’ing Beijing Nov 3rd, Seoul Nov 8th, Tokyo Nov 6th, and Singapore Nov 12th (https://springonetour.io/2018/singapore). Nov 14th to 16th - Devoxx Belgium (https://devoxx.be/), Antwerp. Coté’s presenting on enterprise architecture (https://dvbe18.confinabox.com/talk/ASN-9274/Rethinking_enterprise_architecture_for_DevOps,_agile,_&_cloud_native_organizations). Dec 12th and 13th - SpringTour Toronto (http://springonetour.io/2018/toronto), Coté. Listener Feedback Jon from the UK said he got a new work laptop and needed some new stickers so we sent him some. SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you a sticker. Brandon built the Quick Concall iPhone App (https://itunes.apple.com/us/app/quick-concall/id1399948033?mt=8) and he wants you to buy it for $0.99. Recommendations Matt: The Dark Forest (https://www.amazon.com/Dark-Forest-Remembrance-Earths-Past-ebook/dp/B00R13OYU6/). Brandon: Frontline: The Facebook Dilemma (https://www.pbs.org/wgbh/frontline/) The Daily 10/31 — The Business of Internet Outrage (https://www.nytimes.com/2018/10/31/podcasts/the-daily/mad-world-news-facebook-internet-anger.html) Coté: Trick-or-treating in Amsterdam. Notablity still good.

The startup story behind the simple, powerful, event software that has sold over €300M worth of tickets sold online by thousands of organisers around the world. What do tech-savvy conferences around the globe including Web Summit, JSConf, Twilio, Shopify and Strange Loop have in common? The all leverage the clever event management software from Tito.io, a small 10-person, Dublin (Ireland) startup you’ve likely never heard of. What’s even more interesting is that Tito is on track to process more than half a billion in event ticket sales by 2019. The company has also caught the eye and the angel funding of Amazon CTO, Werner Vogels and Intercom Co-Founder, Des Traynor. The secret to the company’s success to date? The confidence of event planners coupled with an intense focus on building a great product, creating a great customer experience, and instilling trust within each and every customer. In a marketplace that’s rife with vendors foisting surprise fees, cumbersome registration, poor UIs and third-party tracking on users, Tito provides a fast, beautiful, transparent & trusted, online ticket experience that’s fully hosted or embedded on a customer’s site in just a few lines of code. Tito’s features have already powered thousands of successful events worldwide. On today's tech podcast I chat with co-founder Paul Campbell who discusses how Tito has created a growth juggernaut in a marketplace where the headlines are dominated by large competitors including Eventbrite and Bizzabo. Other topics we address that inspire event organizers to use Tito include: If you focus on building a great product that customers want to pay for, it can work out - well. if you have a strict data privacy policy and a simple checkout UX - it can work out really, really well for an event management startup. If you respect your customer and do not “growth hack” them, they’ll naturally support you and champion you in the marketplace. Your customers’ customers’ email addresses are precious and need to be treated as such. Respect your customer’s wishes and never email market to their customers...and the market will come to you.  

The digital revolution has already hit our homes - with almost every type of device having a 'smart' alternative available now. So if you're one of the early adopters, how much of that tech in your house will be sticking around - and how much will be abandoned?  In this episode we speak to the companies battling for control of our homes - including Samsung, Philips and Amazon. Amazon's Chief Technology Officer strongly makes the case for voice, but admits voice-controlled devices won't control everything and will only form part of the mix.  We'll also hear how technology is changing how our houses are built - and whether advancements can help solve the housing crisis. Do you really need windows is flatscreen panels can easily switch between glorious vistas all around the world and provide us with natural spectrum light? 

The future is here and it's called AWS.   I decided to attend the AWS Summit in San Francisco this week on a whim -- I am not a developer and have no intention of becoming one but as a small biz owner and leadership specialist, I believe it's important that everyone has a basic level of understanding around what this mega company known as Amazon is up to.   Long story short:    Mind. Blown. AWS stands for Amazon Web Services and it is true to its namesake. I had the chance to listen to Werner Vogels, Amazon dot com's CTO and Vice president speak about big things happening with AWS and my mind is still reeling from what I learned. In today's audible, you will hear me share 10 leadership lessons I learned from going to this summit. I recorded those lessons on my iPhone in my hotel room right after getting back from the event. You will hear that I sound a bit fatigued after a full day at the Summit, but also A LOT of excitement about what's happening with this company. If there's one thing I can stress here it's that AWS is laying the groundwork to change the way companies function. Cloud computing is here and we are just at the early stages of what's possible. As a futurist, as a business woman, as a podcaster, as a writer... what AWS is doing thrills me even if I don't understand most of the technical jargon! I hope my takeaways give you something to think about and use as you continue your journey. Enjoy today's Audible, Team PYP! Let me know what you liked. Connect with me on social media and use the hashtag #pyp ! Twitter   LinkedIn Instagram Facebook   PYP Leadership Academy

Watch Werner Vogels deliver his AWS re:Invent 2017 keynote, featuring the launch of Alexa for Business, AWS Cloud9, new AWS Lambda features, and Serverless App Repository.

CTO Werner Vogels discusses the latest AWS news and announcements.

Dr Werner Vogels, VP & CTO of Amazon.com, spent some time down under and chats with Russ and Dr Pete about Australian Rules Football, the last 10 years of Amazon Web Services and more.

Werner Vogels, CTO and VP at Amazon.com and a world-leading expert on scalable systems, didn’t have the traditional entry into tech one might expect. Responsible for driving Amazon’s technology vision, which is to continuously enhance innovation on behalf of Amazon’s customers at a global scale, Werner is one of the architects behind Amazon’s approach to cloud computing, Amazon Web Services (AWS). Tune in to the 100th Seedcamp podcast special for a deep-dive as Werner talks to Carlos about his fascinating and varied journey from studying Computer Science aged 28 and a 10 year career in academia, to co-founding his own business before starting his first “real job” at Amazon in 2004. Learn more about the core pillars that uphold Amazon’s approach to hiring, team work and commercialisation as well as how a relentless focus on customer centricity guides all product development. With references to Seedcamp-backed companies such as TransferWise - improving customer experience and disrupting staid industries such as financial services - hear Werner’s thoughts on the need for enterprise to innovate to compete with younger companies or risk going out of business. If the above player doesn’t work for you, you can also listen directly from our Soundcloud page. Show notes from the episode: Carlos Website: www.carlosespinal.com Seedcamp: www.seedcamp.com Amazon: http://aws.amazon.com Related bio links: Carlos: uk.linkedin.com/in/carloseduardoespinal / twitter.com/cee Werner: www.linkedin.com/in/wernervogels / twitter.com/Werner

10 Years of AWS Ten Years in the AWS Cloud by Jeff Barr A Decade of Innovation by James Hamilton 10 Lessons from 10 Years of Amazon Web Services by Werner Vogels the story of hod ancient blog post talking about our old internal EMR-like workflow service

Werner Vogels (Amazon) over NSA en de trends in cloudcomputing by Fast Moving Targets