Question 1

How does EISK compare to the default ASP.NET Core Web API template?

Accepted Answer

EISK adds a clean architecture layer, reusable CRUD classes, and Swagger integration out-of-the-box, making it more feature-rich but also more opinionated than the minimalist default template, which is better for quick starts without overhead.

Question 2

Can I use EISK with .NET 7 or .NET 8?

Accepted Answer

EISK is built on .NET 6.0, so using it with newer versions might require manual upgrades or modifications, as the template is not officially updated for later releases, based on the README's technology stack.

Question 3

How to add authentication to an EISK API?

Accepted Answer

You would need to integrate authentication mechanisms like JWT or OAuth manually, as EISK does not include pre-configured authentication, focusing instead on core API structure and leaving security implementation to the developer.

Question 4

Does EISK support NoSQL databases?

Accepted Answer

No, EISK is designed with Entity Framework and SQL Server in mind for database testing, so adapting it for NoSQL databases would require significant changes to the data layer and utilities.

Question 5

Is EISK suitable for building microservices?

Accepted Answer

While EISK provides a solid foundation for individual APIs, its clean architecture might introduce overhead for microservices that prioritize simplicity and independence; additional customization would be needed for distributed systems.

Question 6

How to customize the database layer in EISK?

Accepted Answer

Modify the Entity Framework configurations and data layer classes, but note that EISK's base classes and testing utilities are tightly coupled to SQL-based approaches, which may limit flexibility.

EISK

What is EISK?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions