Overall, the key takeaway is the importance of thoughtful design and architecture in building scalable, maintainable, and resilient web applications, while embracing principles such as modularity, scalability, and adherence to SOLID principles.
My takeaways are when asking on what project to do, don't jump/create immediately. ask more details about the said project. It is important to know the Why's and How's when doing the project to architect it properly.
ask questions such as is this a feature that requires a real-time interaction...
research about 3-rd party libraries, apis, services you can use
choose a language, framework, db
think about managing micro-services
I have never thought that there are a LOT of processes that go behind the scenes when I use a particular app. The video and the article showed that the complexity of the web app is only limited by how complex of an app we wanna make and requires good understanding of how microservices work together.
- Always ask questions before jumping into conclusions
- Learn and understand the system requirements to know when to use a heavy or light framework
- Continuously learn. You can use cloud services to do the heavy lifting (container orchestration, server management, serverless)
- Try not to be overwhelmed and break it down to simplicity
Top Comments
an elaborative way to discuss how to create a system. very informative. learned a lot. thank you
There are many ways to develop an app. It would be best to ask questions, review on what is needed and plan rigorously to make the best possible way.
Other Comments
Overall, the key takeaway is the importance of thoughtful design and architecture in building scalable, maintainable, and resilient web applications, while embracing principles such as modularity, scalability, and adherence to SOLID principles.
I study first what techstack I can use to build sites and apps.
Very good explanation
Have a rough plan for my capstone project now. Thank you Michael!
My takeaways are when asking on what project to do, don't jump/create immediately. ask more details about the said project. It is important to know the Why's and How's when doing the project to architect it properly.
ask questions such as is this a feature that requires a real-time interaction... research about 3-rd party libraries, apis, services you can use choose a language, framework, db think about managing micro-services
I have never thought that there are a LOT of processes that go behind the scenes when I use a particular app. The video and the article showed that the complexity of the web app is only limited by how complex of an app we wanna make and requires good understanding of how microservices work together.
- Always ask questions before jumping into conclusions - Learn and understand the system requirements to know when to use a heavy or light framework - Continuously learn. You can use cloud services to do the heavy lifting (container orchestration, server management, serverless) - Try not to be overwhelmed and break it down to simplicity