Skip to content

Update conclusion.md #15

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
+1 −1
Open

Update conclusion.md #15

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion lessons/conclusion.md
View file
Original file line number Diff line number Diff line change
@@ -15,7 +15,7 @@ Having a decent amount of familiarity with the databases I've shown you as well
- Do I have highly relational data where I'll many tables that need to join to other tables? SQL/Relational databases are probably best here
- Do I have highly unstructured data where I'll have collections of related objects that are differently shaped? Document-based databases are going to shine here
- Do I have data where I need to describe graphs of relationships? A graph database can work best here
- Do I have simple needs of just retreiving data based on keys? Key-value stores can be a primary database in these cases
- Do I have simple needs of just retrieving data based on keys? Key-value stores can be a primary database in these cases
- Do I have pipelines of information that need to filter, split, combined, and republished? Something like [Apache Kafka][kafka] could be really helpful here

Do none, some, or all of these fit? Do you have other considerations? Take a second to consider all of your data needs.