Data in Microservices

Learn about the Materialized View pattern to manage data in microservices architecture.

[@manaspradhan7978]

Excellent ..Thanks for the good explaination

[@mohamedadnanealkhiati5006]

This is an extremely amazing helpful video!

[@emadabushofa2379]

I always use the materialized view approach for most of the services, the only downside is not just duplicating data but also too much data will be copied in too many services, of course they are synchronised with rabbitmq or azure service bus but I also find myself adding a direct http call for reading data from other microservices especially when creating a new service that has 0 data and it needs to read everything around to get started. But anyway it's fun to develop, thanks a lot for your great videos.

[@edwardwong654]

There are details that are either incorrect or inconsistent at best. The matericalized view is READONLY, so the B service can't update it. Typically a MV is setup to by to perform an update after every time inverval, like once a day, or whatever. The update on the price should trigger an event to force the view to do an immediate synch, rather than to update it directly. That is the proper pattern. Also he did not say why the aggregator pattern was not good.

[@mostafasaeedhashhash8718]

Real Big Thanks for all Your Videos.❤️ Your Channel is one of the most high quality channels & really deserve more than subscriptions.

[@senburbensgaming]

Agree

[@Areyousureyouwantto]

thank you for the excellent video brother

[@bobbyiliev_]

This video is amazing!

[@32zim32]

I don't understand why first approach is coupling and is bad, because materializes view is the same coupling, service B dependable on service A, but now this dependency is hidden. So you just replace http or other grpc query from B to A, by some other sync protocol.

[@krzysztofbuczak1212]

Sorry for nooby question but: how is it possible to update (by event) read only table by basket ms? Its "read only"

[@mustaphag]

Bravo Houssem, Excellent work

[@isaiahkhalid7795]

sorry to be so offtopic but does anybody know of a trick to log back into an Instagram account? I was dumb lost my password. I would love any tips you can give me

[@abdullahdanny9420]

@Isaiah Khalid instablaster :)

[@isaiahkhalid7795]

@Abdullah Danny thanks for your reply. I got to the site through google and Im in the hacking process now. Seems to take quite some time so I will reply here later with my results.

[@isaiahkhalid7795]

@Abdullah Danny It worked and I finally got access to my account again. I am so happy:D Thanks so much, you saved my ass :D

[@abdullahdanny9420]

@Isaiah Khalid Glad I could help :)

[@abdelrahmane657]

Very good. Thank you. Yet the last option is best to be avoided. It is not a solution, it’s a risk .

[@easonex02]

Great sharing. By the way, how to present like you, seems a transparent glass between you and the cam. if need some hardware or software?

[@TimBee100]

What is a local database in a cloud environment? How does that work? If you have multiple occurrences of the basket microservice, how many versions of the database do you have?

[@joshuam6013]

I am struggling with finding an approach to insert and retrieve data from the Catalog DB. I am thinking that I would create an insertCatalog Microservice connecting to a write-only DB with a catalog table, and then replicate that data to a read-only DB where I use the getCatalog microservice to get from that replicated DB? Or am I able to create a get/post RESTful API's in the Catalog microservice?

[@khalednabilcs]

Well Said Brother, Can you make a video of implementing the last approach and show it in code Much Appreciate

[@HoussemDellai]

I'll take that into account :)

[@khalednabilcs]

@@HoussemDellai Thank you 🙏

[@khalednabilcs]

@@HoussemDellai Brother I made a full tutorial based on your video including rabbitmq and ocelot I am writing it now once I publish it i will update you hopefully you review it when you have time Thanks again

[@balachanderharivarsha9757]

@@khalednabilcs where is the tutorial plz share link

[@rahulrsavant]

explanation is excellent, i am working on "database per service" pattern.I confuse about how to write materialized view & trigger for this pattern

[@AndreanoCelentano]

Data sharing has its issues. Consider schema change and its implications on cross service communications. With api this problem either does not exist since data is abstracted away or is handled by client versioning and proper version deprecation. Thanks for the presentation.

[@KaranKumar-wb5bn]

then why not just use monolithic?

[@anujchaturvedi6296]

Is it a good idea to share the SQL database with both Catalog Microservice and Basket Microservice?

[@jomarilangamon2323]

what if i added a new materialized view (table), it's empty at the start, how am i going to populate it with data?

[@khalednabilcs]

Either copy the whole data from the original or make a service to get the data on batches

[@sandeeproy3126]

what about grpc , what does it do?

[@khalednabilcs]

Good point, that would be a quicker for services to communicate together

[@prashanthb6521]

I think creating http coupling is easy and we should not shy away from taking that path. Purists might not agree.