Hello @Lauren_Schaefer,
I enjoyed all 3 parts of your video very much, together with building-with-patterns-a-summary. I think it’s really great, and hope that there would be more of these, especially with some real-world use-case and example would definitely be better.
Having said that, most of the videos and guides and pattern only seem to be focusing a lot of the read portion but I thought that maybe there could be a series that focuses of the write? Like what’s the best way to handle the write when there’s need to.
For example, as mentioned in extended-reference-pattern, we duplicate a couple of data that is frequently accessed but rarely updated in the collection, so that the read is fast which I agree, but I don’t know what’s the best way to handle if I have to update my collection in the event that the duplicated data is updated. Let me try to give an example of that.
I have x number of collections, all having a same subset of data in each collection using the extended-reference-pattern
.
// collection-a
{
name: 'a1',
epd: {
profile_key: '12345',
profile_name: 'helloworld',
}
}
// collection-b
{
name: 'b1',
epd: {
profile_key: '12345',
profile_name: 'helloworld',
}
}
// continue for up to collection-n
// collection epd
{
profile_key: '12345',
profile_name: 'helloworld',
// and some more fields
}
Assuming that profile_name
rarely gets updated, but if it ever does, what would be the best way to handle these kind of updates across numerous collection? Is there a good pattern for this sort of stuff?
This is just one example, but I hoped that I did bring the point across where most of the guides only tells the pros of having the patterns, and the cons are (e.g) data duplication. But it doesn’t also tells us how to handle the data duplication properly whenever it does get updated. I thought it was also as important as identify the pattern to resolve the read issue.
Another quick example would be subset-pattern, it tells us to place only a couple of document in collection-a so to quickly access a sub-set of information but it doesn’t tell us how to manage effectively/efficiently on updating the docs.
// movies
{
title: 'fast',
reviews: [
// keep top 10 here
]
}
// reviews
// all the rest of the reviews
Say I have a review that will be promoted to the movies
top 10 review, and one of the top 10 review will be demoted to the reviews
collection. Is there any recommended pattern/practice to do this sort of thing?
I hope I did make some sense here, because those are the things that I don’t quite understand fully.
Lastly, thank you for all the videos and blogs post which is very useful, and keep them coming!