Forem: Muhammad Adil

✨ Defense Against the Dark Arts of SaaS: Single vs Multi-Tenancy

Muhammad Adil — Fri, 26 Sep 2025 19:20:42 +0000

Imagine you’re at Hogwarts. Every wizard needs a wand, but here’s the problem: do you give each wizard their own wand, or do you enchant one wand to be shared among many?

That’s exactly the choice we face when building SaaS (Software-as-a-Service) applications.

Think of SaaS Application as a magical shop in Diagon Alley. Instead of everyone brewing their own potion at home, they subscribe to your shop and use your ready-made potions. Examples: Gmail, Slack, Notion. You don’t install them yourself; you “rent” the service.

The catch? How do you handle all these customers (tenants)? That’s where tenancy models come in.

🧙 Single-Tenant (Each Wizard Has Their Own Wand)
Every customer gets their own dedicated resources (database, instance, or server).
Pros:
✅ Strong isolation (Hermione’s spells won’t mess up Ron’s work).
✅ Easier compliance/security.
Cons:
❌ Costly to scale (imagine crafting a new wand for every wizard).
❌ Harder to maintain (every wand might break differently).

🧙 Multi-Tenant (One Wand Shared by Many Wizards)
All customers share the same app/resources, but data is partitioned logically.
Pros:
✅ Cost-efficient (fewer wands to make).
✅ Easier to upgrade everyone at once (one spell = everyone benefits).
Cons:
❌ Isolation is tricky (if Voldemort corrupts the wand, everyone’s in trouble).
❌ Performance tuning gets complex.

⚡ Why Does This Matter ?
Startups often go Multi-Tenant → cheaper, faster.
Enterprises may prefer Single-Tenant → secure, compliance-friendly.
Some systems even offer a hybrid model — the Sorting Hat decides based on the customer’s needs.

💡 Takeaway :
Building SaaS applications isn’t just about coding features. It’s about choosing the right tenancy model to balance cost, performance, and security.

In the next lessons of this “Wizarding Series,” we’ll dive deeper into:

🔮 Levels of isolation in a multi-tenant environment.
🔮 Implementation strategies with a real world projects.
🔮 Best practices to stop Voldemort (downtime, breaches, scaling nightmares).

So, apprentice wizards, sharpen your wands and IDEs — this is your first Defense Against the Dark Arts class in SaaS! 🧙‍♂️✨

🚀Life of a Software Engineer: How I Patched an NPM Package and Saved the Day

Muhammad Adil — Fri, 19 Sep 2025 15:36:10 +0000

A couple of days ago, we hit a real wall in one of our projects. If you’ve ever worked with client-side PDF/doc generation, you’ll know this pain 👀.

With the latest Chrome update, some internal style and rendering changes came in. Sounds good for browsers… but for us? 💥 Boom — all our client-side PDF generation went from a few seconds ⏱️ to a terrifying 10–15 minutes. The app froze, users got frustrated, and our docs feature was basically unusable.

The culprit: our trusted but aging library html2pdf.js, which relies on html2canvas to render HTML into a canvas and then stuff it into a PDF. Pretty cool stuff, but not so cool when Chrome breaks it.

👉 Red flag reminder: Client-side doc generation was never ideal. Server-side is always the safer bet. But since the project was already built this way, we had to roll with it.

Now here’s where things got interesting:

Tried server-side generation with Puppeteer + templates — worked for simple docs ✅, broke for complex ones ❌
Dug through GitHub issues like a detective 🕵️‍♂️.
Finally found a gem 💎: a library called Snapdom, which could step in for html2canvas.

I rolled up my sleeves, pulled down the HTML2PDF source code, and after hours of poking around, found the “hidden goblin” 🐉 — a single function where html2canvas was doing the heavy lifting. Swapped it out for Snapdom, did some param tweaking, bundled it back into Angular, and… VOILÀ 🎉.

⚡ With minimal changes to our existing code, docs were back to downloading in seconds. The fix took a day of focused work — way better than the wild goose chase with headless browsers.

✨ Key Takeaways:

Always pay attention to NPM warnings ⚠️ — ignoring them is like an ostrich burying its head in the sand.
Before diving headfirst into code, research 🧑‍💻. Someone might’ve already hit (and solved) the same issue.
Temporary fixes are fine — they buy you time to work on the real, long-term solution.

At the end of the day, sometimes the fastest way forward is not rewriting everything, but tweaking just the right piece in the puzzle 🧩.

💡 Have you ever patched a dependency yourself to save a project? Would love to hear your war stories!

Here is the code change comparion:

My First Hacktoberfest

Muhammad Adil — Wed, 28 Oct 2020 17:48:56 +0000

[Introduction]

My name is Muhammad Adil. I am a Computer Science student currently pursuing my Bs CS degree from UET,Lahore. I am a passionate Front End developer(Vue.js) and Desktop Developer(C++).
I decided to join Dev Community because one of our DSC Leads told us that Dev Community is a social media platform for Developers and every developer should be a part of this community.

Background

I have been coding for around two years now and still I was unaware of what Open Source is, untill last year in 2019 when I joined DSC(Developers Student Clubs) community and I came to know about Open-Sourcing and Github. I was very fascinated by the idea of sharing your code online and I started using Git and Github.

Progress

"I love coding, its my passion" but I hesitated to participate in the "Hacktoberfest 2019" and thought whether I am good enough to participate in the Event. Finally, this year I participated in the "Hactoberfest" and completed the challenge. This gave me the confidence to contribute more to the open-source community.

Contributions

The contributions I made in this Hactoberfest are:

A Protfolio design template (https://github.com/Muhammad-Adil-arch/website-for-company/tree/master/Muhammad-Adil-arch_%2310)
I chose this project because really like to try different designs for protfolios.
A covid-19 stats web app (https://github.com/Muhammad-Adil-arch/Covid-19-Stats)
I chose this project because I had seen many similar web applications and I wanted to try one.
A simple Contact Management System in C++ (https://github.com/Muhammad-Adil-arch/Contribute-to-HacktoberFest2020/tree/main/Projects/Contact%20Management%20System)
I chose this project because I really like to create Console and GUI desktop Applications.
A Simple C++ Function to swap the values without using temporary variable (https://github.com/Muhammad-Adil-arch/Hacktoberfest-2020/blob/main/Programs/Swap.cpp)

Reflections

Overall, my Hactoberfest experience was really great. I learned alot new things like how to clone a repository and then contribute in it. This event also showed me that there is alot more things that I need to learn about the latest web and desktop technologies.
Since it was my first hacktoberfest, I will surely participate next year.
Before, Hacktoberfest I hardly had any followers and now I have around 11 followers and I am very happy with it.
For next step, I really want to contribute for the Vue.js Community as the community is growing and it still needs help to grow into a big Open-Source Community like React.

Thanks for this great experience.