A microservice should implement a storage provider that best suits its needs.
The platform implements several on-premise and cloud-based persistent storage providers. Each Service Brick we develop can be run on all supported storage providers. A customized design for each storage provider is implemented that best utilizes the features of that platform.
Running Everything In One Database
Each of the Service Bricks we have developed can run independently in their own database, or they can all be located within the same database. We use schema names and/or prefixed catalog names to make sure all services can be co-located together, further reducing costs of supporting multiple databases.
Supported Storage Providers
We are currently developing more storage providers which will be released as they finish testing. You can also create your own provider implementations using our exposed interfaces.
Azure Data Tables
We support Microsoft Azure Data Tables. It is a cloud-based, NoSQL data store for storing large amounts of structured data.
Azure Cosmos DB
We support Azure Comos DB. Azure Cosmos DB is a globally distributed, scalable, NoSQL database service for the cloud. You can use with the Azure Data Tables provider or the MongoDB provider to communicate with Cosmos DB without any additional configuration.
Entity Framework Core
We support Entity Framework Core. Use Microsoft's Object Relational Mapping (ORM) technology along with migrations to keep your models synced to your database. You can use Azure SQL, Microsoft SQL Server, SqLite and PostgreSQL.
We support MongoDB. MongoDB is a cross-platform, non-relational, NoSQL document-oriented database engine.