text stringlengths 0 2.67k |
|---|
• The project has a native orchestration system that handles service discovery and connection management, making it more portable than Kubernetes. |
• wasmCloud's operator uses interface-driven design to scale workloads natively and take advantage of WebAssembly components' small size and fast startup times. |
• The backend of wasmCloud is designed as an application platform, providing building blocks for applications rather than just infrastructure tools like Kubernetes. |
• wasmCloud uses NATS as its networking layer |
• wasmCloud provides a command and control API for starting, stopping, and linking distributed applications across multiple clusters |
• WADM (Web Application Model) is an orchestration layer that allows users to define components and requirements for their application |
• WADM can manage applications across multiple Kubernetes clusters, clouds, or data centers |
• The wasmCloud operator integrates with Kubernetes, allowing users to deploy wasmCloud hosts and use Kubernetes tooling |
• The goal of wasmCloud is to provide a cloud-agnostic infrastructure that allows users to run applications on any platform without modification |
• Designing WebAssembly (WASM) with resiliency and scalability in mind |
• Importance of responsibility and control when building with WASM |
• How wasmCloud addresses the needs of users and customers in a changing technology landscape |
• Comparison of wasmCloud to other event-driven runtimes, such as Knative |
• The Bytecode Alliance and its goal of creating modular APIs for WebAssembly |
• The need for capability-driven interfaces in modern software development |
• Concerns about supply chain attacks and security |
• Issues with low-code solutions and automation of infrastructure |
• Problems with giving one service control over entire infrastructure |
• Discussion of Kubernetes and the "trash bag method" of deployment |
• Benefits of abstraction in development with WASM (WebAssembly) |
• Importance of separating concerns and responsibilities in development and operations |
• WebAssembly (WASM) ecosystem overview |
• wasmCloud features and differences from Kubernetes |
• Balancing security and usability in WASM applications |
• Request for Comments (RFCs) and their importance |
• Personal anecdotes about reading RFCs and white papers for learning and problem-solving |
• RFCs (Request for Comments) define internet protocols and technologies |
• Research papers and white papers explain how technology works, while RFCs specify what technology should be |
• Understanding foundational technologies like DNS, IPv4, and IPv6 is crucial |
• White papers help build systems, while RFCs help dissect them |
• The conversation touches on the importance of learning from resources and experts in specific areas |
• Networking can be complex and confusing, but breaking it down into smaller parts helps |
• Having friends or colleagues who are experts in various areas can make complex topics more manageable |
• Knowing when to ask for help and connecting people with the right expertise is a valuable skill. |
• The importance of sidestepping ticket filing processes and instead building relationships with technical support personnel |
• The existence of free public databases for finding information, such as RFCs |
• The value of having a foundational understanding of networking basics, including TCP layers and VPCs |
• The benefits of starting with basic knowledge before moving on to more advanced topics |
**Justin Garrison:** Hello, and welcome to Ship It, the podcast all about what happens after you git push. I'm your host, Justin Garrison, and with me as always is Autumn Nash. \[unintelligible 00:00:58.11\] |
**Autumn Nash:** \[unintelligible 00:01:00.18\] cup of coffee, and it's hitting... |
**Justin Garrison:** Energy... |
**Autumn Nash:** The caffeine has kicked in, y'all... |
**Justin Garrison:** It reminds me of -- you never had an old desktop, did you? a '90s desktop, with a turbo button? Did you have a turbo button on your computer? |
**Autumn Nash:** No... |
**Justin Garrison:** Oh, ma... It was the old school overclocking. Technically, it was the clock speed, and everything else was underclocked... But whoever turned off the Turbo button? |
**Autumn Nash:** There was a Turbo button? I feel I've missed so much... |
**Justin Garrison:** It was good times. |
**Autumn Nash:** You old people had all the cool stuff. I had a computer 2000... 2001? 2002 was my first computer. But it was a computer from the '90s. What was the -- E-machine, I think is what it was? |
**Autumn Nash:** My first computer was the iMac. It was \[unintelligible 00:01:50.23\] |
**Justin Garrison:** That's not even a computer, that's a product. |
**Autumn Nash:** No... It was the cute little desktop, and I was in love with it. I've never loved something so -- I played Descent space game, and Oregon Trail, and then I learned what a file system was, and the nerd in me blossomed that day. |
**Justin Garrison:** I never played Oregon Trail. That's what I missed out on. |
**Autumn Nash:** What is wrong with you? I have a shirt that says "I died of dysentery from the Computer Museum \[unintelligible 00:02:23.02\] I'm so sad that closed down... I was looking at it and I was "Justin is coming to Seattle", and I was "I'll take him to the computer museum", and it closed down. It made me so s... |
**Justin Garrison:** Yeah, I remember I was probably in second or third grade... |
**Autumn Nash:** If we get rich, we've got to open the computer museum again. |
**Justin Garrison:** That's just gonna be my garage. I have so much old stuff in here... |
**Autumn Nash:** Dude, they have one of those Hidden Figures computers in a room. It's so cool. And every old computer -- like, the computers of my childhood were in there... And you can play games on them. That was one of the oldest Linux I've ever played with, was they had a whole room of just old computers, and you ... |
**Justin Garrison:** I am on the lookout right now literally for a project to find old Linksys WRT54G's, the old, the blue... |
**Autumn Nash:** If you find an old iMac, you better get it for me. |
**Justin Garrison:** Oh, these old iMacs, they're a couple 100 bucks. I actually saw one, I was a thrift store... |
**Autumn Nash:** And you didn't get it for me? |
**Justin Garrison:** They were $300. |
**Autumn Nash:** Okay, I would have Apple paid you if you had told me about it... Because you keep trying to suggest I get that dude's iPad cases, I was "I could buy a real iMac for that price." I don't know what I would do with it though... |
**Justin Garrison:** I have a \[unintelligible 00:03:41.03\] I could throw a rock at it right now. |
**Autumn Nash:** I'm trying to think of what I would do with it. My kid has my old iMac, and he acts he's dying because it's slow, and I'm "Sir, that was the business when I bought that..." |
**Justin Garrison:** 733 MHz |
**Autumn Nash:** I was "Just because you live in the world of fast processors and everything..." I had to use dial-up internet, okay? I had to save up for that iMac. |
**Justin Garrison:** Go get your kids a NetZero CD, and like the free 90 minutes a month... |
**Autumn Nash:** I am like the \*bleep\* parent. I'm like "If you want to get into tech, you can go build your own computer." We're going to a thrift shop this weekend, and he's going to figure out -- I was like "You need to research all the different parts of a computer and how you put it together." |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.