Data storage documentation

[gk-8]

Please elaborate a bit more on the data storage section, giving the reasoning of why to use SQL vs Cosmos (relational vs non-relational) depending on the scenario, and how a microservices approach helps to make this kind of decisions

[khaledhikmat]

Actually the solution uses two: Cosmos and Azure SQL Database. Cosmos is used to store entities such as Drivers, Passengers and Trips and Azure SQL Database is used to persist trip summaries so they can be reported on in PowerBI, for example.

I made this section a little bit clearer by adding the key advantages that Cosmos offer for the Relecloud solution.

[gk-8]

Thanks Khaled! But still missing a bit on the point we wanted to make here. Right now it might look like the only reason we are choosing SQL vs Cosmos DB for the historic data is the Power BI reporting, but that is actually something you could also do with Cosmos DB.

The point here should be more pivoted based on the following:

• Scenario: Cosmos DB is a better fit for "hot data", live reads/writes in near real time, with high throughput vs more static data used for analytics, monitoring or stats visualization in Azure SQL.
• Flexibility thanks to a microservices approach, which lets you choose the best approach for each scenario, as every service will be independent and agnostic of what you are using.

That was the point of using different languages and data stores, it'd be great to have it reflected.

[khaledhikmat]

Ah...I see ...the blind man says :blush: Thanks. Let me discuss with Joel ...we will amend.

[gk-8]

Great, thanks! Please keep me posted when it's added :)