-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
new data hub #3836
new data hub #3836
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here are some comments!
text: "Microsoft.Data.Sqlite overview" | ||
- url: /sql/ | ||
text: "Microsoft SQL documentation" | ||
- url: /azure/postgresql/flexible-server/connect-csharp |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to point to an Azure-specific page for the general MSSQL link? Could be confusing (maybe at least amend the text)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that page has both Azure and on-premises docs
text: "Use C# .NET to connect and query data in Azure Database for MySQL" | ||
|
||
# Card | ||
- title: Document databases |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So it's a bit odd to have many links for just a single database under "Document databases" 😉 Maybe just call this card "Cosmos"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The intent is for people new to .NET/etc. They won't search for Cosmos, but rather "document database" and the one we happen to have is Cosmos.
text: "EF Core Azure Cosmos DB provider" | ||
|
||
# Card | ||
- title: Graph databases |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
MSSQL also has graph capabilities: https://docs.microsoft.com/en-us/sql/relational-databases/graphs/sql-graph-architecture?view=sql-server-ver15
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice I'll add it
text: "Overview" | ||
|
||
# Card | ||
- title: EF Core |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does EF Core belong under "Databases", as opposed to maybe Data Services below?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
great point! I'm mixed thoughts. To me discoverability is the most important and when looking at databases, seems not like a bad thing to include "this is our recommended way to connect to databases (in most scenarios).
text: "Analyze it!" | ||
|
||
# Card | ||
- title: SignalR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is SignalR really a data API?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, it's one of the preferred ways in .NET to send/receive realtime/streaming data
text: "Analyze it!" | ||
|
||
# Card | ||
- title: gRPC |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would probably bump this up - it definitely seems more important than CoreWCF at the least.
brand: dotnet | ||
|
||
metadata: | ||
title: .NET data documentation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we style it .NET Data? (everywhere) This just makes me ask, "What's data documentation?"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great!
If @smitpatel is able to take a quick look, I will merge after his approval. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great @JeremyLikness. LGTM
Initial layout for new data hub. Addresses #3833