The interest in Native AOT is significant ever since it became possible with .NET 8 to deliver ASP.NET Core apps directly as machine code. However, a major problem is that Entity Framework Core is currently not compatible with Native AOT. In this presentation, we explore alternatives for designing the Data Access Layer in Native AOT projects: We look at different micro-ORMs and examine how we can use Humble Objects (DB Sessions) to clearly separate our business logic from the data access layer. The goal is to create a structure that looks almost as if we were using EF Core. In doing so, we also delve into patterns such as "Unit of Work" and "Repository," discussing how these can be profitably integrated into our codebase.