Why we use containers

If you've got any questions feel free to DM on Twitter @reillyjodonnell
Search for a command to run...

If you've got any questions feel free to DM on Twitter @reillyjodonnell
No comments yet. Be the first to comment.
Someone shared this image above. At first glance, I wasn’t sure about the perf implications — so let’s break it down from first principles :D Let’s deconstruct this monster Here’s the code: // Function to flatten React Context Providers. const flatte...

Intro Hello it’s me from the future! I originally was going to go over file based routing but pivoted to going over important SSR concepts with React / how Bun makes it easy. It’s full of struggles with hydration (mismatches), React entry points, and...

history? Serverless is EVERYWHERE and for good reason: nearly infinite scalability, physically closer to users, and pay-for-what-you-use pricing. But not without tradeoffs — vendor lock-in, (potentially) higher costs, and the infamous cold-starts. cf...

Powered by bash and AppleScript!

Sockets can only transmit binary (text.) Imagine we have this data const message = {id: '123', name: 'Reilly', message: 'Hey'} Here's the problem: we want to send this data to the ui but we have hundreds of useEffects spread throughout the codebase....

There are a metric shit ton of things that interact with an application that you run locally - your OS, system & env variables, software deps, & configs. It's super common in the software industry to run into problems like: "This works on my computer - I'm not sure why it's not working on yours."
There's a solution - containerization.
TLDR; containerization allows applications to run consistently on any computer no matter what the differences mentioned above may be.
Containerization packs all the important shit into a standardized environment that locks in all of the dependencies into its own isolated segment. This means that we don't have to worry about interferences between containers - we could conceptually have thousands of containers running on the same OS and there would be no risk of them interfering with each other (handling a lot of containers efficiently is difficult - which is why container orchestration platforms like Kubernetes exist.)
All of this is made possible by images - which feels like a strange word but it just refers to a "snapshot" of the configuration needed to create the standardized environment.