Most developers analyze their system design by designing a system that keeps latency constant as throughput increases. Of course, this definition is correct, but the point is that in this regard, more attention is paid to the scaling category (focusing on horizontal scaling) and all the solutions offered are in line with this concern. And the point that always remains is the consistency and concurrency category. Many developers forget that for all software with a very serious and important problem that lurks like a hidden danger to seriously affect constancy and throughput. The name of the problem? concurrency

Now the point is that all the solutions proposed to solve this problem neutralize and make ineffective all or at least a large part of the measures taken to scale and increase throughput

But...

Wait

Is this really the case?

A bulk operation refers to the process of inserting, updating, or deleting a large number of records in a database in a single, optimized command or batch, rather than executing individual statements for each row.

This is critically important for performance in data-intensive applications(e.g. as ETL processes, migrations, or real-time analytics) because it reduces network latency, minimizes transaction log overhead, and can improve throughput by 10x to 100x compared to row-by-row operations.

So now that we understand the importance of the topic, let's take a look at ef's support for bulk operations and see if functions like AddRange() and RemoveRange() are considered bulk operations or not.

words developers often throw around casually, but that have specific meanings or connotations.

In developer culture, words like boilerplate, spaghetti code, yak shaving, bike-shedding, and technical debt are shortcuts — they carry a whole concept and mood in one phrase.

Here’s a curated list of common developer terms, metaphors, and slang (with plain explanations and tone).

Record type or record is a very interesting feature introduced in C# 9.0 , everything is considered immutable, and similarly, in C#, record types help us to work with immutable types.

In this article , we provide a practical, step-by-step guide to making software systems scalable , from a single-server setup to a fully distributed architecture.

It begins with the fundamentals of I/O performance, explaining how hardware limitations such as disk speed and network latency affect system throughput. Then it explores progressive scaling strategies, including vertical and horizontal scaling, caching, asynchronous processing, and load balancing.

Finally, it addresses the deeper challenges of distributed systems . data consistency, CAP theorem, replication, sharding, and event-driven communication .

offering clear, real-world approaches for designing resilient, high-performance application

EPPlus is a powerful and easy-to-use .NET library for reading, creating, and modifying Excel .xlsx files (Office Open XML format).
It provides an API similar to working with Excel itself — with support for formulas, charts, tables, styles, data validation, pivot tables, and more — all without needing Excel installed.

It’s ideal for:

• Generating Excel reports dynamically
• Importing or exporting data from databases
• Creating dashboards or analytics reports
• Building REST APIs that return Excel files

CAP is a .NET library that helps implement the Outbox Pattern and distributed event publishing reliably.

It supports multiple databases (SQL Server, MySQL, PostgreSQL, etc.) and message brokers (RabbitMQ, Kafka, Azure Service Bus).

It automatically stores events in an outbox table within your database transaction and publishes them asynchronously.

It handles retries, failure scenarios, and event deduplication.

CAP is a great fit if you want out-of-the-box support for transactional outbox + message broker integration.

It abstracts away a lot of complexity.

Widely used in .NET microservice and event-driven architectures.

• Transactional consistency: Your business data and events are saved atomically.
• Reliable event publishing: Events are published asynchronously with retries.
• Supports multiple brokers and databases.
• Minimal setup: Integrates easily with EF Core and other ORMs.
• Automatic cleanup and monitoring.
• Helps you avoid reinventing the wheel.

A Progressive Web App (PWA) is a web application that uses modern browser APIs to provide an experience similar to a native mobile app.

characteristics:

• Progressive – Works on any browser.
• Responsive – Fits desktop, mobile, or tablet.
• Offline-ready – Can work on low-quality networks or without connection.
• App-like – Feels like a native app (navigation, interactions).
• Fresh – Always up-to-date with service workers.
• Safe – Served via HTTPS.
• Installable – Users can add to their home screen.
• Discoverable – Search engines can find them (via manifest).
• Re-engageable – Can send push notifications.
• Linkable – Shared via simple URLs (no store required).

Looking for an open-source way to implement 𝗦𝗦𝗢 in ASP.NET Core? This guide shows how to build a central authentication system using 𝗢𝗽𝗲𝗻𝗜𝗱𝗱𝗶𝗰𝘁, a free alternative to Duende Identity.

It includes:
  • A working AuthServer and MVC client
  • Login and consent pages
  • Proper handling of first-time login flows

K6 is both an HTTP load and functional test tool, written in Go and using the goja embedded JavaScript interpreter for test scripting purposes

Ever wondered how your API performs under heavy load?
I just wrote a practical guide on API load testing with k6 – from setup to thresholds and real-world scenarios.