It’s been more than a decade since I started writing blogs. Small snippets of code I tried out, turned into blogs. I myself depended on so many sources (including blogs) on the web, so this became both a learning and giving back opportunity for me. Over the years I have hosted my site on Godaddy’s WordPress platform to now managing on AWS Lightsail. It’s definitely been a fun ride. But everything good must have its end or more precisely in this case, a rebirth.
Tag Archives: software engineering
Zero Trust Security Architecture
Remember when we used to think of security like a medieval castle? High walls, a moat, and guards at the gate. Once you were inside, you were trusted. In the Tech world, that model worked great when our entire tech stack lived in a data center down the hall. Unfortunately, that castle doesn’t exist anymore.
According to IBM, the average cost of a data breach reached $4.9 million, with compromised credentials being the most common initial attack vector. Organizations that still trust their internal networks face a harsh reality: once an attacker gains authenticated access, they often have free rein to move laterally through systems. The philosophical shift from perimeter-based to Zero Trust security isn’t just about technology; it’s about survival in the modern threat landscape.
Microservices vs Monoliths vs Modular Monoliths: A 2025 Decision Framework
The question arises frequently in engineering discussions: “Should we break up our monolith into microservices?” The answer is often surprising: “Probably not” or “It depends”. This isn’t because microservices are bad—they’re not. It’s because the industry has finally moved past the religious wars where you were either team microservices or team monolith, with no middle ground. The reality in 2025 is far more nuanced.
Mikro’s Serverless Saga: From Microservices to Madness and back
This is part 2 of a humor-inspired take on Monoliths to microservices that I wrote a few years back: https://blogs.justenougharchitecture.com/monos-journey-from-monolith-to-microservices/. If you did not read that, please do so first.
Mikro was serving his consumers as always. He consistently met his promises (SLAs), and his life was good. Suddenly, he felt a stab and excruciating pain. “Damnit, what was that?” he said. To Mikro’s horror, he found himself being sliced and diced into smaller and smaller pieces. “But I thought I was already micro enough!” he wailed as functions were extracted from his very being.
Optimizing Software Engineering with the AWS Well-Architected Framework
Designing and building robust, scalable, and efficient systems is a fundamental requirement in software engineering. The AWS Well-Architected Framework is an essential resource that can significantly aid this process. Although it originates from Amazon Web Services, the principles and best practices it outlines are universally applicable. This blog aims to provide an understanding of the AWS Well-Architected Framework, its core focus areas, and its value to software engineering practices, regardless of whether you use AWS services.
Unlocking the Power of LLMs with LangChain
As an AI and software professional, you’ve likely heard the buzz around large language models (LLMs) like GPT-3, ChatGPT, and their growing capabilities. These powerful models can handle a wide range of natural language tasks, from text generation to question answering. However, effectively leveraging LLMs in your own applications can be a complex challenge. That’s where LangChain comes in.
Thoughts on dealing with burnout in tech
Mental Health with Kelsey Hightower on the always amazing Software Engineering Daily podcast – https://softwareengineeringdaily.com/2022/02/25/mental-health-with-kelsey-hightower/
This was a great podcast, and I want to thank Kelsey and Jeff for doing this talk. Burnout is a topic we do not talk about openly in the tech community; at least that is my experience over the years. I wish Jeff the very best as he navigates this. In this blog, I share some thoughts about one mental health condition that some of us face – burnout at work. My thoughts here are tied to the software engineering occupation, but it might resonate with other fields too.
Engineering Management
It has been a few years now since I moved into the role of Software Engineering Management. While there may be various reasons for one to move to this role, it is a change that comes with very little training and no guidebook. In this blog, I will go over a few areas that I felt are areas to keep an eye on when in this role (a lot of it is relevant to non-manager lead roles too).
