Blog

A client shared a problem regarding scaling tech infrastructure they faced recently. The simplest and quickest solution was adding a queue in between to manage the load.

Scalability is often a buzzword, but what does it really mean? We explore horizontal vs. vertical scaling and database optimization.

Don't reinvent the wheel is very common while building tech. But what does it even mean and when is it applicable? Here are the 4 situations when this common phrase is applicable to you.

Continuing on the previous post of Don't reinvent the wheel and when it is applicable. Let's look at resources and skills needed to build things from scratch.

Security in Software is similar to security in real-world. No system is 100% fool proof, and so our best bet is to make the system so difficult to hack, that it will take a lot of time, energy and resources for someone to breach.

A client wanted a highly available system while ensuring that no events are lost. My initial solution was to add a queue in between to maintain downtime between services.

A client wanted security and privacy like a single-tenant application but while also having the cost effective benefits of multi-tenant. Here's the hybrid approach we used.

A while ago, I was having a conversation with a founder looking to add AI to for digital marketing web based app. His concern was that a good prompt with LLM can also do what they are building.

Most of the people over-complicate tech when building the MVP / v1 of their product. Solution? Use a BaaS instead! Your GTM takes upto 5x less time.

Where does one even begin with Security for Software applications? Answer is OWASP! OWASP is an international non-profit organisation dedicated to software security.

Re-inventing the wheel in tech is challenging, and you must be careful about when and how you do it. Here are the 6 cases when you can, and should re-invent the wheel.