-
|
Hi, I started working on a new Aspire component for a new generation database but then I re-read the guidelines and one thing clicked: I suppose that most databases in the database world are not well-known/widely used apart from the big ones (MySQL, SQL Server, Postgres, Oracle, MongoDb, Cassandra, Redis and Neo4j). So my question is, should we have a limit in to what database Aspire should support? Considering things like Firestore (localhost emulator at most), ArangoDb, CockroachDB, etc... |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
We expect to support all databases, but they won’t be part of the initial release of part of this repository. Once we GA, many of these components will live outside of this project and others will be able to build components and resources and publish them to nuget. What we did was attempt to bootstrap the project and ecosystem to figure out what patterns would be effective for a wide variety of libraries. Now that we’ve done that, the work will be figuring out how to make it more distributed. |
Beta Was this translation helpful? Give feedback.
We expect to support all databases, but they won’t be part of the initial release of part of this repository. Once we GA, many of these components will live outside of this project and others will be able to build components and resources and publish them to nuget.
What we did was attempt to bootstrap the project and ecosystem to figure out what patterns would be effective for a wide variety of libraries. Now that we’ve done that, the work will be figuring out how to make it more distributed.