Hassan Abu Bakar

🚀 𝗦𝗶𝗺𝗽𝗹𝗶𝗳𝘆 .𝗡𝗘𝗧 𝗕𝗮𝗰𝗸𝗴𝗿𝗼𝘂𝗻𝗱 𝗧𝗮𝘀𝗸𝘀 𝗨𝘀𝗶𝗻𝗴 𝗛𝗮𝗻𝗴𝗳𝗶𝗿𝗲 Building background processes in .NET? 𝗛𝗮𝗻𝗴𝗳𝗶𝗿𝗲 is your go-to framework for managing background jobs 𝗿𝗲𝗹𝗶𝗮𝗯𝗹𝘆, 𝘀𝗰𝗮𝗹𝗮𝗯𝗹𝘆, 𝗮𝗻𝗱 𝘄𝗶𝘁𝗵 𝘇𝗲𝗿𝗼 𝗵𝗮𝘀𝘀𝗹𝗲. 🔧 𝗪𝗵𝘆 𝗛𝗮𝗻𝗴𝗳𝗶𝗿𝗲? Hangfire lets you run background tasks without writing custom threading code or managing your own workers. It handles: • ✅ Job queuing • 🔁 Retries • 💥 Error handling • 💾 Persistence • 📊 Real-time monitoring 🧱 𝗧𝘆𝗽𝗲𝘀 𝗼𝗳 𝗝𝗼𝗯𝘀 𝗶𝗻 𝗛𝗮𝗻𝗴𝗳𝗶𝗿𝗲: 1️⃣ 𝗙𝗶𝗿𝗲-𝗮𝗻𝗱-𝗙𝗼𝗿𝗴𝗲𝘁 – Run immediately in the background 2️⃣ 𝗗𝗲𝗹𝗮𝘆𝗲𝗱 𝗝𝗼𝗯 – Scheduled to run after a delay 3️⃣ 𝗥𝗲𝗰𝘂𝗿𝗿𝗶𝗻𝗴 𝗝𝗼𝗯 – Based on CRON schedules 4️⃣ 𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗮𝘁𝗶𝗼𝗻 𝗝𝗼𝗯 – Runs after another job completes 5️⃣ 𝗕𝗮𝘁𝗰𝗵 & 𝗕𝗮𝘁𝗰𝗵 𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗮𝘁𝗶𝗼𝗻 – Grouped or dependent jobs 📦 𝗖𝗼𝗿𝗲 𝗖𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁𝘀: • 🖥️ 𝗗𝗮𝘀𝗵𝗯𝗼𝗮𝗿𝗱 – Real-time job monitoring • 🛢️ 𝗦𝘁𝗼𝗿𝗮𝗴𝗲 – SQL Server, Redis, PostgreSQL • 🔁 𝗥𝗲𝘁𝗿𝗶𝗲𝘀 – Built-in error handling • ⚙️ 𝗙𝗶𝗹𝘁𝗲𝗿𝘀 – Custom job behaviors • 📡 𝗦𝗰𝗮𝗹𝗮𝗯𝗶𝗹𝗶𝘁𝘆 – Works across multiple servers 📌 𝗪𝗵𝗲𝗻 𝘁𝗼 𝗨𝘀𝗲 𝗛𝗮𝗻𝗴𝗳𝗶𝗿𝗲? Use it when you need: • A full-featured 🖥️ monitoring dashboard • 💾 Persistence across app restarts • 🕒 Recurring jobs (CRON-style) • 🔁 Automatic retries + error logs • 🔗 Chained or dependent jobs • 🚀 Production-ready background workers ⚖️ 𝗔𝗹𝘁𝗲𝗿𝗻𝗮𝘁𝗶𝘃𝗲𝘀 𝘁𝗼 𝗛𝗮𝗻𝗴𝗳𝗶𝗿𝗲: 🔸 𝗤𝘂𝗮𝗿𝘁𝘇.𝗡𝗘𝗧 – Powerful scheduler, CRON-friendly 🔸 𝗖𝗔𝗣 – Event-based background processing 🔸 𝗠𝗮𝘀𝘀𝗧𝗿𝗮𝗻𝘀𝗶𝘁 + 𝗥𝗮𝗯𝗯𝗶𝘁𝗠𝗤 – Distributed message queues 🔸 𝗔𝘇𝘂𝗿𝗲 𝗙𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝘀 – Serverless background jobs 🔸 𝗪𝗼𝗿𝗸𝗲𝗿 𝗦𝗲𝗿𝘃𝗶𝗰𝗲 – Lightweight OS-level background tasks 📖 𝗥𝗲𝗮𝗱 𝘁𝗵𝗲 𝗮𝗿𝘁𝗶𝗰𝗹𝗲 👉 https://lnkd.in/dwb_vSb4 💻 𝗦𝗼𝘂𝗿𝗰𝗲 𝗖𝗼𝗱𝗲 👉 https://lnkd.in/dRnWurjt 💬 𝗪𝗵𝗮𝘁’𝘀 𝘆𝗼𝘂𝗿 𝗳𝗮𝘃𝗼𝗿𝗶𝘁𝗲 𝗯𝗮𝗰𝗸𝗴𝗿𝗼𝘂𝗻𝗱 𝗷𝗼𝗯 𝗳𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸 𝗶𝗻 .𝗡𝗘𝗧? 𝗟𝗲𝘁’𝘀 𝗱𝗶𝘀𝗰𝘂𝘀𝘀 👇 👉 Follow me (Kanaiya Katarmal) and hit the 🔔 on my profile so you don’t miss upcoming .NET tips and deep dives. 𝗧𝗵𝗮𝗻𝗸𝘀 𝗳𝗼𝗿 𝗿𝗲𝗮𝗱𝗶𝗻𝗴 𝗹𝗲𝘁’𝘀 𝗰𝗼𝗻𝘁𝗶𝗻𝘂𝗲 𝗴𝗿𝗼𝘄𝗶𝗻𝗴 𝗮𝗻𝗱 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴 .𝗡𝗘𝗧 𝘁𝗼𝗴𝗲𝘁𝗵𝗲𝗿! 👉 𝗦𝘂𝗯𝘀𝗰𝗿𝗶𝗯𝗲 𝘁𝗼 𝗺𝘆 𝗻𝗲𝘄𝘀𝗹𝗲𝘁𝘁𝗲𝗿: https://lnkd.in/dp7tz_3V #𝗱𝗼𝘁𝗻𝗲𝘁 #𝗰𝘀𝗵𝗮𝗿𝗽 #𝗮𝘀𝗽𝗻𝗲𝘁𝗰𝗼𝗿𝗲 #𝗵𝗮𝗻𝗴𝗳𝗶𝗿𝗲 #𝗯𝗮𝗰𝗸𝗴𝗿𝗼𝘂𝗻𝗱𝗷𝗼𝗯𝘀 #𝗴𝗶𝘁𝗵𝘂𝗯 #𝗺𝗶𝗰𝗿𝗼𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀 #𝗾𝘂𝗮𝗿𝘁𝘇𝗻𝗲𝘁 #𝗰𝗮𝗽 #𝗺𝗮𝘀𝘀𝘁𝗿𝗮𝗻𝘀𝗶𝘁

318

55 Comments

My history with the Aggregate Root pattern (Part 1) Today, I'd like to share my journey with one of DDD's core concepts, the Aggregate Root. Let's rewind the clock 23 years and take a trip down memory lane... My first professional experience, as an intern, dates back to the year 2000-2001. I've been taught modeling techniques such as Entity Relationship Diagrams and the Unified Modeling Language, which are used by companies all across the industry to represent their Canonical Data Model. One model to rule them all! Turns out there were always 2 versions of that model though, one in a relational database and an object-oriented one in code. With an Object Relational Mapper (or ORM) in between to deal with the Object–relational impedance mismatch between them. If you're still working in this age, please join me to 2007: the year I discovered Domain Driven Design. At the time I worked at Fluxys, a Belgian based Gas Infrastructure Group, on a system called BoSS (Booking of Services System). Over my years at Fluxys, I read the book 3 times, and started applying its concepts to slowly reduce the pain we were suffering from their canonical model. Initially Aggregates were used mainly to control the Unit Of Work of our ORM, and stored procedures, to map sections of the canonical database model to that of the code. Groups of entities and value objects were loaded and persisted as a single unit. In 2008, after taking on a gas storage related project within the organization, we also started to apply the concept of an Aggregate Root, in order to simplify the relationships between the aggregates. One of the entities inside of the aggregate was appointed as aggregate root, and only relationships towards that root were allowed from that point on. Other entities and value objects within the aggregate were considered private from that point on. I spent a total of 5 years in this organization, long enough to start understanding the business domains themselves. The strategic section of the DDD book urged me to learn more about it! Systems in the organization had code names, BoSS, Nomad, Alladin, ... and I started to notice that their section of the canonical model had entities called resp. Booking, Nomination, Allocation, ... These entities were clearly more important than the others, as the systems were named after them. These were business capabilities! (I just did not realize it yet, at the time) Activities, or processes if you will, that were guided by these systems. These entities represented the current state of those processes. Around 2009, all my aggregates gradually started to represent business processes, and they communicated to each other through messages, instead of through a shared database. Given LinkedIn doesn't allow me tell the full story in one go, the second part is scheduled for tomorrow, stay tuned...

69

4 Comments

💡 .𝗡𝗘𝗧 𝗧𝗶𝗽 - 𝗖# 𝘄𝗶𝘁𝗵𝗼𝘂𝘁 𝗮 𝗽𝗿𝗼𝗷𝗲𝗰𝘁? 𝗬𝗘𝗦, 𝗶𝘁’𝘀 𝗽𝗼𝘀𝘀𝗶𝗯𝗹𝗲 𝗻𝗼𝘄! With .NET 10, you can simply run a .cs file directly using 𝙙𝙤𝙩𝙣𝙚𝙩 𝙧𝙪𝙣 𝙖𝙥𝙥.𝙘𝙨, — no project files, no boilerplate setup. Why does this matter? ✅ Perfect for quick experiments ✅ Great for learning and teaching ✅ Makes scripting in C# easier than ever ✅ Feels like Python or JavaScript dev experience In this article, I break down how this new feature works, including: ✅ File-level directives like #:𝙥𝙖𝙘𝙠𝙖𝙜𝙚 and #:𝙨𝙙𝙠 ✅ Referencing NuGet packages ✅ Adding build properties directly Whether you're testing APIs or building simple tools, this change makes working with C# more lightweight and fun. 👉 Read the full article here: https://lnkd.in/gDRSjXSy 💬 Have you tried this new approach yet? Would love to hear your thoughts. 🧠 Let me know what you think — and don’t forget to subscribe to my newsletter .𝙉𝙀𝙏 𝙒𝙚𝙚𝙠𝙡𝙮 𝙏𝙞𝙥𝙨 𝙗𝙮 𝙋𝙤𝙤𝙧𝙣𝙖 to get more content like this delivered to your inbox! ♻️ If you found this helpful, consider reposting to help others in the community. 👉 Follow me, Poorna Soysa, and hit the 🔔 on my profile so you don’t miss upcoming .NET tips and deep dives. Thanks for reading — let’s keep learning .NET together.

185

31 Comments

Kubernetes: 50M+ concurrent users. Yes, this architecture supports it. 50 million. But to build something like this, you must first ask right questions. Questions like: Where are my network bottlenecks? ✅ How to handle sudden spikes with millions of concurrent users? ✅ What compute resources are required to handle high concurrency? ✅ How much network bandwidth and throughput will these services need at a scale of 50+ million concurrent users? ✅ But why are these questions important? Because they help you gather right data. And only right data can help you scale things efficiently 💯 Proof? JioHotstar handled over 61 million concurrent users with this architecture. More about it in the comments. Hope this is useful. Thank you for reading.

610

33 Comments

Learning Kubernetes can be 100% free and 100% projects based. My 4+2 blogs on Medium will teach you more about Kubernetes than any tutorials ever will. 1. Stop Over-Complicating Kubernetes: This is How You Should Actually Learn It. https://lnkd.in/g_qM4hFK 2. Building Your First Real Kubernetes Application. https://lnkd.in/gXn8C74h 3. Deploying a production-ready 3-tier (React frontend+Flask backend + Postgres)application on AWS EKS with real-world setup (EKS, RDS, ALB, Route53, OIDC, IAM, EC2). https://lnkd.in/g6A8RKFx 4. A step-by-step guide to adding free, self-managed SSL certificates to your Kubernetes application Running On EKS. https://lnkd.in/g-mwaePg 👉You cannot learn Kubernetes until you learn Docker, and these two blogs will teach you everything. 5. Everything You Need To Know About Docker https://lnkd.in/gC6DfRrJ 6. Run Multi-Container Applications With Docker Compose https://lnkd.in/gwFwTMeS 🔁Consider a repost to help reach more people.

173

2 Comments

🚀 .NET Developers in 2025 – Expectations vs. Reality I’m speaking with both companies and developers daily, and one theme keeps coming up: 👉 The “ideal” .NET candidate profile many companies are aiming for doesn’t always match what’s available in today’s market. That gap is natural, but being aware of it helps both sides make better decisions. #dotnet #hiring #developers #softwaredevelopment #backend #fullstack #cloud #azure #careers #talentacquisition

73

4 Comments