Want a clear path to get started?
Grab my Free .NET Backend Developer Roadmap 👇
juliocasal.com/roadmap

𝗥𝗲𝗮𝗰𝘁
The leading frontend framework; full-stack .NET developers who use React are in demand.

𝗔𝗻𝗴𝘂𝗹𝗮𝗿
Common in enterprise; adaptability across frameworks shows seniority.

𝗝𝗮𝘃𝗮𝗦𝗰𝗿𝗶𝗽𝘁
The foundation of the web; strong fundamentals prove you can work beyond frameworks.

𝗠𝗶𝗰𝗿𝗼𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀
Among the top requested skills; services that scale independently are essential.

𝗘𝘃𝗲𝗻𝘁 𝗗𝗿𝗶𝘃𝗲𝗻
Modern systems rely on events; resilient, eventually consistent designs matter.

𝗞𝗮𝗳𝗸𝗮
Event streaming is mainstream; designing and consuming pipelines shows readiness.

𝗥𝗮𝗯𝗯𝗶𝘁𝗠𝗤
Common in .NET stacks; exchanges, routing, and retries highlight reliability.

𝗦𝗲𝗿𝘃𝗶𝗰𝗲 𝗕𝘂𝘀
Core in Azure; decoupling services with queues and topics builds resilience.

𝗪𝗧
Token-based auth is everywhere; APIs must implement JWT correctly.

𝗢𝗔𝘂𝘁𝗵 𝟮.𝟬
The standard for delegated access; integrating identity providers is critical.

𝗧𝗟𝗦
Encryption is non-negotiable; enforcing protocols and certificate renewal is required.

𝗗𝗼𝗰𝗸𝗲𝗿
Baseline for backend devs; containerized apps ensure consistent deployments.

𝗞𝘂𝗯𝗲𝗿𝗻𝗲𝘁𝗲𝘀
The orchestration standard; deployments and rollbacks show maturity.

𝗛𝗲𝗹𝗺
Default for Kubernetes apps; managing deployments with charts is common.

𝗔𝘇𝘂𝗿𝗲 𝗗𝗲𝘃𝗢𝗽𝘀
Central in enterprise; pipelines, repos, and releases are core.

𝗚𝗶𝘁𝗛𝘂𝗯 𝗔𝗰𝘁𝗶𝗼𝗻𝘀
Rapid adoption in modern teams; CI/CD automation experience is valued.

𝗧𝗲𝗿𝗿𝗮𝗳𝗼𝗿𝗺
Infrastructure as Code is table stakes; reproducible infra is expected.

𝗚𝗿𝗮𝗳𝗮𝗻𝗮
Dashboards must be actionable; metrics tied to outcomes matter most.

𝗢𝗽𝗲𝗻𝗧𝗲𝗹𝗲𝗺𝗲𝘁𝗿𝘆
Now the tracing standard; consistent instrumentation across services is expected.

𝗔𝗽𝗽 𝗜𝗻𝘀𝗶𝗴𝗵𝘁𝘀
Native Azure monitoring; instrumentation and analysis skills are critical.

𝗣𝗼𝘀𝘁𝗴𝗿𝗲𝗦𝗤𝗟
Popular for new projects; SQL fluency, indexing, and tuning skills are needed.

𝗦𝗤𝗟 𝗦𝗲𝗿𝘃𝗲𝗿
Entrenched in enterprise; stored procedures and optimization remain essential.

𝗖𝗼𝘀𝗺𝗼𝘀 𝗗𝗕
Central to Azure apps; modeling and querying NoSQL data is common.

𝗔𝘇𝘂𝗿𝗲
The top cloud for .NET; deployment, monitoring, and scaling apps are in demand.

𝗔𝗪𝗦
Hybrid setups are common; knowledge of core services shows flexibility.

𝗖#
The core of .NET roles; fluency in modern features and writing clean, efficient code is baseline.

𝗥𝗘𝗦𝗧 𝗔𝗣𝗜𝘀
The main integration style; secure, scalable endpoints with clear documentation matter.

𝗚𝗿𝗮𝗽𝗵𝗤𝗟
Adoption keeps growing; well-designed schemas and resolvers improve efficiency.

What if you are using GUIDs for your IDs? Then use UUID Version 7, which is designed to be globally unique and sortable.

--
Get my Free .NET Backend Blueprint 👇
juliocasal.com/blueprint

But with Keyset pagination, you don’t need to skip any rows. You just remember the last key you fetched and use it to fetch the next rows.

As long as your ID column is indexed, queries that use Keyset pagination will be very efficient, even for large datasets.

It's called 𝗞𝗲𝘆𝘀𝗲𝘁 𝗽𝗮𝗴𝗶𝗻𝗮𝘁𝗶𝗼𝗻 or 𝘀𝗲𝗲𝗸-𝗯𝗮𝘀𝗲𝗱 𝗽𝗮𝗴𝗶𝗻𝗮𝘁𝗶𝗼𝗻 and is a much more efficient way to paginate through a large dataset.

The problem with Offset pagination (skip and take) is that the DB must still process the skipped entries, even if they aren’t used.