This is the first time in my life that I will search for a video, even after it disappeared abruptly, just to subscribe and like it. The content is truly excellent!
Yeah I did that too, I had meant to the whole way through but the abruptness of the "goodbye" didn't give me enough time to get my feet of the desk. Excellent teacher.
please continue to be straight to the point.thank u so much. we need people like u on you tube. not this other people who talk a lot about nothing important in particular
I have no idea why, but I expected a poor quality click-bait video, but after watching this, I'm really enlightened on this. Thank you so much for making and posting this. 🌹
Bro I'd like to thank you for the effort you put in trying to explain all of this info in a way that we could understand. It's very overwhelming when you're starting off as a developer and you receive a bunch of info that's just all over the place. Please please please keep structuring your videos like this, especially tutorials.
There's been a lot of backlash against micro-services with many teams running back to good ol fashioned monolithic architecture, as microservces can quickly become unmanageable and create impenetrable silos among larger teams where one team has no idea what the other team is doing even though both work on the same app, but neither team knows each other's codebases.
Maybe they don't need to know, micro-services use internal API, there shouldn't be much issue though unless they don't have good documentation of their API
This sounds like a product management issue. For any well-managed product, micro-services management will be well documented and roles clearly assigned.
The state of the art is: you start with monolith, and then introduce micro-services when needed. And you consider introducing micro-services only if you have many small teams in your organisation (to reflect that structure in your app for development and maintenance).
That's the most comprehensive explanation for beginners out there! Usually, we have to search each term separately, but this video puts everything in context
I came here as I got curious about web apps and I loved the way you explained it. I am not from a tech background and I thought I couldn't understand it but I did. Now I can explain this to anyone. Thank you!
thank you for explaining, microservices because as a student i really couldn't understand that concept. if you have time it would be appreciated if you could do a small demo app using the microservice architecture, looking at the code would further cement this knowledge!
This video is so so soooooo well done. Love the way you teach and gesticulate (and may or may not have stolen this habit to apply it to my own teaching). This video would have been super helpful for me 1 week earlier, so I would have scored a few bonus points at the recent interviews. Anyway, I did pass them. As for yourself sir, keep up a good job!
Microservices are only necessary for large scale apps with very specific business cases. It is incredibly hard to define a domain inside a large application and when starting on your app a “monilith” structure is the way to go for most. As long as they keep the backend en frontend separated through “SPA” design and implement a pub/sub event driven architecture. Microservices can be created by cutting up the original monolith (if even necessary). But by doing tasks out of sync you can also easily scale up by deploying more workers
So, now I know EVERYTHING and I suppose I am a senior engineer now...thank you for making me senior in 10 minutes. Damn clickbait. From 10 minutes 2 min is an ad so you made it even faster!
Love how the code coffee transforms into a breakfast smoothie at 9:14 lol But for real thank you for this video; I'm completely teaching myself all of these computer science concepts so having a fairly bite sized, well-explained video laying these out is an especially helpful starting point on my way to understanding the overall picture.
Such a great video, and the end though😅 was not expecting that😂 . This is the first time I wanted a you tube video to actually be longer 🤦♀️ awesome 👏
Consider modular monolith. When properly done (with discipline) gives you the same architecture as based on microservices but without the REST overload. During development you work, debug and test only a module and once accepted, merge it to your project main frame. Use microservices when they are needed, but if they live in the same context, make your application modular especially when your application is sensitive on pinball communication time consumption.
Insightful post! Thanks for breaking down web app architecture essentials. Clear and concise, it's a valuable resource for understanding the fundamentals. Great job!
Great video. It's all about modules AKA objects AKA functions AKA subroutines… …client-server = sub-modules talking to a main module, peer-to-peer = modules talking to each other... (before computers = Betty in payroll talking to John in accounting...)
Thanks for the very informative and well-explained video! You have a great talent for explaining complex architectures very simply in terms that everyone can understand. Liked and subscribed! P.S. Could you please make a video about Event-Driven Architecture?
Its the first time I heed outside advice, realizing their value to an organizations sometimes I dislike, the CaesarKing I now activate those 2 racks of servers I destroyed belonging to 2 different organizations or groups. My mind is cooler now. Let it be
Great video, would've been better if you took a section to talk about the downsides of micro services architecture such as how challenging they can be to manage when they grow in number or how cloud functions may take a significant amount of time to warm up.
I have lost count of the number of times that engineers have recommended the microservice holy grail an the number of times the engineering team missed their deadlines and ultimately resorted to the traditional./non-microservice approach. Common sense modular development is a timeless approach.
microservices is unix way rephrased. there's also federated architecture in terms of networking structure (it inlines between p2p to client-server, and email is one of the oldest representatives, along with xmpp). monolithic and microservices are just enterprise buzzwords by people who sell stuff to sell same stuff in different packaging. in sentient world reasonable approach to modularity is generally taken:)
@ForrestKnight I need a few book recommendations. You covered a lot of stuff in this video and I appreciate it... but seriously Good Bye....I love it... great video as always.
All the video was super cool, I understood a lot, thanks. A small advance: the end of the video was very brutal, maybe you can do a summary of what you explained. Excepting that, everything was at the point, with very good real life examples.
usually ill design most apps as n-tier compatible, with the idea that the db, server, and client, and gateways must be scalable, with a preference to microservices so it can be used at very little cost across multiple cloud platforms. pretty tricky sometimes, but usually i'll design it all in python using flask, or sometimes just building my own socket servers for the backend stuff. one of these days though i'll finally get up the courage to read through libcurl and try to make it in c XD
Would share the series #2 of this video, it was really like korean drama movie whereby the main actor almost got shot by flying bullet, and the movie just ending abruptly. What a nice way to raise audience interest. Well done but...byeee...
okay so i have a question. I just read an article about three tier web app architecture and it says that the frontend is in a public subnet and the backend is on a private subnet Therefore, the backend is only accessible from the frontend ec2 instance (I'm using aws here as an example) and not from the public internet. My question is when a user in his laptop access the web which is the frontend ec2 instance and made a backend request (let's say the user clicks a button that has fetch("some backend url")) does the request come from the user's laptop or from the frontend ec2 instance? because if the request comes from the user's laptop does that mean it will not be allowed since the backend is only accessible from the frontend ec2 instance? or does the request is actually made from the frontend ec2 instance? Thank you in advance.
🖥 Dev Notes Newsletter 👉www.devnotesdaily.com/
📓 Studious, Notion Template for Students 👉notionstudent.com (limited time discount added at checkout)
Is there a mobile app?
Forrest, where did you get that Keyboard? What is it?
This guy explained everything perfectly for me, got my undivided attention, then randomly dipped. Absolute legend.
This is the first time in my life that I will search for a video, even after it disappeared abruptly, just to subscribe and like it. The content is truly excellent!
Yeah I did that too, I had meant to the whole way through but the abruptness of the "goodbye" didn't give me enough time to get my feet of the desk. Excellent teacher.
please continue to be straight to the point.thank u so much. we need people like u on you tube. not this other people who talk a lot about nothing important in particular
I have no idea why, but I expected a poor quality click-bait video, but after watching this, I'm really enlightened on this. Thank you so much for making and posting this. 🌹
Bro I'd like to thank you for the effort you put in trying to explain all of this info in a way that we could understand. It's very overwhelming when you're starting off as a developer and you receive a bunch of info that's just all over the place. Please please please keep structuring your videos like this, especially tutorials.
That ending though...
GOODBYE
😂
Right felt like it was in the middle of him explaining.
Wtf 😂😂😂
Like he has been explaining to people who hardly understand what he is trying to say then realized it's nolonger worth it and stopped immediately
There's been a lot of backlash against micro-services with many teams running back to good ol fashioned monolithic architecture, as microservces can quickly become unmanageable and create impenetrable silos among larger teams where one team has no idea what the other team is doing even though both work on the same app, but neither team knows each other's codebases.
chronic 😮💨
monolithic won't work for large applications like youtube where scalability becomes considerable factor
Maybe they don't need to know, micro-services use internal API, there shouldn't be much issue though unless they don't have good documentation of their API
This sounds like a product management issue. For any well-managed product, micro-services management will be well documented and roles clearly assigned.
The state of the art is: you start with monolith, and then introduce micro-services when needed. And you consider introducing micro-services only if you have many small teams in your organisation (to reflect that structure in your app for development and maintenance).
This video was on my home feed for the last one year. Just watched it. Awesome piece. The way he ended the video was hilarious!
That's the most comprehensive explanation for beginners out there! Usually, we have to search each term separately, but this video puts everything in context
I came here as I got curious about web apps and I loved the way you explained it.
I am not from a tech background and I thought I couldn't understand it but I did. Now I can explain this to anyone. Thank you!
Love the way you architected this video.... Came In, Told us everything & said Goodbye, no BS in between.
Great Video BTW.
Are you sure we saw the same video?
@@StijnHommes Man must be on youtube subscription
I think this is the simplest, most understandable and beautiful explanation about WEB APPS Architecture ever. Great video!
Thanx brother for explaining this to a complete beginner like me trying to learn software development!
Dude I have the worst attention span but this video is great, so much information in so little time. No time wasting. Subscribed
thank you for explaining, microservices because as a student i really couldn't understand that concept. if you have time it would be appreciated if you could do a small demo app using the microservice architecture, looking at the code would further cement this knowledge!
About time RUclips recommends a video that makes sense and provides enlightening information.
This video is so so soooooo well done. Love the way you teach and gesticulate (and may or may not have stolen this habit to apply it to my own teaching). This video would have been super helpful for me 1 week earlier, so I would have scored a few bonus points at the recent interviews. Anyway, I did pass them. As for yourself sir, keep up a good job!
gesticulate
first time watching your video, I love it. Can't wait to learn more from you.
Microservices are only necessary for large scale apps with very specific business cases. It is incredibly hard to define a domain inside a large application and when starting on your app a “monilith” structure is the way to go for most. As long as they keep the backend en frontend separated through “SPA” design and implement a pub/sub event driven architecture. Microservices can be created by cutting up the original monolith (if even necessary). But by doing tasks out of sync you can also easily scale up by deploying more workers
whats "SPA"
@@howwwwwww. singe page applications but most often used to describe a vue/angular/react paired with a loosely couples backend api
So, now I know EVERYTHING and I suppose I am a senior engineer now...thank you for making me senior in 10 minutes. Damn clickbait. From 10 minutes 2 min is an ad so you made it even faster!
Man that was a very well-structured, comprehensive explanation. Thank you!
This video is so insightful. I've been looking for something like this for literally a while now but don't know the right query. Thanks, bruv.
Thanks for sharing ForrestKnight! This is helpful: "Microservice architecture - A collection of services, that each serves a unique responsibility."
Love how the code coffee transforms into a breakfast smoothie at 9:14 lol
But for real thank you for this video; I'm completely teaching myself all of these computer science concepts so having a fairly bite sized, well-explained video laying these out is an especially helpful starting point on my way to understanding the overall picture.
I get the feeling this is the type of dude who can accomplish everything I'm trying to do
you deserve 100 subs from a single account brother. You gave me a good idea about how development work
The examples you gave really helped me wrap my head around the concepts. Appreciate the effort and to the point explanations!
Bro this is best video I’ve seen in a long time simple and effective
love the effort you put in these videos !
That was awesome man!🌟 I loved every minute of it
Such a great video, and the end though😅 was not expecting that😂 . This is the first time I wanted a you tube video to actually be longer 🤦♀️ awesome 👏
Consider modular monolith. When properly done (with discipline) gives you the same architecture as based on microservices but without the REST overload. During development you work, debug and test only a module and once accepted, merge it to your project main frame. Use microservices when they are needed, but if they live in the same context, make your application modular especially when your application is sensitive on pinball communication time consumption.
That Goodbye was so sudden.....
I like it 💯
😂😂😂
I didnt understand anything at the introduction, but decided to bear with u a moment and it paid off well!
LOL the goodbye at the end killed me
Great explanation, no gimmicks. Very much appreciated 👍
This is a GREAT explanation for beginners!
Well explained. One of the best I’ve seen.
Love your videos man. Keep up the great work!!
thank you so much for this. It made me realise the app i'm working on will require micro-services architecture.
So simple and clear. Great place to start. Thank you.
Insightful post! Thanks for breaking down web app architecture essentials. Clear and concise, it's a valuable resource for understanding the fundamentals. Great job!
In this 10 min I learnt more than my uni taught in God dam 3 years.
Wow thank you for such a great explanation
Great video. It's all about modules AKA objects AKA functions AKA subroutines…
…client-server = sub-modules talking to a main module, peer-to-peer = modules talking to each other...
(before computers = Betty in payroll talking to John in accounting...)
This couldn't have come at a better time
nice explanation! Web app architectures is pure art, I really like dive in the topic!
Thanks for the very informative and well-explained video! You have a great talent for explaining complex architectures very simply in terms that everyone can understand. Liked and subscribed!
P.S. Could you please make a video about Event-Driven Architecture?
I agree…
Hi thanks for this video I've learnt a lot in just10mins. Subscribed already!!
Thank you so much for this informative video. You explained so well and I am no longer confused.
Its the first time I heed outside advice, realizing their value to an organizations sometimes I dislike, the CaesarKing I now activate those 2 racks of servers I destroyed belonging to 2 different organizations or groups. My mind is cooler now. Let it be
Thanks for the time and effort you put into making such educational videos. Much appreciated.
Wonderful job here❤❤
Yeeeyy, great timing💛 Thank u🫂
bravo! thank you for that detailed description./ I feel a little more comfortable at understanding my job now.
Great video, would've been better if you took a section to talk about the downsides of micro services architecture such as how challenging they can be to manage when they grow in number or how cloud functions may take a significant amount of time to warm up.
this is so amazing, you've earned my subscription & many more views to come
This is one really strange way to end your video 😅. Great content 👌
Dude, it's videos like this that transform OK coders into great coders! Please keep making awesome videos like this!
Thank you, great explanation!
absolutely gorgeous maaan!!!
this video is a piece of art. thank you.
excellent info bro thanks, please do continue like this
Love your content! I wouldn't have started my own Tech RUclips channel if it wasn't for finding yours. Can't wait for your future content!
Man! Im new in your channel but hollyy... I love it already! Thanks for all the info 🥳
big thanks to you for most insightful information about web architecture, I am grateful to you,✨
Really great explanation!
This is actually very informative. I never really understood microservices and serverless computing before!
Serverless computing is easy. It's what you do offline. What we did before everything was hooked up to the web even though most of it shouldn't be.
Superb explanation, thank you for the video.
Awesome video! Thanks. The short hair makes me want to stop calling you tech Jesus 😂😂
This was a great intro, thank you so much
Really nice video bro!
I'm calling you babe from today😂😪😂, this took me out a black hole😭😭 very very helpful!!!🔥🔥
Very well articulated and to the point. Thank you
I have lost count of the number of times that engineers have recommended the microservice holy grail an the number of times the engineering team missed their deadlines and ultimately resorted to the traditional./non-microservice approach.
Common sense modular development is a timeless approach.
This was brilliant, much appreciated.
microservices is unix way rephrased.
there's also federated architecture in terms of networking structure (it inlines between p2p to client-server, and email is one of the oldest representatives, along with xmpp).
monolithic and microservices are just enterprise buzzwords by people who sell stuff to sell same stuff in different packaging. in sentient world reasonable approach to modularity is generally taken:)
Awesome explanation, thanks a lot
@ForrestKnight I need a few book recommendations. You covered a lot of stuff in this video and I appreciate it... but seriously Good Bye....I love it... great video as always.
Love the video !
Would like to see one about micro front end architecture if possible !
All the video was super cool, I understood a lot, thanks.
A small advance: the end of the video was very brutal, maybe you can do a summary of what you explained.
Excepting that, everything was at the point, with very good real life examples.
Thanks FK, well explained for non-IT ppl
This videos was really helpful. Thanks
usually ill design most apps as n-tier compatible, with the idea that the db, server, and client, and gateways must be scalable, with a preference to microservices so it can be used at very little cost across multiple cloud platforms. pretty tricky sometimes, but usually i'll design it all in python using flask, or sometimes just building my own socket servers for the backend stuff. one of these days though i'll finally get up the courage to read through libcurl and try to make it in c XD
Man! You’re amazing. Thanks for
Perfectly explained
incredible explanation
Very much needed video!
That was the quickest outro ever. Almost insulting
Amazing Video... Thanks for this informative video
Would share the series #2 of this video, it was really like korean drama movie whereby the main actor almost got shot by flying bullet, and the movie just ending abruptly. What a nice way to raise audience interest. Well done but...byeee...
Heeey @fknight! Never do that again! Was so hooked and you just "goodbye" like that?😂
this is the best explanation
Learning the way of the ForrestKnight.
Amazing video, thank you
absolutely love that, thanks!!
That's the most abrupt ending I've ever witnessed. Felt like untimely death 😆
okay so i have a question. I just read an article about three tier web app architecture and it says that the frontend is in a public subnet and the backend is on a private subnet Therefore, the backend is only accessible from the frontend ec2 instance (I'm using aws here as an example) and not from the public internet. My question is when a user in his laptop access the web which is the frontend ec2 instance and made a backend request (let's say the user clicks a button that has fetch("some backend url")) does the request come from the user's laptop or from the frontend ec2 instance? because if the request comes from the user's laptop does that mean it will not be allowed since the backend is only accessible from the frontend ec2 instance? or does the request is actually made from the frontend ec2 instance? Thank you in advance.
Weird ending, but good overview. 🙂
Great one! Now do monorepo and micro frontends.