Every once in a while I send hand picked things I've learned. Kind of like your filter to the tech internet. No spam, I promise!
The Future of DevOps
|
Hi friends, If you had asked me about the future of DevOps / infrastructure a few years ago, I would’ve pointed straight to serverless. I don’t think that anymore. After this week’s Kubecon in Paris (amazing event by the way!), here’s a collection of thoughts and prediction on the future of tech. While serverless was a big deal, the rise of container technology and Kubernetes has been astonishing, even the biggest advocates of the technology did not expect this much adoption. Serverless, as a function-based solution, seem to be stagnating. It’s driven by practical issues like cost, complexity, and the developer experience. Plus, Amazon’s shift from Lambda to a monolith earlier this year alongside DDH’s take on it, shedding even more light on the subject, did not contribute. Looking ahead, I see a trend towards automated solutions that simplify using cloud services from providers like AWS, Azure, Hetzner, or OVH. This approach is “somewhat serverless” but leans more towards using containers. Let me explain. Examples like Heroku, Netlify, Vercel, and AWS Amplify are making it easier for developers by reducing complexity, and automating DevOps tasks. These platforms are mainly for smaller projects right now, but I believe bigger operations will soon catch on. They realize these automated solutions can take over much of the DevOps workload, especially with a bit of AI integration. I predict that such solutions like these could meet the needs of about 80% of businesses. The remaining 20% might find the cost too high or the solutions not fitting their unique needs. There’s also a wave of new technologies making cloud services faster, more efficient, and cheaper—like faster Docker builds with deopt, better microVMs with KraftCloud, and enhanced object storage (Minio), or even better block storage with SimplyBlock. It’s clear that user-friendly, integrated deployment solutions are becoming more common, promising lower costs and better performance. I’m excited to watch how this evolves and am even considering creating something myself in this space. For now, these are the trends shaping our industry’s future. |
ESPRESSO FRIDAYS
Every once in a while I send hand picked things I've learned. Kind of like your filter to the tech internet. No spam, I promise!
Focus is a huge problem in modern days. These days, lots of apps and websites try to grab our attention and keep us hooked. Most of us know we should resist these distractions. But instead of making a plan, many people just wing it. I used to do that too. But I’ve had enough. Another Instagram post, YouTube short, or funny meme won’t make me feel good about my day. In fact, they: Make my workday longer. Slow down my progress, bit by bit. So, I put together some tools and rules to help me stay...
Hi friends, On July 15th, 2019, I messed up bad. Real bad. I wanted to finish a project quickly, and show a quick POC to a customer I was working with. To make a long story short, I pushed a container, to a public repo, containing admin credentials to an AWS account. I thought of myself as a senior consultant, who delivers, fast, with no mistakes. Man I managed to break that reputation. The silver-lining however, is that I learned my lesson. So deeply so, that I’ve implemented these same...
Hi friends, Today we’re going to explore a lesser-known but incredibly powerful feature of Git: git rerere. This feature is particularly useful for anyone who frequently manages branches and encounters merge conflicts. * not a real magician What is git rerere? The git rerere feature stands for “reuse recorded resolution.” It helps to automate the resolution of merge conflicts by remembering how you’ve resolved them in the past. When enabled, git rerere kicks in as soon as a conflict occurs...