This is part 2 of our three-part series where we make sense of the alphabet soup of acronyms for database consistency models.
In this episode of Mobycast, we learn how the explosion of the Internet created new challenges for strongly consistent systems, leading to the "discovery" of the CAP theorem. The CAP theorem reminds us that as systems scale, errors will become more likely, forcing us to choose our priorities.
We also learn what Chris shares in common with Eric Brewer, the creator of the CAP theorem. It's a roller coaster ride that comes to a crashing halt.
Databases are one of the fundamental building blocks for cloud-native apps. And with so many types of databases to choose from, it's important to understand their consistency models so that we can make smart choices.
But with acronyms such as ACID and BASE, making sense of them can feel like swimming in a big bowl of database soup. Spoiler alert, they have nothing to do with high school chemistry class.
In this episode of Mobycast, Jon and Chris kick off a three-part series where we dive deep on this database soup. In part 1, we learn about transaction processing, the ACID acronym and say hello to strong consistency.
Technology is changing rapidly and it is a major investment to learn a new skill, technique or technology. Our knowledge gained is so hard fought that it is only natural to rely on it dearly.
But it's a mistake to hold on to this knowledge for too long - you must be open to new ideas.
In this episode of Mobycast, Chris shares with Jon a personal story about learning and growth. After being blindsided by relying on a familiar pattern, a valuable lesson is learned, one summed up well by author Stephen King when he implores us to "kill your darlings".
What is the future of containers? In this three-part series, we are exploring the promising technologies aiming to make our cloud-native apps more secure without giving up performance.
Previously, we learned all about microVMs, taking a deep dive on the most talked about microVM - AWS Firecracker.
This week on Mobycast, we finish looking at microVMs with a discussion of Kata Containers. Then we explore the world of unikernels, which promise the same benefits as microVMs but with a dramatically different approach. Oh... and somewhere along the way, Chris accidentally invents a new technology - "conternels".
Maybe you've heard some of the buzzwords everyone seems to be talking about when discussing the future of containers. Strange words like "microVMs"... "unikernels"... "sandboxes".
Have you wondered what these things are and how you can use them? Or, for that matter, should you use them?
In this episode of Mobycast, Jon and Chris continue their three-part series on the future of containers. We go deep on the most talked about microVM - AWS Firecracker. We learn how Amazon uses Firecracker and its tremendous benefits. We then discuss how to use Firecracker for your own containers and get the same great results.
With cloud computing, we started with virtual machines. They allow us to virtualize an entire server, while providing strong isolation and security.
Then containers came along. They allow us to virtualize just our applications, making containers faster and less resource intensive than VMs. But with these gains we lose strong isolation.
What if we could have the speed and resource efficiency of containers coupled with the enhanced security and isolation of VMs?
In this episode of Mobycast, Jon and Chris kick off a three-part series on the future of containers. We dive deep on microVMs, unikernels and container sandboxes, understanding what they are, how they work, and how well they combine the best of both VM and container worlds.
In episode #93 of Mobycast, we discussed secrets management for our cloud-native applications. We learned why we need secrets management and some of the possible solutions available to us.
Now that we know the "theory", it's time to put that knowledge into practice.
In this episode of Mobycast, Jon and Chris finish their two-part series on handling secrets with cloud-native apps. We show you how to easily implement secrets management for a containerized application running on Amazon Elastic Container Service (or ECS). After this episode, you'll be a pro at keeping a secret!
Applications frequently need access to sensitive data, such as database credentials, API keys, passwords and tokens.
Of course, we can't just store these secrets in plain text or hard-coded into our applications. Rather, we need to securely protect this sensitive information to ensure that only those with a "need to know" basis can access it.
In this episode of Mobycast, Jon and Chris kick off a two-part series on handling secrets for your cloud-native applications. We discuss various approaches to secrets management, ranging from basic roll-your-own techniques to fully managed solutions. We explore some of the most popular options out there and help you decide which one is best for you.
In the first two episodes of this series, we learned how to build a VPC with public and private subnets. We did a deep dive on NAT, or network address translation, and then setup a software-only VPN for secure access to the private subnets.
Now, it's time to put everything together and earn our cloud networking black belt.
This week on Mobycast, Jon and Chris conclude their three-part series on how to incorporate private subnets for your cloud network. We finish by explaining step-by-step how to move an existing ECS application onto our new private subnets. Now... go build, ninja!
Last episode of Mobycast, we began our post-coverage analysis of AWS re:Invent 2019. With a major theme of "transformation", we walked through some of the key advancements being made by AWS to drive innovation now and into the future. From supercomputing to networking to AI and ML, AWS is proof that there is "no compression algorithm for experience."
In this episode of Mobycast, Jon and Chris conclude their special two-part mini-series on this year's re:Invent conference. We finish recapping the big keynote sessions and highlight the major themes of this year's show. We close it all out by sharing our most important takeways that you need to know.
We're happy to report that we are back and survived AWS re:Invent. As promised, re:Invent is a heavyweight of a conference and this year did not disappoint!
With 4 keynotes, over 3,000 sessions, and hundreds of new product and feature announcements, we've got a lot of ground to cover. In fact, we have so much to share with you, that we are splitting this into a special two-part mini-series.
In this episode of Mobycast, we start by recapping some of the big keynote sessions and discuss the new products and technologies that we are most excited about.
In episode #89 of Mobycast, we introduced using private subnets for your cloud network. We learned about the differences between public and private subnets, as well as some of the key technologies they depend upon such as NAT, or network address translation.
We also learned that using private subnets comes with a new problem - how to access these private resources? We discussed three primary approaches, before settling on VPN as our choice.
In this episode of Mobycast, Jon and Chris continue their three-part series on using private subnets with your cloud network. We finish our network design by guiding you step-by-step in setting up a software-based VPN and building out private subnets. We also share some inside tips that will make you look like a cloud networking pro.
You may know that it is best practice to use private subnets for your cloud network. But, have you actually implemented them?
They can be challenging to setup, especially if you have an existing VPC. And using private subnets creates a new dilemma... how do you even connect to these resources?
Jon sometimes complains that Mobycast makes him eat his "security broccoli". Well, its time we add "networking cauliflower" to the mix to ensure that he (and you!) have a well-balanced cloud-native diet.
In this episode of Mobycast, we kick off a three-part series detailing step-by-step how to incorporate private subnets for your cloud network. After listening to these episodes, you'll be able to setup your VPC like a true networking ninja!
Let's get ready to rumble! It's that time of year when we head to Las Vegas with 50,000 of our closest friends for the biggest AWS event of the year: re:Invent.
Five days long, with more than 2,500 sessions, taking place in 6 huge venues spread over 2.5 miles, re:Invent is a heavyweight of a conference. If you don't plan ahead, re:Invent will take you down in a TKO.
In this episode of Mobycast, Jon and Chris are in your corner, breaking down this year's event with the tips, tricks and secrets you need to make the most of re:Invent.
You may not be an expert on container networking, but wouldn't you like to impress guests at your next party by explaining the difference between "host" and "bridge" networking?
This week on Mobycast, Jon and Chris conclude their three-part series on serverless containers with AWS Fargate. We wrap our heads around container networking and its various networking modes, with particular emphasis on task networking (aka "awsvpc" mode).
We finish by pulling together everything we learned over these 3 episodes to walk step-by-step through the migration of a container from EC2 to Fargate. After this episode, you'll be the life of the party!
Docker sold its Docker Enterprise business to Mirantis last week. The internet has been abuzz with hot takes and laments for the once high flying unicorn.
In this short bonus episode of Mobycast, Jon and Chris discuss what this really means for Docker, we use some logic to calculate what the likely sale price was, and we make a prediction for what will happen to what is left of Docker within the next year.
Chris has been taking careful notes on Docker as a business for a few years now, so he has absolutely brilliant insight into what this sale means not just for Docker but for the cloud industry as a whole.
Give this bonus episode a listen and wow your colleagues with your expert analysis on Monday when you roll into the office.
In episode #85 of Mobycast, we introduced AWS Fargate, which brings the serverless concept to running containers on ECS. We discussed the features and benefits of Fargate, as well as how it differs from normal EC2 launch types.
Now it's time to dive deeper into some of the details you need to know to successfully run your containers on Fargate.
In this episode of Mobycast, Jon and Chris continue their three-part series on serverless containers with an in-depth discussion of identity and access management for ECS. We learn about the various roles you will encounter, why they are needed and how to use them. We also share a best practice that will make you look like a security pro!
The Amazon Elastic Container Service (or ECS) is the container orchestration system built by AWS. ECS features tight integration with many AWS services, and is a powerful choice for running containers in the cloud.
We first discussed ECS back in episode 3 of Mobycast. But so much has changed in the 18 months since then, bringing many major improvements. One new feature is Fargate, which brings the serverless concept to containers.
With Fargate, you no longer need to manage servers. You don't pay for idle CPU. And there is the promise of seamless scaling. Sounds perfect, right? Well, as with most things that sound too good to be true, there are some limitations and gotchas.
In this episode of Mobycast, Jon and Chris kick off a three-part series where we dive deep into Fargate. We learn the ins and outs of running containers without managing servers and discuss the trade-offs we make when ditching those servers.
In episode #83 of Mobycast, we learned that containers are normal Linux processes. But they take advantage of powerful operating system functionality that gives these processes their container superpowers. In particular, we learned about namespaces and control groups and how these features give rise to containers.
This week on Mobycast, Jon and Chris wrap up their four-part series by discussing the runtimes and platforms used to run containers in production. We dive deep on ContainerD and RunC, arguably the most important container runtime out there. We also revisit our pseudo code example of how to build a container from scratch, bringing us full circle on our quest to understand the differences between virtual machines and containers.
Containers are just lightweight virtual machines, right? No, not really. There's much more to the story than that, so we decided to do a four-part series on virtual machines versus containers.
In parts 1 and 2, we discussed virtual machines in detail and how they work. Now, in parts 3 and 4, we turn our attention to containers. Turns out, containers are not very complicated. They are just normal Linux processes with some isolation superpowers.
In today's episode of Mobycast, Jon and Chris go into depth on containers, their history and the underlying operating system technologies that make them possible. If you ever wondered why you can't run Windows containers on a Linux host, this episode will clear up the mystery.