Introduction

REN.Kit’s DataKit module brings your data access to the next level by introducing a robust, extensible, and modern approach for all database operations. Out of the box, it supports the classic Repository and Unit of Work (UoW) design patterns—battle-tested, maintainable, and perfect for both simple CRUD APIs and complex enterprise scenarios.

Also, DataKit is built on top of Entity Framework Core, meaning it works effortlessly with any EF Core-supported database—including Microsoft SQL Server, PostgreSQL, MySQL, SQLite, Oracle, and more. No matter your underlying database technology, DataKit adapts, so you can focus on your business logic—not plumbing code.

Why use Repository and UoW?

  • Decoupling: Keeps your business logic and data access code cleanly separated.

  • Testability: Makes your code easy to mock and unit test.

  • Consistency: All database changes can be batched and committed together—no more partial saves or accidental data loss!

  • Reusability: Common data operations (query, insert, update, delete, bulk, etc.) are already implemented, so you avoid boilerplate code.

  • Extensibility: Override or extend the default behavior easily to suit your project’s unique requirements.

What Does REN.Kit Provide?

  • A fully generic IRENRepository<TEntity> interface and RENRepository<TEntity> base implementation for all your entities

  • An intuitive IRENUnitOfWork<TDbContext> interface to coordinate multiple repositories and manage database transactions

  • Built-in support for EF Core bulk operations, async/sync flows, and advanced query scenarios

  • Advanced extension points: customize or override any repository or unit-of-work method without touching core logic

Typical Usage

With REN.Kit, you simply inject a unit of work into your service or controller, and obtain repository instances for any entity you want to work with.

Whether you need rapid CRUD for prototyping, or strict control for enterprise workloads, REN.Kit’s repository and UoW system adapts to your needs—so you can focus on your business logic, not plumbing code.

PreviousMigration GuideNextVersion Notes

Last updated