Everything You NEED to Know About WEB APP Architecture

Video quality	The size	Download

Information Everything You NEED to Know About WEB APP Architecture

Title	:	Everything You NEED to Know About WEB APP Architecture
Lasting	:	10.27
Date of publication	:
Views	:	267 rb

🖥 Dev Notes Newsletter 👉 wwwdevnotesdailycom/ br📓 Studious, Notion Template for Students 👉 notionstudentcom (limited time discount added at checkout)
Comment from : ForrestKnight

Great video
Comment from : Nima Mehrjoo

this is gold thanks mate
Comment from : InspireForward

Not only the new shirt but the cup was also replaced by a bottle
Comment from : Prabhakar Mishra

thank you so much for this It made me realise the app i'm working on will require micro-services architecture
Comment from : lemonyth

microservices is unix way rephrasedbrbrthere'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)brbrmonolithic 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:)
Comment from : Alexander Betaev

How many times you gonna adjust your sleeves during the video? lol
Comment from : First Last

The ending is like a console app lol
Comment from : imgrori

I didnt understand anything at the introduction, but decided to bear with u a moment and it paid off well!
Comment from : Булат Почанов

Jesse? so you're being a developer now?
Comment from : Kusuma Inc

micro services requires deep consideration such as transaction crossing services, performance as overhead on intensive massaging if you are talking about complex system, it cannot be truly stateless there is no single technology can work without flaw, especially micro services, experience on architecture design and implementation cycle do counts a lot
Comment from : Alex Wing

"All these problems can be solved with mocroservices!" If you say so
Comment from : Gilbert Ssenyonjo

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
Comment from : John Doe

Thanks ! ❤❤❤
Comment from : Nature Lovers

You dont see something on the server side of youtube unless something goes terribly wrong 😂😂😂
Comment from : Eswar Prasad

Nice ending
Comment from : MitoTV - Random Content

I get the feeling this is the type of dude who can accomplish everything I'm trying to do
Comment from : Ojay Matuso

Love how the code coffee transforms into a breakfast smoothie at 9:14 lolbrbrBut 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
Comment from : HeroineOfTwilight

LOL the goodbye at the end killed me
Comment from : Aleksandra Teng Ma

Meanwhile some of Microsoft and other tech giants most profitable applications live in a mono repo
Comment from : jonathan naranjo

thank you :)
Comment from : Happy Home

Great explanation, no gimmicks Very much appreciated 👍
Comment from : James Bentley

Superb explanation, thank you for the video
Comment from : Rolando Lopez

Stop using microservices You can modularize your code without microservices It's just a matter of structuring your source code and configuring your build system Only break your services up when there is a real world performance bottleneck The added complexity is not worth it for anything less than real world performance benefits
Comment from : T1Oracle

w t h how you end it like that great video though
Comment from : Viajes Culinarios

Wasted 11 minutes
Comment from : Max Bezs

The team that works on youtubes search service is terrible at their job, it's starting to look like instagram and facebook search It use to be good, but now it's spam and unrelated things
Comment from : 𝟺𝟷𝟷𝟻𝚜𝚝𝚎𝚟𝚎𝚌𝚘𝚖

So, now I know EVERYTHING and I suppose I am a senior engineer nowthank you for making me senior in 10 minutes Damn clickbait From 10 minutes 2 min is an ad so you made it even faster!
Comment from : Анатолій Ветренко

30 of the video is about promo! what a low quality channel
Comment from : A Schulz Albrecht

Amazing video, thank you
Comment from : Ali Kassem

Thank you
Comment from : Salaheddin AbuEin

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
Comment from : ConstantinCI

The jetbrains ad was too long
Comment from : Robert Ussery

Great one! Now do monorepo and micro frontends
Comment from : Deyan Dachev

Use erlang
Comment from : Qwerty Plm

in microservices what connects each system or service with each other? or how all these microservices are connected and how they talk to each other if each service is developed in a different language?
Comment from : Natural Thoughts

Thanks
Comment from : Gustavo Machado

Very well articulated and to the point Thank you
Comment from : Amikawi

Wonderful job here❤❤
Comment from : holyKane

it look like all the WEP APP Architecture build on monolith?
Comment from : hani issa

Funny that Amazon went back to monolithic lol
Comment from : DM Sanchez

I think this is the simplest, most understandable and beautiful explanation about WEB APPS Architecture ever Great video!
Comment from : imAlexisdzn

But reality is completely different 😅 microservices are not about app design, and monolyth is not about spaghetti code So just follow SOLID principles and everything will be okay 👍
Comment from : Maksym Mospanenko

Dis video is not complete
Comment from : JBLE

I'm calling you babe from today😂😪😂, this took me out a black hole😭😭 very very helpful!!!🔥🔥
Comment from : Yamashita

I was hoping for a 20 hour video tbh LOL
Comment from : Ali Akram

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!
Comment from : alabi light

Web 3 is about being on the path to get rid of the extractive middle layer that is the bane of all teh edge dwelling people for last millennia direct to trustless truths, and each can access the resources of the entire network, the issue is that it requires a staking-in ATM
Comment from : UnifyBags

Thank you for sharing!
Comment from : phuc tran

I create app in a monolith codebase but each domain loosely coupled, so i can freely to combine multiple domain as a service or separate them as independent service, this creates a scalable and manageable system
Comment from : Alvin xyz

thank you
Comment from : Business Wolf

In this 10 min I learnt more than my uni taught in God dam 3 years brWow thank you for such a great explanation
Comment from : Keshava kumar

boy that JetBrains ad was longbrbr2:31 to continue
Comment from : Jacob L

We wouldn’t have noticed the new shirt if didn’t tell us 😂😂
Comment from : Yogesh Singla

Jet brains space would probably go along well with the Thunderbird email client
Comment from : Spicey French Toast

Amazing Video Thanks for this informative video
Comment from : Jatil Yadav

what are you referring to when you say the server is running on one "machine"?
Comment from : Git Money

Guess I am an expert at architecting apps now
Comment from : Dhruv Patel

JetBrains is from Russia Hence, you've been sponsored by terrorist country
Comment from : MrBratkenSolov

Everything hahahahah :)
Comment from : M Z

where does the mvc architecture fit in
Comment from : Damintel

We don't need to know about "web app" architecture Devs need to learn native app development and web development without poisoning the website they're building
Comment from : Stijn Hommes

Awesome explanation, thanks a lot
Comment from : Oscar Lemus

Just curious what books have you read related to programming, software development and computer science? can you make a video about it?
Comment from : John Nazarene Dela Pisa

This video should be titled as "Singles watch me as I seduce women"
Comment from : Ajin

Lol was pronouncing 'Azure' wrong a joke? Otherwise a decent video, I think maybe including Web3 is kind of pointless though because it's all hype from cyrpto bros
Comment from : joeylantis22

Excellent
Comment from : Programmer

very less informative given 10 minute video Pls try getting into more technical depth
Comment from : Ashutosh Ganguly

please continue to be straight to the pointthank u so much we need people like u on you tube not this other people who talk a lot about nothing important in particular
Comment from : Eng Danson

Ok good bye !
Comment from : -]Na[-NoMaD

Simple yet informative, nicely done I took away a lot from this video thanks Forrest 🫡
Comment from : Sean Gray

Man you just enlightened my mind I've been looking for this kind of explanation for a long long time I suggest add more visual animations on every explanation some of begginer coders learn from visual like me And some of us don't understand english
Comment from : Jan Jan

In serverless architecture do the fubctions have a shared database?
Comment from : Mayukhee Das

this is so amazing, you've earned my subscription & many more views to come
Comment from : Son Nguyen Hoang

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
Comment from : ConquerJS

I fucking loved that outro
Comment from : Gena

Dude I have the worst attention span but this video is great, so much information in so little time No time wasting Subscribed
Comment from : JP G

This was a great intro, thank you so much
Comment from : Morton Fizzback

🙌💯✨
Comment from : LifeExplorer

Goodbye 👁👄👁 👩‍💻
Comment from : Semii

I liked 👍and subscribed 🔔
Comment from : West Palmera

woow love this guy
Comment from : Salah Eddine

In the serverless architecture, why is it easier to keep the "validate customer" logic on an AWS Lambda function than within the microservice itself? I know you're only charged when Lambda executes the function, but what's the value in breaking out that function in this example? Does it prevent the code base of the microservice from getting weighed down? Thanks!
Comment from : SaaS Savvy

Good Bye! Perfect!
Comment from : Jordan Garcia

[^_^]
Comment from : josedavidpc310

Love your videos man Keep up the great work!!
Comment from : Andrew McFarlane

Awesome thanks bro for explaining
Comment from : R R

That ending was epic goodbye 😂
Comment from : Buddha Nag

God tier outro
Comment from : Nick Mothershed

this video is a piece of art thank you
Comment from : Akshat Ramanathan

This is a GREAT explanation for beginners!
Comment from : Darren Finch

The ending XD
Comment from : Suleiman Zhukov

Hi how can I contact you for a project
Comment from : Sam TLT

Love your content! I wouldn't have started my own Tech Youtube channel if it wasn't for finding yours Can't wait for your future content!
Comment from : Felix C Programs