Software Architecture From 0 To Enterprise

Подписаться 828

Просмотров 1,1 тыс.

50% 1

My desk setup:
💻 Macbook Air M2 8GB RAM, 512GB SSD: (US) amzn.to/4ckunuo | (UK) amzn.to/3PrjddH
⌨️ Apple Magic Keyboard: (US) amzn.to/3IGam3J | (UK) amzn.to/3TetzOQ
🖱️ Apple Magic Mouse: (US) amzn.to/3J1Juf3 | (UK) amzn.to/48YZvfZ
📱 Laptop stand: (US) amzn.to/49X0Ghu | (UK) amzn.to/3wZYwPy
🖥️ Dell 27 inch Full HD Monitor: (US) amzn.to/3TFj0FX | (UK) amzn.to/49ZaIi4
🔲 Dual Monitor Stand: (US) amzn.to/3vr0MyG | (UK) amzn.to/48XxRjK
🎧 Beats Studio Pro: (US) amzn.to/3Tj3yy9 | (UK) amzn.to/3ViiaAr
💡 Notion software project template: affiliate.notion.so/lv-softwa...
Wondering how to architect a web application from an MVP (Minimum Viable Product) to an enterprise-level solution? In this video, we'll delve into the intricacies of web application architecture, exploring system-level design, MVP architecture solutions, and enterprise-level architectures. Join me as we navigate the journey of architecting a new web application.
🌐 Context
As I transitioned from monolithic architecture to serverless microservices, I've gained valuable insights into effective web application design. Today, I'll share my approach to architecting a side project for meal planning, from concept to execution.
🏗️ Architecture Examples
Let's briefly explore common architecture types and patterns:
Monolithic Architecture
Microservices Architecture
Serverless Architecture
🚧 MVP
Starting with the MVP, we'll outline the basic entities of our meal planning app: ingredients, meals, and weekly meal plans. Here's a simplified architectural overview:
🌐 Enterprise
Now, let's elevate our architecture to an enterprise-level solution. We'll adopt microservices architecture, dividing the application into independent services:
🎬 Outro
Architecting software applications requires careful consideration and planning, whether for small side projects or enterprise solutions. While the microservice pattern offers scalability and flexibility, it's essential to match the architecture with the project's scope and requirements. Stay tuned for more insights into web development tools and techniques.
🔗 Links:
Understanding Web Application Architecture: chat.openai.com/c/67389687-d8...
Deploying Next.js Apps on Vercel: chat.openai.com/c/67389687-d8...
Stay tuned for more coding tips and tutorials. Happy coding, and I'll catch you in the next one! 🌟🚀👨‍💻
Background song by:
/ dahjp

Опубликовано:

17 мар 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 11

@guizaoacc 3 месяца назад

That is good content! I’m surprised that there are not many videos talking about this. Most of the content about architecture are talking cloud environments and networks protocols. What about the regular software developer that wants to ship fast, usually deploys on Vercel and having a BaaS in Supabase, Appwrite or Firebase… There’s no content for scheming it in an intuitive way.

@LjupcheVasilev 3 месяца назад

Thank you! I agree 100%. I did go a bit overboard on this one with the enterprise architecture but like I said at the end, starting with something small and validating the idea is the most important step

@Jonty800 3 месяца назад

Great video! For a serverless architecture, what's your opinion on bundling all CRUD operations into 1 lambda VS decoupling into separate lambdas for each operation?

@LjupcheVasilev 3 месяца назад

Glad you like it! I think it depends on the load of the api. Like I said in the video for MVP it doesn’t really need a lot of lambdas, one graphql lambda is enough. As the load increases decoupling helps serve the users faster and more efficiently. This can be done gradually for example instead of making one lambda per operation it can be one lambda per micro service first and if load increases even more then split those into separate lambdas per operation.

@TheBlackGentlemanGeek 3 месяца назад

I like this video bro. Now I’m more comfortable with architecture. Coming from the frontend side, I always thought that you needed some special skill to design an architecture, since every time I saw one, it was complex with many bits and pieces including spaghetti arrows and shapes. It used to put me off app architecture for years. But lately I decided to step up and dive into it. I still didn’t know there was a thinking process until I saw videos like this, which makes it more palatable and fun. It’s all about following a process, not the lines and shapes. Thanks bro. Also what software did you use in your video to draw your architecture?

@LjupcheVasilev 3 месяца назад

Appreciate the comment. Software architecture can seem daunting but with anything it just needs time to understand it and then the repetitions to fully comprehend and understand how to use it. I used Eraser in this video.