Urgent.News

What's breaking now, across thousands of outlets.

Tech

FastIngest: Zero-Allocation Bulk Ingestion Pipeline for .NET

Every time I built data-intensive systems in .NET, handling bulk data ingestion always felt fragmented. Different databases required completely different boilerplate, performance quirks, and error-handling strategies. So I spent the week solving it cleanly from first principles. I’m excited to introduce FastIngest: a modular, high-throughput bulk ingestion framework for .NET. Published completely…

FastIngest introduces a new bulk ingestion pipeline for .NET, addressing the challenges of fragmented data handling in data-intensive systems. The open-source framework, released under the MIT license, provides a unified, optimized API for heavy write loads and streaming pipelines. It eliminates the need for provider-specific bulk copy hacks, available since its release on NuGet (v0.3.2).

The core components of FastIngest include the FastIngest.Core pipeline engine and modular providers for relational databases such as SQL Server, PostgreSQL, MySQL, and SQLite. It also supports document and cloud stores like Azure Cosmos DB, MongoDB, and Elasticsearch, along with search and indexing capabilities for Elasticsearch.

Within the first 48 hours of its release, the suite garnered over 1,600 downloads across nine packages, demonstrating its immediate popularity. FastIngest is free for commercial and non-commercial use, with comprehensive documentation and GitHub sources available under the MIT License.

Developers working on data migration tools, event processors, or high-throughput write services in .NET are encouraged to test and provide feedback for FastIngest. Contributions in the form of issues, pull requests, and additional extensions are welcomed by the project's team.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

64-Day Certificates Are Coming: Two Small Tweaks to Your Renewal Logic

Let's Encrypt is dropping certificate validity from 90 days to 64 days starting February 2027. If you're like me, your first thought was probably "64 days is still 64 days, what's the big deal?" The…

  • Let's Encrypt reducing certificate validity to 64 days from February 2027.
  • Renewal scripts may fail with hardcoded 30-day check before expiry.
  • Adjust renewal threshold to 70% of certificate lifetime or monitor at 15 days.

I Used to Think Software Testing Was Unnecessary. Then I Started Building My Own Project.

I used to think writing unit tests, E2E tests, and maintaining a proper testing suite was unnecessary for most projects. If developers write the code, can't they just test it themselves?

  • Started building open-source platform The Last Deploy in late June
  • Real users caused issues with manual testing approach
  • Learned importance of unit, integration, end-to-end, and regression tests

More from Thursday 15 October →