Stop using SQL JOINS. Switch to READ MODELS

Does your application require a database? What if you wrote no more complex SQL joins and replaced them with one query that returns all the information you need in one call. But engineering is all about compromise, you have to sacrifice something. And in this case, all we have to sacrifice is strict consistency, which is not a big deal anyway if you ask me… 🚀 Best AWS Prep Courses: → Ultimate AWS Certification Course Bundle: https://tinyurl.com/aws-certs-bundle → Certified Solutions Architect Course: https://tinyurl.com/AWS-SAA-CO2 📅 Have questions on how to join AWS? How to plan your career in order to become an AWS Solutions Architect? Which certificate to get? Salary negotiation? Resume re-write? Or any other question related to AWS or to the SA position? I'll be happy to offer a 1:1 video call to answer all your questions: https://calendly.com/ilyas_in_cloud ☕️ LOVING THE VIDEOS? BUY ME A COFFEE 😄 https://www.youtube.com/channel/UCwpIueN8B-42Z8vfxVt0yEQ/join In favour of a lightning-fast reading. The idea is to let go of complex SQL joins and to shift the heavy lifting toward the writing side, every time a user does an action, an update needs to be done on the read model, which we were doing before anyway, every time something changes, we update it in the Database somewhere, it's just now we do it with the intention of pushing it as close as possible to the final user. Expensive writing, cheap reads, this is the subject of this episode of Serverless Design Patterns you have to know about! → Use the index below to navigate 00:00 intro 00:29 The landing page is your website killer 01:37 Read Models pattern 04:29 The proper use case 05:07 Outro → Various things mentioned in the video DynamoDB Accelerator (DAX): https://aws.amazon.com/dynamodb/dax/ 🔔 Follow me for more content: iLyas Bakouch → Youtube: https://www.youtube.com/c/iLyasInTheCloud/ → Twitter: https://twitter.com/ilyas_in_cloud → LinkedIn: https://linkedin.com/in/ilyasbakouch/ #sql #serverless #sqljoins