Podcast appearances and mentions of julian wood

This interview was recorded for GOTO Unscripted.https://gotopia.techRead the full transcription of this interview here:https://gotopia.tech/articles/347Tudor Girba - Software Environmentalist and CEO of feenk Julian Wood - Serverless Developer Advocate at AWSRESOURCESTudorhttps://bsky.app/profile/tudorgirba.comhttps://github.com/girbahttps://www.linkedin.com/in/girbahttp://www.tudorgirba.comhttps://medium.com/@girbaJulianhttps://bsky.app/profile/julianwood.comhttp://www.wooditwork.comhttps://www.linkedin.com/in/julianrwoodDESCRIPTIONGet a sneak peak into the concept of moldable development as a transformative approach through a discussion between Tudor Girba and Julian Wood. By emphasizing the creation of tailored, flexible tools, Girba presents a way to reduce the friction of working with complex systems and legacy code. He explores how contextualized tools, such as those provided by the Glamorous Toolkit, allow developers to engage with software environments in a more intuitive and efficient manner.The integration of generative AI is also examined, where Girba argues that AI's true potential lies not in providing definitive answers but in assisting developers by generating hypotheses and creating tools that support deeper engagement with code. Additionally, the concept of "habitability" is introduced, proposing that software systems, like physical spaces, should be navigable and comprehensible to developers, fostering a more productive and enjoyable experience.This vision of a future where software systems are more accessible and adaptable reflects the growing need to rethink how we interact with code, empowering developers with the tools and perspectives necessary to navigate increasingly complex digital landscapes.RECOMMENDED BOOKSRichard P. Gabriel • Patterns of SoftwareSusanne Kaiser • Adaptive Systems With Domain-Driven Design, Wardley Mapping, and Team TopologiesEric Evans • Domain-Driven DesignMatthew Skelton & Manuel Pais • Team TopologiesHeidi Helfand • Dynamic ReteamingVlad Khononov • Learning Domain-Driven DesignErik Schön • The Art of StrategyThomas BlueskyTwitterInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

This interview was recorded for GOTO Unscripted.https://gotopia.techRead the full transcription of this interview hereDaniel Terhorst-North - Originator of Behavior Driven Development (BDD) & Principal at Dan North & AssociatesJulian Wood - Serverless Developer Advocate at AWSRESOURCESDanielhttps://bsky.app/profile/tastapod.comhttps://www.linkedin.com/in/tastapodhttps://github.com/tastapodhttps://mastodon.social/@tastapodhttp://dannorth.net/blogJulianhttps://bsky.app/profile/julianwood.comhttps://twitter.com/julian_woodhttp://www.wooditwork.comhttps://www.linkedin.com/in/julianrwoodhttps://s12d.com/gotoDESCRIPTIONDaniel Terhorst-North and Julian Wood share decades of experience to offer a nuanced view of programming, governance, and product delivery. By framing programming as a socio-technical activity, they emphasize the critical role of collaboration, feedback, and sustainable practices.The conversation challenges traditional governance models, advocating for hypothesis-driven product management and continuous feedback mechanisms. Through humorous anecdotes and hard-won wisdom, Terhorst-North inspires people to look beyond technical expertise to the broader ecosystem of teams, culture, and organizational alignment. [...]RECOMMENDED BOOKSJez Humble & David Farley • Continuous DeliveryNicole Forsgren, Jez Humble & Gene Kim • AccelerateKim, Humble, Debois, Willis & Forsgren • The DevOps HandbookJez Humble, Joanne Molesky & Barry O'Reilly • Lean EnterpriseHeidi Helfand • Dynamic ReteamingHeidi Helfand • How to Change Your TeamsCarl Larson & Frank M J LaFasto • TeamworkGene Kim & Steve Spear • Wiring the Winning OrganizationMatthew Skelton & Manuel Pais • Team TopologiesBlueskyTwitterInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

This interview was recorded for GOTO Unscripted.https://gotopia.techRead the full transcription of this interview hereBen Ellerby - Founder of aleio & AWS Serverless HeroJulian Wood - Serverless Developer Advocate at AWSRESOURCESBenhttps://twitter.com/EllerbyBenhttps://www.linkedin.com/in/benjaminellerbyhttps://github.com/BenEllerbyhttps://medium.com/@bene_37069Julianhttps://twitter.com/julian_woodhttp://www.wooditwork.comhttps://www.linkedin.com/in/julianrwoodDESCRIPTIONJulian Wood and Ben Ellerby explore the challenges and innovations in event-driven architectures, generative AI, and serverless technologies. They emphasize the importance of well-structured event schemas and the role of platform teams in reducing cognitive load for developers.Ben Ellerby highlights the potential of generative AI in modernizing legacy codebases and discusses the resurgence of event-driven architectures, driven by improved tools and frameworks that promote decoupling and efficiency.The conversation also touches on the future of serverless computing, edge computing, and the significance of data management in global applications, underscoring a transformative shift toward more scalable and flexible cloud solutions.RECOMMENDED BOOKSDavid Anderson, Marck McCann & Michael O'Reilly • The Value Flywheel EffectAdam Bellemare • Building Event-Driven MicroservicesLauren Maffeo • Designing Data Governance from the Ground UpVaughn Vernon & Tomasz Jaskula • Strategic Monoliths & MicroservicesGregor Hohpe • Platform StrategyPeter Sbarski • Serverless Architectures on AWSMichael Stack • Event-Driven Architecture in GolangJames Urquhart • Flow ArchitecturesBlueskyTwitterInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

This interview was recorded for GOTO Unscripted.https://gotopia.techRead the full transcription of this interview hereSam Newman - Microservices Expert & Author of "Monolith to Microservices" & "Building Resilient Distributed Systems"Julian Wood - Serverless Developer Advocate at AWSRESOURCESSamhttps://twitter.com/samnewmanhttps://hachyderm.io/@samnewmanhttps://www.linkedin.com/in/samnewmanhttp://samnewman.iohttp://samnewman.io/bloghttps://github.com/snewmanJulianhttps://bsky.app/profile/julianwood.comhttps://twitter.com/julian_woodhttps://www.linkedin.com/in/julianrwoodDESCRIPTIONJulian Wood and Sam Newman delve into the complexities of software architecture, focusing on critical concepts such as microservices, asynchronous communication, and the importance of architectural decision-making.Sam emphasizes the need for clear definitions in computing, particularly around terms like asynchronicity, advocating for an understanding of communication styles—event-driven versus request-response—as pivotal for effective system design. They discuss the value of architectural decision records (ADRs) as tools for fostering collaboration and documenting trade-offs in decision-making.Additionally, the conversation highlights the evolving role of AI in software development, stressing that while AI can assist in understanding and maintaining existing codebases, the human element of critical thinking remains essential in navigating the complexities of modern software systems.RECOMMENDED BOOKSSam Newman • Building Resilient Distributed Systems • https://www.oreilly.com/library/view/building-resilient-distributed/9781098163532Sam Newman • Monolith to Microservices • https://amzn.to/2Nml96ESam Newman • Building Microservices • https://amzn.to/3dMPbOsRonnie Mitra & Irakli Nadareishvili • Microservices: Up and Running• https://amzn.to/3c4HmmLMitra, Nadareishvili, McLarty & Amundsen • Microservice Architecture • https://amzn.to/3fVNAb0BlueskyTwitterInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

This interview was recorded at GOTO Amsterdam for GOTO Unscripted.http://gotopia.techRead the full transcription of this interview hereSigne Simonsen - Founder of Race for OceansJulian Wood - Serverless Developer Advocate at AWSRESOURCESSignehttps://twitter.com/signe_simonsenhttps://www.linkedin.com/in/signe-simonsenhttps://www.instagram.com/signessimonsenJulianhttps://bsky.app/profile/julianwood.comhttps://twitter.com/julian_woodhttps://www.linkedin.com/in/julianrwoodLinkshttps://raceforoceans.org/enhttps://raceforoceans.org/en/support-ushttps://www.instagram.com/raceforoceansDESCRIPTIONJulian Wood sits down with Signe Simonsen, the visionary behind “Race for Oceans”, to explore her inspiring journey from Danish army captain to environmental advocate.Signe shares her mission to combat plastic pollution using innovative technology, including AI-driven drones and robots, to clean beaches and protect our oceans. With a blend of military precision and environmental passion, Signe Simonsen is pioneering a solution to a challenge that has persisted for decades, aiming to leave a lasting impact on the planet for future generations.RECOMMENDED BOOKSVictor Vasques Ribeiro • Plastic pellets on sandy beaches Volume I • https://amzn.to/4crhYECSubramanian Senthilkannan Muthu • Microplastic Pollution • https://amzn.to/4cnijItIoannis Kolaxis • 101 Green Software • https://www.kolaxis.dev/book-green-softwareLässig, Kersting & Morik • Computational Sustainability • https://amzn.to/3APBW8rCarola Lilienthal • Sustainable Software Architecture • https://amzn.to/3yFXxoSBlueskyTwitterInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

This interview was recorded at GOTO Amsterdam for GOTO Unscripted.http://gotopia.techRead the full transcription of this interview here:https://gotopia.tech/articles/329Flavia Naezer - Product Thinker, Public Speaker, ArtistJulian Wood - Serverless Developer Advocate at AWSRESOURCESFlaviahttps://github.com/flavianaezerhttps://www.linkedin.com/in/flavia-naezer-449b285https://x.com/flaviasomethingJulianhttps://twitter.com/julian_woodhttp://www.wooditwork.comhttps://www.linkedin.com/in/julianrwoodLinkshttps://dl.acm.org/doi/pdf/10.1145/3595878https://www.designcouncil.org.uk/our-resources/the-double-diamondDESCRIPTIONExplore the evolving relationship between technology and product management with Julian Wood and Flavia Naezer. Discover how Flavia's tech and product expertise highlights the need for user-centric design thinking and thorough research in developing internal tools and platforms.Discover how Julian and Flavia explore the intersection of tech and product management, highlighting the importance of user-centric design and thorough research in developing internal tools and platforms.RECOMMENDED BOOKSMarty Cagan • Inspired • https://amzn.to/4e5l2r2Anthony W. Ulwick • Jobs to Be Done • https://amzn.to/4elaVhuGregor Hohpe • Enterprise Integration Patterns, Vol 2 • https://amzn.to/3TNedQ3Gregor Hohpe • Platform Strategy • https://amzn.to/4fPLW7pStephanie Stimac • Design for Developers • https://amzn.to/3EhuN4TGene Kim, Jez Humble, Patrick Debois, John Willis & Nicole Forsgren • The DevOps Handbook • https://amzn.to/3WBjzCMMatthew Skelton & Manuel Pais • Team Topologies • http://amzn.to/3sVLyLQGene Kim, Nicole Forsgren & Jez Humble • Accelerate • https://amzn.to/3WCG5uTMarty Cagan • Empowered • https://amzn.to/42kuKAjTwitterInstagramLinkedInFacebookLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

This interview was recorded for GOTO Unscripted.https://gotopia.techRead the full transcription of this interview hereJulian Wood - Serverless Developer Advocate at AWSMarcia Villalba - Serverless Developer Advocate at AWSRESOURCESMarciahttps://twitter.com/mavi888uyhttps://www.linkedin.com/in/marciavillalbahttps://marcia.devhttps://github.com/mavi888Julianhttps://twitter.com/julian_woodhttp://www.wooditwork.comhttps://www.linkedin.com/in/julianrwoodLinkshttps://serverlessland.comhttps://aws.amazon.com/blogs/compute/optimizing-lambda-functions-packaged-as-container-imageshttps://serverlessland.com/patterns/s3-lambda-container-samhttps://aws.amazon.com/blogs/compute/building-php-lambda-functions-with-docker-container-imagesJulian & James: https://youtu.be/KDtsC7SjsdAMarcia: https://youtu.be/bC51iRtXlRwLiz: https://youtu.be/8fi7uSYlOdcJulian: https://youtu.be/4YeZf3HupQADESCRIPTIONExplore the seamless integration of container images with AWS Lambda! Marcia Villalba and Julian Wood unravel the intricacies of development, deployment, and optimization. Discover how containers revolutionize serverless computing, offering speed, efficiency, and scalability in the cloud. From demystifying cold starts to harnessing caching technologies, this is your chance to learn from the experts. [...]RECOMMENDED BOOKSAdam Bellemare • Building Event-Driven MicroservicesPeter Sbarski • Serverless Architectures on AWSMichael Stack • Event-Driven Architecture in GolangFord, Richards, Sadalage & Dehghani • Software Architecture: The Hard PartsGerardus Blokdyk • Event-Driven Architecture EDAJames Urquhart • Flow ArchitecturesTwitterInstagramLinkedInFacebookLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

Bionca Ellis esbozó sonrisas burlonas mientras se le leían los cargos, desatando la ira y el dolor en la comunidad de North Olmsted. Ellis agredió con un cuchillo a Margot Wood y a su hijo de tres años, Julian Wood. El pequeño murió por las heridas pese a la rápida intervención de los paramédicos. “La investigación sobre el motivo de este ataque aún está en curso, pero todo lo que se sabe hasta ahora indica que se trató de un acto aleatorio de violencia”, informó Matt Beck, sargento de la policía de North Olmsted. El domingo 16 de junio se suscitó un fuerte accidente vehicular en calles de Tijuana, Baja California, en el que se vieron involucrados dos vehículos y por el que murieron dos hombres en pleno Día del Padre. Tras el choque, los cuerpos de los dos conductores quedaron atrapados adentro de las unidades. De acuerdo a los reportes, el accidente se registró en Calle Décima y Avenida Negrete. El joven que asesinó a sus padres por dinero: el brutal relato de cómo intentó hacer desaparecer los cuerpos Joel Guy había participado de la cena de Acción de Gracias familiar. Pese a los brindis, tenía anotado en un cuaderno todo el plan criminal. Las huellas que halló la policía y los 500.000 dólares que estaban en juego Una suegra sospechosa, una carta misteriosa y un amante: el curso del caso de la bella joven acusada de matar a su esposo por codicia Distribuido por Genuina Media

Our resident historian Azzmador died at 57! Evil in America and around the world! Callers "cry" about it! The Hake Report, Tuesday, June 18, 2024 AD TIME STAMPS * (0:00:00) Topics: RIP Azzmador, Evil News (Not kids) * (0:02:02) Hey, guys! Stretch Arm Strong tee * (0:03:20) RIP Azzmador, Robert Wray, 57, 1966-2024* (0:08:59) DANIEL, TX: Azzmador saved Sam Houston statue * (0:16:01) Coffees: RIP Azzmador, Tupac * (0:18:52) Coffee: Suggestion box * (0:19:43) Coffee: Not shadow banned, the Lord's refuge * (0:20:27) HECTOR, NM: Mexicans' origin; historians; mixing * (0:28:17) Rumble: BrandonM, RIP great storyteller Azzmador * (0:29:01) "Undocumented spouses," Biden amnesty (CNN) * (0:39:20) "LGBTQ+ rights": "marriage equality" in Thailand (CNN) * (0:49:43) ASH, Lithuania (1st) shopping carts, civilized Europe * (0:59:01) Supers: Cashapp * (0:59:42) Supers: black slave owner Anthony Johnson * (1:01:52) MARK, CA: LGBT history; Charlottesville, crimes, anti-white * (1:14:04) FREDERICK: The Cry Report, blame, MESS, God's plan, Fathers * (1:26:22) Don't cry. Love. False guilt over false history. * (1:28:02) DAVID, FL: 3yo face; Mother, Salvadorian; US end; Think special * (1:37:36) 3yo Julian Wood, perp Bionca Ellis * (1:39:19) JIM/JAMES, IL: Grandma died. 9/11, shutdowns, drugs, Aeon, Aura * (1:49:12) Super: Anthony Johnson made slave children? * (1:49:56) JEFF, OH: Nice story about N-word, people getting along * (1:52:59) Closing: "Good Morning" - Bullfrogs and Butterflies LINKS BLOG  https://www.thehakereport.com/blog/2024/6/18/the-hake-report-tue-6-18-24 PODCAST / Substack  HAKE NEWS from JLP  https://www.thehakereport.com/jlp-news/2024/6/18/hake-news-tue-6-18-24 Hake is live M-F 9-11a PT (11-1CT/12-2ET) Call-in 1-888-775-3773 https://www.thehakereport.com/show VIDEO  YouTube  -  Rumble*  -  Facebook  -  X  -  BitChute  -  Odysee*  PODCAST  Substack  -  Apple  -  Spotify  -  Castbox  -  Podcast Addict  *SUPER CHAT on platforms* above or  BuyMeACoffee, etc.  SHOP  Spring  -  Cameo  |  All My Links  JLP Network:  JLP  -  Church  -  TFS  -  Nick  -  Joel  Get full access to HAKE at thehakereport.substack.com/subscribe

A look into Julian Wood's case that happened recently on June 3rd and is being called “a random act of violence”

Bionca Ellis was calmer during a short hearing in an Ohio court on Monday, after smiling and even laughing during her arraignment last week. Ellis is accused of stabbing 3-year-old Julian Wood multiple times in a grocery store parking lot, killing him. Julian's mother Margot was injured trying to protect her son. Law&Crime's Jesse Weber discusses the decisions made during Monday's hearing and what happens next with former prosecutor Sarena Townsend.PLEASE SUPPORT THE SHOW: If you experienced adverse side effects after taking Ozempic or another weight loss medication, check your eligibility to file a claim by visiting https://www.glp1case.com/sidebar/?v=osb15HOST:Jesse Weber: https://twitter.com/jessecordweberLAW&CRIME SIDEBAR PRODUCTION:YouTube Management - Bobby SzokeVideo Editing - Michael DeiningerScript Writing & Producing - Savannah WilliamsonGuest Booking - Alyssa Fisher & Diane KayeSocial Media Management - Vanessa BeinSTAY UP-TO-DATE WITH THE LAW&CRIME NETWORK:Watch Law&Crime Network on YouTubeTV: https://bit.ly/3td2e3yWhere To Watch Law&Crime Network: https://bit.ly/3akxLK5Sign Up For Law&Crime's Daily Newsletter: https://bit.ly/LawandCrimeNewsletterRead Fascinating Articles From Law&Crime Network: https://bit.ly/3td2IqoLAW&CRIME NETWORK SOCIAL MEDIA:Instagram: https://www.instagram.com/lawandcrime/Twitter: https://twitter.com/LawCrimeNetworkFacebook: https://www.facebook.com/lawandcrimeTwitch: https://www.twitch.tv/lawandcrimenetworkTikTok: https://www.tiktok.com/@lawandcrimeSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

This interview was recorded for GOTO Unscripted.https://gotopia.techRead the full transcription of this interview hereJulian Wood - Developer Advocate at AWSJames Beswick - Senior Manager, AWS Serverless Developer AdvocacyRESOURCESJulianhttps://twitter.com/julian_woodhttp://www.wooditwork.comhttps://www.linkedin.com/in/julianrwoodJameshttps://twitter.com/jbeswhttps://linkedin.com/in/jamesbeswickLinkshttps://serverlessland.comhttps://www.comicrelief.com/rednosedayhttps://www.nationwidechildrens.orgJulian: https://youtu.be/4YeZf3HupQAJames: https://youtu.be/dUXDuxqTxmoNicki: https://youtu.be/4N2ywun-wTEJohn: https://youtu.be/_76uaHtthYsSarah: https://youtu.be/6_Yzybhmj-8Veda: https://youtu.be/-X-YHHU7p20Uma & Dhiraj: https://youtu.be/dzW3-Mol1yoRicardo: https://youtu.be/YPQ65budGnIRosemary: https://youtu.be/7j3h2IqkmIARebekah: https://youtu.be/_ugRNuE9xmADESCRIPTIONJames Beswick and Julian Wood analyze the evolving landscape of serverless computing, from its current state to its future trajectory. They discuss the fusion of containers and serverless, highlighting the flexibility and efficiency gained from running Lambda functions from container images.Moreover, they emphasize the importance of asynchronous development and the role it plays in scaling applications, with Julian Wood noting its under-appreciated potential for high performance.Throughout the dialogue, they touch on cost management, architectural decisions and the collaborative relationship between AWS and its customers in shaping the future of serverless technologies. As they envision the next five years, they anticipate a continued integration of best practices, platform evolution, and groundbreaking innovations influenced by customer feedback and industry trends. [...]RECOMMENDED BOOKSAdam Bellemare • Building Event-Driven MicroservicesPeter Sbarski • Serverless Architectures on AWSMichael Stack • Event-Driven Architecture in GolangFord, Richards, Sadalage & Dehghani • Software Architecture: The Hard PartsGerardus Blokdyk • Event-Driven Architecture EDAJames UrquhTwitterInstagramLinkedInFacebookLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

Do you carry your fundamental four everywhere, even to the grocery store? A woman was stabbed and her child murdered by a maniac wielding a knife in a grocery store parking lot in Ohio. What lessons can we learn?  Three people were attacked and maimed by sharks in Florida on the same day in the same area. Fortunately none died despite life-threatening injuries due to the efforts of the people on the scene. Are you carrying medical gear to the beach?  Also, during our Tech Talk from EOTech we consider the importance of understanding off set. We have a Frog Lube Pro Tip of the week for you as well.  Thanks for being a part of SOTG! We hope you find value in the message we share. If you've got any questions, here are some options to contact us: Send an Email Send a Text Call Us Enjoy the show! And remember… You're a Beginner Once, a Student For Life! FEATURING: The Outdoor Wire, PNJ.com, Guns.com, News 5 Cleveland, Madison Rising, Jarrad Markel, Paul Markel, SOTG University PARTNERS: EOTech, FrogLube, Hi-Point Firearms, Spikes Tactical FIND US ON: iTunes, Stitcher, AppleTV, Roku, Amazon, GooglePlay, YouTube, Threads, Instagram, Facebook, X TOPICS COVERED THIS EPISODE Huge thanks to our Partners: EOTech | FrogLube | Hi-Point Firearms | Spike's Tactical Father's Day Sale over on ShopSOTG.com! Blood Trail, Dad Rules, Leadership Traits Poster, AND MORE! [0:03:00] New Review of Blood Trail by Jim Shepherd www.theoutdoorwire.com [0:08:44] EOTech Talk - EOTechInc.com TOPIC: Calculating off-set is easy with EOTech reticle [0:17:08] Pro Tip of the Week - FrogLube.com TOPIC: Of All the things that can affect your gun's reliability, cleaning and lube should not be one of them. [0:33:58] SOTG Homeroom - SOTG University TOPIC: Florida beaches open after shark attacks injure 3 and take a woman's hand www.pnj.com Hemingway was right www.guns.com [0:58:03] Suspect in North Olmsted fatal toddler stabbing obtained knife at thrift store just before attack www.news5cleveland.com Follow Up - Julian Wood's suspected killer claims she's killed before fox8.com SOURCES From www.pnj.com: Two teenagers and a woman were injured in two shark attacks less than two hours apart Friday afternoon in the Florida Panhandle. The woman lost her lower left arm and suffered "significant trauma" to other areas of her body, officials said at a Friday afternoon news conference. The mother of one of the teens said the girl's hand had been taken and her right leg had to be amputated. Both incidents happened between Miramar Beach and Panama City Beach on the Gulf of Mexico. Beaches in Walton and Bay counties were closed Friday and reopened Saturday morning, with warnings. The Walton County Sheriff's Office and Florida Fish and Wildlife monitored the shoreline by boat through the weekend. Panama City Beach Police in the Sheriff's Office helicopter Saturday reported seeing "a notable presence of sharks, specifically bull sharks," near the first incident. (Click Here for Full Article)   From www.news5cleveland.com: North Olmsted officials held a news conference Tuesday afternoon to shed light on what happened in the minutes leading up to the fatal stabbing of a toddler in the Giant Eagle parking lot. According to North Olmsted Police Detective Sgt. Matt Beck, the suspect, 32-year-old Bionca Ellis, was at the Volunteers of America store, which is a thrift shop adjacent to the grocery store, where she obtained some sort of kitchen knife. It's unclear if she paid for it or stole it. Ellis then left the store, walked over to Giant Eagle, located in the 27000 block of Lorain Road, just after 3 p.m., and approached the 38-year-old mother, who was pushing her 3-year-old Julian Wood in a grocery cart as they were nearing their vehicle. Ellis allegedly stabbed the woman and Julian multiple times and walked off. The entire attack unfolded quickly, Beck said. (Click Here for Full Article)

Three-year-old Julian Wood and his mother Margot were in the parking lot of an Ohio grocery store when Bionca Ellis, 32, allegedly attacked them with a knife. Julian was severely wounded and died at the hospital. His mom is expected to survive. During her arraignment, Ellis refused to cooperate via video stream, so the judge brought her into the courtroom to hear the 10 charges against her. Law&Crime's Jesse Weber analyzes Ellis's bizarre courtroom behavior with Ohio trial attorney Diane Menashe.PLEASE SUPPORT THE SHOW: If you've used Incognito mode in Google's Chrome browser, find out if you have a claim in a few clicks by visiting: https://www.incognitoclaims.com/sidebar/?v=sb46HOST:Jesse Weber: https://twitter.com/jessecordweberLAW&CRIME SIDEBAR PRODUCTION:YouTube Management - Bobby SzokeVideo Editing - Michael DeiningerScript Writing & Producing - Savannah WilliamsonGuest Booking - Alyssa Fisher & Diane KayeSocial Media Management - Vanessa BeinSTAY UP-TO-DATE WITH THE LAW&CRIME NETWORK:Watch Law&Crime Network on YouTubeTV: https://bit.ly/3td2e3yWhere To Watch Law&Crime Network: https://bit.ly/3akxLK5Sign Up For Law&Crime's Daily Newsletter: https://bit.ly/LawandCrimeNewsletterRead Fascinating Articles From Law&Crime Network: https://bit.ly/3td2IqoLAW&CRIME NETWORK SOCIAL MEDIA:Instagram: https://www.instagram.com/lawandcrime/Twitter: https://twitter.com/LawCrimeNetworkFacebook: https://www.facebook.com/lawandcrimeTwitch: https://www.twitch.tv/lawandcrimenetworkTikTok: https://www.tiktok.com/@lawandcrimeSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Welcome to the Annual "Very Best of the Year" episode!  2023 was the biggest year yet for us and we're so grateful for you to join us as we look back on the year that was with the very best bits.  This episode is split into four categories...the funniest, most shocking, Dos & D uncut and the heartfelt/inspiring moments.  We try and sprinkle humour into every episode we put out and when trying to find only four clips to play, trust us, it was a difficult job!  This segment will have you in stitches as Sam Newman shares his relationship with "the chief", Jason Dunstall, Hugh van Cuylenburg's horrendously awkward first encounter's with now friend, Hamish Blake, Julian Wood's involvement with Marty & Michael's streaking of the AFL Grand Final and Rob Mills caught on stage with literally his pants around his ankles...  Then we turn our attention to the parts which will shock you for different reasons.  Survival Expert, Ky Furneaux's experience on "Naked & Afraid, Celebrity Bodyguard, Wayne Mattei's hairiest moments, Aussie Sprinter, Morgan Mitchell being the victim of a pathetic attack and World Renowned Artist. Danielle Weber's painting of "The Rock" that didn't go to plan all feature in this segment.  Each month we release one Dos & D "uncut" episode where the two of us banter and share some horrifying stores. This year, these episodes really gained momentum and we've got some of the best for you today.  From pranking our family members to try not to laugh competition's and of course our famous stories like nearly ruining a wedding and wingmanning gone wrong all are hear for you to enjoy.  And finally, to send you into 2024 with some inspiration as well as some heart felt moments we have Zed Nasheet's incredible story of selling hotdogs outside nightclubs at 14 years old to escape poverty, Black Manwaring's story of being coward attacked, Ironman, Matt Bevilacqua's crazy training schedule in the freezing cold Tasmania at just 16 years old and Prime Train's advice on how to build a brand is priceless.  Thank you all for your support in 2023, we can't wait for 2024. We couldn't do this without you and appreciate and love you all!    Here are the episode's (in order of appearance) from the clips played in this episode for you to go back and listen.    Sam Newman - 164  Hugh van Cuylenburg - 158 Julian Woods - 161  Rob Mills - 173  Ky Furneaux - 137  Wayne Mattei - 131  Morgan Mitchell - 170  Danielle Weber - 156  Wedding Gone Wrong - 143  What's That? Prank - 159  Wingman Disaster - 127  Try Not to Laugh - Available on YouTube & 163  Zed Nasheet - 155  Blake Manwaring - 152  Matt Bevilacqua - 153  Prime Train - 157    Follow us on Instagram @dosandd_ Follow us on TikTok @dosandd  Watch & Subscribe to our YouTube Channel here - Dos and D - YouTube Follow us on Facebook here - The Dos & D Show | Facebook  Questions & Enquiries - thedosanddshow@gmail.com  It would mean the world to us if you could follow, subscribe and leave a 5-star review on Spotify & Apple Podcasts. 

Julian is a former pro cricketer turned coach and pioneer in the field of #powerhitting. Listen to find out more about his background and approach.

This interview was recorded for GOTO Unscripted at GOTO Copenhagen.gotopia.techRead the full transcription of this interview hereChristian Heilmann - uthor of Several JS Books & Previously Worked at Yahoo, Mozilla & MicrosoftJulian Wood - Developer Advocate at AWSRESOURCEScodepo8.github.io/more-developer-tools-trickscodepo8.github.io/dearconsoledevtoolstips.orgcanidev.toolsChristianchristianheilmann.com@codepo8toot.cafe/@codepo8github.com/codepo8linkedin.com/in/christianheilmannJulian@julian_woodwooditwork.comlinkedin.com/in/julianrwoodDESCRIPTIONDevelopers often face challenges in setting up their development environments and experience a lot of time wasted on customization. In this episode of GOTO Unscripted, Julian Wood interviews Christian Heilmann, former principal program manager for developer tools at Microsoft. Christian emphasizes the need to break free from the traditional monolithic IDE and debugging tools by leveraging the power of web technology and standardizing extensions. By highlighting the importance of contextual tooling, where interfaces learn from user behavior and provide automated suggestions and simplified workflows, he aims to streamline the development process and make it more accessible, empowering developers to focus on writing code rather than navigating complex environments.RECOMMENDED BOOKSChristian Heilmann & Jens Oliver Meiert • The Developer Advocacy HandbookChristian Heilmann & Russ Ferguson • Beginning JavaScript with DOM Scripting and AjaxChristian Heilmann & Mark Norm Norman Francis • Web Development SolutionsMultiple Authors • Web AccessibilityTwitterLinkedInFacebookLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted almost daily

This interview was recorded for GOTO Unscripted at GOTO Copenhagen.gotopia.techRead the full transcription of this interview hereBen Sadeghipour - VP of Research at Hadrian SecurityJulian Wood - Developer Advocate at AWS @julian_wood  RESOURCEStryhackme.comhackthebox.compentesterlab.comctfchallenge.combugbountyhunter.comportswigger.net/burpBennahamsec.com@nahamsectwitch.tv/nahamsecinstagram.com/nahamsecJulian@julian_woodwooditwork.comlinkedin.com/in/julianrwoodDESCRIPTIONJoin us for an engaging conversation between Ben Sadegiphour, VP of Research at Hadrian Security, and Julian Wood, Developer Advocate at AWS. In this conversation, we will explore a range of captivating topics, such as: Bug bounties, ethical hacking, Skills, Resources, tips and much more.Whether you're an aspiring ethical hacker or simply interested in the fascinating world of cybersecurity, this video is packed with knowledge and practical advice. Get ready to hack like a pro and join us on this exciting journey!RECOMMENDED BOOKSPeter Yaworski • Real-World Bug HuntingVickie Li • Bug Bounty BootcamCarlos A. Lozano & Shahmeer Amir • Bug Bounty Hunting EssentialSanjib Sinha • Bug Bounty Hunting for Web SecurityJim Manico & August Detlefsen • Iron-Clad JavaLiz Rice • Container SecurityAaron Parecki • OAuth 2.0 SimplifiedAaron Parecki • OAuth 2.0 ServersErdal Ozkaya • Cybersecurity: The Beginner's GuideTwitterLinkedInFacebookLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted almost daily

This interview was recorded for GOTO Unscripted at GOTO Copenhagen.gotopia.techRead the full transcription of this interview hereChristian Clausen - Author of "Five Lines of Code", Founder of mist-cloud & Technical Agile CoachJulian Wood - Developer Advocate at AWSDESCRIPTIONRevamp your code with refactoring! In an insightful interview with Julian Wood, Christian Clausen, author of Five Lines of Code, shares practical tips for improving your code without relying on “code smells”. Simplifying your code is the key to running your business smoothly. Clausen highlights what matters most in terms of simplifying your code and how it can aid in choosing the right architectural paradigm. Streamline your code today and focus on what really matters!RECOMMENDED BOOKSChristian Clausen • Five Lines of CodeMartin Fowler • RefactoringMaude Lemaire • Refactoring at ScaleUncle Bob • Clean CodeAdam Tornhill • Software Design X-RaysAdam Tornhill • Your Code as a Crime SceneTwitterLinkedInFacebookLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted almost daily

This interview was recorded for GOTO Unscripted at GOTO Copenhagen.gotopia.techRead the full transcription of this interview hereJessica Cregg - Information Technology Operations engineer at CybSafeJulian Wood - Developer Advocate at AWSDESCRIPTIONWhat are the technologies that one should leverage to build modern, scalable, and flexible applications?Julian Wood, developer advocate at AWS Serverless, talks with Jessica Cregg, previously a developer advocate at LaunchDarkly, now an information technology operations engineer at CybSafe about the mindset and tools required to build scalable software without over-engineering a solution.RECOMMENDED BOOKSAdzic & Korac • Running ServerlessScott Patterson • Learn AWS Serverless ComputingPeter Sbarski • Serverless Architectures on AWSGregor Hohpe • The Software Architect ElevatorHenney & Monson-Haefel • 97 Things Every Software Architect Should KnowMatthew Skelton & Manuel Pais • Team TopologiesForsgren, Humble & Kim • Accelerate: The Science of Lean Software and DevOpsTwitterLinkedInFacebookLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted almost daily

ServerlessDays Belfast was on the 28th of February. It's a volunteer, community, and not-for-profit event. We had a bunch of sponsors: AWS, Bazaarvoice, EverQuote, G-P, Instil and LibertyIT. Our organizers are me, Gillian Armstrong, Garth Gilmour, Peter Farrell, Julie Sherlock, and Treasa Anderson. We had 12 speakers, and over 260 attendees from over 40 companies. But most excitingly we had it at the Game of Thrones Studios Tour. The theme was 'The Reality and Fantasy of Serverless, Building Serverless Teams and Making it Real'. Phil Le-Brun, who is the Director of the Enterprise Strategy Team for AWS launched the event. And give us a perspective of what he sees when he is speaking to the leaders of the industry. IT Revolution was very generous to sponsor and provide 250 of 'The Value Flyweel Effect' books. Julian Wood gave the Keynote. Even though he works for AWS as a Serverless Developer Advocate, he gave his opinion on where he sees the industry. I thought that paired really nicely with Mattie Wilson from Instil. He gave a brilliant talk on an engineering team going through the journey from a cloud application to a serverless application. Sheen Brisals from The LEGO Group, as ever, gave an absolutely brilliant talk about Lego's journey. Going Serverless to EDA and the team topologies of an event-driven organisation. Sheen is an absolute master. Jonah Andersson did a talk on the .NET stack. And Conall Bennett and Roger Moore did a talk on CME Group's move to a Google tech stack. Craig McCarter talked about large-scale serverless. And I took comfort from hearing about a team that's doing something financially significant at a massive scale. And they're pushing those limits. I really enjoyed the talk by Anna Carlin and Emma Patton from Aflac Northern Ireland. They called their talk: 'A rookie journey of discovery and learning'. So they came in as grads and basically built a serverless system. And Chintan Parmar's Dunelm story was really interesting about Dunelm's e-commerce site because it's quite an unknown story. Most people had no idea that they had a whole big serverless ecommerce site. Ben Ellerby from Aleios closed out with his Serverless Staircase Framework. I've been a fan of Ben's for many years. He's an AWS Hero. He's brilliant and very experienced. And he's worked on a lot of serverless projects. That is what his company does. So he's got lots of war stories from doing this with real customers. Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on Twitter @ServerlessEdge

AWS Lambda is one of the most famous AWS services these days. If you are just starting with your cloud journey you might be confused about what Lambda actually is, what are the limitations, and when you should be using it or not. In this episode, we provide a beginner-friendly introduction to Lambda and summarise everything there's to know about it: when to use it and when not, differences with containers, the pricing model, limitations, and integrations. By the end of this episode, we will also chime in with some of our opinions and share whether we believe that Lambda is the future of cloud computing or not!

We are talking about Event Driven Architecture examples today. There was an event in London a few weeks ago, called EDA Day. It was organised by GOTO with a lot of AWS contributors. It was neat because it was one day focused on event driven architectures. It showed the coming together of a 15 to 20 year old pattern of EDA, plus serverless. And all the bigger services on top of that, like Eventbridge and Step Functions. Gregor Hohpe's Keynote Gregor Hohpe did the keynote talk: 'I made everything loosely coupled. Does my app fall apart?' Gregor is an AWS enterprise strategist. And he talked about the event landscape and the complexities behind event driven and architecture. He had a diagram called: 'A calls B'. It looked pretty simple until you get to the million things you need to think about when A calls B! He said that there were three languages in a cloud native serverless domain. The business domain and how you talk about the business domain as a business person. The eventing architecture and how you talk about it as an architect. And the cloud native area, and how you talk about it as a cloud engineer. So DDD, event framework and CDK for automation. It's about having those three separate languages and how you talk. And bringing them together at the end. Serverless Espresso And one neat thing to mention is a developer advocate called Julian Wood. He's worth looking up on Twitter. He, Ben Smith, and a few others from Serverless Land, put together a demo called Serverless Espresso. You scan a barcode and through an event driven step function, event bridge sequence, you can order a coffee from your phone. It looks and sounds really simple. But you watch the whole thing happen. That's a great lab. So look up AWS labs, to see Serverless Espresso. It's well put together to show how you build an event driven architecture from the ground up. Ben Ellerby - Minimal Viable Migrations Another good speaker was Ben Ellerby. He worked in Theodo and is an AWS Serverless Hero. He has a thing about Minimal Viable Migrations. A lot of people think event driven is a greenfield or brand new thing. But he had a great talk about existing architecture and going event driven. He talked about doing a small part of your architecture and going bit by bit. By using an incremental model. David Boyne - Awesome EventBridge David Boyne joined AWS and does ‘Awesome EventBridge'. He has open source projects. And he does a great talk on 'Thinking Event First'. How to approach events and get your schemes right. And really think about your domain model and lock it in from day one. So he's got a bunch of tools as well. So it's worth looking up his resources on ‘awesome event bridge'. Marcia Villalba - FooBar Serverless Another great speaker was Marcia Villalba. She's one of the developer advocates at AWS. She's got great content on good practices and getting started. She has a really nice way of explaining these concepts. There is one thing I get nervous about around event driven and domain driven. People who are good at it tend to get very complicated very quickly and lose everyone. But Marcia's super at bringing these concepts across and helping normal teams, which is every team. Check out her FooBar Serverless YouTube channel. There is tons of developer friendly content from beginner to more advanced. It's one of my YouTube subscriptions that I watch quite regularly. Lego Talk - Sarah Hamilton and Sheen Brisals The last one to talk about is Lego. They sponsored the event. And they had two talks. Sarah Hamilton is one of the software engineers and she gave a really good talk about the advanced techniques they're using in their event driven architecture. My friend, Sheen Brisals was speaking as well. They have a fantastic story, which is well worth listening to. It's about how they moved to an event driven serverless architecture. There's a socio-technical element to this. How you organise your teams and the attitude is what I would call a core engineering competency and mindset. As opposed to an architectural pattern. Lego tells their story brilliantly. Product Leader panel The event ended with a panel of product leaders from Eventbridge, Step Functions and MongoDB. It was a really relaxed panel. Emily Shea, who we know well, was there. She works in go to market for serverless. It was a relaxed chat. No one was pushing any tools. They were shooting the breeze on good practice and what's coming down the track. The evolution of event driven architecture and the tie in with serverless. There's something in it! I don't want to say Serverless is becoming EDA or EDA is becoming serverless. But serverless enables EDA for sure. https://gotoldn.com/ https://theserverlessedge.com/ https://twitter.com/ServerlessEdge  

In this episode, Dave continues his conversation with Julian Wood, Senior Developer Advocate for AWS Serverless. In part two of this two-part series, Julian digs into real world serverless, lessons learned, AWS services to think about, event-driven computing, recent serverless launches, and tips for serverless development with local environments. Julian on Twitter: https://twitter.com/julian_wood Dave on Twitter: https://twitter.com/thedavedev Julian on LinkedIn: https://www.linkedin.com/in/julianrwood/ Julian's Website: http://www.wooditwork.com/ Best Practices of Advanced Serverless Developers – Julian's recent re:Invent 2021 Talk: https://bit.ly/3JGiSyt Innovator Island Lab - Deploy a Completely Serverless Web App: https://bit.ly/3rXJF3e Accelerating Serverless Development with AWS SAM Accelerate: https://go.aws/3I0YZS2 CDK Construct Library to Run a Serverless Valheim Server: https://bit.ly/3BrLnwK AWS Step Functions – Visual Workflows for Modern apps: https://go.aws/3BwqFf3 Serverless on AWS: https://go.aws/3HJAR6w Serverless Land – News on all things AWS Serverless - https://serverlessland.com/ Subscribe: Amazon Music: https://music.amazon.com/podcasts/f8bf7630-2521-4b40-be90-c46a9222c159/aws-developers-podcast Apple Podcasts: https://podcasts.apple.com/us/podcast/aws-developers-podcast/id1574162669 Google Podcasts: https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5zb3VuZGNsb3VkLmNvbS91c2Vycy9zb3VuZGNsb3VkOnVzZXJzOjk5NDM2MzU0OS9zb3VuZHMucnNz Spotify: https://open.spotify.com/show/7rQjgnBvuyr18K03tnEHBI TuneIn: https://tunein.com/podcasts/Technology-Podcasts/AWS-Developers-Podcast-p1461814/ RSS Feed: https://feeds.soundcloud.com/users/soundcloud:users:994363549/sounds.rss

In this episode, Dave chats with Julian Wood, Senior Developer Advocate for AWS Serverless. Julian shares his time transitioning from an IT Infrastructure job into the cloud, the start of Serverless at AWS, Serverless modern app development, and career advice for continued learning. This episode is part one of a two-part series on Serverless on AWS. Julian on Twitter: https://twitter.com/julian_wood Dave on Twitter: https://twitter.com/thedavedev Julian on LinkedIn: https://www.linkedin.com/in/julianrwood/ Julian's Website: http://www.wooditwork.com/ Serverless on AWS: https://go.aws/3HJAR6w Serverlessland – Latest news on all things AWS Serverless - https://serverlessland.com/ Subscribe: Amazon Music: https://music.amazon.com/podcasts/f8bf7630-2521-4b40-be90-c46a9222c159/aws-developers-podcast Apple Podcasts: https://podcasts.apple.com/us/podcast/aws-developers-podcast/id1574162669 Google Podcasts: https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5zb3VuZGNsb3VkLmNvbS91c2Vycy9zb3VuZGNsb3VkOnVzZXJzOjk5NDM2MzU0OS9zb3VuZHMucnNz Spotify: https://open.spotify.com/show/7rQjgnBvuyr18K03tnEHBI TuneIn: https://tunein.com/podcasts/Technology-Podcasts/AWS-Developers-Podcast-p1461814/ RSS Feed: https://feeds.soundcloud.com/users/soundcloud:users:994363549/sounds.rss

Julian Wood (@julian_wood, Sr. Developer Advocate @AWSCloud) talks about the evolution of serverless from niche to mainstream applications, and how the technology stack has evolved to a broad set of use-cases.SHOW: 516SHOW SPONSOR LINKS:CBT Nuggets: Expert IT Training for individuals and teamsSign up for a CBT Nuggets Free Learner account Datadog Security Monitoring Homepage: Modern Monitoring and AnalyticsTry Datadog yourself by starting a free, 14-day trial today. Listeners of this podcast will also receive a free Datadog T-shirt.Okta - Safe Identity for customers and workforceTry Okta for FREE (Trial in 10 minutes)CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotwCHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"SHOW NOTES:Serverless LandServerless LiveAWS Serverless HomepageLambda ExtensionsLambda container image supportTopic 1 - Welcome to the show. Before we dive into the work you’re doing with Serverless, let’s talk about your background. Topic 2 - Let’s begin with “What is Serverless at AWS in 2021?” Sometimes it’s Lambda, sometimes it's a database, sometimes it's a CDN edge service. When is it App-Centric and when is it NoOps-centric?Topic 3 - AWS Lambda has expanded in functionality quite a bit over the years. Walk us through how it’s evolved across languages, event-sources, functions vs. containers, etc. Topic 4 - How do you think about Serverless use-cases? What are common usage patterns? Topic 5 - For a while, Lambda was mostly focused within the AWS ecosystem. Is it expanding to include 3rd-party services, or custom-built tools from customers/companies? Topic 6 - We’ve done a couple recent shows about event-driven applications. I tend to think about Serverless (or FaaS) as mostly event-driven apps. How is that space evolving?FEEDBACK?Email: show at thecloudcast dot netTwitter: @thecloudcastnet

About Julian WoodJulian Wood is a Senior Developer Advocate for the AWS Serverless Team. He loves helping developers and builders learn about, and love, how serverless technologies can transform the way they build and run applications at any scale. Julian was an infrastructure architect and manager in global enterprises and start-ups for more than 25 years before going all-in on serverless at AWS.Twitter: @julian_woodAll things Serverless @ AWS: ServerlessLandServerless Patterns CollectionServerless Office Hours – every Tuesday 10am PTLambda ExtensionsLambda Container ImagesWatch this episode on YouTube: https://youtu.be/jtNLt3Y51-gThis episode sponsored by CBT Nuggets and Lumigo.TranscriptJeremy: Hi everyone, I'm Jeremy Daly and this is Serverless Chats. Today I'm joined by Julian Wood. Hey Julian, thanks for joining me.Julian: Hey Jeremy, thank you so much for inviting me.Jeremy: Well, I am super excited to have you here. I have been following your work for a very long time and of course, big fan of AWS. So you are a Serverless Developer Advocate at AWS, and I'd love it if you could just tell the listeners a little bit about your background, so they get to know you a bit. And then also, sort of what your role is at AWS.Julian: Yeah, certainly. Well, I'm Julian Wood. I am based in London, but yeah, please don't let my accent fool you. I'm actually originally from South Africa, so the language purists aren't scratching their heads anymore. But yeah, I work within the Serverless Team at AWS, and hopefully do a number of things. First of all, explain what we're up to and how our sort of serverless things work and sort of, I like to sometimes say a bit cheekily, basically help the world fall in love with serverless as I have. And then also from the other side is to be a proxy and sort of be the voice of builders, and developers and whoever's building service applications, and be their voices internally. So you can also keep us on our toes to help build the things that will brighten your days.And just before, I've worked for too many years probably, as an infrastructure racker, stacker, architect, and manager. I've worked in global enterprises babysitting their Windows and Linux servers, and running virtualization, and doing all the operations kind of stuff to support that. But, I was always thinking there's a better way to do this and we weren't doing the best for the developers and internal customers. And so when this, you know in inverted commas, "serverless way" of things started to appear, I just knew that this was going to be the future. And I could happily leave the server side to much better and cleverer people than me. So by some weird, auspicious alignment of the stars, a while later, I managed to get my current dream job talking about serverless and talking to you.Jeremy: Yeah. Well, I tell you, I think a lot of serverless people or people who love serverless are recovering ops and infrastructure people that were doing racking and stacking. Because I too am also recovering from that and I still have nightmares.I thought that it was interesting too, how you mentioned though, developer advocacy. It's funny, you work for a specific company, AWS obviously, but even developer advocacy in general, who is that for? Who are you advocating for? Are you advocating for the developers to use the service from the company? Are you advocating for the developers so that the company can provide the services that they actually need? Interesting balance there.Julian: Yeah, it's true. I mean, the honest answer is we don't have great terms for this kind of role, but yeah, I think primarily we are advocating for the people who are developing the applications and on the outside. And to advocate for them means we've got to build the right stuff for them and get their voices internally. And there are many ways of doing that. Some people raise support requests and other kind of things, but I mean, sometimes some of our great ideas come from trolling Twitter, or yes, I know even Hacker News or that kind of thing. But also, we may get responses from 10 different people about something and that will formulate something in our brain and we'll chat with other kind of people. And that sort of starts a thing. It's not just necessarily each time, some good idea in Twitter comes in, it gets mashed into some big surface database that we all pick off.But part of our job is to be out there and try and think and be developers in whatever backgrounds we come from. And I mean, I'm not a pure software developer where I've come from, and I come, I suppose, from infrastructure, but maybe you'd call that a bit of systems engineering. So yeah, I try and bring that background to try and give input on whatever we do, hopefully, the right stuff.Jeremy: Right. Yeah. And then I think part of the job too, is just getting the information out there and getting the examples out there. And trying to create those best practices or at least surface those best practices, and encourage the community to do a lot of that work and to follow that. And you've done a lot of work with that, obviously, writing for the AWS blog. I know you have a series on the Serverless Lens and the Well-Architected Framework, and we can talk about that in a little while. But I really want to talk to you about, I guess, just the expansion of serverless over the last couple of years.I mean, it was very narrowly focused, probably, when it first came out. Lambda was ... FaaS as a whole new concept for a lot of people. And then as this progressed and we've gotten more APIs, and more services and things that it can integrate with, it just becomes complex and complicated. And that's a good thing, but also maybe a bad thing. But one of the things that AWS has done, and I think this is clearly in reaction to the developers needing it, is the ability to extend what you can do with a Lambda function, right? I mean, the idea of just putting your code in there and then, boom, that's it, that's all you have to do. That's great. But what if you do need access to lifecycle hooks? Or what if you do want to manipulate the underlying runtime or something like that? And AWS, I think has done a great job with that.So maybe we can start there. So just about the extensibility of Lambda in general. And one of the new things that was launched recently was, and recently, I don't know what was it? Seven months ago at this point? I'm not even sure. But was launched fairly recently, let's say that, is Lambda Extensions, and a couple of different flavors of that as well. Could you kind of just give the users an over, the users, wow, the listeners an overview of what Lambda Extensions are?Julian: I could hear the ops background coming in, talking about our users. Yeah. But I mean, from the get-go, serverless was always a terrible term because, why on earth would you name something for what it isn't? I mean, you know? I remember talking to DBAs, talking about noSQL, and they go, "Well, if it's not SQL, then what is it?" So we're terrible at that, serverless as well. And yeah, Lambda was very constrained when it came out. Lambda was never built being a serverless thing, that's what was the outcome. Sometimes we focus too much on the tools rather than the outcome. And the story is S3, just turning 15. And the genesis of Lambda was being an event trigger for S3, and people thought you'd upload something to S3, fire off a Lambda function, how cool is that? And then obviously the clever clubs at the time were like, "Well, hang on, let's not just do this for S3, let's do this for a whole bunch of kind of things."So Lambda was born out of that, as that got that great history, which is created an arc sort of into the present and into the future, which I know we're also going to get on about, the power of event driven applications. But the power of Lambda has always been its simplicity, and removing that operational burden, and that heavy lifting. But, sometimes that line is a bit of a gray area and there're people who can be purists about serverless and can be purists about FaaS and say, "Everything needs to be ephemeral. Lambda functions can't extend to anything else. There shouldn't be any state, shouldn't be any storage, shouldn't be any ..." All this kind of thing.And I think both of us can agree, but I don't want to speak for you, but I think both of us would agree that in some sense, yeah, that's fine. But we live in the real world and there's other stuff that needs to connect to and we're not here about building purist kind of stuff. So Lambda Extensions is a new way basically to integrate Lambda with your favorite tools. And that's the sort of headline thing we like to talk about. And the big idea is to open up Lambda to more effectively work mainly with partners, but also your own tools if you want to write them. And to sort of have deeper hooks into the Lambda lifecycle.And other partners are awesome and they do a whole bunch of stuff for serverless, plus customers also have connections to on-prem staff, or EC2 staff, or containers, or all kind of things. How can we make the tools more seamless in a way? How can we have a common set of tools maybe that you even use on-prem or in the cloud or containers or whatever? Why does Lambda have to be unique or different or that kind of thing? And Extensions is sort of one of the starts of that, is to be able to use these kind of tools and get more out of Lambda. So I mean, just the kind of tools that we've already got on board, there's things like Splunk and AppDynamics. And Lumigo, Epsagon, HashiCorp, Honeycomb, CoreLogic, Dynatrace, I can't think. Thundra and Sumo Logic, Check Point. Yeah, I'm sorry. Sorry for any partners who I've forgotten a few.Jeremy: No, right, no. That's very good. Shout them out, shout them out. No, I mean just, and not to interrupt you here, but ...Julian: No, please.Jeremy: ... I think that's great. I mean, I think that's one of the things that I like about the way that AWS deals with partners, is that ... I mean, I think AWS knows they can't solve all these problems on their own. I mean, maybe they could, right? But they would be their own way of solving the problems and there's other people who are solving these problems differently and giving you the ability to extend your Lambda functions into those partners is, there's a huge win for not only the partners because it creates that ecosystem for them, but also for AWS because it makes the product itself more valuable.Julian: Well, never mind the big win for customers because ultimately they're the one who then gets a common deployment tool, or a common observability tool, or a HashiCorp Vault that you can manage secrets and a Lambda function from HashiCorp Vault. I mean, that's super cool. I mean, also AWS services are picking this up because that's easy for them to do stuff. So if anybody's used Lambda Insights or even seen Lambda Insights in the console, it's somewhere in the monitoring thing, and you just click something over and you get this tool which can pull stuff that you can't normally get from a Lambda function. So things like CPU time and network throughput, which you couldn't normally get. But actually, under the hoods, Lambda Insights is using Lambda extensions. And you can see that if you look. It automatically adds the Lambda layer and job done.So anyway, this is how a lot of the tools work, that a layer is just added to a Lambda function and off you go, the tool can do its work. So also there's a very much a simplicity angle on this, that in a lot of cases you don't have to do anything. You configure some of the extensions via environment variables, if that's cooled you may just have an API key or a log retention value or something like that, I don't know, any kind of example of that. But you just configure that as a normal Lambda environment variable at this partner extension, which is just a Lambda layer, and off you go. Super simple.Jeremy: Right. So explain Extensions exactly, because I think that's one of those things because now we have Lambda layers and we have Lambda Extensions. And there's also like the runtime API and then something else. I mean, even I'm not 100% sure what all of the naming conventions. I'm pretty sure I know what they do ...Julian: Yeah, fair enough.Jeremy: ... but maybe we could say the names and say exactly what they do as well.Julian: Yeah, cool. You get an API, I get an API, everybody gets an API. So Lambda layers, let's just start, because that's, although it's not related to Extensions, it's how Extensions are delivered to the power core functions. And Lambda layers is just another way to add code to a Lambda function or not even code, it can be a dependency. It's just a way that you could, and it's cool because they are shareable. So you have some dependencies, or you have a library, or an SDK, or some training data for something, a Lambda layer just allows you to add some bits and bobs to your Lambda function. That's a horrible explanation. There's another word I was thinking of, because I don't want to use the word code, because it's not necessarily code, but it's dependency, whatever. It's just another way of adding something. I'll wake up in a cold sweat tonight thinking of the word I was thinking of, but anyway.But Lambda Extensions introduces a whole new companion API. So the runtime API is the little bit of code that allows your function to talk to the Lambda service. So when an event comes in, this is from the outside. This could be via API gateway or via the Lambda API, or where else, EventBridge or Step Functions or wherever. When you then transports that data rise in the Lambda services and HTTP call, and Lambda transposes that into an event and sends that onto the Lambda function. And it's that API that manages that. And just as a sidebar, what I find it cool on a sort of geeky, technical thing is, that actually API sits within the execution environment. People are like, "Oh, that's weird. Why would your Lambda API sit within the execution environment basically within the bubble that contains your function rather than it on the Lambda service?"And the cool answer for that is it's actually for a security mechanism. Like your function can then only ever talk to the Lambda runtime API, which is in that secure execution environment. And so our security can be a lot stronger because we know that no function code can ever talk directly out of your function into the Lambda service, it's all got to talk locally. And then the Lambda service gets that response from the runtime API and sends it back to the caller or whatever. Anyway, sidebar, thought that was nerdy and interesting. So what we've now done is we've released a new Extensions API. So the Extensions API is another API that an extension can use to get information from Lambda. And they're two different types of extensions, just briefly, internal and external extensions.Now, internal extensions run within the runtime process so that it's just basically another thread. So you can use this for Python or Java or something and say, when the Python runtime starts, let's start it with another parameter and also run this Java file that may do some observability, or logging, or tracing, or finding out how long the modules take to launch, for example. I know there's an example for Python. So that's one way of doing extensions. So it's internal extensions, they're two different flavors, but I'll send you a link. I'll provide a link to the blog posts before we go too far down the rabbit hole on that.And then the other part of extensions are external extensions. And this is a cool part because they actually run as completely separate processes, but still within that secure bubble, that secure execution environment that Lambda runs it. And this gives you some superpowers if you want. Because first of all, an extension can run in any language because it's a separate process. So if you've got a Node function, you could run an extension in other kind of languages. Now, what do we do recommend is you do run your extension in a compiled binary, just because you've got to provide the runtime that the extensions got to run in any way, so as a compiled binary, it's super easy and super useful. So is something like Go, a lot of people are doing because you write a single extension and Go, and then you can use it on your Node functions, your Java functions, your PowerShell functions, whatever. So that's a really good, simple way that you can have the portability.But now, what can these extensions do? Well, the extensions basically register with extensions API, and then they say to Lambda, "Lambda, I want to know about what happens when my functions invoke?" So the extension can start up, maybe it's got some initialization code, maybe it needs to connect to a database, or log into an observability platform, or pull down a secret order. That it can do, it's got its own init that can happen. And then it's basically ready to go before the function invokes. And then when the extension then registers and says, "I want to know when the function invokes and when it shuts down. Cool." And that's just something that registers with the API. Then what happens is, when a functioning invoke comes in, it tells the runtime API, "Hello, you now have an event," sends it off to the Lambda function, which the runtime manages, but also extension or extensions, multiple ones, hears information about that event. And so it can tell you the time it's going to run and has some metadata about that event. So it doesn't have the actual event data itself, but it's like the sort of Lambda context, a version of that that it's going to send to the extension.So the extension can use that to do various things. It can start collecting telemetry data. It can alter instrument some of your code. It could be managing a secret as a separate process that it is going to cache in the background. For example, we've got one with AppConfig, which is really cool. AppConfig is a service where you manage parameters external to your Lambda function. Well, each time your Lambda function warm invokes if you've got to do an external API call to retrieve that, well, it's going to be a little bit efficient. First of all, you're going to pay for it and it's going to take some time.So how about when the Lambda function runs and the extension could run before the Lambda function, why don't we just cache that locally? And then when your Lambda function runs, it just makes a local HTTP call to the extension to retrieve that value, which is going to be super quick. And some extensions are super clever because they're their own process. They will go, "Well, my value is for 30 minutes and every 30 minutes if I haven't been run, I will then update the value from that." So that's useful. Extensions can then also, when the runtime ... Sorry, let me back up.When the runtime is finished, it sends its response back to the runtime API, and extensions when they're done doing, so the runtime can send it back and the extension can carry on processing saying, "Oh, I've got the information about this. I know that this Lambda function has done X, Y, Z, so let me do, do some telemetry. Let me maybe, if I'm writing logs, I could write a log to S3 or to Kinesis or whatever. Do some kind of thing after the actual function invocation has happened." And then when it says it's ready, it says, "Hello, extensions API, I'm telling you I'm done." And then it's gone. And then Lambda freezes the execution environment, including the runtime and the extensions until another invocation happens. And the cycle then will happen.And then the last little bit that happens is, instead of an invoke coming in, we've extended the Lambda life cycles, so when the environment is going to be shut down, the extension can receive the shutdown and actually do some stuff and say, "Okay, well, I was connected to my observer HTTP platform, so let me close that connection. I've got some extra logs to flush out. I've got whatever else I need to do," and just be able to cleanly shut down that extra process that is running in parallel to the Lambda function.Jeremy: All right.Julian: So that was a lot of words.Jeremy: That was a lot and I bet you that would be great conversation for a dinner party. Really kicks things up. Now, the good news is that, first of all, thank you for that though. I mean, that's super technical and super in-depth. And for anyone listening who ...Julian: You did ask, I did warn you.Jeremy ... kind of lost their way ... Yes, but something that is really important to remember is that you likely don't have to write these yourself, right? There is all those companies you mentioned earlier, all those partners, they've already done this work. They've already figured this out and they're providing you access to their tools via this, that allows you to build things.Julian: Exactly.Jeremy: So if you want to build an extension and you want to integrate your product with Lambda or so forth, then maybe go back and listen to this at half speed. But for those of you who just want to take advantage of it because of the great functionality, a lot of these companies have already done that for you.Julian: Correct. And that's the sort of easiness thing, of just adding the Lambda layer or including in a container image. And yeah, you don't have to worry any about that, but behind the scenes, there's some really cool functionality that we're literally opening up our Lambda operates and allowing you to impact when a function responds.Jeremy: All right. All right. So let me ask another, maybe an overly technical question. I have heard, and I haven't experienced this, but that when it runs the life cycle that ends the Lambda function, I've heard something like it doesn't send the information right away, right? You have to wait for that Lambda to expire or something like that?Julian: Well, yes, for now, about to change. So currently Extensions is actually in preview. And that's not because it's in Beta or anything like that, but it's because we spoke to the partners and we didn't want to dump Extensions on the world. And all the partners had to come out with their extensions on day one and then try and figure out how customers are going to use them and everything. So what we really did, which I think in this case works out really well, is we worked with the partners and said, "Well, let's release this in preview mode and then give everybody a whole bunch of months to work out what's the best use cases, how can we best use this?" And some partners have said, "Oh, amazing. We're ready to go." And some partners have said, "Ah, it wasn't quite what we thought. Maybe we're going to wait a bit, or we're going to do something differently, or we've got some cool ideas, just give us time." And so that's what this time has been.The one other thing that has happened is we've actually added some performance enhancements during it. So yes, currently during the preview, the runtime and all extensions need to finish before we give you your response back to your Lambda function. So if you're in an asynchronous mode, you don't really care, but obviously if you're in a synchronous mode behind an API, yeah, you don't really want that. But when Extensions goes GA, which isn't going to be long, then that is no longer the case. So basically what'll happen is the runtime will respond and the result goes directly back to whoever's calling that, maybe API gateway, and the extensions can carry on, partly asynchronously in the background.Jeremy: Yep. Awesome. All right. And I know that the plan is to go GA soon. I'm not sure when around when this episode comes out, that that will be, but soon, so that's good to know that that is ...Julian: And in fact, when we go GA that performance enhancement is part of the GA. So when it goes GA, then you know, it's not something else you need to wait for.Jeremy: Perfect. Okay. All right. So let's move on to another bit of, I don't know if this is extensibility of the actual product itself or more so I think extensibility of maybe the workflow that you use to deploy to Lambda and deploy your serverless applications, and that's container image support. I mean, we've discussed it a lot. I think people kind of have an idea, but just give me your quick overview of what that is to set some context here.Julian: Yeah, sure. Well, container image support in a simple sort of headline thing is to be able to build and package your functions as a container image. So you basically build a function using a Docker file. So before if you use a zip function, but a lot of people use Serverless Framework or SAM, or whatever, that's all abstracted away from you, but it's actually creating a zip file and uploading it to Lambda or S3. So with container image support, you use a Docker file to build your Lambda function. That's the headline of what's happening.Jeremy: Right. And so the idea of creating, and this is also, and again, you mentioned packaging, right? I mean, that is the big thing here. This is a packaging format. You're not actually running the container in a Lambda function.Julian: Correct. Yeah, let's maybe think, because I mean, "containers," in inverted commas again for people who are on the audio, is ...Jeremy: What does it even mean?Julian: Yeah, exactly. And can be quite an overload of terms and definitely causes some confusion. And I sort of think maybe there's sort of four things that are in the container world. One, containers is an isolation mechanism. So on Linux, this is UNC Group, seccomp, other bits and pieces that can be used to isolate processes or maybe groups of processes. And then a second one, containers as the packaging mechanism. This is what Docker really popularized and this is about taking some code and the dependencies needed to run the code, and then packaging them all out together, maybe with some metadata to describe it.And then, three is containers as also a design philosophy. This is the idea, if we can package and isolate software, it's easier to run. Maybe smaller pieces of software is easy to reason about and manage independently. So I don't want to necessarily use microservices, but there's some component of that with it. And the emphasis here is on software rather than services, and standardized tooling to simplify your ops. And then the fourth thing is containers as an ecosystem. This is where all the products, tools, know how, all the actual things to how to do containers. And I mean, these are certain useful, but I wouldn't say there're anything about the other kind of things.What is cool and worth appreciating is how maybe independent these things are. So when I spoke about containers as isolation, well, we could actually replace containers as isolation with micro VMs such as we do with Firecracker, and there's no real change in the operational properties. So one, if we think, what are we doing with containers and why? One of those is in a way ticked off with Lambda. Lambda does have secure isolation. And containers as a packaging format. I mean, you could replace it with static linking, then maybe won't really be a change, but there's less convenience. And the design philosophy, that could really be applicable if we're talking microservices, you can have instances and certainly functions, but containers are all the same kind of thing.So if we talk about the packaging of Lambda functions, it's really for people who are more familiar with containers, why does Lambda have to be different? You've got, why does Lambda to have to be a snowflake in a way that you have to manage differently? And if you are packaging dependencies, and you're doing npm or pip install, and you're used to building Docker files, well, why can't we just do that for Lambda at the same things? And we've got some other things that come with that, larger function sizes, up to 10 gig, which is enabled with some of this technology. So it's a packaging format, but on the backend, there's a whole bunch of different stuff, which has to be done to to allow this. Benefits are, use your tooling. You've got your CI/CD pipelines already for containers, well, you can use that.Jeremy: Yeah, yeah. And I actually like that idea too. And when I first heard of it, I was like, I have nothing against containers, the containers are great. But when I was thinking about it, I'm like, "Wait container? No, what's happening here? We're losing something." But I will say, like when Lambda layers came out, which was I think maybe 2019 or something like that, maybe 2018, the idea of it made a lot of sense, being able to kind of supplement, add additional dependencies or code or whatever. But it always just seemed awkward. And some of the publishing for it was a little bit awkward. The versioning used like a numbered versioning instead of like semantic versioning and things like that. And then you had to share it to multiple places and if you published it as a SAR app, then you got global distri ... Anyways, it was a little bit hard to use.And so when you're trying to package large dependencies and put those in a layer and then combine them with a Lambda function, the other problem you had was you still had a maximum size that you could use for those, when those were combined. So I like this idea of saying like, "Look, I'd like to just kind of create this little isolate," like you said, "put my dependencies in there." Whether that's PyCharm or some other thing that is a big dependency that maybe I don't want to install, directly in a Lambda layer, or I don't want to do directly in my Lambda function. But you do that together and then that whole process just is a lot easier. And then you can actually run those containers, you could run those locally and test those if you wanted to.Julian: Correct. So that's also one of the sort of superpowers of this. And that's when I was talking about, just being able to package them up. Well, that now enables a whole bunch of extra kind of stuff. So yes, first of all is you can then use those container images that you've created as your local testing. And I know, it's silly for anyone to poo poo local testing. And we do like to say, "Well, bring your testing to the cloud rather than bringing the cloud to your testing." But testing locally for unit tests is super great. It's going to be super fast. You can iterate, have your Lambda functions, but we don't want to be mocking all of DynamoDB, all of building harebrained S3 options locally.But the cool thing is you've got the same Docker file that you're going to run in Lambda can be the same Docker file to build your function that you run locally. And it is literally exactly the same Lambda function that's going to run. And yes, that may be locally, but, with a bit of a stretch of kind of stuff, you could also run those Lambda functions elsewhere. So even if you need to run it on EC2 instances or ECS or Fargate or some kind of thing, this gives you a lot more opportunities to be able to use the same Lambda function, maybe in different way, shapes or forms, even if is on-prem. Now, obviously you can't recreate all of Lambda because that's connected to IM and it's got huge availability, and scalability, and latency and all that kind of things, but you can actually run a Lambda function in a lot more places.Jeremy: Yeah. Which is interesting. And then the other thing I had mentioned earlier was the size. So now the size of these container or these packages can be much, much bigger.Julian: Yeah, up to 10 gig. So the serverless purists in the back are shouting, "What about cold starts? What about cold starts?"Jeremy: That was my next question, yes.Julian: Yeah. I mean, back on zip functional archives are also all available, nothing changes with that Lambda layers, many people use and love, that's all available. This isn't a replacement it's just a new way of doing it. So now we've got Lambda functions that can be up to 10 gig in size and surely, surely that's got to be insane for cold starts. But actually, part of what I was talking about earlier of some of the work we've done on the backend to support this is to be able to support these super large package sizes. And the high level thing is that we actually cache those things really close to where the Lambda layer is going to be run.Now, if you run the Docker ecosystem, you build your Docker files based on base images, and so this needs to be Linux. One of the super things with the container image support is you don't have to use Amazon Linux or Amazon Linux 2 for Lambda functions, you can actually now build your Lambda functions also on Ubuntu, DBN or Alpine or whatever else. And so that also gives you a lot more functionality and flexibility. You can use the same Linux distribution, maybe across your entire suite, be it on-prem or anywhere else.Jeremy: Right. Right.Julian: And the two little components, there's an interface client, what you install, it's just another Docker layer. And that's that runtime API shim that talks to the runtime API. And then there's a runtime interface emulator and that's the thing that pretends to be Lambda, so you can shunt those events between HTTP and JSON. And that's the thing you would use to run locally. So runtime interface client means you can use any Linux distribution at the runtime interface client and you're compatible with Lambda, and then the interface emulators, what you would use for local testing, or if you want to spread your wings and run your Lambda functions elsewhere.Jeremy: Right. Awesome. Okay. So the other thing I think that container support does, I think it opens up a broader set of, or I guess a larger audience of people who are familiar with containerization and how that works, bringing those two Lambda functions. And one of the things that you really don't get when you run a container, I guess, on EC2, or, not EC2, I'm sorry, ECS, or Fargate or something like that, without kind of adding another layer on top of it, is the eventing aspect of it. I mean, Lambda just is naturally an event driven, a compute layer, right? And so, eventing and this idea of event driven applications and so forth has just become much more popular and I think much more mainstream. So what are your thoughts? What are you seeing in terms of, especially working with so many customers and businesses that are using this now, how are you seeing this sort of evolution or adoption of event driven applications?Julian: Yeah. I mean, it's quite funny to think that actually the event of an application was the genesis of Lambda rather than it being Serverless. I mentioned earlier about starting with S3. Yeah, the whole crux of Lambda has been, I respond to an event of an API gateway, or something on SQS, or via the API or anything. And so the whole point in a way of Lambda has been this event driven computing, which I think people are starting to sort of understand in a bigger thing than, "Oh, this is just the way you have to do Lambda." Because, I do think that serverless has a unique challenge where there is a new conceptual learning maybe that you have to go through. And one other thing that holds back service development is, people are used to a client's server and maybe ports and sockets. And even if you're doing containers or on-prem, or EC2, you're talking IP addresses and load balances, and sockets and firewalls, and all this kind of thing.But ultimately, when we're building these applications that are going to be composed of multiple services talking together through using APIs and events, the events is actually going to be a super part of it. And I know he is, not for so much longer, but my ultimate boss, but I can blame Jeff Bezos just a little bit, because he did say that, "If you want to talk via anything, talk via an API." And he was 100% right and that was great. But now we're sort of evolving that it doesn't just have to be an API and it doesn't have to be something behind API gateway or some API that you can run. And you can use the sort of power of events, particularly in an asynchronous model to not just be "forced" again in inverted commas to use APIs, but have far more flexibility of how data and information is going to flow through, maybe not just your application, but your suite of applications, or to and from your partners, or where that is.And ultimately authentications are going to be distributed, and maybe that is connecting to partners, that could be SaaS partners, or it's going to be an on-prem component, or maybe things in other kind of places. And those things need to communicate. And so the way of thinking about events is a super powerful way of thinking about that.Jeremy: Right. And it's not necessarily new. I mean, we've been doing web hooks for quite some time. And that idea of, something is going to happen somewhere and I want to be notified of it, is again, not a new concept. But I think certainly the way that it's evolved with Lambda and the way that other FaaS products had done eventing and things like that, is just those tight integrations and just all of the, I guess, the connective tissue that runs between those things to make sure that the events get delivered, and that you can DLQ them, and you can do all these other things with retries and stuff like that, is pretty powerful.I know you have, I actually just mentioned this on the last episode, about one of my favorite books, I think that changed my thinking and really got me thinking about how microservices communicate with one another. And that was Building Microservices by Sam Newman, which I actually said was sort of like my Bible for a couple of years, yes, I use that. So what are some of the other, like I know you have a favorite book on this.Julian: Well, that Building Microservices, Sam Newman, and I think there's a part two. I think it's part two, or there's another one ...Jeremy: Hopefully.Julian: ... in the works. I think even on O'Riley's website, you can go and see some preview copies of it. I actually haven't seen that. But yeah, I mean that is a great kind of Bible talking. And sometimes we do conflate this microservices things with a whole bunch of stuff, but if you are talking events, you're talking about separating things. But yeah, the book recommendation I have is one called Flow Architectures by James Urquhart. And James Urquhart actually works with VMware, but he's written this book which is looking sort of at the current state and also looking into the future about how does information flow through our applications and between companies and all this kind of thing.And he goes into some of the technology. When we talk about flow, we are talking about streams and we're talking about events. So streams would be, let's maybe put some AWS words around it, so streams would be something like Kinesis and events would be something like EventBridge, and topics would be SNS, and SQS would be queues. And I know we've got all these things and I wish some clever person would create the one flow service to rule them all, but we're not there. And they've got also different properties, which are helpful for different things and I know confusingly some of them merge. But James' sort of big idea is, in the future we are going to be able to moving data around between businesses, between applications. So how can we think of that as a flow? And what does that mean for designing applications and how we handle that?And Lambda is part of it, but even more nicely, I think is even some of the native integrations where you don't have to have a Lambda function. So if you've got API gateway talking to Step Functions directly, for example, well, that's even better. I mean, you don't have any code to manage and if it's certainly any code that I've written, you probably don't want to manage it. So yeah. I mean this idea of flow, Lambda's great for doing some of this moving around. But we are even evolving to be able to flow data around our applications without having to do anything and just wire up some things in a console or in a terminal.Jeremy: Right. Well, so you mentioned, someone could build the ultimate sort of flow control system or whatever. I mean, I honestly think EventBridge is very close to that. And I actually had Mike Deck on the show. I think it was like episode five. So two years ago, whenever it was when the show came out. I mean, when EventBridge came out. And we were talking and I sort of made the joke, I'm like, so this is like serverless web hooks, essentially being able, because there was the partner integrations where partners could push events onto an event bus, which they still can do. But this has evolved, right? Because the issue was always sort of like, I would have to subscribe to web books, I'd have to build a web hook to get events from a particular company. Which was great, always worked fine, but you're still maintaining that infrastructure.So EventBridge comes along, it creates these partner integrations and now you can just push an event on that now your applications, whether it's a Lambda function or other services, you can push them to an SQS queue, you can push them into a Kinesis stream, all these different destinations. You can go ahead and pull that data in and that's just there. So you don't have to worry about maintaining that infrastructure. And then, the EventBridge team went ahead and released the destination API, I think it's called.Julian: Yeah, API destinations.Jeremy: Event API destinations, right, where now you can set up these integrations with other companies, so you don't even have to make the API call yourself anymore, but instead you get all of the retries, you get the throttling, you get all that stuff kind of built in. So I mean, it's just really, really interesting where this is going. And actually, I mean, if you want to take a second to tell people about EventBridge API destinations, what that can do, because I think that now sort of creates both sides of that equation for you.Julian: It does. And I was just thinking over there, you've done a 10 times better job at explaining API destinations than I have, so you've nailed it on the head. And packet is that kind of simple. And it is just, events land up in your EventBridge and you can just pump events to any arbitrary endpoint. So it doesn't have to be in AWS, it can be on-prem. It can be to your Raspberry PI, it can literally be anywhere. But it's not just about pumping the events over there because, okay, how do we handle failover? And how do we handle over throttling? And so this is part of the extra cool goodies that came with API destinations, is that you can, for instance, if you are sending events to some external API and you only licensed for 1,000 invocations, not invocations, that could be too Lambda-ish, but 1,000 hits on the API every minute.Jeremy: Quotas. I think we call them quotas.Julian: Quotas, something like that. That's a much better term. Thank you, Jeremy. And some sort of quota, well, you can just apply that in API destinations and it'll basically store the data in the meantime in EventBridge and fire that off to the API destination. If the API destination is in that sort of throttle and if the API destination is down, well, it's going to be able to do some exponential back-off or calm down a little bit, don't over-flood this external API. And then eventually when the API does come back, it will be able to send those events. So that does just really give you excellent power rather than maintaining all these individual API endpoints yourself, and you're not handling the availability of the endpoint API, but of whatever your code is that needs to talk to that destination.Jeremy: Right. And I don't want to oversell this to anybody, but that also ...Julian: No, keep going. Keep going.Jeremy: ... adds the capability of enhanced security, because you're not exposing those API keys to your developers or anybody else, they're all baked in and stored within, the API destinations or within an EventBridge. You have the ability, you mentioned this idea of not needing Lambda to maybe talk directly, API gateway to DynamoDB or to step function or something like that. I mean, the cool thing about this is you do have translation capabilities, or transformation capabilities in EventBridge where you can transform the event. I haven't tried this, but I'm assuming it's possible to say, get an event from Salesforce and then pipe it into Stripe or some other API that you might want to pipe it into.So I mean, just that idea of having that centralized bus that can communicate with all these different things. I mean, we're talking about distributed systems here, right? So why is it different sending an event from my microservice A to my microservice B? Why can't I send it from my microservice A to company-wise, microservice B or whatever? And being able to do that in a secure, reliable, just with all of that stuff kind of built in for you, I think it's amazing. So I love EventBridge. To me EventBridge is one of those services that rivals Lambda. It's as, I guess as important as Lambda is, in this whole serverless equation.Julian: Absolutely, Jeremy. I mean, I'm just sitting here. I don't actually have to say anything. This is a brilliant interview and Jeremy, you're the expert. And you're just like laying down all of the excellent use cases. And exactly it. I mean, I like to think we've got sort of three interlinked services which do three different things, but are awesome. Lambda, we love if you need to do some processing or you need to do something that's literally your business logic. You've got EventBridge that can route data from in and out of SaaS partners to any other kind of API. And then you've got Step Functions that can do some coordination. And they all work together, but you've got three different things that really have sort of superpowers in terms of the amount of stuff you can do with it. And yes, start with them. If you land up bumping up against any kind of things that it doesn't work, well, first of all, get in touch with me, I'll work on that.But then you can maybe start thinking about, is it containers or EC2, or that kind of thing? But using literally just Lambda, Step Functions and EventBridge, okay. Yes, maybe you're going to need some queues, topics and APIs, and that kind of thing. But ...Jeremy: I was just going to say, add DynamoDB in there for some permanent state or for some data persistence. Right? Yeah. But other than that, no, I think you nailed it. Honestly, sometimes you're starting to build applications and yeah, you're right. You maybe need a queue here and there and things like that. But for the most part, no, I mean, you could build a lot with those three or four services.Julian: Yeah. Well, I mean, even think of it what you used to do before with API destinations. Maybe you drop something on a queue, you'd have Lambda pull that from a queue. You have Lambda concurrency, which would be set to five per second to then send that to an external API. If it failed going to that API, well, you've got to then dump it to Lambda destinations or to another SQS queue. You then got something ... You know, I'm going down the rabbit hole, or just put it on EventBridge ...Jeremy: You just have it magically happen.Julian: ... or we talk about removing serverless infrastructure, not normal infrastructure, and just removing even the serverless bits, which is great.Jeremy: Yeah, no. I think that's amazing. So we talked about a couple of these different services, and we talked about packaging formats and we talked about event driven applications, and all these other things. And a lot of this stuff, even though some of it may be familiar and you could probably equate it or relate it to things that developers might already know, there is still a lot of new stuff here. And I think, my biggest complaint about serverless was not about the capabilities of it, it was basically the education and the ability to get people to adopt it and understand the power behind it. So let's talk about that a little bit because ... What's that?Julian: It sounds like my job description, perfectly.Jeremy: Right. So there we go. Right, that's what you're supposed to be doing, Julian. Why aren't you doing it? No, but you are doing it. You are doing it. No, and that's why I want to talk to you about it. So you have that series on the Well-Architected Framework and we can talk about that. There's a whole bunch of really good resources on this. Obviously, you're doing videos and conferences, well, you used to be doing conferences. I think you probably still do some of those virtual ones, right? Which are not the same thing.Julian: Not quite, no.Jeremy: I mean, it was fun seeing you in Cardiff and where else were you?Julian: Yeah, Belfast.Jeremy: Cardiff and Northern Ireland.Julian: Yeah, exactly.Jeremy: Yeah, we were all over the place together.Julian: With the Guinness and all of us. It was brilliant.Jeremy: Right. So tell me a little bit about, sort of, the education process that you're trying to do. Or maybe even where you sort of see the state of Serverless education now, and just sort of where it's evolved, where we're getting best practices from, what's out there for people. And that's a really long question, but I don't know, maybe you can distill that down to something usable.Julian: No, that's quite right. I'm thinking back to my extensions explanation, which is a really long answer. So we're doing really long stuff, but that's fine. But I like to also bring this back to also thinking about the people aspect of IT. And we talk a lot about the technology and Lambda is amazing and S3 is amazing and all those kinds of things. But ultimately it is still sort of people lashing together these services and building the serverless applications, and deciding what you even need to do. And so the education is very much tied with, of course, having the products and features that do lots of kinds of things. And Serverless, there's always this lever, I suppose, between simplicity and functionality. And we are adding lots of knobs and levers and everything to Lambda to make it more feature-rich, but we've got to try and keep it simple at the same time.So there is sort of that trade-off, and of course with that, that obviously means not just the education side, but education about Lambda and serverless, but generally, how do I build applications? What do I do? And so you did mention the Well-Architected Framework. And so for people who don't know, this came out in 2015, and in 2017, there was a Serverless Lens which was added to it; what is basically serverless specific information for Well-Architected. And Well-Architected means bringing best practices to serverless applications. If you're building prod applications in the cloud, you're normally looking to build and operate them following best practices. And this is useful stuff throughout the software life cycle, it's not just at the end to tick a few boxes and go, "Yes, we've done that." So start early with the well-architected journey, it'll help you.And just sort of answer the question, am I well architected? And I mean, that is a bit of a fuzzy, what is that question? But the idea is to give you more confidence in the architecture and operations of your workloads, and that's not a goal it's in, but it's to reduce and minimize the impact of any issues that can happen. So what we do is we try and distill some of our questions and thoughts on how you could do things, and we built that into the Well-Architected Framework. And so the ServiceLens has a few questions on its operational excellence, security, reliability, performance, efficiency, and cost optimization. Excellent. I knew I was going to forget one of them and I didn't. So yeah, these are things like, how do you control access to an API? How do you do lifecycle management? How do you build resiliency into your application? All these kinds of things.And so the Well-Architected Framework with Serverless Lens there's a whole bunch of guidance to help you do that. And I have been slowly writing a blog series to literally cover all of the questions, they're nine questions in the Well-Architected Serverless Lens. And I'm about halfway through, and I had to pause because we have this little conference called re:Invent, which requires one or two slides to be created. But yeah, I'm desperately keen to pick that up again. And yeah, that's just providing some really and sort of more opinionated stuff, because the documentation is awesome and it's very in-depth and it's great when you need all that kind of stuff. But sometimes you want to know, well, okay, just tell me what to do or what do you think is best rather than these are the seven different options.Jeremy: Just tell me what to do.Julian: Yeah.Jeremy: I think that's a common question.Julian: Exactly. And I'll launch off from that to mention my colleague, James Beswick, he writes one or two things on serverless ...Jeremy: Yeah, I mean, every once in a while you see something from it. Yeah.Julian: ... every day. The Besbot machine of serverless. He's amazing. James, he's so knowledgeable and writes like a machine. He's brilliant. Yeah, I'm lucky to be on his team. So when you talk about education, I learn from him. But anyway, in a roundabout way, he's created this blog series and other series called the Lambda Operations Guide. And this is literally a whole in-depth study on how to operate Lambda. And it goes into a whole bunch of things, it's sort of linked to the Serverless Lens because there are a lot of common kind of stuff, but it's also a great read if you are more nerdily interested in Lambda than just firing off a function, just to read through it. It's written in an accessible way. And it has got a whole bunch of information on how to operate Lambda and some of the stuff under the scenes, how to work, just so you can understand it better.Jeremy: Right. Right. Yeah. And I think you mentioned this idea of confidence too. And I can tell you right now I've been writing serverless applications, well, let's see, what year is it? 2021. So I started in 2015, writing or building applications with Lambda. So I've been doing this for a while and I still get to a point every once in a while, where I'm trying to put something in cloud formation or I'm using the Serverless Framework or whatever, and you're trying to configure something and you think about, well, wait, how do I want to do this? Or is this the right way to do it? And you just have that moment where you're like, well, let me just search and see what other people are doing. And there are a lot of myths about serverless.There's as much good information is out there, there's a lot of bad information out there too. And that's something that is kind of hard to combat, but I think that maybe we could end it there. What are some of the things, the questions people are having, maybe some of the myths, maybe some of the concerns, what are those top ones that you think you could sort of ...Julian: Dispel.Jeremy: ... to tell people, dispel, yeah. That you could say, "Look, these are these aren't things to worry about. And again, go and read your blog post series, go and read James' blog post series, and you're going to get the right answers to these things."Julian: Yeah. I mean, there are misconceptions and some of them are just historical where people think the Lambda functions can only run for five minutes, they can run for 15 minutes. Lambda functions can also now run up to 10 gig of RAM. At re:Invent it was only 3 gig of RAM. That's a three times increase in Lambda functions within a three times proportional increase in CPU. So I like to say, if you had a CPU-intensive job that took 40 minutes and you couldn't run it on Lambda, you've now got three times the CPU. Maybe you can run it on Lambda and now because that would work. So yeah, some of those historical things that have just changed. We've got EFS for Lambda, that's some kind of thing you can't do state with Lambda. EFS and NFS isn't everybody's cup of tea, but that's certainly going to help some people out.And then the other big one is also cold starts. And this is an interesting one because, obviously we've sort of solved the cold start issue with connecting Lambda functions to VPC, so that's no longer an issue. And that's been a barrier for lots of people, for good reason, and that's now no longer the case. But the other thing for cold starts is interesting because, people do still get caught up at cold starts, but particularly for development because they create a Lambda function, they run it, that's a cold start and then update it and they run it and then go, oh, that's a cold start. And they don't sort of grok that the more you run your Lambda function the less cold starts you have, just because they're warm starts. And it's literally the number of Lambda functions that are running at exactly the same time will have a cold start, but then every subsequent Lambda function invocation for quite a while will be using a warm function.And so as it ramps up, we see, in the small percentages of cold starts that are actually going to happen. And when we're talking again about the container image support, that's got a whole bunch of complexity, which people are trying to understand. Hopefully, people are learning from this podcast about that as well. But also with the cold starts with that, those are huge and they're particular ways that you can construct your Lambda functions to really reduce those cold starts, and it's best practices anyway. But yeah, cold starts is also definitely one of those myths. And the other one ...Jeremy: Well, one note on cold starts too, just as something that I find to be interesting. I know that we, I even had to spend time battling with that earlier on, especially with VPC cold starts, that's all sort of gone away now, so much more efficient. The other thing is like provision concurrency. If you're using provision concurrency to get your cold starts down, I'm not even sure that's the right use for provision concurrency. I think provision concurrency is more just to make sure you have enough capacity because of the ramp-up time for Lambda. You certainly can use it for cold starts, but I don't think you need to, that's just my two cents on that.Julian: Yeah. No, that is true. And they're two different use cases for the same kind of thing. Yeah. As you say, Lambda is pretty scalable, but there is a bit of a ramp-up to get up to many, many, many, many thousands or tens of thousands of concurrent executions. And so yeah, using provision currency, you can get that up in advance. And yeah, some people do also use it for provision concurrency for getting those cold starts done. And yet that is another very valid use case, but it's only an issue for synchronous workloads as well. Anything that is synchronous you really shouldn't be carrying too much. Other than for cost perspective because it's going to take longer to run.Jeremy: Sure. Sure. I have a feeling that the last one you were going to mention, because this one bugs me quite a bit, is this idea of no ops or some people call it ops-less, which I think is kind of funny. But that's one of those things where, oh, it drives me nuts when I hear this.Julian: Yeah, exactly. And it's a frustrating thing. And I think often, sometimes when people are talking about no ops, they either have something to sell you. And sometimes what they're selling you is getting rid of something, which never is the case. It's not as though we develop serverless applications and we can then get rid of half of our development team, it just doesn't work like that. And it's crazy, in fact. And when I was talking about the people aspect of IT, this is a super important thing. And me coming from an infrastructure background, everybody is dying in their jobs to do more meaningful work and to do more interesting things and have the agility to try those experiments or try something else. Or do something that's better or even improve the way your build or improve the way your CI/CD pipeline runs or anything, rather than just having to do a lot of work in the lower levels.And this is what serverless really helps you do, is to be able to, we'll take over a whole lot of the ops for you, but it's not all of the ops, because in a way there's never an end to ops. Because you can always do stuff better. And it's not just the operations of deploying Lambda functions and limits and all that kind of thing. But I mean, think of observability and not knowing just about your application, but knowing about your business. Think of if you had the time that you weren't just monitoring function invocations and monitoring how long things were happening, but imagine if you were able to pull together dashboards of exactly what each transaction costs as it flows through your whole entire application. Think of the benefit of that to your business, or think of the benefit that in real-time, even if it's on Lambda function usage or something, you can say, "Well, oh, there's an immediate drop-off or pick-up in one region in the world or one particular application." You can spot that immediately. That kind of stuff, you just haven't had time to play with to actually build.But if we can take over some of the operational stuff with you and run one or two or trillions of Lambda functions in the background, just to keep this all ticking along nicely, you're always going to have an opportunity to do more ops. But I think the exciting bit is that ops is not just IT infrastructure, plumbing ops, but you can start even doing even better business ops where you can have more business visibility and more cool stuff for your business because we're not writing apps just for funsies.Jeremy: Right. Right. And I think that's probably maybe a good way to describe serverless, is it allows you to focus on more meaningful work and more meaningful tasks maybe. Or maybe not more meaningful, but more impactful on the business. Anyways, Julian, listen, this was a great conversation. I appreciate it. I appreciate the work that you're doing over at AWS ...Julian: Thank you.Jeremy: ... and the stuff that you're doing. And I hope that there will be a conference soon that we will be able to attend together ...Julian: I hope so too.Jeremy: ... maybe grab a drink. So if people want to get a hold of you or find out more about serverless and what AWS is doing with that, how do they do that?Julian: Yeah, absolutely. Well, please get hold of me anytime on Twitter, is the easiest way probably, julian_wood. Happy to answer your question about anything Serverless or Lambda. And if I don't know the answer, I'll always ask Jeremy, so you're covered twice over there. And then, three different things. James is, if you're talking specifically Lambda, James Beswick's operations guide, have a look at that. Just so much nuggets of super information. We've got another thing we did just sort of jump around, you were talking about cloud formation and the spark was going off in my head. We have something which we're calling the Serverless Patterns Collection, and this is really super cool. We didn't quite get to talk about it, but if you're building applications using SAM or serverless application model, or using the CDK, so either way, we've got a whole bunch of patterns which you can grab.So if you're pulling something from S3 to Lambda, or from Lambda to EventBridge, or SNS to SQS with a filter, all these kind of things, they're literally copy and paste patterns that you can put immediately into your cloud formation or your CDK templates. So when you are down the rabbit hole of Hacker News or Reddit or Stack Overflow, this is another resource that you can use to copy and paste. So go for that. And that's all hosted on our cool site called serverlessland.com. So that's serverlessland.com and that's an aggregation site that we run because we've got video talks, and we've got blog posts, and we've got learning path series, and we've got a whole bunch of stuff. Personally, I've got a learning path series coming out shortly on Lambda extensions and also one on Lambda observability. There's one coming out shortly on container image supports. And our team is talking all over as many things as we can virtually. I'm actually speaking about container images of DockerCon, which is coming up, which is exciting.And yeah, so serverlessland.com, that's got a whole bunch of information. That's just an easy one-stop-shop where you can get as much information about AWS services as you can. And if not yet, get in touch, I'm happy to help. I'm happy to also carry your feedback. And yeah, at the moment, just inside, we're sort of doing our planning for the next cycle of what Lambda and what all the service stuff we're going to do. So if you've got an awesome idea, please send it on. And I'm sure you'll be super excited when something pops out in the near issue, maybe just in future for a cool new functionality you could have been involved in.Jeremy: Well, I know that serverlessland.com is an excellent resource, and it's not that the AWS Compute blog is hard to parse through or anything, but serverlessland.com is certainly a much easier resource to get there. S

Last month we hosted Ven Dr Lyndon Drake and Maxim Institute Senior Researcher Julian Wood at the MIC 13 event | On debt, our COVID-19 recovery, and where to from here? This podcast is a recording of the event, including the audience Q+A, so sound quality isn't our usual standard. Julian and Lyndon both make valuable contributions arguing and discussing New Zealand's debt, government responses to COVID-19, the housing crisis, interest rates, and the K-shaped recovery. We hope you enjoy the listen as much as we enjoyed the event. Head to our website at www.maxim.org.nz/sign-up to register for event emails so you don't miss out.

Today's Day Two Cloud podcast is a thorough introduction to AWS Lambda, which is AWS's serverless compute service. We discuss how Lamdba works, what it can do, use cases, and more. Our guide for today's conversation is Julian Wood, Senior Developer Advocate for the Serverless Product Group at AWS. This is not a sponsored show.

Today's Day Two Cloud podcast is a thorough introduction to AWS Lambda, which is AWS's serverless compute service. We discuss how Lamdba works, what it can do, use cases, and more. Our guide for today's conversation is Julian Wood, Senior Developer Advocate for the Serverless Product Group at AWS. This is not a sponsored show.

Today's Day Two Cloud podcast is a thorough introduction to AWS Lambda, which is AWS's serverless compute service. We discuss how Lamdba works, what it can do, use cases, and more. Our guide for today's conversation is Julian Wood, Senior Developer Advocate for the Serverless Product Group at AWS. This is not a sponsored show.

Today's Day Two Cloud podcast is a thorough introduction to AWS Lambda, which is AWS's serverless compute service. We discuss how Lamdba works, what it can do, use cases, and more. Our guide for today's conversation is Julian Wood, Senior Developer Advocate for the Serverless Product Group at AWS. This is not a sponsored show. The post Day Two Cloud 092: What AWS Lambda Is Good For appeared first on Packet Pushers.

Today's Day Two Cloud podcast is a thorough introduction to AWS Lambda, which is AWS's serverless compute service. We discuss how Lamdba works, what it can do, use cases, and more. Our guide for today's conversation is Julian Wood, Senior Developer Advocate for the Serverless Product Group at AWS. This is not a sponsored show. The post Day Two Cloud 092: What AWS Lambda Is Good For appeared first on Packet Pushers.

Today's Day Two Cloud podcast is a thorough introduction to AWS Lambda, which is AWS's serverless compute service. We discuss how Lamdba works, what it can do, use cases, and more. Our guide for today's conversation is Julian Wood, Senior Developer Advocate for the Serverless Product Group at AWS. This is not a sponsored show. The post Day Two Cloud 092: What AWS Lambda Is Good For appeared first on Packet Pushers.

Julian wood is a Senior Developer Advocate for the Serverless Product Group at AWS.  We discuss lots of great stuff around the serverless platforms, transforming IT (yes DIgital Transformation is real) and transitioning careers and methods from "traditional" Ops to new was of operating your environment. Check out lots of AWS Serverless resources here at https://serverlessland.com  Follow Julian on Twitter here:  https://twitter.com/julian_wood  This episode is sponsored by Veeam Software and the 4-Step Guide to Delivering Extraordinary Software Demos that Win Deals

Ben catches up with Power hitting coach Julian Wood. Julian discusses his theories and how he coaches some of the leading T20 players across the world. Where to find Guernsey Cricket Online LinkedIn -https://www.linkedin.com/company/guernsey-cricket-board/ Twitter -https://twitter.com/guernseycricket Facebook - https://www.facebook.com/guernseycricket Instagram -https://www.instagram.com/guernseycricket YouTube - https://www.youtube.com/channel/UCFiW9PhroVLRGhrT5_NfatQ *Website - *www.guernseycricket.com

In this podcast I am joined by Julian Wood.  A former professional cricketer who was a naturally attacking. He now coaches cricketers all around the world to not only hit the ball further, but also bat better in general. He has worked with individuals like Carlos Brathwaite (West Indies) and Sam Billings (England) as well as with teams like… England, Australia, Dolphins in South Africa. Connect with Julian: Website: http://www.jwcricketacademy.com Email: coach@jwcricket.com

Andrew McKenna and the former England bowler Steve Harmison look back at the first week of the 2020 Indian Premier League. They are joined by power hitting consultant Julian Wood to look at the art of hitting the ball a long way, review the performances of the English players, and hear from the Rajasthan Royals all-rounder Tom Curran. See acast.com/privacy for privacy and opt-out information.

Last month we released Julian's latest research paper on Active Labour Market Policies, looking at the ways that government can spend money to try to save or create jobs for people. Our conversation covers Julian’s thoughts on how effect this Government’s response has been, what the next government should focus on to try to stem unemployment, and more broadly, where he thinks the economy is going and how long we’ll take to recover. Enjoy the listen

The Maxim Institute has researched how government led Active Labour Market Policies work in real terms. Report author and economist, Julian Wood, talks to Jesse about the research.

A wake up call.That's how the Auditor-General's report into the management of the Provincial Growth Fund is being described.It recommends MBIE  evaluates its effectiveness - to make sure what's planned and what's achieved,  match up.Maxim Institute senior researcher Julian Wood told Kate Hawkesby regional policy is not bad policy, but it needs to be done well - and at the moment, it isn't."It says we don't know what the PGF money is being spent on, and whether it's going to make a difference."Wood says it's a loss for the regions, in what the project could've been."Every dollar wasted on the PGF is a dollar we could've spent on education or health in the regions."LISTEN ABOVE 

Dying towns, urban drift, housing crisis, and immigration: over the last five years, Senior Researcher Julian Wood has been digging into some of the big topics that face New Zealand now and over the coming decades. In this podcast, Jeremy Vargo talks with Julian about the big picture issues that create the context for his research, and what New Zealand should do to change regional development and migration for the better. Click to listen to the whole episode.

A call for an overhaul of the way we invite and welcome immigrants to this country.Conservative think tank the Maxim Institute has put forward nine ways we can do this.They include expanding the existing welcoming programme, teaching history to adult migrants and providing formal sports programmes for migrants' children.Spokesman Julian Wood told Kate Hawkesby we need to put a freeze on the level of temporary work visa approvals.He says it's not good enough to continue the way we're going."This over-reliance on temporary workers is having an impact on productivity, is creating conditions for migrant worker exploitation and means there's mutual under-investment by workers, firms and communities."LISTEN ABOVE

Julian Wood has added power and guile to some of the biggest names in cricket. You can win a batting masterclass to add sixes to your season! Julian Wood is a former Hampshire batsman who now coaches the very best in the world to hit the ball with power and find the angles to maximise their scoring in the shorter forms of the game. [**ENTER HERE**](http://proatar.com/win/)

It's a coaching special on the Cricket Badger Radio Show Podcast this week as James Buttler is joined by power hitting coach Julian Wood and Christy Kulasingam. Julian Wood is a former Hampshire batsman who now coaches the very best in the world to hit the ball with power and find the angles to maximise their scoring in the shorter forms of the game. Christy Kulasingam is the co-founder of a new coaching app which will be launched on 15 September. The Proatar app allows cricketers of any standard to upload footage of their game to get personalised coaching tips from some of the best cricketers and coaches around. And, Christy and Julian have kindly donated themselves as a prize to one lucky winner who will get a free Proatar coaching masterclass with the powerhitting maestro. Do you want more power in your game? [**ENTER THE COMPETITION TO WIN A PROATAR POWER HITTING SESSION WITH JULIAN WOOD HERE**](http://proatar.com/win/) All here in the Cricket Badger Radio Show Podcast! Contact the show via Twitter on @cricket_badger or email us at cricketbadger@hotmail.com. Also send us your recorded audio for our new Letters Page feature. Get something off your chest in less than a minute, email it in and you could well find yourself on the Podcast next week!

In the latest episode of Cloud Insiders, Insight’s Pre-Sales Manager for Hybrid Cloud, Chan Ekanayake and Chief Technologist of WoodITWork.com, Julian Wood join us for an interesting discussion on Serverless Computing. Our guests explore the pain points and trends driving its adoption, how it compares with other forms of utility computing, and identify the benefits that its implementation could ensure for organisations. Chan and Julian also address how a serverless approach is beneficial in relation to IoT (Internet of Things) applications, and how businesses are leveraging serverless computing platforms. Our guests also discuss why, having been around for over a decade, serverless computing is only becoming mainstream now, as well as the role that microservices can play within the serverless space. See acast.com/privacy for privacy and opt-out information.

So, lets get 2015 started with an episode recorded way back in 2014. We're sorry about the delay, but this one needed some time to simmer. After all, one of our guests ends up singing. To find out which of our two guests, Julian Wood and Matthew Northam, channel his inner Beyoncé, you'll just have to […] The post vSoup Filer Swinger Parties #53 first appeared on vSoup.

vSoup Episode #3 is now available! If the normal dose of Chris, Ed and Christian isn't enough, this time we brought on a guest as well: Julian Wood who blogs over at WoodITWork.com Episode #3 Linkware: Digital Ship Scandinavia – 2 & 3 February 2011 UK London VMware User Group: Designing a Virtual Infrastructure that […] The post vSoup on the Desktop – Episode #3 first appeared on vSoup.