Podcast appearances and mentions of adrian cockcroft

Analyst roundtable with Adrian Cockcroft, Stephen Perrenod, Chris Kruell, and Shahin Khan. In this episode: Tariffs and how companies are or should be approaching them, The Triffin Dilemma, Strategic Bitcoin Reserve, FinTech software around BTC, Turing Complete smart contract languages, AI Chips, Intel, Nvidia, TSMC, AI pricing, Data Center carbon footprint, Green Software Foundation. [audio mp3="https://orionx.net/wp-content/uploads/2025/04/OXD028_ART_Tariffs_AI-Chips_BTC-Reserve_AI-Pricing_DC-Carbon_20250428.mp3"][/audio] The post Analyst Roundtable: Tariffs, AI Chips, BTC Reserve, AI Pricing, DC Carbon – OXD28 appeared first on OrionX.net.

Analyst roundtable with Adrian Cockcroft, Stephen Perrenod, Chris Kruell, and Shahin Khan covering recent advances in, and impacts of: GPUs, including a post-view of the GTC conference, AI DataCenters, Quantum Computing, Bitcoin, and China. [audio mp3="https://orionx.net/wp-content/uploads/2025/04/OXD027_ART_GPUs_Quantum_Crypto_China_20250408.mp3"][/audio] The post Analyst Roundtable: GPUs, AI, Quantum, Bitcoin, China – OXD27 appeared first on OrionX.net.

Analyst roundtable with Adrian Cockcroft, Stephen Perrenod, Chris Kruell, and Shahin Khan covering recent advances in, and impacts of: Chips, AI, Search, Quantum Computing, Bitcoin, and Fusion energy. [audio mp3="https://orionx.net/wp-content/uploads/2025/03/OXD026_AR_Chips-AI-Search-Quantum-Bitcoin-Fusion_20250310.mp3"][/audio] The post Analyst Roundtable: Chips, AI, Search, Quantum, Bitcoin, Fusion – OXD26 appeared first on OrionX.net.

Review of SC24, RISC-V Summit, and AWS Reinvent. Topics include: HPC and AI Clouds, CXL, Liquid Cooling, Optical Interconnects, Optical Computing, Novel CPUs and GPUs, the state of RISC-V in servers and supercomputers, TOP500, Chiplets, AWS CPU and GPU strategies. [audio mp3="https://orionx.net/wp-content/uploads/2025/01/095@HPCpodcast_SP_Adrian-Cockcroft_SC24-RISCV_AWS-Reinvent-Q2B-Events_20250108.mp3"][/audio] The post @HPCpodcast-95: Adrian Cockcroft on SC24, RISC-V Summit, AWS Reinvent appeared first on OrionX.net.

We have a full house with Adrian Cockcroft, Stephen Perrenod, Chris Kruell, and Shahin Khan with a "postview" of the SC24 conference, the latest CryptoSuper500 list, a snapshot of quantum computing, and the RISC-V Summit. They also discuss Bitcoin, AI vs. HPC, HPC in the cloud, liquid cooling, InfraTech, Interconnects, Optical Computing, OpenMP, PCIe, CXL, GPUs, CPUs, and energy efficiency and ESG. [audio mp3="https://orionx.net/wp-content/uploads/2024/12/OXD025_SC24-Postview_CryptoSuper500_Quantum_RISCV-Summit_20241216.mp3"][/audio] The post SC24, Supercomputing, CryptoSuper500, Quantum, RISC-V Summit – OXD25 appeared first on OrionX.net.

In this special episode of Book Overflow, Carl Brown (of the YouTube channel Internet of Bugs) joins Carter and Nathan to share some of his favorite books! Carl is incredibly well read and shares which books have influenced him over his very impressive 35 year career. 00:00 Intro 02:17 How did Internet of Bugs come to be? 06:03 Why still read tech books? 08:32 Mythical Man-Month 14:40 Philosophy of Software Design, TCL/TK, 25:56 Advanced Programming in Unix and TCP/IP Illustrated 32:32 How important is it to be well-versed in Unix? 42:27 Freelance, Business, and Consulting book recommendations 52:57 Lightning Round: Managing your programming career, philosophy, and general advice 01:02:34 Final Thoughts -- Books Mentioned in this Episode -- Note: As an Amazon Associate, we earn from qualifying purchases. ---------------------------------------------------------- App Accomplished: Strategies for App Development Success 1st Edition, Kindle Edition by Carl Brown https://amzn.to/473mG9C (paid link) Mythical Man-Month, The: Essays on Software Engineering, Anniversary Edition Anniversary Edition by Frederick Brooks Jr. https://amzn.to/3XnDhlm (paid link) A Philosophy of Software Design, 2nd Edition by John Ousterhout https://amzn.to/473OISA (paid link) Tcl and the Tk Toolkit 1st Edition by John K. Ousterhout https://amzn.to/3X7sdHX (paid link) Advanced Programming in the Unix Environment by W. Richard Stevens https://amzn.to/477PayZ (paid link) TCP/IP Illustrated, Vol. 1: The Protocols by W. Richard Stevens https://amzn.to/3T6ZFgo (paid link) {Carl says Volumes 2 and 3 are great, too} Sun Performance and Tuning: Java and the Internet (2nd Edition) Subsequent Edition by Adrian Cockcroft, Richard Pettit https://amzn.to/3Xkczdt (paid link) Free Agent Nation: How America's New Independent Workers Are Transforming the Way We Live by Daniel H. Pink https://amzn.to/47mhDBD (paid link) The Computer Consultant's Guide: Real-Life Strategies for Building a Successful Consulting Career 2nd Edition by Janet Ruhl https://amzn.to/3T9IT0d (paid link) Getting Started in Consulting by Alan Weiss https://amzn.to/3T7INpY (paid link) The Pragmatic Programmer: From Journeyman to Master by Andrew Hunt and David Thomas https://amzn.to/3T6lvk9 (paid link) The Pragmatic Programmer: 20th Anniversary Edition, 2nd Edition: Your Journey to Mastery by David Thomas, Andrew Hunt, et al. https://amzn.to/3TafdQp (paid link) My Job Went to India (and All I Got Was This Lousy Book): 52 Ways to Save Your Job (Pragmatic Programmers) 1st Edition by Chad Fowler https://amzn.to/3T8ubGu (paid link) Programming Perl by Tom Christiansen, Randal L. Schwartz, et al. https://amzn.to/4g32KYy (paid link) Speed Reading: Third Edition by Tony Buzan https://amzn.to/3X7qCla (paid link) The 7 Habits of Highly Effective People: 30th Anniversary Edition (The Covey Habits Series) by Stephen R. Covey , Jim Collins, et al. https://amzn.to/4geWVYm (paid link) Don't Make Me Think, Revisited: A Common Sense Approach to Web Usability (3rd Edition) by Steve Krug | Dec 24, 2013 https://amzn.to/3X1RRxD (paid link) Database in Depth: Relational Theory for Practitioners by C. J. Date | May 15, 2005 https://amzn.to/3z055D4 (paid link) Joe Celko's SQL for Smarties: Advanced SQL Programming by Joe Celko | Dec 16, 2014 https://amzn.to/4geWYn0 (paid link) Problem Frames and Methods: Analysing and Structuring Software Development Problems Paperback – January 1, 2001 by Michael A. Jackson https://amzn.to/4g6sdjO (paid link) Learning to Classify Text Using Support Vector Machines 2nd Edition by Thorsten Joachims https://amzn.to/3ACf95y (paid link) Driving Technical Change: Why People On Your Team Don't Act On Good Ideas, and How to Convince Them They Should by Terrence Ryan | Dec 28, 2010 https://amzn.to/3MoUpRC (paid link) Understanding Deep Learning by Simon J.D. Prince https://amzn.to/3TafqTH (paid link) As an Amazon Associate, we earn from qualifying purchases.

☁️ What can AWS users achieve today in terms of decarbonization? And what can they expect tomorrow?

This New Stack Makers podcast co-hosted by Alex Williams, TNS founder and publisher, and Adrian Cockcroft, Partner and Analyst at OrionX.net, discussed Nvidia's GH200 Grace Hopper superchip. Industry expert Sunil Mallya, Co-founder and CTO of Flip AI weighed in on how it is revolutionizing the hardware industry for AI workloads by centralizing GPU communication, reducing networking overhead, and creating a more efficient system. Mallya noted that despite its innovative design, challenges remain in adoption due to interface issues and the need for software to catch up with hardware advancements. However, optimism persists for the future of AI-focused chips, with Nvidia leading the charge in creating large-scale coherent memory systems. Meanwhile, Flip AI, a DevOps large language model, aims to interpret observability data to troubleshoot incidents effectively across various cloud platforms. While discussing the latest chip innovations and challenges in training large language models, the episode sheds light on the evolving landscape of AI hardware and software integration.Learn more from The New Stack about Nvidia and the future of chip design  Nvidia Wants to Rewrite the Software Development Stack Nvidia GPU Dominance at a Crossroads Join our community of newsletter subscribers to stay on top of the news and at the top of your game.  

This New Stack Makers podcast co-hosted by Adrian Cockroft, analyst at OrionX.net and TNS founder and publisher, Alex Williams discusses the importance of monitoring services utilizing Large Language Models (LLMs) and the emergence of tools like LangChain and LangSmith to address this need. Adrian Cockcroft, formerly of Netflix and now working with The New Stack, highlights the significance of monitoring AI apps using LLMs and the challenges posed by slow and expensive API calls from LLMs. LangChain acts as middleware, connecting LLMs with services, akin to the Java Database Controller. LangChain's monitoring capabilities led to the development of LangSmith, a monitoring tool. Another tool, LangKit by WhyLabs, offers similar functionalities but is less integrated. This reflects the typical evolution of open-source projects into commercial products. LangChain recently secured funding, indicating growing interest in such monitoring solutions. Cockcroft emphasizes the importance of enterprise-level support and tooling for integrating these solutions into commercial environments. This discussion  underscores the evolving landscape of monitoring services powered by LLMs and the emergence of specialized tools to address associated challenges. Learn more from The New Stack about LangChain: LangChain: The Trendiest Web Framework of 2023, Thanks to AI How Retool AI Differs from LangChain (Hint: It's Automation)  Join our community of newsletter subscribers to stay on top of the news and at the top of your game.  

How can the lessons learned from a childhood of tinkering and a career influenced by tech visionaries like Bill Joy and Andy Bechtolsheim guide us toward a more sustainable future for technology? We're joined today by Adrian Cockcroft, a trailblazer in cloud architecture at Netflix and a proponent of open source at Amazon Web Services, who is now channeling his expertise into the vital cause of sustainability in cloud computing. Adrian shares his journey from the early days of building computers to his influential roles in shaping the tech industry and how these experiences have informed his current focus on sustainability. Together, we can build a future that is not only technologically advanced but also environmentally responsible.Early Career Experiences and InfluenceAdrian shares the experiences that shaped his professional life, especially his time at Sun Microsystems, and the influence of visionaries like Bill Joy and Andy Bechtolsheim. He discusses the power of thinking into the future and anticipating trends. "It was clear [Bill] lived five years in the future... that was one of those inspiring moments." This experience alone highlighted the significance of forward-thinking and the impact it can have on shaping one's career trajectory. It serves as a reminder to embrace curiosity and explore emerging technologies and trends, as they can lead to groundbreaking opportunities and shape the future of industries.The Power of Putting Ideas Out ThereSharing ideas can be transformational. Adrian and Barry, both authors, discuss the importance of writing and publishing, which goes beyond the unique experience of writing a book or the influence it has on the readers. It also shapes and influences their own organizations. Being open and vulnerable might be difficult, but the rewards are priceless. “Everyone should write a book. It's 10 times harder than you think." Putting your ideas out there helps you overcome self-doubt and fear of judgment and embrace the opportunity to contribute your unique perspectives and insights to the broader discourse.Transitioning to a Focus on SustainabilityAdrian doesn't just preach sustainability; he lives it. In addition to his current work, Adrian was also an early adopter of solar panels and electric cars. Professionally, Adrian shares his experience championing these values within AWS and helping his peers understand the importance of transparency and accountability in addressing environmental impact. Companies need to do more than give lip service to a better future. They must also align their actions to those values and actively seek ways to reduce their environmental footprint. Sustainability is not just a buzzword but a fundamental responsibility that requires commitment and action.Challenges in Achieving Sustainability in the CloudBarry and Adrian delve into the challenges faced by companies in achieving sustainability in their technology infrastructure. It's not enough to have accurate measurements and proper reporting of carbon emissions. Organizations must also ensure their supply chain adheres to the same standards and values. Allocation and attribution of carbon emissions on a global scale can be incredibly complex, so if we hope to address emerging climate risks and create a sustainable future, complying with regulations and being transparent is key.The Need for Measurement, Reporting, and ActionOrganizations need to go beyond measurement and reporting. Instead, the actions a company takes to ensure sustainability should be used as a measure of a company's quality and care. Consumers can take an active role in encouraging companies to be sustainable and holding them accountable when they aren't. The mix of regulations, reporting, market demands, and social pressure will cause companies to think about the future of the environment and take action, not just internally but also in their supply chains.ResourcesAdrian Cockcroft on LinkedIn | X(Twitter)

Adrian Cockcroft joins us again after SC23 to discuss TOP500 trends, the AI-HPC crossover, chiplets, and the emergence of UCIe and CXL advancements. Be sure to listen to previous episodes with Adrian; Episode 36 on HPC in cloud and sustainability data and Episode 55 on decarbonization and ESG. [audio mp3="https://orionx.net/wp-content/uploads/2023/11/077@HPCpodcast_Adrian-Cockcrofy_Future-Architectures_20231130.mp3"][/audio] The post @HPCpodcast-77: Adrian Cockcroft on Future Architectures appeared first on OrionX.net.

In an interview with The New Stack, renowned technologist Adrian Cockcroft discussed the process of fine-tuning Large Language Models (LLMs) through prompt engineering. Cockcroft, known for his roles at Netflix and Amazon Web Services, explained how to obtain tailored programming advice from an LLM. By crafting specific prompts like asking the model to provide code in the style of a certain expert programmer, such as Java's James Gosling, users can guide the AI's output.Prompt engineering involves setting up conversations to bias the AI's responses. These prompts are becoming more advanced with plugins and loaded information that shape the model's behavior before use. Cockcroft highlighted the concept of fine-tuning, where models are adapted beyond what a prompt can contain. Companies are incorporating vast amounts of their internal data, like wiki pages and corporate documents, to train the model to understand their specific domain and processes.Cockcroft pointed out the efficacy of ChatGPT within certain tasks, illustrated by his experience using it for data analysis and programming assistance. He also discussed the growing need for improved results from LLMs, which has led to the demand for vector databases. These databases store word meanings as vectors with associated weights, enabling fuzzy matching for enhanced information retrieval from LLMs. In essence, Cockcroft emphasized the multifaceted process of shaping and optimizing LLMs through prompt engineering and fine-tuning, reflecting the evolving landscape of AI-human interactions.Learn more from The New Stack about LLMs and Prompt Engineering:Top 5 Large Language Models and How to Use Them EffectivelyThe Pros (And Con) of Customizing Large Language ModelsPrompt Engineering: Get LLMs to Generate the Content You WantDeveloper Tips in AI Prompt Engineering

In this episode of TWiGS we delve into the intricate world of measuring software energy consumption, a topic vital for reducing our carbon footprint. Despite the strides in greening software, knowing how much energy software consumes remains a challenging puzzle, especially in the cloud computing era. Joining host Chris Adams are guests, Aditya Manglik and Hongyu Hè, graduate students from ETH Zurich in Switzerland. With their expertise in improving energy efficiency in systems, particularly operating systems, microarchitecture, and machine learning, we embark on a captivating journey to understand why quantifying software energy usage is intricate and what innovative solutions are emerging. Stay tuned as we amplify the geek factor to 11 and uncover the complexities of this critical field.

Host Chris Adams is joined by Niki Manoledeki of Grafana and Ross Fairbanks of Flatpeak in this edition of TWiGS focused on Carbon Aware Spatial Shifting. They dive into Amazon's 2022 Sustainability Report, highlighting 19 AWS regions powered by 100% renewable energy, and explore videos from the Linux Foundation energy summit (links below). They also discover the importance of measuring carbon footprints in personal computing and IT, and learn about Kepler Power Estimation and the PLATYPUS Attack. Plus, they share some exciting upcoming events from the CNCF and some interesting Barbenheimer inspired portmanteaus from the world of Green Software!

In this episode of Environment Variables Chris Adams is joined by Fershad Irani, an independent web sustainability consultant and maintainer of CO2.js. They discuss topics like open data on the greenness of power, the wonders of HotCarbon, new projects from the cloud native computing foundation and the Green Software Foundation, and gzip.ai. Fershad shares his experiences working with the Green Web Foundation and the growth of the open-source carbon estimation library, CO2.js and there's a cameo from Fershad's cat!

On this episode of Environment Variables, host Chris Adams is joined by Asim Hussain as they dive into a mailbag session, bringing you the most burning unanswered questions from the recent live virtual event on World Environment Day that was hosted by the Green Software Foundation on June 5 2023. Asim and Chris will tackle your questions on the environmental impact of AI computation, the challenges of location shifting, the importance of low-carbon modes, and how to shift the tech mindset from "more is more" (Jevons Paradox). Chock-full of stories about projects implementing green software practices, and valuable resources, listen now to have your thirst for curiosity quenched!

This week we discuss Coinbase's $65 million DataDog bill, the factors that drive developer experience, and Google Bard. Plus, some tips on London Airports and the ideal airport arrival time. Watch the YouTube Live Recording of Episode 415 (https://www.youtube.com/watch?v=ysNsrYSkYsY&t=4s) Runner-up Titles Two hours before boarding $65 million is a lot of nines You can buy a lot of Nagios with that Just write the check for $65 million Boxes Inciting chaos Steady state is stopped Developers are just like the rest of us Unsummarizable AI in the Streets Rundown Datadog's $65M/year customer mystery solved (https://newsletter.pragmaticengineer.com/p/datadogs-65myear-customer-mystery) Google drops waitlist for AI chatbot Bard and announces oodles of new features (https://www.theverge.com/2023/5/10/23718066/google-bard-ai-features-waitlist-dark-mode-visual-search-io) DevEx: What Actually Drives Productivity (https://queue.acm.org/detail.cfm?id=3595878) Relevant to your Interests Google launches a GitHub Copilot competitor (https://techcrunch.com/2023/05/10/google-launches-a-github-copilot-competitor/) IBM Watson missed the AI revolution, but Watsonx could become the heartbeat of the Generative Enterprise - Horses for Sources | No Boundaries (https://www.horsesforsources.com/ibm-watsonx_051023/) It's not just cloud costs that are out of control (https://world.hey.com/dhh/it-s-not-just-cloud-costs-that-are-out-of-control-efcd098c) Microsoft just made a huge, far-from-certain bet on nuclear fusion (https://www.theverge.com/2023/5/10/23717332/microsoft-nuclear-fusion-power-plant-helion-purchase-agreement?_hsmi=257843304) Testing a new encrypted messaging app's extraordinary claims (https://crnkovic.dev/testing-converso/) Adrian Cockcroft (@adrianco@mastodon.social) (https://mastodon.social/@adrianco/110327883488321584) Goldman Sachs downgrades Twilio, other software names on 'limited catalyst' path (TWLO) (https://seekingalpha.com/news/3970029-goldman-sachs-downgrades-twilio-other-software-names-on-limited-catalyst-path) Meta announces generative AI features for advertisers (https://techcrunch.com/2023/05/11/meta-announces-generative-ai-features-for-advertisers/?utm_source=newsletter&utm_medium=email&utm_campaign=newsletter_axioslogin&stream=top) The .zip TLD sucks and it needs to be immediately revoked. (https://financialstatement.zip/) Netflix Reportedly Cutting Spending By $300 Million After Delay On Password Sharing Crackdown (https://www.forbes.com/sites/katherinehamilton/2023/05/12/netflix-reportedly-cutting-spending-by-300-million-after-delay-on-password-sharing-crackdown/?sh=4c6e2a1eaee2) Thank you, Enterprisers! (https://enterprisersproject.com/article/2023/5/thank-you-enterprisers) Somehow OpenSearch has succeeded (https://www.infoworld.com/article/3695576/somehow-opensearch-has-succeeded.html) Docker makes comeback with over $50M in ARR two years into restructuring (https://techcrunch.com/2022/02/01/docker-makes-comeback-reaching-over-50m-in-arr/) Calendly Welcomes Former Salesforce Product Executive Stephen Hsu as CPO (https://www.businesswire.com/news/home/20230509005168/en/Calendly-Welcomes-Former-Salesforce-Product-Executive-Stephen-Hsu-as-CPO?utm_source=newsletter&utm_medium=email&utm_campaign=newsletter_axioslogin&stream=top) Farewell to the Era of Cheap EC2 Spot Instances | Eric Pauley (https://pauley.me/post/2023/spot-price-trends/) The .zip TLD sucks and it needs to be immediately revoked. (https://financialstatement.zip/) The Dangers of Google's .zip TLD (https://medium.com/@bobbyrsec/the-dangers-of-googles-zip-tld-5e1e675e59a5) Conferences June 1st VMUG Belgium in Brussels (https://vmug.be/) , free. June 7th State of Kubernetes overview (https://tanzu.vmware.com/content/webinars/jun-7-emea-state-of-kubernetes-2023-solving-kubernetes-challenges?utm_source=cote&utm_campaign=devrel&utm_content=newsletter), online. June 8th to 9th PlatformCon (https://platformcon.com/), online. June 22nd to 23rd DevOpsDays Amsterdam (https://devopsdays.org/events/2023-amsterdam/welcome/), attending. June 27th to 30th FinOps X (https://x.finops.org/) San Diego, attending. August 21st to 24th SpringOne (https://springone.io/) & VMware Explore US (https://www.vmware.com/explore/us.html), in Las Vegas. Explore EU CFP is open. Sep 6th to 7th DevOpsDays Des Moines (https://devopsdays.org/events/2023-des-moines/welcome/), speaking. Sep 18th to 19th SHIFT (https://shift.infobip.com/) in Zadar, speaking. If you want your conference mentioned, let's talk media sponsorships. SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Get a SDT Sticker! Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Follow us on Twitch (https://www.twitch.tv/sdtpodcast), Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/), Mastodon (https://hachyderm.io/@softwaredefinedtalk), LinkedIn (https://www.linkedin.com/company/software-defined-talk/), TikTok (https://www.tiktok.com/@softwaredefinedtalk) and YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured). Use the code SDT to get $20 off Coté's book, Digital WTF (https://leanpub.com/digitalwtf/c/sdt), so $5 total. Become a sponsor of Software Defined Talk (https://www.softwaredefinedtalk.com/ads)! Recommendations Brandon: POLAR H9 Heart Rate Sensor (https://www.amazon.com/dp/B08411DQ96?psc=1&ref=ppx_yo2ov_dt_b_product_details) Matt: Critical Mass (https://amzn.to/42MCaMg) Sydney Half Marathon (https://runawaysydneyhalf.com.au/) Coté: Pipers Great Berwick Longhorn Beef “crisps.” (https://www.piperscrisps.com/en/great-berwick-longhorn-beef) Photo Credits Header (https://unsplash.com/photos/so9S78y64zk) Artwork (https://labs.openai.com/e/oLKoWqA6Gqx4kvjQ2wKHkgK4/rfcnCgVl74kVlDhNE4OEwHRy)

Host Chris Adams is joined by the GSF's Asim Hussain on this episode of The Week in Green Software. They discuss some interesting news about Amazon, AWS and their scope 3 GHG protocol emission data. We also find out how Python has got its Mojo back and we have a very exciting tool from Catchpoint WebpageTest for measuring site's carbon footprint. Finally, some great green software events that you can be part of!

Host Chris Adams is joined by Max Schulze from the SDIA (The Sustainable Digital Alliance) and they discuss three stories from the worlds of IaaS, PaaS and Saas! While these three acronyms are more than likely ever present in most digital people's lives, we might not know about the environmental impact that they have. Chris and Max cover stories from the CNCF, Google, CIODive and OpenJS as well as upcoming events in the Green Software community.

We caught up with Adrian Cockcroft again, this time to discuss the growing importance of, and the HPC market's efforts towards, decarbonization, the use of renewable energy, and meeting environment, sustainability, and governance (ESG) objectives. This episode is sponsored by Lenovo. [audio mp3="https://orionx.net/wp-content/uploads/2023/05/057@HPCpodcast_Adrian-Cockcroft_Carbon-ESG_20230503.mp3"][/audio] The post @HPCpodcast-57: Decarbonization, Renewable Energy, ESG, w Adrian Cockcroft appeared first on OrionX.net.

Chris Adams is joined by cloud sustainability advocate and founder of Cloud Sustainably, Aerin Booth in this episode of TWiGS brought to you by the Green Software Foundation. On this episode Aerin provides his insight into the cloud to discuss cloud zombies, the effect that generative AI is having on the environment and exciting developments from Xbox (including a list of some of Aerin's favourite nostalgic games!). We also touch on GreenOps and the future for green software developers.

On this episode of The Week in Green Software, Chris Adams and Asim Hussain discuss the latest research on streaming emissions from Netflix and DIMPACT, the environmental impact of refurbished tech from Back Market, The European Commission's Right to Repair Law and their proposal for an Anti Greenwashing Law which is being echoed across the channel with the UK's Digital Markets, Competition and Consumer Bill. Asim also discovers an alternative to central heating with his hot TV! The usual exciting resources and events in the show notes from TWiGS, Environment Variables and the Green Software Foundation.

Adrian Cockcroft, Stephen Perrenod, and Shahin Khan get together in a free-flowing coffee-shop style discussion of future system architecture in supercomputing. [audio mp3="https://orionx.net/wp-content/uploads/2023/03/OXD021_Supercomputing-Arch_12-Myths_20230329.mp3"][/audio]   The post OrionX Download Podcast: Future System Architecture appeared first on OrionX.net.

This week we discuss Docker's Business Model, the Stack Overflow's Sentiment Survey and ChatGPT use cases. Plus, some predictions about VR/AR headsets. Watch the YouTube Live Recording of Episode 406 (https://www.youtube.com/watch?v=hxvIBIzlmbM) Runner-up Titles Free isn't good enough I'm not that disconnected It's a presentation with yourself We still hate this Open Source Continuity Founder Magic Syntactic Sugar How cool do you feel, Tim Cook? Rundown Docker is deleting Open Source organisations - what you need to know (https://blog.alexellis.io/docker-is-deleting-open-source-images/) Docker's bad week (https://www.infoworld.com/article/3691292/dockers-bad-week.html) After the buzz fades: What our data tells us about emerging technology sentiment (https://stackoverflow.blog/2023/03/09/after-the-buzz-fades-what-our-data-tells-us-about-emerging-technology-sentiment/) Best printer 2023: just buy this Brother laser printer everyone has, it's fine (https://www.theverge.com/23642073/best-printer-2023-brother-laser-wi-fi-its-fine) The ‘Enshittification' of TikTok (https://www.wired.com/story/tiktok-platforms-cory-doctorow/) Google has discontinued the Glass Enterprise Edition (https://9to5google.com/2023/03/15/google-glass-enterprise-edition-discontinued/) Meta's metaverse is on the back burner (https://www.axios.com/newsletters/axios-login-c7503b12-b371-4a85-86f0-dacb9b3426fc.html?chunk=0&utm_term=emshare#story0) Who Is Still Inside the Metaverse? (https://nymag.com/intelligencer/article/mark-zuckerberg-metaverse-meta-horizon-worlds.html) Meta announces big price cuts for its VR headsets (https://www.cnbc.com/2023/03/03/meta-quest-pro-vr-headset-gets-price-cut.html) Mark Gurman details Apple's Reality Pro headset (https://www.gsmarena.com/mark_gurman_gives_huge_breakdown_of_apples_reality_pro_headset-news-57314.php) Relevant to your Interests 4K Blu-Rays Vs. 4K Streaming: Which Is the Best Way to Enjoy Movies? (https://www.tcl.com/global/en/blog/4k-blu-rays-vs-4k-streaming-which-is-the-best-way-to-enjoy-movies) Tweetbot and Twitterrific Face the Cliff (https://daringfireball.net/2023/03/tweetbot_and_twitterrific_face_the_cliff) Salesforce shares jump 16% on better-than-expected forecast (https://www.cnbc.com/2023/03/01/salesforce-crm-earnings-q4-2023.html) Lilly Cuts Insulin Prices by 70% and Caps Patient Insulin Out-of-Pocket Costs at $35 Per Month | Eli Lilly and Company (https://investor.lilly.com/news-releases/news-release-details/lilly-cuts-insulin-prices-70-and-caps-patient-insulin-out-pocket) Adrian Cockcroft on LinkedIn: Amazon denies claims hiring freeze is slowing AWS sustainability work (https://www.linkedin.com/posts/adriancockcroft_amazon-denies-claims-hiring-freeze-is-slowing-activity-7035729287030730752-eIog?utm_source=share&utm_medium=member_ios) NPM repository flooded with 15,000 phishing packages (https://www.scmagazine.com/analysis/devops/npm-repository-15000-phishing-packages) Introducing Service Weaver (https://twitter.com/kelseyhightower/status/1630995723956412420) A Basic iPhone Feature Helps Criminals Steal Your Entire Digital Life (https://www.wsj.com/articles/apple-iphone-security-theft-passcode-data-privacya-basic-iphone-feature-helps-criminals-steal-your-digital-life-cbf14b1a) Ford announces it hired 550 former Argo devs (https://twitter.com/Carnage4Life/status/1631485994322239489) Amazon says it is pausing construction at HQ2 in Arlington (https://www.washingtonpost.com/dc-md-va/2023/03/03/amazon-hq2-construction-delay-arlington/?utm_campaign=wp_post_most&utm_medium=email&utm_source=newsletter&wpisrc=nl_most&carta-url=https%3A%2F%2Fs2.washingtonpost.com%2Fcar-ln-tr%2F3946bb7%2F64022c3bd8b4d160753c68fc%2F5ed96de79bbc0f3a78a62db3%2F10%2F74%2F64022c3bd8b4d160753c68fc&wp_cu=adfcfd8deaffd0ba2a9ca872039c1c5f%7CA74A34F443CC71B2E0530100007FCBF9) National Cybersecurity Strategy (https://twitter.com/ENERGY/status/1631412407565180928?s=20) Richard Seroter's take on Web Assembly (https://twitter.com/rseroter/status/1631723362371371008?s=20) VMware's SaaS Sales Surge As Broadcom Deal Nears (https://www.crn.com/news/channel-news/vmware-s-saas-sales-surge-as-broadcom-deal-nears) Technology Chiefs Seek Help Wrangling Cloud Costs (The Wall Street Journal) (https://artifact.news/s/ZAPppeImSUI=) Top Apple Supplier Foxconn Plans Major India Expansion (https://www.wsj.com/articles/top-apple-supplier-plans-major-india-expansion-f2908b88) Zoom boss Greg Tomb fired ‘without cause' (https://www.bbc.com/news/technology-64835239) A cloud migration in wartime (https://www.mckinsey.com/capabilities/mckinsey-digital/our-insights/a-cloud-migration-in-wartime) Apple's VP of Cloud Engineering Michael Abbott Reportedly Leaving Company in April (https://www.pymnts.com/apple/2023/apples-vp-of-cloud-engineering-michael-abbott-reportedly-leaving-company-in-april/) ARM vs Intel on Amazon's cloud: A URL Parsing Benchmark (https://lemire.me/blog/2023/03/01/arm-vs-intel-on-amazons-cloud/?ck_subscriber_id=512840665) Microsoft brings an AI-powered Copilot to its business app suite (https://techcrunch.com/2023/03/06/microsoft-dynamics-copilot/?guccounter=1&guce_referrer=aHR0cHM6Ly9uZXdzLmdvb2dsZS5jb20v&guce_referrer_sig=AQAAAGcA6HN4Zti_4dKCpuMURoiAkkQ_uR0GBWFOG215KnmRsvryBDclj9SjWv-95R0yA0wFRXevcP-HUdwk-E3ZyR3d23rc5VGVCNXFGK5L3mAPvoEOJxRs6WZFKQvDUBIyw5V3NpdWGkkQ-fXDh4Rijfdp2l_ekJTxepVJjoYJSyKz) NOSSHJJ talking about 1Password (https://www.youtube.com/watch?v=vfmKwjiVf-U) Alphabet headcount on Google Cloud (https://twitter.com/jordannovet/status/1632842179281387522) How a single engineer brought down Twitter on Monday (https://www.platformer.news/p/how-a-single-engineer-brought-down?utm_source=substack&utm_medium=email) Kubernetes as a platform vs. Kubernetes as an API | Amazon Web Services (https://aws.amazon.com/blogs/containers/kubernetes-as-a-platform-vs-kubernetes-as-an-api-2/) Atlassian to Eliminate 500 Jobs in Latest Software Cutbacks (https://www.bloomberg.com/news/articles/2023-03-06/atlassian-will-eliminate-500-jobs-in-latest-software-cutbacks?leadSource=uverify%20wall&utm_source=newsletter&utm_medium=email&utm_campaign=newsletter_axioslogin&stream=top#xj4y7vzkg) Even Slack has a ChatGPT app now (https://www.engadget.com/even-slack-has-a-chatgpt-app-now-154334452.html) The Pursuit of Shareholder Value: Cisco's Transformation from Innovation to Financialization (https://www.ineteconomics.org/research/research-papers/the-pursuit-of-shareholder-value-ciscos-transformation-from-innovation-to-financialization) Google I/O 2023 takes place on May 10th in front of a 'limited' in-person audience (https://www.engadget.com/google-io-2023-takes-place-on-may-10th-in-front-of-a-limited-in-person-audience-232154501.html) Datadog's software is down — and so is its stock (https://www.marketwatch.com/story/datadogs-software-is-down-and-so-is-its-stock-3d0dc2e6) Southwest lands on AWS as preferred cloud for modernization push (https://www.ciodive.com/news/Southwest-airlines-AWS-cloud-modernization/644510/) Microsoft says Bing has crossed 100 million daily active users | Engadget (https://www.engadget.com/microsoft-bing-crossed-100-million-daily-active-users-080138371.html) SCOOP: Stripe Is Raising $6 Billion to Resolve Taxes & Expiring Employee Shares, Delaying Public Listing (https://www.newcomer.co/p/scoop-stripe-is-raising-6-billion) After Stadia, Google's new gaming roadmap (https://www.axios.com/newsletters/axios-login-231e8237-d33a-4d1a-b810-5e2e729eff66.html?chunk=2&utm_term=emshare#story2) GM offers buyouts to 'majority' of U.S. salaried workers (https://www.cnbc.com/2023/03/09/gm-buyouts-us-salaried-workers.html) Meta is building a decentralized, text-based social network (https://www.platformer.news/p/meta-is-building-a-decentralized?utm_source=substack&utm_medium=email) VMware turns to containerization to improve virtual apps (https://www.theregister.com/2023/03/09/vmware_apps_on_demand/) Exclusive: Meta mulls a Twitter competitor codenamed ‘P92' that will be interoperable with Mastodon (https://www.moneycontrol.com/news/business/startup/meta-mulls-a-twitter-competitor-codenamed-p92-that-will-be-interoperable-with-mastodon-10223961.html?utm_source=newsletter&utm_medium=email&utm_campaign=newsletter_axioslogin&stream=top) Oracle shares sink nearly 5% after third-quarter revenue miss (https://www.cnbc.com/2023/03/09/oracle-shares-sink-nearly-5percent-after-third-quarter-revenue-miss.html) How Ahrefs Saved US$400M in 3 Years by NOT Going to the Cloud (https://tech.ahrefs.com/how-ahrefs-saved-us-400m-in-3-years-by-not-going-to-the-cloud-8939dd930af8) U.S. government steps in and says people with funds deposited at SVB will be able to access their money (https://www.cnbc.com/2023/03/12/regulators-unveil-plan-to-stem-damage-from-svb-collapse.html) Joint Statement by the Department of the Treasury, Federal Reserve, and FDIC (https://home.treasury.gov/news/press-releases/jy1337) GitLab loses one-third of its value after software company issues weak revenue forecast (https://www.cnbc.com/2023/03/13/gitlab-gtlb-earnings-q4-2023.html) Hashi Stack To Break $1 Billion, With Profits, In Two Years (https://www.nextplatform.com/2023/03/10/hashi-stack-to-break-1-billion-with-profits-in-two-years/) Gowalla returns to see if location-based networking is ready for its mainstream moment (https://techcrunch.com/2023/03/10/gowalla-location-based-social-app/) Amazon's New Home Internet Service Announces New Details | Cord Cutters News (https://cordcuttersnews.com/amazons-new-home-internet-service-announces-new-details/) Grammarly's New AI Tool Can Do More Than Check Your Spelling (https://www.cnet.com/tech/services-and-software/grammarlys-new-ai-tool-can-do-more-than-check-your-spelling/) Google Cloud gives developers access to its foundation models (https://techcrunch.com/2023/03/14/google-cloud-gives-developers-access-to-its-foundation-models/) The inside story on Mountpoint for Amazon S3, a high-performance open source file client (https://aws.amazon.com/blogs/storage/the-inside-story-on-mountpoint-for-amazon-s3-a-high-performance-open-source-file-client/) Meta to Lay Off Another 10,000 Workers (https://www.nytimes.com/2023/03/14/technology/meta-facebook-layoffs.html) Zed raises $10M for a code editor built for collaboration (https://techcrunch.com/2023/03/15/zed-code-editor-raises-10m/) Apple is reportedly experimenting with language-generating AI (https://techcrunch.com/2023/03/16/apple-is-reportedly-experimenting-with-language-generating-ai/) Twitch CEO Emmett Shear is stepping down (https://techcrunch.com/2023/03/16/twitch-ceo-emmett-shear-is-stepping-down/) The Four Domains of Wasm (https://www.fermyon.com/blog/four-domains-wasm) Navigating SVB's new era (https://www.axios.com/newsletters/axios-pro-rata-3bd96e9e-2dbf-4d32-8008-30800f298ac7.html?chunk=0&utm_term=emshare#story0) Hewlett Packard Enterprise to acquire OpsRamp, advancing hybrid cloud leadership and expanding HPE GreenLake into IT Operations Management (https://www.hpe.com/us/en/newsroom/press-release/2023/03/hewlett-packard-enterprise-to-acquire-opsramp-advancing-hybrid-cloud-leadership-and-expanding-hpe-greenlake-into-it-operations-management.html) Proximus and Google Cloud to Deliver Sovereign Cloud Services in Belgium and Luxembourg (https://www.proximus.com/news/2023/20230315-disconnected-sovereign-cloud-platform.html) Netflix plans 40 more game releases in 2023 (https://www.axios.com/2023/03/20/netflix-40-video-games) Dragonfly - Dragonfly Is Production Ready (and we raised $21m) (https://dragonflydb.io/blog/dragonfly-production-ready) HPE picks up OpsRamp for Greenlake multi-cloud AIOps (https://www.theregister.com/2023/03/20/hpe_opsramp_acquisition/) Nutanix To Miss SEC Deadline Amid Internal Software Probe (https://www.crn.com/news/cloud/nutanix-to-miss-sec-deadline-amid-internal-software-probe) Nutanix's latest bumper financials overshadowed by 3rd party evaluation software probe – Blocks and Files (https://blocksandfiles.com/2023/03/07/terrific-nutanix-results-overshadowed-by-expense-investigation/) AWS Cost Leaderboard (https://leaderboard.vantage.sh/) GitHub releases blueprint for budding open source program offices (https://techcrunch.com/2023/03/15/github-releases-blueprint-for-budding-open-source-program-offices/) Introducing GPT-4 in Azure OpenAI Service (https://azure.microsoft.com/en-us/blog/introducing-gpt4-in-azure-openai-service/) Cloud Repatriation Trends: Where Are We Now? (https://blog.container-solutions.com/cloud-repatriation-trends-where-are-we-now) The cloud backlash has begun: Why big data is pulling compute back on premises (https://techcrunch.com/2023/03/20/the-cloud-backlash-has-begun-why-big-data-is-pulling-compute-back-on-premises/) Nonsense Goldman Sachs arm among bidders with appetite for $10bn Subway (https://news.sky.com/story/goldman-sachs-arm-among-bidders-with-appetite-for-10bn-subway-12825817) This smart toaster lets you cook two slices of bread at different temperatures at the same time (Yanko Design) (https://artifact.news/s/Ug-RYHqMfFE=) A Matt Levine Effect? (https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4386256) Tiny data centre used to heat public swimming pool (https://www.bbc.co.uk/news/technology-64939558) Man Sues Buffalo Wild Wings Over ‘Boneless' Wings (https://www.nytimes.com/2023/03/14/business/buffalo-wild-wings-boneless-wings-lawsuit.html) Metallica Acquires Furnace, One of America's Largest Vinyl-Manufacturing Companies (https://variety.com/2023/music/news/metallica-acquires-furnace-vinyl-pressing-plants-1235553683/) Got a question for Twitter's press team? The answer will be a poop emoji (https://www.npr.org/2023/03/20/1164654551/twitter-poop-emoji-elon-musk?_hsmi=251042455) Sponsors The MacGeekGab.com Podcast (https://www.macgeekgab.com) provides tips, Cool Stuff Found, and answers to your questions about anything and everything Apple. Subscribe now! (https://www.macgeekgab.com/subscribe-to-podcast/) Conferences PyTexas 2023, Austin, TX April 1 - 2, 2023 (https://www.pytexas.org) KubeCon EU Amsterdam, April 18-21 (https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/) - Matt & Cote will be there DevOpsDays Birmingham, AL 2023 (https://devopsdays.org/events/2023-birmingham-al/welcome/), April 20 - 21, 2023 DevOpsDays Austin 2023 (https://devopsdays.org/events/2023-austin/welcome/), May 4-5 SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Get a SDT Sticker! Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Follow us on Twitch (https://www.twitch.tv/sdtpodcast), Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/), Mastodon (https://hachyderm.io/@softwaredefinedtalk), LinkedIn (https://www.linkedin.com/company/software-defined-talk/) and YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured). Use the code SDT to get $20 off Coté's book, Digital WTF (https://leanpub.com/digitalwtf/c/sdt), so $5 total. Become a sponsor of Software Defined Talk (https://www.softwaredefinedtalk.com/ads)! Recommendations Brandon: YouTube TV Multiview (https://blog.youtube/news-and-events/multiview-on-youtube-tv/) Matt: Barkley Marathons: The Race That Eats its Young (https://www.youtube.com/watch?v=UQmoxlUy33A) Manly Dam 21k (https://www.sydneytrailseries.com.au/course/manly-dam) Jabulani Challenge 22k (https://jabulanichallenge.com.au/) Coté: EQPMNT inflight bag, steel grey, toiletry bag (https://www.amazon.de/-/en/dp/B091P451DQ?psc=1&ref=ppx_yo2ov_dt_b_product_details). Photo Credits Header (https://unsplash.com/photos/3eAByt3-eOw)

In this the latest episode of The Week in Green Software, Chris Adams is joined by first time Environment Variables guest Tammy McClellan and regulars Anne Currie and Asim Hussain. They discuss the concept of greenwashing; what it is and how companies can avoid it, and why green IT is no longer an option for the tech sector. They cover various statistics about the environmental impact of data centers and cloud computing, the importance of optimizing code and algorithms to reduce emissions, and how developers can't just rely on hardware to reduce emissions. The hosts also touch on some valuable resources to further your knowledge in the world of Green Software - links below!

Welcome to the Jon Myer Podcast! In this episode, we are excited to have Adrian Cockcroft, a technology visionary, and former Cloud Architect at Netflix. Adrian will be sharing his insights on the four principles of platform engineering teams done right. As more organizations adopt cloud technologies, these principles can help engineering teams build and manage scalable platforms that can support the needs of modern applications. So, let's dive in and learn from one of the best in the business!

Welcome to the Jon Myer Podcast! In this episode, we are excited to have Adrian Cockcroft, a technology visionary, and former Cloud Architect at Netflix. Adrian will be sharing his insights on the four principles of platform engineering teams done right. As more organizations adopt cloud technologies, these principles can help engineering teams build and manage scalable platforms that can support the needs of modern applications. So, let's dive in and learn from one of the best in the business!

Charles Humble talks to Adrian Cockcroft, ex of AWS, Battery Ventures and Netflix. They discuss: memes in computing, serverless first, chaos and ideas around continuous resilience, strategy and Wardley Mapping, using large hardware such as AWS ultra clusters, and sustainable software.

theCUBE host John Furrier is joined by Christopher Hoff, Adrian Cockcroft and Lori Mac Vittie for our coverage of Supercloud22

Netflix's move to the cloud, ESG and HPC data, Formula-1 racing, and cloud configurations and interconnects for HPC and AI workloads. Cool stories and valuable insights in this episode as we get together with tech luminary and OrionX partnerAdrian Cockcroft. [audio mp3="http://orionx.net/wp-content/uploads/2022/09/036@HPCpodcas_Adrian-Cockcroft_Cloud_ESG_20220914.mp3"][/audio] The post @HPCpodcast-36: Adrian Cockcroft on Cloud, HPC Data, ESG, and Netflix appeared first on OrionX.net.

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

Lessons learned from a 27 years old UNIX book, Finally dRAID, Setting up a Signal Proxy using FreeBSD, Annotate your PDF files on OpenBSD, Things You Should Do Now, Just: More unixy than Make, and more NOTES This episode of BSDNow is brought to you by Tarsnap (https://www.tarsnap.com/bsdnow) Headlines Lessons learned from a 27 years old UNIX book (https://www.linux.it/~ema/posts/porsche-book/) One of the Amazon reviewers of "Sun Performance and Tuning: Java and the Internet" gave it 3/5 stars. While still a nice introduction, the book by Adrian Cockcroft has become dated — claimed Roland in 2003, which believe it or not was 18 years ago... dRAID, Finally! (https://klarasystems.com/articles/openzfs-draid-finally/) Admins will often use wide RAID stripes to maximize usable storage given a number of spindles. RAID-Z deployments with large stripe widths, ten or larger, are subject to poor resilver performance for a number of reasons. Resilvering a full vdev means reading from every healthy disk and continuously writing to the new spare. This will saturate the replacement disk with writes while scattering seeks over the rest of the vdev. For 14 wide RAID-Z2 vdevs using 12TB spindles, rebuilds can take weeks. Resilver I/O activity is deprioritized when the system has not been idle for a minimum period. Full zpools get fragmented and require additional I/O’s to recalculate data during reslivering. A pool can degenerate into a never ending cycle of rebuilds or loss of the pool Aka: the Death Spiral. News Roundup Setting up a Signal Proxy using FreeBSD (https://www.neelc.org/posts/freebsd-signal-proxy/) With the events that the private messaging app Signal has been blocked in Iran, Signal has come up with an “proxy” solution akin to Tor’s Bridges, and have given instructions on how to do it. For people who prefer FreeBSD over Linux like myself, we obviously can’t run Docker, which is what Signal’s instructions focus on. Fortunately, the Docker image is just a fancy wrapper around nginx, and the configs can be ported to any OS. Here, I’ll show you how to set up a Signal Proxy on FreeBSD. Annotate your PDF files on OpenBSD (https://www.tumfatig.net/20210126/annotate-your-pdf-files-on-openbsd) On my journey to leave macOS, I regularly look to mimic some of the features I use. Namely, annotating (or signing) PDF files is a really simple task using Preview. I couldn’t do it on OpenBSD using Zathura, Xpdf etc. But there is a software in the ports that can achieve this: Xournal. Xournal is “an application for notetaking, sketching, keeping a journal using a stylus“. And now that my touchscreen is calibrated, highlighting can even be done with the fingers :) Things You Should Do Now (https://secure.phabricator.com/book/phabflavor/article/things_you_should_do_now/) Describes things you should do now when building software, because the cost to do them increases over time and eventually becomes prohibitive or impossible. Just: A command runner. More unixy than Make because it does even less. (https://github.com/casey/just/) I think it's in the do-one-thing-well spirit of Unix, because it's just a command runner, no build system at all. Just has a bunch of nice features: Can be invoked from any subdirectory Arguments can be passed from the command line Static error checking that catches syntax errors and typos Excellent error messages with source context The ability to list recipes from the command line Recipes can be written in any language Works on Linux, macOS, and Windows And much more! Just doesn't replace Make, or any other build system, but it does replace reverse-searching your command history, telling colleagues the weird flags they need to pass to do the thing, and forgetting how to run old projects. Tarsnap This weeks episode of BSDNow was sponsored by our friends at Tarsnap, the only secure online backup you can trust your data to. Even paranoids need backups. Feedback/Questions Marc - Confused about Snapshots (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/393/feedback/Marc%20-%20Confused%20about%20Snapshots) Dan’s gist: https://gist.github.com/dlangille/3140e60a816226ed75365ba8af185085 Pete - A Question (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/393/feedback/Pete%20-%20A%20Question) Rick - ZFS Idea (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/393/feedback/Rick%20-%20ZFS%20Idea) Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) *** Special Guest: Dan Langille.

With firms navigating unprecedented levels of volatility, cloud technology has taken on a new level of importance. It’s no secret that businesses now have a heightened focus on resilience. Join the discussion with Adrian Cockcroft, Vice President of Cloud Architecture Strategy at Amazon Web Services, and James Lee, Chief Technology Officer at DTCC, on how cloud technology can help businesses with their resilience strategy. Copyright 2020 - DTCC. All rights reserved. DTCC, DTCC (Stylized), ADVANCING FINANCIAL MARKETS. TOGETHER, and the Interlocker Graphic are registered and unregistered trademarks of The Depository Trust & Clearing Corporation.The information and views contained herein are provided for informational purposes only and should not be relied on for any other reason. This material is not intended to be relied upon as a forecast, research, legal or investment advice and is not a recommendation, offer or solicitation to buy or sell any securities or to adopt an investment strategy. The information and views expressed are current as at the date of this document, but subject to change and do not necessarily reflect the views of DTCC and no assurances are made as to their accuracy. Any reliance upon information in this material is at the sole risk of the recipient. Where the information contained in this material is from third party sources, this information is from sources believed to be reliable, but DTCC has not independently verified any of the information contained herein and does not assume any liability for it nor any obligation to modify or update it. This Service is governed by applicable Rules, Procedures, and Services Guide for each DTCC subsidiary, which contain the full terms, conditions, and limitations applicable to this Service.

Kicking off the first episode of 2021, Mik is joined by Adrian Cockcroft, VP of Cloud Architecture Strategy at Amazon Web Services. In this episode, Mik and Adrian discuss Adrian's predictions for application architecture in 2021, what's happening with microservices architecture and other key discussion points including: - Serverless services and why the time is now to use the fastest way to deliver these applications - Adrian's guidance for using AWS' new greenfield applications that can help quickly bring a product to market - How organizations can use Wardley maps as a powerful tool to map out their efforts and navigate rapidly changing technology landscapes - How Adrian approaches chaos engineering - Big data, its uses and what problems you can solve with it - Amazon's efforts with sustainability and renewable energy, and how moving a workload to the cloud could dramatically reduce a client's carbon footprint Subscribe to the Mik + One podcast today so you never miss an episode and don't forget to leave your review. Follow Mik on Twitter: @mik_kersten #MikPlusOne www.tasktop.com For more information about Adrian Cockcroft, visit: https://projecttoproduct.org/podcast/adrian-cockcroft-ep-24/

Joining Mik in this episode of Mik + One is Adrian Cockcroft, VP of Cloud Architecture Strategy at Amazon Web Services. In this episode, Mik and Adrian provide concrete advice on moving ahead in the digital world, and cover many key discussion points including: - Insight into Adrian's experiences establishing technical practices in organizations like eBay, Netflix and AWS. - The importance of product-centred innovation in order to pave the path for faster success. - Business agility, and why all organizations must have this in order to innovate and stay ahead of the competition. - The importance of feedback loops when delivering software, with a key focus on the four stages of the OODA loop. - The notion of ‘Flow Time' or ‘Time to Value' and why it is a crucial and powerful metric that all CEO's must prioritize. - The use of VSM in order to achieve better decision making and build a scalable organization. Subscribe to the Mik + One podcast today so you never miss an episode and don't forget to leave your review. Follow Mik on Twitter: @mik_kersten #MikPlusOne www.tasktop.com For more information about Adrian Cockcroft, visit: https://projecttoproduct.org/podcast/adrian-cockcroft/

In 2018 Adrian Cockcroft was quoted with: “Chaos Engineering is an experiment to ensure that the impact of failures is mitigated”! In 2019 we sit down with one of his colleagues, Adrian Hornsby (@adhorn), who has been working in the field of building resilient systems over the past years and who is now helping companies to embed chaos engineering into their development culture. Make sure to read Adrian’s chaos engineering blog and then listen in and learn about the 5 phases of chaos engineering: Steady State, Hypothesis, Run Experiment, Verify, Improve. Also learn why chaos engineering is not limited to infrastructure or software but can also be applied to humans.Adrian on Twitter:https://twitter.com/adhornAdrian's Blog:https://medium.com/@adhorn/chaos-engineering-ab0cc9fbd12a

In 2018 Adrian Cockcroft was quoted with: “Chaos Engineering is an experiment to ensure that the impact of failures is mitigated”! In 2019 we sit down with one of his colleagues, Adrian Hornsby (@adhorn), who has been working in the field of building resilient systems over the past years and who is now helping companies to embed chaos engineering into their development culture. Make sure to read Adrian’s chaos engineering blog and then listen in and learn about the 5 phases of chaos engineering: Steady State, Hypothesis, Run Experiment, Verify, Improve. Also learn why chaos engineering is not limited to infrastructure or software but can also be applied to humans.Adrian on Twitter:https://twitter.com/adhornAdrian's Blog:https://medium.com/@adhorn/chaos-engineering-ab0cc9fbd12a

Adrian Cockcroft (VP Cloud Architecture Strategy at AWS) joins Simon for a wide-ranging discussion about chaos in architectures, the requirements of Financial organisations, the use of the cloud in Formula One racing and Amazon's Open Source activities. https://aws.amazon.com/architecture/ https://aws.amazon.com/financial-services/ https://aws.amazon.com/solutions/case-studies/formula-one/ https://aws.amazon.com/opensource

Get Caught Trying to Make the World Better! This is a podcast from 2016 - remember those days?   I love this podcast because it started all of us thinking differently about how we test our NORMAL systems...  What a great intellectual romp through the safety community.  Enjoy! Best Safety Podcast, Safety Program, Safety Storytelling, Investigations, Human Performance, Safety Differently, Operational Excellence, Resilience Engineering, Safety and Resilience Incentives... Give this a listen. Thanks for listening and tell your friends.  See you on Audible...a couple books are up on there.  Have a great day as well.    

פרק מספר 365 (מספר קוסמי!) של רברס עם פלטפורמה - קרבורטור מספר 26: אורי ורן מארחים את נתי שלום (היזם של חברת Cloudify) לשיחה התקופתית על קוד פתוח, עננים, תשתיות ואירועים מהתחום מהזמן האחרון.קצת רקע להיום: ב - 11 למרץ 2019 פורסמה הודעה של AWS על התאגדות משותפת עם מספר חברות (בינהן Expedia ו-Netflix), על מנת לקחת מוצר בשם Elastic Search (חברה שהיזם שלה ישראלי, תזכורת לפרק 362 עם אורי כהן, וגם התגובה של שי בנון המייסד) וליצור עבורו מודל הפצה חדש (Re-distribution), מה שמרעיד את אמות הסיפין בתחום ומעורר לא מעט שאלות.נתי גם אמר את זה קודם . . .הנושא הציף קודם כל את הבלבול שקיים סביב המודל העסקי של חברות קוד פתוח והאופן שבו הן מייצרות רווח - נכון עבור Elastic אבל באותה מידה גם עבור Redis או GitHub וכו’.כל המוצרים של החברות הללו מגיעים מחברות ממומנות ולמטרת רווח ישיר, בשונה למשל מפרויקט כמו Kubernetes, שגוגל מעודדת על מנת לעודד צריכה של Google Cloud (ומשם לייצר רווח “משני”).יש מספר דרכים לרווח ישיר ממוצר קוד פתוח - רישיון שימוש (Subscription license)שירות כ-SaaS (ותשלום לפי צריכה)שירות מנוהל (Managed Service) - דומה ל-SaaS, רק שיש אפשרות גם להריץ בעצמךתשלום על תמיכה ו-Extra Featuresנקודה עדינה, כי יש גבול דק שקל לעבור ולהפסיק להיות “באמת” קוד פתוח. כל ה-API למפתחים חייבים להיות פתוחים, אבל תחומים של Clustering או Security למשל כבר נחשבים כ”איזורי מוניטיזציה” - זה כבר לא POC או פיתוח אלא שימוש משמעותי שמצדיק תשלום.ההבדל המשמעותי לעומת “קוד סגור” הוא היחס שבין הספק ללקוח - צריך לשלם, אבל לא מיד ברגע שנוגעים במוצר אלא רק כשיש ערך ברור.חשוב לשים לב שגם צד הלקוח מעוניין הרבה פעמים בתשלום כלשהו עבור שימוש משמעותי - יוצר מחוייבות לתמיכה (או לפחות תחושה כזו) ואומר שיש מישהו מאחורי המוצר שיכול לתמוך במקרה הצורך.זו מערכת מבוססת אמון (Trust system) - ויש מגוון סוגי רשיונות שמגדירים מה מותר לעשות עם החלק הפתוח (החינמי)הרשיון “המתירני” ביותר נקרא Apache 2.0, שמאפשר כמעט הכל (כולל re-distribution) והרבה ארגונים משתמשים בו, גם מתוך חשש מרישיונות כמו GPL למשל, שאומר שאם מבצעים שינוי בקוד חייבים לשתף גם אותו (מה שעשוי להיות קשה לשליטה ובעייתי באופן כללי לארגונים גדולים).למיטבי לכת (ושמע) - היה פרק שלם גם על זה עם עו”ד(!) דביר גסנר (ב-2012, ועדיין), ועוד אחד על רשיונות קוד פתוח (פרק 211 מ-2014), וגם זהר זקס הרחיב על הנושא בפרק 317 על Zusammen. הרבה שיעורי בית.בשורה התחתונה - חברות פחדו ממצב בו מפתח בודד יעשה שימוש בקוד עם רישיון שמעבר ל-Apache 2.0 (או MIT License שהוא די מקביל) ויחייב את החברה לשיתוף שהיא לא יכולה לעמוד בו.השוני הגדול הוא בעיקר בזכויות ההפצה (Re-distribution) ושימוש כ-SaaS.העיקרון הבסיסי הוא שהפרויקטים הללו דורשים הרבה מאוד השקעה, חדשנות וטכנולגיה, ועומדות מאוריחהם חברות גדולות שבסופו של דבר צריכות מודל עסקי על מנת להתקיים ולהרוויח (ולהנפיק…).לא צריכה להיות סתירה בין זה לבין טובת המשתמש, שעדיין נהנה ממוצר באיכות מאוד גבוהה בחלק הפתוחשונה מפרוייקטים שמבוססים לחלוטין על  תרומות קוד של משתמשים, מה שעובד לרוב רק כשיש חברות שמאגדות את הפרוייקט על מנת להפיק ערך באופן אחר (שוב - דוגמת Kubernetes ו-Google).אז בחזרה לשאלה המקורית -  למה רעדו אמות הסיפין?המרכיב הראשון הוא עניין האמון - ברגע שיש שימוש משמעותי במוצר צריך להתחיל לשלם. מה זה “משמעותי”? בדיוק . . .אם אני עושה שימוש משמעותי בקוד הפתוח, אבל גם מאפשר להשתמש בו בחינם (או לקבל תמיכה בחינם וכו’), נוצרת פגיעה בחברה שפיתחה את הקוד, ולא נהנית מרווח בשלב בו הוא הופך ”לגיטימי”אם נוסף על כך את העובדה שזה קורה בפרויקט שבו לא תרמתי למוצר מלכתחילה, ורק אפשרתי שימוש משמעותי בחינם - נוצר משבר אמון עמוק.אז AWS.משמעות ההודעה של AWS היא שעבור מוצרי קוד פתוח שהם לא באמת תרמו לפיתוחם, הם חותכים את קווי המוניטיזציה - על מנת להנות מהשימוש הרב בהם (להנות מהרווח הנגזר מהשוק שגדל, בלי להשקיע בשלב הראשון של יצירת ופיתוח השוק).נותנים שירות ותמיכה לחלק החינמי של השירות - ובפועל מתחרים בחברה המפתחת על התמיכה במוצר (החינמי) שלה, אותה תמיכה שהרווח הפוטנציאלי ממנה היה הבסיס והתמריץ לפיתוח.הדרך של החברה להגיע למשתמשים הייתה, למשל, לאפשר שירות במודל SaaS על התשתיות של AWS (שמרוויחה כבר בשלב הזה, אבל זה ממודל אחר), ולהרוויח מתמיכה. בשלב הזה נכנסת AWS שוב, ומתחרה בחברה המפתחת על תמיכה במוצר הקוד הפתוח שלה.מעבר ל- Elastic Search היו מקרים דומים גם עם MongoDB ו - Redis, וגם עם InfluxDB - שהגיבו ע”י שינוי מודל הרשיונות שלהן. יש הרבה דוגמאות כאלה עם AWS, שמאוד עקבית במדיניות הזו.התגובה הסטנדרטית של AWS במקרים כאלה היא שהם רוצים לתת שירות טוב יותר למשתמשים - ועבור הלקוחות יש לכאורה שירות יותר טוב במחיר יותר נמוך.האם באמת יש כאן Win-Win? שאלה טובה, נחזור אליה.אז הכל היה כבר קודם - מה קרה עכשיו ששונה?נחזור לכותרת של הפוסט - “Keeping Open Source Open – Open Distro for Elasticsearch”נכתב ע”י Adrian Cockcroft, ארכיטקט Cloud ב-AWS, בעבר גם ב-Netflix, ביקר בארץ באמצע מרץ (Keynote speaker ב- AWS Summit 2019, אפשר גם להשלים בוידאו).מאז היו עוד פרסומים.נתפס כמעיין “הרצחת וגם ירשת?” . . . יש כאן  מתקפה על חברות הקוד הפתוח בטענה שהן לא באמת מספקות קוד פתוח (כי הן מרשות לעצמן לרצות להרוויח), והצגה של AWS ככזו (בזמן שרוב המוצרים שהיא מפתחת בעצמה אינם בקוד פתוח כלשהו).הטענות שעולות בפוסט הן ש-Elastic במשך הזמן הוסיפו סעיפים שהופכים את הקוד ללא באמת פתוח, יחד עם הדוגמא של Java (סיפור ה-End of Life מבחינת אורקל, כש-AWS “ראו את טובת המשתמשים” והחליטו להמשיך ולתמוך).בשורה התחתונה - לא רק לקחו “פרי בשל” של חברה אחרת, אלא גם הטיפו מוסר. אין כאן שום דבר לא חוקי, אבל נראה לא משהו בכלל.הסכנה לטווח הארוך היא פגיעה בשוק הקוד הפתוח לטווח הארוך - משקיעים מתחילים לשאול איך (ואם בכלל) אפשר למנוע מ-AWS לעשות מהלכים כאלה בעתיד?התשובה הפשוטה - להשתמש ברשיונות פחות פתוחיםרואים את זה כבר עם Elastic ועם MongoDB, שמתחילות להגן על עצמן מפני הפרות אמון כאלו, מה שהופך את הדיון לכללי יותר, עבור כלל התעשייה: איך בונים יחסים של Win-Win בין ספקי הקוד הפתוח לספקי תשתיות הענן (Cloud Providers)?האם הכיוון הוא חרם צרכנים? - מי בדיוק יחרים? . . .אם חברות הקוד הפתוח לא ישתמשו ב-AWS, הם יעשו את זה בעצמם. נראה ש-AWS מפסידה בעצמה כי ככל שיותר חברות קוד פתוח ישתמשו בתשתיות של AWS כך היא תרוויח.זו לא באמת שאלה של מי צודק, אלא שאלה של טובת הצרכן לנוכח ניגוד האינטרסים.שווה לשאול מה קורה עם מוצרים שאינם קוד פתוח - תוכנות Microsoft למשל.כאן ב-AWS ידעו למצוא מודלים של Win-Win עבור כל הצדדיםלכאורה ההבדל היחיד הוא שבמקרה של קוד פתוח יש פירצה משפטית (או מערכת מבוססת אמון) שמאפשרת לעקוף את זה, וניצלו אותה.יכול להיות שהדרך היא להסתכל באותה צורה גם על חברות קוד פתוח וגם על חברות “מסורתיות” (ראה מקרה Oracle).ההבדל הוא שבמקרה של קוד פתוח, AWS לכאורה מספקים את השירות בחינם (הם עדיין מרוויחים על התשתיות).כל זאת - בזמן שעל AWS רצים יותר שרתי Windows מכל מערכת אחרת (ע”פ Adrian Cockcroft ב-AWS Summit בתל אביב), וכולם מרוויחים יפה.בזמן שעל Azure רצים עם Linux . . .כל ההבדל הוא הפירצה, והיכולת לנצל אותה.אין משקיע שישקיע בחברה ללא כל סיכוי לרווח כלשהו. המודל אינו התנדבות מלאה (לא מודל בר-קיימא בכל אופן).זה בסדר להשתמש בקוד פתוח ולא לשלם, וזה אכן נכון ל-90% מהמשתמשים. השאלה מה קורה כשמגזימים.אם למשל Outbrain משתמשים ב-Hadoop בלי לשלם (לשימוש פנימי), זה כנראה בסדר - כי הם לא מוכרים את המוצר, ולא מתחרים ביצרן - וזה גם כנראה נלקח בחשבון במודל העסקי של היצרן.זה לא המקרה עם AWS, וזה ההבדל הגדול - זה לא שימוש פנימי אלא תחרות ביצרן: הצעה של חלקים גדולים מאותו שירות לאותו בסיס לקוחות, עם התשתיות האדירות של AWS ובלי הוצאות

This week, we spoke with Sharone Revah Zitzman, developer relations at AppsFlyer and author of the contributed piece we ran last week titled “What the Fork, Amazon?” In the last episode, we talked about Amazon Web Services' new distribution of the open source Elasticsearch which has stirred up much debate and angst in the open source community. The move was necessary, AWS' Adrian Cockcroft argued in a blog post, in that elastic has intermingled proprietary code with the open source code that makes up the core of Elastic. He writes that with Elastic: Neither release notes nor documentation make it clear what is open source and what is proprietary. Enterprise developers may inadvertently apply a fix or enhancement to the proprietary source code. This is hard to track and govern, could lead to breach of license, and could lead to immediate termination of rights (for both proprietary free and paid). Individual code commits also increasingly contain both open source and proprietary code, making it very difficult for developers who want to only work on open source to contribute and participate. In particular, AWS releases open source components of Elastic providing functionalities that were previously only handled by Elastic's proprietary code, namely security, event monitoring and alerting.

Originally published on July 6, 2016. Scheduling is the method by which work is assigned to resources to complete that work. At the operating system level, this can mean scheduling of threads and processes. At the data center level, this can mean scheduling Hadoop jobs or other workflows that require the orchestration of a network The post Schedulers with Adrian Cockcroft Holiday Repeat appeared first on Software Engineering Daily.

Big thanks goes out to the GOTO Confernce 2018 in Chicago for this pod. Our friend Adrian Cockcroft talks about big failure and the systems that support these failures successfully...this is a great pod.  I am sure you will enjoy this discussion.  You can see this speech on Youtube for the visuals - but, I am pretty confident that this will make your drive to work interesting. Mr. Cockcroft rarely disappoints when he is on the pod. Listen to this podcast. Best Safety Podcast, Safety Program, Safety Storytelling, Investigations, Human Performance, Safety Differently, Operational Excellence, Resilience Engineering, Safety and Resilience Incentives Give this a listen. Thanks for listening and tell your friends.  See you in the funnypapers, someplace.

Simon speaks with Adrian Cockcroft (VP of Cloud Architecture Strategy, AWS) about the domain of Chaos Engineering and Architecture. They also discuss AWS activity in the Open Source community. Shownotes: Adrian’s 2017 re:Invent Presentation: https://www.youtube.com/watch?v=aLSFGLJ6Byo Drift Into Failure: https://www.amazon.com/Drift-into-Failure-Components-Understanding-ebook/dp/B009KOKXKY Netflix Chaos Engineering: http://www.oreilly.com/webops-perf/free/chaos-engineering.csp Open Source at AWS: https://aws.amazon.com/opensource/

In the fifth episode of the Cloud Choice podcast, Rene Claudio and Dan O’Riordan discuss how some of the best are using Cloud Native. This week’s show includes an interview with Adrian Cockcroft, VP Cloud Architecture Strategy at AWS, to discuss the move to cloud native. Dan & Rene will also chat about their experiences working with some of the top companies and the best methods for cloud native adoption. For the full Capgemini Cloud Native report, the blog series and previous podcasts, visit: https://www.capgemini.com/cloudnative Links: Rene’s Twitter - https://twitter.com/reneclaudi0 Dan’s Twitter - https://twitter.com/danoriordan?lang=en-gb Cloud Native Hub - https://www.capgemini.com/cloudnative

Para você assistir um filminho, muito código foi escrito! Conversamos com engenheiros da netflix sobre monolitos, microserviços, nodejs, testes em múltiplivos dispositivos, arquivos .jar de 10 gigabytes e, claro, sobre séries. E muitas outras coisas estranhas. Participantes: Paulo Silveira, host do Hipsters, quer assinatura perpétua da Netlix Mauricio Balboa Linhares, o cohost que não curtiu 3% Fabio Kung, senior software engineer na Netflix Bruno Tavares, senior software engineer na Netflix Cassiano Coria, gerente de engenharia na Netflix Links: Blog de tecnologia da Netflix Slides do Adrian Cockcroft, ex-netflix Produção e conteúdo: Alura Cursos online de Tecnologia Caelum Ensino e Inovação Edição e sonorização: Radiofobia Podcast e Multimídia

Para você assistir um filminho, muito código foi escrito! Conversamos com engenheiros da netflix sobre monolitos, microserviços, nodejs, testes em múltiplivos dispositivos, arquivos .jar de 10 gigabytes e, claro, sobre séries. E muitas outras coisas estranhas. Participantes: Paulo Silveira, host do Hipsters, quer assinatura perpétua da Netlix Mauricio Balboa Linhares, o cohost que não curtiu 3% Fabio Kung, senior software engineer na Netflix Bruno Tavares, senior software engineer na Netflix Cassiano Coria, gerente de engenharia na Netflix Links: Blog de tecnologia da Netflix Slides do Adrian Cockcroft, ex-netflix Produção e conteúdo: Alura Cursos online de Tecnologia Caelum Ensino e Inovação Edição e sonorização: Radiofobia Podcast e Multimídia

Para você assistir um filminho, muito código foi escrito! Conversamos com engenheiros da netflix sobre monolitos, microserviços, nodejs, testes em múltiplivos dispositivos, arquivos .jar de 10 gigabytes e, claro, sobre séries. E muitas outras coisas estranhas. Participantes: Paulo Silveira, host do Hipsters, quer assinatura perpétua da Netlix Mauricio Balboa Linhares, o cohost que não curtiu 3% Fabio Kung, senior software engineer na Netflix Bruno Tavares, senior software engineer na Netflix Cassiano Coria, gerente de engenharia na Netflix Links: Blog de tecnologia da Netflix Slides do Adrian Cockcroft, ex-netflix Produção e conteúdo: Alura Cursos online de Tecnologia Caelum Ensino e Inovação Edição e sonorização: Radiofobia Podcast e Multimídia

Tune into the latest episode of AWS TechChat as special guest Adrian Cockcroft, Vice President, Cloud Architecture Strategy, AWS joins our hosts Dr Pete and Russ to talk about Innovation, Architecture and the AWS Cloud.

Adrian Cockcroft has been a great supporter of my work around microservices, and I was really grateful he was able to find the time to catch up with me at Yow 2015 late last year. Few people have done as much to help share the power of the cloud in recent years as Adrian, but he certainly has a career that predates the explosion of Amazon Web Services. In episode 22 of the Magpie Talkshow, he shares is journey so far in the IT industry, from physics to venture capital firm Battery Ventures, with stops at Sun, EBay and Netflix in-between. We also find time to talk about the future of memory, security & compliance, bad puns and flying spaghetti monster simulators. As always you can find more information about the episode over at the blog: http://samnewman.io/blog/2016/10/08/magpie-talkshow-episode-22-adrian-cockcroft/

"Incremental change may be good theory, but in practice you have to have a big enough stick to hit everybody with to make everything move at once". So shares Adrian Cockcroft, who helped lead Netflix's migration from datacenter to the cloud -- and from monolithic to microservices architecture -- when their streaming business (the "stick"!) was exploding. So how did they -- and how can other companies -- make such big, bet-the-company kind of moves, without getting mired in fanatical internal debates? Does organizational structure need to change, especially if moving from a more product-, than project-based, approach? What happens to security? And finally, what happens to the role of CIOs; what can/should they do? Most interestingly: How will the entire industry be affected as companies not only adopt, but essentially offer, microservices or narrow cloud APIs? How do the trends of microservices, containers, devops, cloud, as-a-service/ on-demand, serverless -- all moves towards more and more ephemerality -- change the future of computing and even work? Cockcroft (who is now a technology fellow at Battery Ventures) joins this episode of the a16z Podcast, in conversation with Frank Chen and Martin Casado (and Sonal Chokshi) to discuss these shifts and more. The views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the enduring accuracy of the information or its appropriateness for a given situation. This content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments and certain publicly traded cryptocurrencies/ digital assets for which the issuer has not provided permission for a16z to disclose publicly) is available at https://a16z.com/investments/. Charts and graphs provided within are for informational purposes solely and should not be relied upon when making any investment decision. Past performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.

Brian talks with Julius Volz (@juliusvolz; Co-Creator of Prometheus) about Project Prometheus, the challenges of monitoring containers, working within the CNCF and where the project will expand. Show Links: Get a free book from O'Reilly media or use promo code PCBW for a discount - 40% off Print Books and 50% off eBooks and videos Prometheus Homepage (project) Getting Started with Prometheus One year of Prometheus development Prometheus Conference (PromCon) Julius’s Homepage Julius’s GitHub Page Show Notes: Topic 1 - Welcome to the show. Our first guest from Germany. Give us a little bit of your background and how you got involved in creating Prometheus. Topic 2 - Let’s talk about the basics of Prometheus. What are the core elements and what problems did you intend for it to solve? [From Prometheus homepage: “Prometheus is an open-source systems monitoring and alerting toolkit originally built at SoundCloud.”] Topic 3 - Prometheus is part of the CNCF, which is also where Kubernetes resides, but it can work with lots of different frameworks. Is there a size of deployment where you’ve found that Prometheus starts to make sense? Topic 4 - Adrian Cockcroft has talked a number of times about the challenges of monitoring these fast moving, fast changing systems. What are the biggest challenges of these types of systems that Prometheus is about to solve today? Topic 5 - We’ve traditionally seen (larger) projects come out of a vendor (e.g. Google), into an open source community. Prometheus came out of SoundCloud, which is more of an end-user. How are the projects different in terms of getting community involvement and adoption? Topic 6 - It’s still early in the project’s life, but have you heard of any Cloud projects that want to offer Prometheus-as-a-Service? Feedback? Email:show at thecloudcast dot net Twitter:@thecloudcastnet YouTube:Cloudcast Channel

Safety Podcast, Safety Program, Investigations, Human Performance, Safety Differently, Operational Excellence I could not wait for this podcast to hit the streets.  This podcast is thoughtful, smart, forward-looking, and super interesting.  In short, I love this episode.  Please meet Adrian Cockcroft...I will grab a bio...he's done everything.  Listen to this twice.   Thanks for being a part of the podcast. Mr. Adrian Cockcroft has been a Technology Fellow at Battery Ventures since 2014. He joined the firm in 2013 and focuses on IT Infrastructure. Mr. Cockcroft advises Battery on technology trends and issues, help with deal sourcing and due-diligence and speak at events around the globe. He served as a Chief Architect and Director of Web Engineering at Netflix, Inc. He joined the Netflix in 2007. Mr. Cockcroft directed a team, and responsible for research and development of scalable personalized web architectures. Prior to Netflix, he joined eBay in 2004, where he initially worked in Operations Architecture, investigating new platforms and providing guidance to the capacity planning groups at eBay and PayPal. As a founding member of eBay Research Labs in 2005, Mr. Cockcroft helped define the initial strategy for the Labs and an Innovation Forum. Prior to eBay, he spent 16 years at Sun Microsystems, became a Distinguished Engineer in 1999, and served as Chief Architect and Product Boss for Sun's High Performance Technical Computing business Unit. During this time he also served as the on-site capacity planning consultant for the Salt Lake 2002 and Athens 2004 Olympic Games. He filed two patents on capacity planning techniques while at Sun, and four patents related to peer to peer marketplaces while at eBay. Mr. Cockcroft has consulted on architecture, scalability and performance for the Bebo.com social network, and is an advisory board member at Holocosmos. Mr. Cockcroft serves as Member of Advisory Board at Infovell, Inc. and DeepDyve, Inc. Mr. Cockcroft is best known as the author of four books including Sun Performance and Tuning (2 editions); Resource Management; and Capacity Planning for Internet Services. He was named one of the top leaders in Cloud Computing in 2011 and 2012 by SearchCloudComputing magazine. He graduated from The City University, London with a B.SC in Applied Physics and Electronics.  (Bloomberg)

Scheduling is the method by which work is assigned to resources to complete that work. At the operating system level, this can mean scheduling of threads and processes. At the data center level, this can mean scheduling Hadoop jobs or other workflows that require the orchestration of a network of computers. Adrian Cockcroft worked on The post Schedulers with Adrian Cockcroft appeared first on Software Engineering Daily.

Scheduling is the method by which work is assigned to resources to complete that work. At the operating system level, this can mean scheduling of threads and processes. At the data center level, this can mean scheduling Hadoop jobs or other workflows that require the orchestration of a network of computers. Adrian Cockcroft worked on The post Schedulers with Adrian Cockcroft appeared first on Software Engineering Daily.

Brian talks with Adrian Cockcroft (@adrianco, Technology Fellow at @BatteryVentures) about the recent Battery Ventures Open Source Summit (#BVOSS), trends in open source business models and how VC are thinking about investing in companies that leverage open source software. Get a free book from O'Reilly media or use promo code PCBW for a discount - 40% off Print Books and 50% off eBooks and videos. Show Links: Podcasts of all discussions from the #BVOSS event will be published in podcast form soon - details TBD Battery Ventures Homepage Adrian’s blog on Battery Ventures “Powered” Battery Ventures Open Source Summit - #BVOSS on Twitter RedMonk discussion of Accel Partners Open Source conference Rob Hirshfeld’s thoughts from the event Are VC’s a Funding Bridge for OSS Projects? Show Notes: Topic 1 - It’s been awhile since you were on last. What are you focus areas these days? Topic 2 - Related to OSS-centric companies, Aaron and I discuss the “will they make any money” question all the time. BV had an event focused on this recently. What was the event? Topic 3 - There seemed to be a theme that OSS projects need to be delivered as-a-service. I saw a tweet that said, “Uber theme at #bvoss today: we need an OSS license that prevents AWS to make money off of our OSS code.” Topic 4 - There were several large end-customers (e.g. - banks) in attendance, talking about their OSS projects. Are they making any significant contributions to these projects, or is this mostly an effort to help them hire developers? Topic 5 - So what were the major takeaways from the conference? Feedback? Email:show at thecloudcast dot net Twitter:@thecloudcastnet YouTube:Cloudcast Channel

Summary: For our inaugural podcast QCon chair Wesley Reisz talks to Adrian Cockcroft, who works for Battery Ventures where he advises the firm and its portfolio companies about technology issues and also assists with deal sourcing and due diligence. Why listen to this podcast • Over the last year a large number of frameworks and libraries for building microservices have emerged and we're seeing a lot of rapid change. • The stack you choose will often be based on the main language you use, so for example Netflix’s stack is language agnostic but the tooling is very Java-centric. • Architectural choices can have a profound impact on success, so some-thing as simple as an overly long timeout with retries can cause your system to suffer from a congestion collapse problem. Have a large timeout at the edge, and progressively smaller and smaller timeouts as you get deeper into the system. • Start with a monolith and move to a distributed architecture when you need to because of team size or to get better separation of concerns. • Other disruptive trends include “serverless architecture” like AWS Lambda, and open source itself which is perhaps the true definition of disruptive. More on this • You can access our in-depth coverage on microservices http://bit.ly/1SRnFz3. • You can also subscribe to our newsletter to receive weekly updates on the hottest topics from professional software development. http://bit.ly/24x3IVq • Attend Adrian Cockcroft 's session at QCon New York 2016, Jun 13-17. http://bit.ly/1TvzlDQ

The New Stack's pancake breakfast and podcast circuit joined the 2015 Software Circus at the Amsterdam Roest. The New Stack Analysts host Alex Williams explored the conference theme, “Programmable Infrastructure,” with a panel that included David Blank-Edelman, Technical Evangelist for Apcera, as well as three of the conference keynote speakers: Adrian Cockcroft of Battery Ventures; Ken Owens, CTO Cloud Services at Cisco Systems; and Kelsey Hightower, Product Manager and Chief Advocate at CoreOS. Watch on YouTube: https://youtu.be/yUaz-cLm9yk Learn more at: https://thenewstack.io/tns-analysts-show-58-programmable-infrastructure-is-developer-driven/

In this episode we talk to the famous (or infamous) Adrian Cockcroft of Battery Ventures. Adrian is known for his work at Netflix and his work to migrate them to a Cloud first strategy, then before that for his book on Sun … Continue reading →

In this monitoring-powered edition of The New Stack Analysts podcast, captured during a break between sessions at Monitorama 2015 in Portland, Oregon, Alex Williams and co-host Donnie Berkholz of 451 Research reflect on the conference's big take-aways, with returning guests Adrian Cockcroft of Battery Ventures, and James Turnbull, VP of engineering at Kickstarter. Watch on YouTube: https://www.youtube.com/watch?v=LuA1AjorCQs Learn more at: https://thenewstack.io/tns-analysts-show-49-reflections-on-monitorama-2015-with-adrian-cockcroft-and-james-turnbull/

В этом выпуске мы поговорили о понятии NoOps, которое "вышло в свет" с легкой руки Adrian Cockcroft. Это был своеобразный "вброс", который многие поняли неправильно, и потом долго обсуждали в твиттере, склоняя Адриана на разные лады. Шоу-ноты и ссылки здесь: http://hangops.ru/noops/

Salve, How can we reduce the fear and cost of change? Is it possible to have multiple languages and frameworks working together side by side? How can we keep systems alive longer and with less pain? Today we talk with Chad Fowler, CTO at 6Wunderkinder, the creators of Wunderlist, and he will share with us how they are using Immutable Infrastructure to work around these problems. Related to the subject, I would like to recommend microXchg 2015, the Microservices Conference in Berlin, that will take place in February 12 and 13, 2015. It's a two day, two track conference with a ton of practioners, including Chad Fowler, James Lewis from Thoughtworks (co-author or the big article about Microservices with Martin Fowler), Adrian Cockcroft, the former cloud architect at Netflix and many others. It's limited to 200 seats, I recommend you register right away. UPDATE NOTICE: I remixed the episode boosting the interview volume, it should be much better now. Thanks a lot for the feedback, I'll be more careful in the future and now I learned how to fix it :) Feedback, corrections and suggestions are welcome. Leave them bellow or reach me on @rafaelrosafu or contact@mindthecloud.com. Have fun and Mind the Cloud. Your browser doesn't support the HTML5 audio tag Download the MP3 Shownotes Chad Fowler (@chadfowler) 6Wunderkinder Wunderlist Trash Your Servers and Burn Your Code: Immutable Infrastructure and Disposable Components - on Chad's blog Legacy by Chad Fowler - Chad's presentation on the subject on Scala Days 2014 Microservices - article by James Lewis and Martin Fowler from Thoughtworks microXchg 2015 - The Microservices Conference in Berlin - February 12th and 13th 2015, limited seats, register now Credits and copyright The music used on the program is called “Impromptu in A” by DoKashiteru, licensed under the Creative Commons. This podcast is licensed under the Creative Commons Attribution-NoDerivatives 4.0 International. Share it but don't change it.

Salve, How can we reduce the fear and cost of change? Is it possible to have multiple languages and frameworks working together side by side? How can we keep systems alive longer and with less pain? Today we talk with Chad Fowler, CTO at 6Wunderkinder, the creators of Wunderlist, and he will share with us how they are using Immutable Infrastructure to work around these problems. Related to the subject, I would like to recommend microXchg 2015, the Microservices Conference in Berlin, that will take place in February 12 and 13, 2015. It's a two day, two track conference with a ton of practioners, including Chad Fowler, James Lewis from Thoughtworks (co-author or the big article about Microservices with Martin Fowler), Adrian Cockcroft, the former cloud architect at Netflix and many others. It's limited to 200 seats, I recommend you register right away. UPDATE NOTICE: I remixed the episode boosting the interview volume, it should be much better now. Thanks a lot for the feedback, I'll be more careful in the future and now I learned how to fix it :) Feedback, corrections and suggestions are welcome. Leave them bellow or reach me on @rafaelrosafu or contact@mindthecloud.com. Have fun and Mind the Cloud. Your browser doesn't support the HTML5 audio tag Download the MP3 Shownotes Chad Fowler (@chadfowler) 6Wunderkinder Wunderlist Trash Your Servers and Burn Your Code: Immutable Infrastructure and Disposable Components - on Chad's blog Legacy by Chad Fowler - Chad's presentation on the subject on Scala Days 2014 Microservices - article by James Lewis and Martin Fowler from Thoughtworks microXchg 2015 - The Microservices Conference in Berlin - February 12th and 13th 2015, limited seats, register now Credits and copyright The music used on the program is called “Impromptu in A” by DoKashiteru, licensed under the Creative Commons. This podcast is licensed under the Creative Commons Attribution-NoDerivatives 4.0 International. Share it but don’t change it.

Adrian Cockcroft discusses the challenges in creating a dynamic, flexible, cloud-based platform with SE Radio host Stefan Tilkov. After briefly discussing the definition of “cloud computing,” Adrian explains the history behind Netflix’s move to the cloud (which he led). After highlighting some of the differences that have developers and architects must face, Adrian talks about […]

On this episode of TNS Analysts, Adrian Cockcroft of Battery Ventures and Christian Gheorghe, CEO of Tidemark, joined co-host Michael Coté and Alex Williams to discuss how executives are adopting the cloud and SaaS platform in particular. Noteworthy: their conversation about the rise of data science in the executive wing and what services management are adopting. Learn more at: https://thenewstack.io/the-new-stack-analysts-show-11-saas-in-the-executive-wing-with-adrian-cockcroft-and-christian-gheorghe/

John and Damon welcome Adrian Cockcroft to the show to discuss the lessons he's learned along his journey from Sun to eBay to Nextflix to Battery Ventures. Adrian talks about building resilient systems, company culture, micro-services, containers, the cloud... and how they are all intertwined.  Show notes at http://devopscafe.org

Adrian Cockcroft (@adrianco), director of architecture for cloud systems at Netflix, joins us from the Google I/O conference and chats about his Google Glasses and also an interesting announcement on charging by the minute for Google’s IaaS platform. He also discusses how Netflix built their massive cloud architecture, how they test the Netflix cloud, and the recently launched $100,000 prize from Netflix for developers who can improve on the company’s open source tools. Our second guest is John Cowan (@cownet), the co-founder and CEO of 6fusion which offers a utility-metered cloud computing platform that enables organizations and IT services providers to access to a federated network of IaaS providers. The foundation of the platform is the Workload Allocation Cube (WAC), which creates a commercial standard to quantify supply and demand for compute resources. Show Timeline: • 0:00: Introductions and News of the Week • 9:50: Interview with Adrian Cockcroft • 21:43: Interview with John Cowan • 39:04: Wrap up

Aaron and Brian talk with Nick Weaver (@lynxbat) about recent conferences (CiscoLive, PartnerExchange, Cloud Connect), the Open Cloud controversy, the evolution of DevOps, and how IT will eventually break off space for new apps. Nick also explains how he name-dropped Christian Reilly (@reillyusa) to meet Adrian Cockcroft from NetFlix.