Really helpful. Thanks so much! Just a question... what if an employee can belong to multiple organizations? For instance, the same employee is a consultant for Orgs A and B. How would you model this?
"oops I forgot to change this to Project Y but yes this should have been Project Y and would have been if I didn't typo." Ah yes therein lies the problem of non-structured data. It relies strongly on good coding practice and checks. Otherwise you can get yourself into a lot of trouble
Hello Manoj, thank you for showing a design pattern for developing DynomoDb tables. It really gave me a different approach to design database in dynomoDb. This pattern helps reduce the number of tables. But still, for big projects, we can't put all the tables into one. Then front end coding becomes more to maintain. Looking more videos on DynomoDb. Thank you for your great time to share your knowledge with us. Good health and let this good work goes on...
@@EnlearAcademy Hi Manoj, in a previous video, you explain how to use Amplify with GrahQL and Appsync to create an application. In this example, Amplify will create more than one tables of course. What do you think on this approach ? Did you change your mind about Amplify/Grahql/Appsync ? Greetings from Belgium Olivier
You have the frontend in front of an API Gateway and some lambdas therefore this one-table design is hidden. The contract between frontend and backend is in the REST API not in the table design. You can change the backend as along as you keep the REST API the same. You don't want to access dynamodb table directly from frontend.
Excellent! Thank you.
Thank you so much for these videos. I can't wait for your future DDB videos!
Really helpful. Thanks so much!
Just a question... what if an employee can belong to multiple organizations? For instance, the same employee is a consultant for Orgs A and B. How would you model this?
Appreciate this video, but what if user Manoj joins 100 projects then decides to change his name, would you need to find and then update them all?
Yea. This is a good question. I am looking forward to an answer.
Very hands on, thank you!
Thank you
Very informative video. Extra question: how do you get all employees who are not assigned to a particular project?
"oops I forgot to change this to Project Y but yes this should have been Project Y and would have been if I didn't typo."
Ah yes therein lies the problem of non-structured data. It relies strongly on good coding practice and checks. Otherwise you can get yourself into a lot of trouble
Hello Manoj, thank you for showing a design pattern for developing DynomoDb tables. It really gave me a different approach to design database in dynomoDb. This pattern helps reduce the number of tables. But still, for big projects, we can't put all the tables into one. Then front end coding becomes more to maintain. Looking more videos on DynomoDb. Thank you for your great time to share your knowledge with us. Good health and let this good work goes on...
@@EnlearAcademy Hi Manoj, in a previous video, you explain how to use Amplify with GrahQL and Appsync to create an application. In this example, Amplify will create more than one tables of course. What do you think on this approach ? Did you change your mind about Amplify/Grahql/Appsync ? Greetings from Belgium Olivier
You have the frontend in front of an API Gateway and some lambdas therefore this one-table design is hidden. The contract between frontend and backend is in the REST API not in the table design. You can change the backend as along as you keep the REST API the same. You don't want to access dynamodb table directly from frontend.
👑🙏
❤