Stefan Sheva Popovski

Core Member @code_chem | Software Engineer | Tech Lover | Traveller | Snowboarder | @ManUtd Fan

[Dave Callan | dotnet @Dave_DotNet]

.NET 10 reduces IEnumerable 'penalty' from 83% to 10%

I posted recently how the compiler team are looking to reduce what's known as the abstraction penalty in #dotnet 10.

It looks like things are progressing well so far. I ran the below benchmark (code snippet in 2nd tweet) off main yesterday.

In .NET 9 the cost of looping through an array via IEnumerable was 83% over directly iterating the array, whereas in .NET 10 the cost was only 10% 👏🏻

[Milan Jovanović @mjovanovictech]

Don't start with microservices. ❌

Even if you think your application will be big enough to justify it.

And here's why. Microservices come with a premium:

- Team coordination
- Dealing with failure
- Eventual consistency
- Automating deployments
- Managing multiple services
- Provisioning additional infrastructure

You don't need this complexity at the start of a new project.

Does this bring value to your users? Most likely, no.

If you can't manage a large monolith system, you won't do better with microservices.

Your team's experience plays a significant role in building successful microservices.

Here's a less risky strategy:

- Start with a Monolith
- Discover the service boundaries (bounded contexts)
- Then decide if you need to break them into microservices

Many other factors also play a role. I can't fit them all into one post.

But I hope I've given you some food for thought.

If you want to learn more about (Modular) monoliths, go here: https://t.co/YqrESYsjbS

Here's a contrarian take if you're up for a good discussion.

Would you start a greenfield project with Microservices, and why?

[Stefan Đokić | .NET @TheCodeMan__]

Don't make this mistake. ❌

Don't use .ToLower() for string comparison. Why?

The .𝗧𝗼𝗟𝗼𝘄𝗲𝗿() method creates a new string memory allocation for each comparison, leading to unnecessary allocations.

Consider a method with frequent requests that can degrade the application performance.

Also, the .ToLower() method is culture-sensitive, which means it might produce different results depending on the current culture set in the executing thread.

What to do instead?

.NET provides a powerful enumeration => 𝗦𝘁𝗿𝗶𝗻����𝗖𝗼𝗺𝗽𝗮𝗿𝗶𝘀𝗼𝗻. ✅

Possible StringComparison Options

• 𝗢𝗿𝗱𝗶𝗻𝗮𝗹: Opt for this in most general-purpose comparisons where cultural rules are irrelevant. It is the fastest option.

• 𝗢𝗿𝗱𝗶𝗻𝗮𝗹𝗜𝗴𝗻𝗼𝗿𝗲𝗖𝗮𝘀𝗲: Best for case-insensitive comparisons where cultural rules do not matter.

• 𝗖𝘂𝗿𝗿𝗲𝗻𝘁𝗖𝘂𝗹𝘁𝘂𝗿𝗲 and 𝗖𝘂𝗿𝗿𝗲𝗻𝘁𝗖𝘂𝗹𝘁𝘂𝗿𝗲𝗜𝗴𝗻𝗼𝗿𝗲𝗖𝗮𝘀𝗲: Use these when comparing strings that are displayed to the user, as they follow cultural rules.

• 𝗜𝗻𝘃𝗮𝗿𝗶𝗮𝗻𝘁𝗖𝘂𝗹𝘁𝘂𝗿𝗲 and 𝗜𝗻𝘃𝗮𝗿𝗶𝗮𝗻𝘁𝗖𝘂𝗹𝘁𝘂𝗿𝗲𝗜𝗴𝗻𝗼𝗿𝗲𝗖𝗮𝘀𝗲: Ideal for scenarios needing consistency across different cultures, such as when storing and retrieving data.

Note: EF Core throws an exception if you use a method such as String.Equals(String, StringComparison) that takes a StringComparison argument, as it won't translate such queries to SQL.

Join https://t.co/65gw5pGHO0 to Master .NET Technologies for free, along with 13k+ engineers.
__

Unlock the power of AI in API development with Postman Flows! Register now for their next session to simplify workflows, visualize data, and boost productivity with AI-driven recommendations here: https://t.co/zKxZP3uv2j

#dotnet

[Dave Callan | dotnet @Dave_DotNet]

.NET 9 LINQ Mind Map 🔥

Includes the three new LINQ methods coming in .NET 9:
"Index," "CountBy," and "AggregateBy".

Thanks to Steven Giesel on LinkedIn for the image ->
https://t.co/PuytOEhfDX

#dotnet

[Milan Jovanović @mjovanovictech]

Modular Monolith Architecture – Explained

A modular monolith is an architectural pattern that structures the application into independent modules or components with well-defined boundaries.

The modules are split based on logical boundaries, grouping together related functionalities. This approach significantly improves the cohesion of the system.

Modular monoliths blend the simplicity and robustness of traditional monolithic applications with the flexibility and scalability of microservices. I'm tempted to say they bring together the best of both worlds.

The modular monolith architecture allows you to work in a unified codebase with clearly defined boundaries and independent modules. This allows you to have a high development velocity without the complexity of distributed systems.

Modular monoliths have many benefits:

- Simplified deployment
- Improved performance
- Enhanced development velocity
- Easier transaction management
- Lower operational complexity
- Easier transition to microservices

How does it compare to microservices?

The biggest difference between modular monoliths and microservices is how they're deployed. Microservices elevate the logical boundaries inside a modular monolith into physical boundaries.

Microservices give you a clear strategy for modularity and decomposing the bounded contexts. But, you can also achieve this without building a distributed system. The problem is people end up using microservices to enforce code boundaries.

Instead, you can build a modular monolith to get most of the same benefits. Modular monoliths give you high cohesion, low coupling, data encapsulation, focus on business functionalities, and more.

Microservices give you all that, plus independent deployments, independent scalability, and the ability to use different technology stacks per service.

What do you think about modular monolith architecture?

---
Subscribe to my weekly newsletter to accelerate your .NET skills: https://t.co/fy9o73DUZh

[Karen Payne MVP @KarenPayneMVP]

EF Core 8: TimeOnly.IsBetween

Code sample
https://t.co/h0hNbixjrJ

[42.mk @42dotmk]

😍 PyData Skopje - November 2023 Meetup
✔ We have excellent news for you! We are excited to announce that the next PyData event is next week.
✔ https://t.co/MPOeYLDnJt

[Stefan Sheva Popovski @ShevaStefan]

- Enhancements of JSON Column mapping
- Complex Types❤️

This gonna save a lot of headaches. #dotnetconf

[Milan Jovanović @mjovanovictech]

Do you want to learn Clean Architecture and DDD?

I have prepared 45 lessons for you 🔥

𝗖𝗹𝗲𝗮𝗻 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 𝗙𝘂𝗻𝗱𝗮𝗺𝗲𝗻𝘁𝗮𝗹𝘀

- Project setup - https://t.co/U0XhBAzpuZ
- Minimal APIs - https://t.co/lBFE7uERr4
- Dependency injection - https://t.co/WMN3XMIIFV
- CA + Document database - https://t.co/G8yfS6saJi
- Project setup from scratch - https://t.co/RSiKbtN0Ix
- 4 Best practices for new project - https://t.co/zsNa58PuwP
- Structured logging - https://t.co/FGqPIcULPc
- Message queues - https://t.co/SeMxe8ab5w

𝗗𝗼𝗺𝗮𝗶𝗻-𝗗𝗿𝗶𝘃𝗲𝗻 𝗗𝗲𝘀𝗶𝗴𝗻 𝗜𝗻𝘁𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻

- Rich Domain model - https://t.co/JLaJtPJSUU
- Entities - https://t.co/xji6B6oJ0K
- Value objects - https://t.co/RSls66545L
- Aggregate root - https://t.co/jJtocCXdHl
- Domain validation - https://t.co/VQISKMj5dn
- Domain model tradeoffs - https://t.co/RTlM5jDgkD
- Repository pattern - https://t.co/K6H8hriLr0
- Specification pattern - https://t.co/HSEdHjpamR
- Unit of work - https://t.co/vHTqb7QwwK
- Smart Enums - https://t.co/paBmAXbiYF
- Snapshot pattern - https://t.co/Cu73dbvQOA
- Strongly typed IDs - https://t.co/TnOtTH8Q7E
- Anemic Domain model - https://t.co/kVLOjc71ab
- DDD modeling - https://t.co/zHeSjkjx2B
- DDD + EF mapping - https://t.co/st0lgt3gdT
- Incomplete aggregates - https://t.co/DLMo62GimV
- Double dispatch - https://t.co/Zz57SFAqaa

𝗖𝗤𝗥��

- CQRS Fundamentals - https://t.co/EzEJRtkZiY
- Validation /w Result - https://t.co/xtSZ0NBrY7
- Validation /w Exception - https://t.co/ZvBFM0fHYr
- Read models - https://t.co/IT8gDZM6ar
- UoW pipeline - https://t.co/5JrJeBkQXe
- The "Truth" on CQRS - https://t.co/cVM86S4BDE
- CQRS Query side - https://t.co/5ejbLchujj
- Materialized views - https://t.co/npfbH1iPOH

𝗧𝗲𝘀𝘁𝗶𝗻𝗴

- Parameterized tests - https://t.co/XqqryJx2HA
- Unit testing - https://t.co/lEQGukvsHc
- Integration testing /w Docker - https://t.co/wkAROO90Vl
- Architecture tests - https://t.co/gSfqV5nJnq

𝗗𝗲𝘀𝗶𝗴𝗻 𝗣𝗮𝘁𝘁𝗲𝗿𝗻𝘀

- Idempotent consumer - https://t.co/bsUSRpc64h
- Saga pattern - https://t.co/xJfS0unZFO
- Compensating transaction (Saga) - https://t.co/pNNIF0Yu3B
- Domain events - https://t.co/VbZJ5x1otQ
- Domain vs. Integration event - https://t.co/v5eDGhloyU
- Options pattern - https://t.co/dLveVow3Bn
- Options pattern validation - https://t.co/08UjBIhvyw
- Decorator pattern - https://t.co/LPTaphKGHk

Hope these are helpful.

If you liked this, consider joining The .NET Weekly - my newsletter with 31,000+ engineers.

Join us here → https://t.co/dCEi48iXpl

Have an awesome day!

[Milan Jovanović @mjovanovictech]

You should never return null collections in C#.

There are better solutions.

What problem do null collections cause?

You will typically iterate over a collection in a loop.

But if your method returns null collections, this can lead to potential errors.

Your code must handle the null case and check for null before accessing any collection elements.

Adding a null check every time can make the code harder to read.

It's even worse if the calling code doesn't handle the null case.

Things will blow up at runtime, which isn't easy to diagnose.

You could argue that a null value expresses some intent.

But I still prefer avoiding null in my code as much as possible.

I think it's a best practice to return:

- a new List()
- Enumerable.Empty
- Array.Empty

This way, your code can safely iterate over the collection without worrying about null checks.

📌 P.S. If you liked this, consider joining The .NET Weekly - my newsletter with 29,000+ engineers that teaches you how to improve at .NET and software architecture.

Subscribe here → https://t.co/xip45XpWuB

What's your approach to working with null collections?

[Dave Callan | dotnet @Dave_DotNet]

#dotnet Performance Improvements 🚀

.NET 8
https://t.co/aYltk7Gdl6

.NET 7
https://t.co/RKl5bB5XwZ

.NET 6
https://t.co/tLAHAm7lE3

.NET 5
https://t.co/5NZONp6VpZ

.NET 3.0
https://t.co/LW33NSRC48

.NET 2.1
https://t.co/r57tQPIVdq

.NET 2.0
https://t.co/MsCPhLbWGs

Bookmark it!

[Swapna Kumar Panda @swapnakpanda]

75 YouTube channels you will never regret subscribing to:

❯ C ➟ Jacob Sorber
❯ C++ ➟ TheCherno
❯ Java ➟ amigoscode
❯ C# ➟ kudvenkat
❯ Python ➟ Corey Schafer
❯ JavaScript ➟ developedbyed
❯ Golang ➟ Jon Calhoun
❯ Swift ➟ CodeWithChris
❯ Kotlin ➟ PhilippLackner
❯ PHP ➟ ProgramWithGio
❯ Ruby ➟ DriftingRuby
❯ Rust ➟ NoBoilerplate
❯ Lua ➟ Steve's teacher
❯ R ➟ marinstatlectures
❯ SQL ➟ Joey Blue

❯ JavaScript ➟ Akshay Saini
❯ TypeScript ➟ basarat
❯ TypeScript ➟ TypeScriptTV
❯ C# ➟ Microsoft Developer [Bob Tabor]
❯ C# ➟ dotnet [Scott/Kendra]
❯ Node.js ➟ Traversy Media
❯ React ➟ Dave Gray
❯ Vue ➟ Vue Mastery
❯ Django ➟ CodingEntrepreneurs
❯ Laravel ➟ LaravelDaily
❯ Blazor ➟ James Montemagno
❯ Spring ➟ SpringSourceDev
❯ SpringBoot ➟ amigoscode
❯ Ruby on Rails ➟ GorailsTV
❯ HTML/CSS ➟ Kevin Powell

-- DSA --

❯ mycodeschool
❯ Abdul Bari
❯ Kunal Kushwaha
❯ Jenny's Lectures CS IT
❯ CodeWithHarry

-- Full Stack --

❯ Traversy Media
❯ NetNinja
❯ Dave Gray

❯ Projects ➟ WebDevSimplified
❯ UI Design
➟ developedbyed
➟ DesignCourse

-- DevOps --

❯ GIT ➟ The Modern Coder
❯ Linux ➟ Learn Linux TV
❯ DevOps ➟ DevOpsToolkit
❯ CI/CD ➟ TechWorld with Nana
❯ Docker ➟ Bret Fisher
❯ Kubernetes ➟ Kubesimplify
❯ Microservices ➟ freeCodeCamp
❯ Selenium ➟ edureka!
❯ Playwright ➟ Jaydeep Karale

-- Cloud Computing --

❯ AWS ➟ amazonwebservices
❯ Azure ➟ Adam Marczak
❯ GCP ➟ edureka!
❯ Serverless ➟ Serverless
❯ Jenkins ➟ DevOps Journey
❯ Puppet ➟ simplilearn
❯ Chef ➟ simplilearn
❯ Ansible ➟ Learn Linux TV

-- Data Science --

❯ Mathematics
➟ 3Blue1Brown
➟ ProfRobBob
➟ Ghrist Math

❯ Machine Learning
➟ sentdex
➟ DeepLearningAI
➟ StatQuest

❯ Excel ➟ ExcelIsFun
❯ Tableau ➟ Tableau Tim
❯ PowerBI ➟ Guy in a Cube

-- Free Education --

➟ freecodecamp
➟ Simplilearn
➟ edureka!

-- Most Valuable --

➟ TechWithTim
➟ programmingwithmosh
➟ Traversy Media
➟ BroCodez
➟ thenewboston
➟ Telusko
➟ Derek Banas
➟ CodeWithHarry
➟ MySirG .com
➟ Leila Gharani
➟ Kunal Kushwaha
➟ TechWorld with Nana
➟ KodeKloud

[Stefan Sheva Popovski @ShevaStefan]

What Design Pattern you prefer when building .NET Core WebAPI? #dotnet #csharp #dotnetcore #webapi

[Dave Callan | dotnet @Dave_DotNet]

4 Use Cases of LINQ in .NET ⬇

Thanks to Keivan Damirchi on LinkedIn for the original image -> https://t.co/In2CvxhXaX

#dotnet #csharp

[Stefan Sheva Popovski @ShevaStefan]

Thoughts: What Project/Folder structure do you prefer for your .NET Web Api? #csharp #dotnet #dotnetcore

[Muhammad Waseem @mwaseemzakir]

Feel like you're falling behind on .NET?

Get ahead by delving into 35 topics I've decoded.

𝗦𝗢𝗟𝗜𝗗 (𝟱)
- S: https://t.co/MfJZyhov8I
- O: https://t.co/nMF8XnIVmQ
- L: https://t.co/Nvf7yAuRbk
- I: https://t.co/Txazh8CduS
- D: https://t.co/HWBJKMgIwT

𝗗𝗲𝘀𝗶𝗴𝗻 𝗣𝗿𝗶𝗻𝗰𝗶𝗽𝗹𝗲𝘀 (𝟯)
- DRY: https://t.co/tWpn3YoHYd
- KISS: https://t.co/j8yvXPiAkb
- YAGNI : https://t.co/se9c0bWdDx

𝗣𝗮𝗰𝗸𝗮𝗴𝗲𝘀 (𝟳)
- Hangfire: https://t.co/V8Af5seROi
- Mapster : https://t.co/s7RURj4eon
- JSON .NET: https://t.co/ZUEhIQLVZ5
- NodaTime: https://t.co/tTJoWxHxZ2
- Automapper : https://t.co/0vc0cLaY15
- Bogus: https://t.co/arwtyU0Off
- Autofac : https://t.co/2qZsAPfA24

𝗠𝗶𝗱𝗱𝗹𝗲𝘄𝗮𝗿𝗲 (𝟲)
- Intro: https://t.co/yQMeKvydui
- CORS : https://t.co/p3Qp1jflLN
- Rate Limiting: https://t.co/cRgP7s3yD7
- Response Caching: https://t.co/sb826JwDdM
- Global Error Handling: https://t.co/Td4HsJ5jFP
- Response Compression: https://t.co/XPd5eZpASt

𝗙𝗶𝗹𝘁𝗲𝗿𝘀 (𝟮)
- Action Filters: https://t.co/jHNzOpewda
- Exception Filters: https://t.co/u9KUXsfXEs

𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 (𝟱)
- Cancellation Token: https://t.co/8NSOVVBs2A
- Tracking vs NoTracking: https://t.co/lUHCHlFsvI
- Compare strings: https://t.co/OoGbBzoASw
- Write better LINQ: https://t.co/wEEYEAWPLU
- Clean Code Tips: https://t.co/6cqv1EnUxW

𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 (𝟭)
- JWT in .NET Core: https://t.co/E5Sk5MkgLG

𝗟𝗼𝗴𝗴𝗶𝗻𝗴 (𝟭)
- NLog: https://t.co/i2rDIgm0yA

𝟭𝟬𝟬𝗞 𝗜𝗺𝗽𝗿𝗲𝘀𝘀𝗶𝗼𝗻𝘀 (𝟱)
- Null Operators Guide: https://t.co/VF0KQCy3nU
- IEnumerable vs List: https://t.co/ONPX1sZafT
- 15 Nuget Packages: https://t.co/bsnvl6RFjC
- Resources to learn .NET: https://t.co/i3PY68QIff
- Dependency Injection: https://t.co/LTWRUC0Xfz

📌𝗣.𝗦:- If you don't want to miss the next updates join my weekly Newsletter with 4500+ engineers here: https://t.co/TDNkmIWiPq

🔄 If you found this post helpful then do repost to help me in reaching more people.

#dotnet

[Dave Callan | dotnet @Dave_DotNet]

New Shuffle method coming in .NET 8 ⬇ ...

Two overloads ->
public void Shuffle<T> (Span<T> values);
public void Shuffle<T> (T[] values);

Available from #dotnet 8 Preview 1.

What do you think?
Have you got use cases for Shuffle?

#csharp

[Stefan Sheva Popovski @ShevaStefan]

You made a history and leave a legacy in @ManUtd

End of one wonderful story. True Red Devil and Legend ❤️

Thank you for everything @D_DeGea

[Stefan Sheva Popovski @ShevaStefan]

No matter what, if @ManUtd goes in Semifinal or not, after these two poor matches @HarryMaguire93 doesn’t go, I will apply for defender in United. I can assure that I’m better.

[Stefan Sheva Popovski @ShevaStefan]

Harry Maguire please GOOOOOO. You are fucking disaster @ManUtd @HarryMaguire93