🧑‍💻 After building the practice project EventSphere, I learned a lot about using clean software architecture and how to utilize .NET more efficiently for backend development. I then wanted to create another practice project to explore and learn Azure-provided services like Azure Functions, Cosmos DB, etc. After spending some time reading the docs, I moved on to build an expense tracker project, TrackItAll.

In this project, I used several Azure services:
1. Azure AD B2C: For seamless user sign-up and sign-in, as well as role-based authorization in the ASP.NET Web API.
2. Azure Functions: To delegate the email sending process for sign-ups and report-sending tasks.
3. Azure Cosmos DB: Used as a NoSQL database to store user expense data.
4. Azure Queue Storage: Coordinated with Azure Functions to queue sign-up emails and report data, allowing Azure Functions to process the messages from the queue.
5. Azure Blob Storage: For storing receipt file data related to expenses.
6. Azure Table Storage: Used as a configuration store where I kept the category types for expenses.

🏖 It was a great learning experience building this project, as it exposed me to many Azure services. While it’s not fully finished, I believe there’s always room for improvement. Any feedback or advice on how to improve would be greatly appreciated. Thank you!

#azure #backend #dotnet #project

3Blue1Brown's animation code is now public 🔥

https://github.com/3b1b/videos

This github realtime data stream is very cool 🔥

Efficient Load Testing with C#: Nginx, Go APIs & Redis Performance Demo


👍 LIKE

💬 Comment on YT

Thanks !

And another thing I discovered is that, when you login, it just creates a dummy session id key in the cookies just to keep track of the fact that you are logged in. No usage of the username and password for basic authentication.. No usage of tokens 😳

A ridiculous router 😂

always learning something new & interesting from Milan's posts 💎

this should be one the perks of being a senior dev 😁

I always hated auto mapper libraries in C# as they are mostly reflection-based. They do runtime reflections to handle mapping, which have a significant performance overhead and potential runtime errors. I always try to avoid anything that involves reflection at all cost, even in a mapping case, I always preferred to write my own mappers.

However, today, I discovered a library called Mapperly 💎

Mapperly is a source generator based library for generating object mappings. A source generator in C# is a powerful compile-time code generation feature introduced in .NET 5 that allows you to generate additional source code during compilation. This means it generates type-safe and highly efficient mapping code at compile time. Since it avoids using reflection, there are no runtime complications.

I can't wait till I use it 🔥

Github Repo: https://github.com/riok/mapperly
Docs: https://mapperly.riok.app/docs/intro/

#csharp #tip #automapping #resource

👉 Read More

#csharp #tip #dotnet