CloudChat

Episode 0032 - Rolling, Rolling, Rolling… Logs are ground truth — high-fidelity, event-level data that anchor observability alongside metrics and traces. Carl and Brandon argue the biggest mistake teams make is treating "more logs" as "better logs." If everything is logged, nothing is useful, and they both share recent troubleshooting sessions where verbose, unstructured output forced them into KQL gymnastics just to find the actual error. Brandon walks through a 503 that turned out to be a database fault hidden one layer down, and Carl recounts a customer whose "unplanned" VM reboots were actually planned Kubernetes node maintenance — a story you can only untangle by correlating infrastructure and platform logs. Along the way they cover the six log sources worth thinking about (application, infrastructure, platform/managed service, security, audit, and access logs), with a detour into a customer whose minute-long latency vanished once infra logs revealed a VPN routing New York users through Texas. The middle of the episode is a clinic on log hygiene. Carl walks through log levels — debug/verbose, info, warn, error, fatal — and the distinction Brandon draws between an exception (a code construct) and an error (a log level): a caught exception is an error, an uncaught one becomes fatal. They make the case for structured logging into stores like Kusto or via OpenTelemetry so keys can be projected, indexed, and fed directly into dashboards, and Brandon's tip on not pre-computing expensive log arguments is a reminder that a disabled verbose call still costs CPU if you build its message eagerly. Centralized logging pipelines beat rolling your own helper class — log4-anything frameworks exist for a reason — and UTC alone won't save you when scaled-out instances drift apart in time. Correlation and trace IDs, especially parent/child IDs from OpenTelemetry, are the thread that stitches a single user's journey back together across microservices. Carl and Brandon close on cost and discipline. Logging budgets balloon fast, so production should not be running verbose, retention should be tiered (a month of exceptions is plenty once the fix ships), duplicate destinations like Log Analytics plus Event Hubs plus a storage account should pick one source of truth, and Application Insights-style sampling can collapse repetitive traffic into representative events. Compliance logs that sit for years belong in cold or frozen storage tiers where the access pattern actually matches the cost. Their do's and don'ts land on a simple posture: log with intent, redact secrets and connection strings, standardize across teams, and — especially if AI agents are writing your code — make sure the logging conventions travel with the work. Point an agent at a recent run and ask where the gaps and noise are; it's a fast way to audit whether your logs are actually doing their job. Links Observability and logging concepts OpenTelemetry OpenTelemetry traces and spans W3C Trace Context (correlation IDs) Structured logging overview (Microsoft Learn) Log levels in .NET (LogLevel enum) Logging frameworks log4j (Apache) log4net (Apache) Serilog (structured logging for .NET) Azure platform logging Azure Monitor Logs / Log Analytics Azure diagnostic settings Azure Application Insights sampling Kusto Query Language (KQL) Azure Event Hubs Azure Blob Storage access tiers (hot/cool/cold/archive) Security and supply chain XZ Utils backdoor (CVE-2024-3094) Veritasium: "The Internet Was Weeks Away From Disaster and No One Knew" Related CloudChat episodes Episode 0024 — Operating Excellently Episode 0025 — The Sound of Security Episode 0026 — Are Your Cloud Costs Too Damn High? Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0031 - AI All the Things? Traditional sprint ceremonies start getting in the way when AI-assisted development outpaces the cadence they were built for. Carl and Brandon unpack why that happens and what to do about it — starting with the basics. Brandon defines context windows, distinguishes original vibe coding from the sloppy way the term is used today, and walks through the software factory model where requirements, source code, and tests live in separate repos. Carl shares how he continuously refines his Copilot instructions file, instructs the agent to detect and document recurring patterns, and leans on intent-based prompting over tactical step-by-step descriptions — a three-sentence prompt describing preset themes and macOS Focus Mode integration wrote his Swift UI code nearly flawlessly. Both hosts dig into context management: plan mode to review before implementing, the "Ralph Wiggum" pattern of starting fresh sessions with just the plan, and Architectural Decision Records that give future sessions a trail to follow. Different models suit different jobs — Claude for architecture, Codex for implementation — and MCP servers let those models reach Git and GitHub without a copy-paste workflow. Brandon argues AI is a tool like the Internet — some roles will shift, but learning and adapting has always been the core tech-industry skill. Carl backs that up with a study showing senior engineers only see productivity gains when they change their process, not when they bolt AI onto the old one. On the junior side, Carl mentors a developer to focus on data structures and algorithms — not for the implementation details, but for knowing when to apply them. An MIT study pegs realistic job displacement at around 11.7 percent, and cases like Box's layoffs look more like post-COVID overcorrection than proof that AI is replacing everyone. Links AI-Assisted Development GitHub Copilot Anthropic Claude OpenAI Codex Model Context Protocol (MCP) T3 Chat — Compare LLM Outputs Development Concepts Strangler Fig Pattern (Martin Fowler) Test-Driven Development (TDD) Behavior-Driven Development (BDD) Tools Mentioned Swift UI (Apple Developer) Draw.io Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0030 - Local‑First Lifeboats: Architecting for Post‑EOL Usability This episode is about designing for the last day, not just the launch day. Carl kicks off with the Bose SoundTouch situation: a vendor moves toward EOL on a cloud-tethered API, users push back, and the outcome (at least in spirit) becomes a blueprint we wish was more common: keep the hardware useful by enabling local control paths and leaning on protocols that already work without your cloud. From there we broaden the conversation to the bigger problem: products and services that do something totally reasonable in a LAN suddenly need a round trip to the internet just to respond to a button press. Carl and Brandon talk through concrete "this actually happened" examples and what good looks like. Belkin's Wemo sunset email is a solid reference: clear dates, repeated notices, and a reality check that local APIs and ecosystems like HomeKit and Matter can keep devices working even when a vendor endpoint is shut off. We contrast that with the messier side of the industry: thermostats and other home gear that still function locally, but lose their main value when the cloud connection is removed, and cloud-only platforms like Stadia where "no backend" means "hard stop" (with the one bright spot being things like refunds and a final firmware update to unlock a controller for normal Bluetooth use). On the builder side, we get practical about how to retire things without surprising your users. We cover technical signaling (Deprecation and Sunset headers), the need for human-friendly comms beyond "put it in the docs," and the architecture patterns that make "minimum viable offline" real: local-first state, local discovery and control surfaces, and fallbacks that do not require re-pairing or re-auth when identity systems go away. We also touch on SaaS escrow and continuity as a way to build trust (especially for startups) and close with a simple gut check: if your cloud disappeared tonight, what can your users still do tomorrow morning? Links News and examples we discussed Bose is open-sourcing its old smart speakers instead of bricking them | The Verge Belkin Wemo cloud service end-of-support notice Google Stadia - Strategy change and shutdown (2021–2023) | Wikipedia Google Stadia controller Bluetooth mode help article API deprecation and shutdown mechanics Deprecation HTTP response header (RFC 9745) Sunset HTTP response header (RFC 8594) Smart-home protocols and "local-first" connectivity Matter (Connectivity Standards Alliance) Thread protocol overview (Thread Group) Multicast DNS (mDNS) (RFC 6762) Tools and patterns Local-first software (Ink & Switch) Strangler Fig Application pattern (Martin Fowler) Automerge (CRDT) - GitHub Yjs (CRDT) - GitHub Contracts and continuity SaaS escrow overview (Escrow London) SaaS escrow overview (PRAXIS Escrow) Software escrow overview (EscrowTech) Other links of interest Microsoft Modern Lifecycle Policy EU Right to Repair overview (European Commission) Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0029 - New Year's ☁️ Resolutions "In 2026, your cloud is not allowed to have the same incidents for the same reasons as last year." Carl and Brandon treat this episode like a retrospective (the kind any good agile team would run), but instead of talking about sprint tickets, they write a New Year's resolution list on behalf of your cloud team. The format is simple: Stop, Start, Keep. Small, opinionated constraints that change day-to-day habits, not vague wishes about "better reliability, security, and cost." The Stop list hits the repeat-incident patterns: single-region "global" apps, treating infrastructure-as-code as optional (and living in the portal), mystery ownership with no clear tags or escalation path, one-off production fix scripts that never get documented, dashboards that are always green while users are hurting, and "temporary" exceptions that turn into permanent risk. The Start list is the muscle-building: run realistic failover/incident drills, measure change and recovery (DORA-style signals and MTTR, not just uptime), budget reliability and cost together, treat internal platforms like products with golden paths, standardize secrets and identity, and add a regular "delete day" so old environments and artifacts do not drag into the new year. The Keep list is what compounds: automate repetitive toil, invest in observability tied to real user flows, keep blameless postmortems with concrete follow-ups, and keep platform/SRE work visible so it does not get squeezed out by features. We hope you and your team are able to embrace some of these resolutions in the coming year, and hope that listening to more CloudChat is at the top of your list. Happy New Year everybody! Links DORA: What is DevOps? Site Reliability Engineering (SRE Book) Azure Well-Architected Framework AWS Well-Architected Framework Google Cloud Architecture Framework Azure Bicep documentation Terraform documentation Azure Key Vault overview Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0028 - Respect My (DNS) Awe-Thor-Ih-TAY!! Your cloud is humming along, then an edge breaks. What lever do you actually still have to steer users? In this episode, Carl and Brandon dig into DNS as a control plane and why "it is always DNS" keeps being true in 2025. DNS was designed for a slower internet with long TTLs and infrequent changes, but we now treat it like a real-time steering wheel for global failover. That mismatch shows up in outages where the backend is fine but nobody can resolve the hostname that front doors, CDNs, and APIs live behind. We unpack how TTL and caching really work (including negative caching and serve-stale), why modern edge products like Azure Front Door and Cloudflare can still turn into global single points of failure, and how DNS-based load balancers actually behave when you flip weights or priorities. From there we move into patterns and mitigations. We walk through hub-and-spoke vs mesh topologies and where public vs private DNS sit in each, plus concrete strategies for what to do when your edge is broken: bypass patterns, equivalent services, and multi-product designs that let you route around a failing front door. We also hit the observability side so "it is DNS" becomes a graph and an alert instead of a guess in a war room. We close with a look at emerging record types like SVCB/HTTPS and how they may help you advertise alternate endpoints and protocol hints without building another fragile tower of CNAMEs. Links DNS Fundamentals RFC 1034: Domain Names - Concepts and Facilities RFC 1035: Domain Names - Implementation and Specification RFC 2308: Negative Caching of DNS Queries RFC 8767: Serving Stale Data to Improve DNS Resiliency DNS Load Balancing and Edge Services Azure Traffic Manager documentation Azure DNS alias records Amazon Route 53 health checks and failover Cloudflare Load Balancing Akamai Global Traffic Management Azure, AWS, and Cloudflare Outage Reading Azure Front Door service documentation AWS DynamoDB and Route 53 service health history Cloudflare status history Architectures and Private DNS Azure Private DNS zones Azure DNS Private Resolver Azure Virtual WAN DNS guidance Emerging DNS Records and HTTP/3 Service binding (SVCB) and HTTPS resource records Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0027 - Whoops, No VM's!!! You've planned for redundancy, scaling, and failover, but what happens when the cloud itself runs out of space? In this episode, Carl and Brandon untangle capacity (what the provider physically or logically has available in a region or zone) versus quota (the soft limit on what you can consume). Mixing the two leads to painful surprises during scale events and failovers. We talk through how capacity shortfalls show up in real life—zones that are full, SKUs that vary by location, and limited supply for GPU-heavy instances, and the patterns that help: design for multiple zones and regions, add retry and fallback logic with flexible SKUs, balance spot with on-demand, and hold a baseline with reservations or time-bound commitments. We close on the business side: the price of headroom, when commitments make sense, and simple pipeline and monitoring checks so "no capacity" errors fail fast instead of 30 minutes into a deploy. Links AWS Auto Scaling allocation strategies AWS EC2 Capacity Reservations AWS insufficient capacity guidance AWS Savings Plans AWS Service Quotas Azure On-demand Capacity Reservations Azure quotas overview Azure region pairs Azure subscription and service limits Azure VM allocation failures Azure VM Scale Sets orchestration modes (Flexible) GCP Compute Engine Reservations GCP quota alerts and monitoring GCP Regional Managed Instance Groups GCP resource availability errors Google Cloud quotas overview Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0026 - Are Your Cloud Costs Too Damn High??? Cloud cost optimization is about designing systems that perform efficiently without wasting money. In this episode, Carl and Brandon break down how AWS, Azure, and Google Cloud help teams rightsize compute, manage storage tiers, and control networking costs. They talk through savings plans, spot instances, lifecycle management, and data transfer strategies that keep performance high and waste low. The discussion then moves into monitoring, automation, and FinOps culture, where budgets, policies, and shared accountability make optimization stick. They cover dashboards, tagging, auto-shutdown routines, and partner-led programs that unlock funding and deeper discounts. Real-world stories from enterprises and startups highlight one key truth: cost management is not a cleanup exercise, it is an ongoing habit that keeps cloud architectures both efficient and sustainable. Links AWS: Well-Architected Framework – Cost Optimization pillar AWS: How to Use AWS Well-Architected with Trusted Advisor for Cost Optimization AWS: AWS Savings Plans AWS: Amazon EC2 Spot Instances Azure: Microsoft Cost Management + Billing (overview) Azure: Quickstart: Start using Cost Analysis Azure: Common cost analysis uses in Cost Management Azure: Control Azure spending and manage bills (learning path) GCP: Create, edit, or delete budgets and budget alerts (Cloud Billing) GCP: Cloud Billing Budget API overview GCP: Committed Use Discounts (Compute) GCP: Understand your bill – pricing & billing (Google Developers) Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0025 - The Sound of Security Security is more than a feature, it's a pillar of the Well-Architected Framework. In this episode, Carl and Brandon explore how AWS, Azure, and GCP approach security across identity and access, infrastructure defense, data protection, monitoring, governance, and the shared responsibility model. They compare tools and practices like IAM, RBAC, and conditional access; network firewalls, WAFs, and DDoS protection; encryption at rest and in transit; and incident detection and automated remediation. The conversation also dives into security testing, drift detection with IaC, compliance posture, and how policy enforcement differs across the big three. The episode closes with a reminder that cloud security is always shared, and is never finished. Links AWS: Well-Architected Framework – Security pillar AWS: Identity and Access Management (IAM) AWS: AWS Shield and WAF AWS: Amazon Macie AWS: Amazon GuardDuty AWS: AWS Config Azure: Azure Well-Architected Framework – Security Azure: Microsoft Entra ID (Azure AD) Azure: Azure Role-Based Access Control (RBAC) Azure: Azure Key Vault Azure: Defender for Cloud Azure: Microsoft Sentinel Google Cloud: Google Cloud Architecture Framework – Security Google Cloud: IAM overview Google Cloud: Cloud Armor Google Cloud: Cloud KMS Google Cloud: Data Loss Prevention (DLP) API Google Cloud: Security Command Center Google Cloud: Assured Workloads Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0024 - Operating Excellently Operational excellence goes beyond uptime, it's about building and operating cloud systems with discipline, automation, and continuous improvement. Carl and Brandon break down what operational excellence really means, drawing a distinction between striving for perfection and building resilient, adaptable systems. They discuss how principles from AWS, Azure, and GCP converge around key practices like repeatable automation, structured change management, and process validation. The episode dives into real-world strategies for automation, incident readiness, and observability, including where and how to insert gates, use feature flags, and integrate infrastructure as code across cloud platforms. From avoiding certificate-induced outages to catching misconfigurations early, the key theme is consistency at scale. The discussion also emphasizes the cultural side, why shared ownership, retrospectives, and iterative postmortems matter just as much as tooling. Links Ansible: Ansible community documentation AWS Docs: Amazon CloudWatch documentation overview AWS Docs: Operational Excellence whitepaper AWS Docs: Prescriptive Guidance: Operational Excellence AWS Docs: Using CloudWatch dashboards and alarms AWS Docs: Well‑Architected Framework – Operational Excellence pillar AWS: Getting started with Amazon CloudWatch Google Cloud: Continuously improve and innovate Google Cloud: Manage incidents and problems Google Cloud: Operational Excellence pillar overview Google Cloud: Operational readiness & performance using CloudOps HashiCorp Docs: Terraform configuration language reference HashiCorp Docs: Terraform documentation Microsoft Docs: Automation of tasks with PowerShell in Power Platform Microsoft Learn: Azure Automation documentation Microsoft Learn: Azure Monitor documentation Microsoft Learn: Operational Excellence maturity model Microsoft Learn: Operational Excellence overview & quickstart Microsoft Learn: Operational Excellence principles (maturity model, practices) Microsoft Learn: PowerShell documentation PowerShell Universal Docs: PowerShell Universal platform guide Red Hat Docs: Ansible Automation Platform guide Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0023 - Turbocharged: Mastering Performance in Cloud Architecture Cloud performance is one of those words that everyone agrees matters, but often means different things depending on who you ask. Is it latency? Is it autoscaling? Is it picking the right SKU size? We cover the fundamentals of designing for performance in the cloud: how to select the right compute options, when to scale up or out, and what it takes to reduce latency across global workloads. We explore autoscaling strategies, observability tooling, cost tradeoffs, and real-world tuning stories—plus we wrap with a cheat sheet of optimization tools across AWS, Azure, and GCP. Performance isn't just about throwing more cores or RAM at a problem. It's a set of design choices you make continuously—choices that affect cost, scalability, and user experience. Use the principles and tools in your cloud provider to experiment, monitor, and improve. Producer's note: we encountered some technical issues during recording, so apologies for the audio quality in some parts. The content is still solid, and we hope you find it valuable! Links: AWS Trusted Advisor AWS Well-Architected Framework Azure Advisor Azure Well-Architected Framework – Performance Cloud Load Balancing (GCP) GCP Architecture Framework GCP Recommender PerfKit Benchmarker SLOs and SLIs (Google SRE Workbook) Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0022 - What is Cloud Resiliency, Really? Carl and Brandon break down the core concepts behind cloud resiliency, availability, reliability, and redundancy — how they relate, where they differ, and why understanding those distinctions is critical. Just because a service is "always on" doesn't mean it's resilient. They explore the difference between planned and unplanned outages, how graceful degradation works in practice, and why resiliency is measured by recovery, not just uptime. It's not just about uptime. It's about what breaks, how you recover, and what keeps going when everything else doesn't. They also cover the architectural side: distributed systems, zone-aware deployments, chaos testing, and recovery strategies that go beyond documentation. With real-world failure scenarios and practical planning advice, this episode helps cloud teams build for failure — before it happens. Links: AWS | Failover with AWS AWS | Well-Architected Framework: Reliability Pillar Azure | Reliability design principles Azure | Resiliency Overview Azure | Well-Architected Framework: Reliability Pillar Google Cloud | Architecture Framework: Reliability Pillar Google Cloud | Patterns for scalable and resilient apps Google Cloud | Site Reliability Engineering (SRE) Book principlesofchaos.org | Principles of Chaos Engineering Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0021 - The 9 Circles of Dependency Hell 🔥 Carl and Brandon descend into the fiery depths of Dependency Hell, exploring nine common (and painful) challenges that plague developers working in modern cloud environments. From version mismatches to licensing traps, each "circle" offers insights, real-world examples, and actionable tips for escaping the chaos. If you've ever watched a cloud deployment crash because of a transitive dependency or scrambled to patch a vulnerability from three layers down in your stack, this episode is for you. Links Reddit: I'm harvesting credit card numbers… FOSSA on Polyfill Supply Chain Attack FOSSA – License Compliance Tool Snyk – Security Scanning Dependabot – GitHub Security Updates Aqua Trivy – Vulnerability Scanner Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0020 - The 3 M's of Going to the Cloud If you've been thinking of moving to the cloud, or are in the first steps of your journey, Carl and Brandon cover the 3 M's of going to the cloud: Migrate, Modernize, and Manage. The hosts cover key points in planning your move, including analyzing and taking inventory if your current on-premises environment, multiple cloud provider options, and the importance of understanding your technical needs based on possibly hidden dependencies in your solution, and starting to think about Day 2 Operations. Sharing real world experience of their own journeys, this episode will give you a lot to think about as you and your team plan the next steps in your journey. Links 10 Practical Tips for On Premise To Cloud Migration | Zeet.co Migrate to Google Cloud: Get started | GCP The difference between day-0, day-1, and day-2 operations | Octopus Deploy What is cloud migration? | AWS What is cloud migration? | Microsoft Azure Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0019 - All Your Data Are Belong to Us In this episode, Carl and Brandon deep dive into the world of data storage in the cloud! With numerous options, different paradigms, and a plethora of scenarios to consider, they discuss the pros and cons of each. They also touch on some "non-traditional" data storage options, such as using an in-memory cache as your primary database. Are you a polyglot database user? Do you have a favorite database that you use no matter what the scenario is? Join us to hear the discussion on both sides of the issue! Links Choosing a Data Store | Azure Architecture Center Choosing an AWS storage service | AWS Navigating Google Cloud: a decision tree for storage workloads | GCP Polyglot Persistence | Wikipedia Redis as a Database Elasticsearch Apache Lucene Apache Solr Azure AI Search Amazon Kendra Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0018 - We Can Hardly Contain Ourselves! In today's episode, Carl and Brandon dive deep into container technology. They cover everything from the container file to orchestrating containers on a cloud platform. Furthermore, Carl and Brandon discuss how Docker is not the end-all-be-all of container technology, and options that you have to use instead of Docker. If you want to learn more about what containers are, how they work, why you would want to use them, and how they apply to more than just the cloud, this is the episode for you! Links Apache Mesos Buildah Docker | Multi-stage builds Docker GitHub | GoogleContainerTools | distroless GitHub | PiHole GitHub | PiKaraoke Google Cloud Architecture Center | Application development resources Google Cloud Blog | 7 Google best practices for building containers Google Cloud Blog | Kubernetes best practices: Setting up health checks with readiness and liveness probes Google Cloud Blog | Kubernetes best practices: terminating with grace Harbor Helm k3s Kubernetes | Configure Probes Kubernetes LXC | Linux Containers Podman Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat  

Episode 0017 - The Source is with Us In this episode, Carl and Brandon speak with Brian Munzenmayer, who shares his extensive experience in the open-source community. Brian discusses his journey from fixing simple typos in documentation to becoming a key maintainer of a large open source website that you've probably used. The discussion delves into the importance of community engagement in open-source projects, the spectrum of contributions, and the various roles individuals can play, from coding to organizing and managing projects. Brian also touches on the challenges of maintaining open-source projects, including the risk of burnout and the need for sustainable practices. The episode also explores the broader impact of open-source software on the tech industry, highlighting how contributions can influence major projects and even corporate products. Brian emphasizes the value of open-source work in professional development and the importance of fostering inclusive and collaborative environments. The episode concludes with insights into the future of open-source software and the ongoing need for community-driven innovation. And of course, we have to mention that Brian is the author ofApproachable Open Source, which is available now for purchase! Links Approachable Open Source by Brian Muenzenmeyer. A brief book with a big vision. Approachable Open Source on Bluesky Brian on Bluesky Brian on LinkedIn Brian's Website Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat  

Episode 0016 - Control All the Things! 🛩️ In this episode, Carl and Brandon dive into the world of control planes, starting with what they are and how they differ from other planes you may see in your solutions and the providers they run on. They chat about the balance between automation and manual operations, and share examples from popular cloud services and technologies like Kubernetes, AWS, and Azure. Then, they explore the key functions of a control plane, such as resource management, policy enforcement, and tenant, security, monitoring, and configuration management. Carl and Brandon also take a closer look at control planes in Kubernetes, explaining the roles of components like the API server, etcd, controller manager, and scheduler, and how they work together to manage clusters. Finally, they discuss the challenges and benefits of deploying and managing control planes across multiple cloud providers, and share best practices for keeping things consistent in multi-cloud and hybrid environments. Links AWS Control planes and data planes Azure control plane and data plane Crossplane.io Kubernetes | Control Plane radius Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat  

Episode 0015 - Dude, Where's My Server? Today, Carl and Brandon cover a comprehensive overview of serverless computing, starting with its importance and benefits. We explain the serverless model, highlighting the differences between serverless and traditional computing, and addresses common misconceptions. The Big Three Cloud provider offerings are covered, including Azure Functions, AWS Lambda, and Google Cloud Run. Each service is explored, with real-world use cases, key features, and best practices for building and deploying serverless functions. We also delve into the challenges and considerations of serverless computing, such as cold start latency, security concerns, and vendor lock-in. The discussion concludes with predictions for the future of serverless computing, including emerging trends, the rise of multi-cloud strategies, how AI may change the game, and the increasing focus on security and compliance. Links Apache Airflow AWS Lambda AWS Step Functions Azure Event Grid | Cloud Event Schema Azure Event Grid Azure Functions | Durable Functions | Monitoring Dashboard Azure Functions | Durable Functions Azure Functions Azure Logic Apps Cloud Events Google Cloud Composer Google Cloud Run Prisma Cloud | Secure hosts, containers and serverless across multicloud and hybrid environments Trend Micro | Azure Serverless Security Risks Exposed by New Study Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0014 - Smooooth Operator: Configuring Your Architecture 🛠️ In this episode, Carl and Brandon dive deep into the world of configuration, exploring various methods for system, app, and user-facing config. Starting with hard-coded values and whether there is ever a time for hard-coding, weighing the benefits and drawbacks. The conversation then shifts to configuration files, including web.config, app.config, and various environment-specific files such as .env files for backend and frontend uses. Carl and Brandon also explore feature flags, databases, and SaaS options for configuration, such as LaunchDarkly, and delve into DevOps patterns, including pipeline sourcing and configuration services like AWS AppConfig and Azure App Configuration. Finally, they cover secrets management with services like Azure Key Vault and AWS Key Management Service. Links Make hard-coding your default choice | Enterprise Craftsmanship Shared library vs Enterprise development | Enterprise Craftsmanship The Pitfalls of Hard Coding: Why Config Files Are Essential in Data Science Projects AWS AppConfig AWS CloudHSM AWS Key Management Service Azure App Configuration Azure Key Vault LaunchDarkly Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0013 - What is the Cloud☁️? Carl and Brandon delve into the fundamentals of cloud computing, exploring its definition, history, key components, and the various "types" of clouds such as public, private, and hybrid. The hosts also highlight the numerous benefits of cloud computing, including cost efficiency, scalability, flexibility, and enhanced security. The episode also addresses common challenges like security concerns, compliance issues, and managing costs, while offering insights into the future of cloud computing with emerging trends like edge computing and AI integration. Links What is Cloud Computing? | Microsoft Azure What is Cloud Computing? | AWS What is Cloud Computing? | Google Cloud Advantages of Cloud Computing | Google Cloud Backup and Disaster Recovery | Microsoft Azure Security | Microsoft Azure Shared Responsibility Model | AWS Shared Responsibility Model | Microsoft Azure Shared Responsibility Model | CrowdStrike Why We're Leaving the Cloud | 37signals We Have Left the Cloud | 37signals Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0012 - Words Mean Things In our latest podcast episode, Carl and Brandon explored the fundamental aspects of cloud computing, focusing on Regions, Availability Zones, Quota, and Capacity. They discussed how regions are collections of zones, each with high-bandwidth, low-latency network connections, and the importance of deploying applications across multiple zones and regions to ensure fault tolerance and high availability. They also delved into the differences between logical and physical zones, and how regional resources can be accessed by any zone within that region. Additionally, they examined Azure's approach to paired regions and the need for custom geo-redundant capabilities in newer regions. The conversation then shifted to the concepts of quota and capacity in cloud computing. Quotas, synonymous with limits, ensure that each service can offer a minimum amount of resources. Carl and Brandon discussed the different types of quotas, including soft limits that can be raised through support requests, and the architectural options available when more resources are needed. They highlighted the importance of diversifying resource types to overcome quota limits and enhance application resilience. Finally, they examined capacity limitations, the concept of capacity reservations in Azure, and the differences between on-demand capacity reservations and reserved instances. Links Regions vs Zones Logical vs Physical Zones Azure - Paired Regions Quota vs Capacity Google Cloud Quotas AWS Service Limits Capacity Reservation (Azure) Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0011 - m*cro-services Carl and Brandon delve into the fascinating world of microservices, starting with a brief introduction and a comparison to macro-services like monolithic and modular monolith architectures. We explored the evolution from monolithic architectures to microservices, highlighting the advantages such as scalability, agility, resilience, and technology diversity. We also discussed the granular scalability of individual services, the independent development and deployment of services, and the use of different technologies for each service. However, we didn't shy away from the challenges, addressing the increased complexity, operational overhead, and resource consumption associated with managing distributed systems. Links Macro-services to Nano-services: Evolution of Software Architecture Scaling up the Prime Video audio/video monitoring service and reducing costs by 90% Performing a Rolling Update | kubernetes Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0010 - Risky Bidness: Ripped from the Headlines In this episode, Carl and Brandon explored the recent CrowdStrike outage and the lessons to take from the event as it relates to high availability, business continuity, and disaster recovery (HA/BCDR) strategies in the cloud. The incident underscored the need for redundancy, swift response, and well-defined recovery procedures. Surprisingly, we drew parallels to the banana crisis of the 1950s. The monoculture of the Gros Michel banana left the industry vulnerable to Panama disease. The lesson? Diversity in dependencies matters—whether in tech or agriculture. Remember: HA/BCDR and diversity are key to resilience. 🎙️🍌🔒 Links: CrowdStrike IT Outage Explained by a Windows Developer | Dave's Garage on YouTube CrowdStrike Update: Latest News, Lessons Learned from a Retired Microsoft Engineer | Dave's Garage on YouTube Remediation and Guidance Hub: Falcon Content Update For Windows Hosts | CrowdStrike Build high availability into your BCDR strategy | Microsoft Docs, Azure Architecture Center Protect and recover in cloud management | Microsoft Docs, Cloud Adoption Framework Imperial Scaling Banana by smc | Printables Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0009 - Knowing Your (Cloud) Tools In this episode, we delve into the world of "Cloud Tooling". We explore how different cloud platforms take similar approaches to tooling, with a variety of tools such as command-line interfaces (CLIs), RESTful APIs (and even gRPC), as well as programming language-specific SDKs. We discuss the spectrum of Graphical User Interfaces (GUIs) and Command Line Interfaces (CLIs), comparing portals, CLI, and Infrastructure as Code (IaC) strategies. We also cover the differences between various Integrated Development Environments (IDEs), and the trend of living in the terminal/shell to be "leetcoderz". The episode also touches on the increasing popularity of the shell among coders and streamers, and the importance of achieving consistent experiences with different shells. Links Azure Developer CLI Overview AWS CLI AWS Shell (Interactive) CloudFormation CLI GCP CLI GCP Cloud API Overview API Design GCP SDKs - Client Libraries Shell Customizations Oh My Posh Brandon's Oh My Posh Configuration zinit ohmyzsh How Terminals Work Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0008 - Container All the Things! In this episode, Carl and Brandon delve into the world of containers, exploring their benefits and complexities. We discuss how containers compare to traditional server deployments and virtual machines, highlighting their advantages in development speed, reliable deployments, and consistency across different environments. However, we also touch on the challenges they present, such as complexity, networking, and security issues. We further explore the concept of container layers, the role of container runtimes, and the importance of container registries and orchestrators. Show links: Understanding Containers Best Practices for Building Containers Demystifying a Docker Image Open Container Initiative Containerd Migrating from Dockershim Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0007 - What the WASM? In this episode, we are joined by our first guest, Steven Murawski, a Principal Cloud Advocate at Microsoft, who provides an insightful discussion on WebAssembly (WASM) and its role in enabling interoperability across programming languages. The conversation delves into Web Assembly's objective of creating a portable execution format for multiple languages with near-native performance, and how it is designed to create a new interface when transitioning from the browser to the server-side. We also explore how WebAssembly can be leveraged to modify application behavior by publishing interfaces for scenarios such as incoming changes, logging, or composing rule components, and the potential standalone use cases in a cloud ecosystem. We also discuss the possibilites of SDKs as wrappers around REST APIs or other shared endpoints, the role of different runtimes like wasmtime and Spin, and the concept of "worlds" in WebAssembly. We would like to extend our gratitude to Steven for joining us and sharing his valuable insights! Show links: Web Assembly System Interface (WASI) Web assembly system interface WASI 0.2 Launched Azure AKS Use WASI Node Pools Component Model Component Model WIT WASM Runtimes Wasmtime Wamr JCO containerd shim Fermyon Fermyon - Spin Fermyon - SpinKube Getting Started with Fermyon Wasmcloud Wasmcloud .NET .NET WASI SDK C# (and .NET) in WebAssembly WASI Developer Experience Goals DeisLabs Hippo Yo Wasm Binding Generation Wit Bind Gen Additional Learning Resources WASM by Example VS Code and WASM VS Code Extensions and WebAssembly Hyperlight Microsoft Build 2023 Inside Azure Innovations - Hyperlight Extending Web Assembly to the Cloud Open Source Projects Cloudflare Cobweb Azure Samples - AKS Store Demo Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0006 - Who's Your Landlord? In this episode, Carl and Brandon discuss the many layers of tenancy within a cloud solution. From single tenant to full multitenant, there are many options to consider. Additionally, building on the past episodoes of IaC and DevOps, Carl and Brandon talk about the disciplines required to move into a modern and automated solution that can scale with your organization and its services. Show links:   What is multitenancy? | CloudFlare Landing Zones AWS Azure GCP Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0005 - Your Ops Are in My Dev In this episode, Carl and Brandon cover a wide range of topics related to DevOps, including the technical and cultural aspects of DevOps, the role of scripting and automation, DevOps tools and infrastructure, communication and teamwork, and additional points on platforms like GitHub and Jira, monitoring tools, and metrics reporting. Show links: DevOps on AWS DevOps on Azure DevOps on GCP Tooling Azure DevOps Bitbucket Chef Circle CI GitHub, the world's source code repository GitLab Jenkins Octopus Deploy Puppet DevSecOps Periodic Table Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0004 - From Portal to Code Following the conversation on Deployment Stamps, Carl and Brandon dive into the concepts of Infrastructure as Code (IaC) and its applications in cloud computing. The hosts discuss the benefits of using IaC, including version control and transparency in infrastructure deployment, making it easier to understand what has been built and why. They also highlight the importance of governance, such as naming conventions, in IaC, as this can make it easier to find resources later on. Carl and Brandon cover both first and third-party IaC frameworks, as well as pros and cons of each. Show links: IaC Frameworks First-Party (Cloud Provider-Specifid) AWS Cloud Formation Azure ARM/Bicep GCP Deployment Manager Third Party (Cloud Agnostic) Ansible Crossplane.io Pulumi Terraform OpenTofu Other Links of Interest Azure Verified Modules Hashicorp Joins IBM How an empty S3 bucket can make your AWS bill explode Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0003 - Paying Forward the Postage   Carl and Brandon discuss the Deployment Stamp pattern and how it can improve your efficiency in the cloud. Create reproducible deployments across multiple environments, save on costs, and scale dynamically to meet demand.   Show links: Deployment Stamps 101 | blog.devgenius.io Types of GitHub accounts | GitHub Docs About organizations | GitHub Docs Azure subscription limits and quotas | Microsoft Learn Scale and manage IoT solutions with deployment stamps | Microsoft Learn Architectural approaches for the deployment and configuration of multitenant solutions | Microsoft Learn Deployment Stamps pattern | Microsoft Learn Coding Blocks Podcast Importance of Data Structures, Bad Documentation and Comments and More | Coding Blocks Podcast Cattle vs Pets | DevOps Explained | hava Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0002 - Agile Hobbies   Carl shares his journey of transitioning a 20-year-old hobby project into a robust app, highlighting the importance of modern software development practices. The hosts discuss version control, formatting, and the concept of cloud readiness, emphasizing their relevance in both professional and personal cloud-based development.   Show links: Using GitHub Issues Developing Inside a DevContainer Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat

Episode 0001 - aaS's of the Cloud In this episode, Carl and Brandon discuss the various "as a Service" models, including Infrastructure as a Service (IaaS), Platform as a Service (PaaS), Software as a Service (SaaS), and Containers as a Service (CaaS). They explore the differences between these models and how they can be used to build and maintain cloud solutions. The hosts also discuss the concept of shared responsibility in the cloud and differences across the types of cloud services. Shared Responsibility Model Pizza as a Service 2.0 PaaS vs. IaaS vs. SaaS vs. CaaS: How are they different? Visit us at: twitter.com/CloudChatTech discord.cloudchat.tech [email protected] linkedin.com/company/cloudchat aaS's of the Cloud

Welcome to episode ZERO of CloudChat! Introducing the best bi-weekly [whatever that means] podcast that covers cloud-focused software and architectural discussions. Stay up to date with the latest and greatest in the cloud from Carl and Brandon and soak in the great discussions on all the classic design patterns that are still tried and true.