Add SQLite Aspire Component

[eerhardt]

We will probably have both EF and non-EF components (just like the other database components).

• https://www.nuget.org/packages/Microsoft.EntityFrameworkCore.Sqlite/
• https://www.nuget.org/packages/Microsoft.Data.Sqlite.Core/

[bgiromini]

My use case would to combine sqlite with litestream as written up here, https://docs.servicestack.net/ormlite/litestream.

[davidfowl]

Unsure if we're doing this for v1.

[SteveSandersonMS]

I'm curious about how this would work if it was done. Would this only be for ephemeral databases (in which case how is it different to the app just creating its own .db file inside its own container?) or would it be persistent across deployments in some way? If it was persistent, where would the .db file be stored?

It would be great if there was some suitable persistent filestore available to mount into ACA containers but Azure file shares seem not to be recommended for this purpose.

The use cases for persistent SQLite (as opposed to Postgres/MySQL/etc) will be things like:

• Parts of an application that are dealing with small amounts of traffic/data and gain no benefit from heaver DBs. Simply working with .db files on disk is a nice and easy developer experience.
• Deploying 3rd-party application components that innately require SQLite and you can't control that (e.g., pgadmin4)
• Experimentation/proofs-of-concept

... so I do think it would be a nice feature, and so wonder how it could be made to work in the long run.

[naillizard]

I'm curious about how this would work if it was done. Would this only be for ephemeral databases (in which case how is it different to the app just creating its own .db file inside its own container?) or would it be persistent across deployments in some way? If it was persistent, where would the .db file be stored?

It would be great if there was some suitable persistent filestore available to mount into ACA containers but Azure file shares seem not to be recommended for this purpose.

The use cases for persistent SQLite (as opposed to Postgres/MySQL/etc) will be things like:

• Parts of an application that are dealing with small amounts of traffic/data and gain no benefit from heaver DBs. Simply working with .db files on disk is a nice and easy developer experience.
• Deploying 3rd-party application components that innately require SQLite and you can't control that (e.g., pgadmin4)
• Experimentation/proofs-of-concept

... so I do think it would be a nice feature, and so wonder how it could be made to work in the long run.

I would love this to be supported, local .db files for local development and integrate with Turso would be amazing.

[aaronpowell]

I've created a Community Toolkit proposal for it - CommunityToolkit/Aspire#364

[maddymontaquila]

Completed in the community toolkit - thank you @aaronpowell !!