Everything You NEED to Know About WEB APP Architecture

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

That Goodbye was so sudden.....
I like it 💯
😂😂😂

Youre a legend for sharing this hosting tutorial! Ive dabbled in A2 Web Hostinng and GoDaddy, however Cloudways with TST20 coupon is the real lifesaver.

“N tier” I get it!
Like nlogn
Jeeez

Thanks FK, well explained for non-IT ppl

Forrest, where did you get that Keyboard? What is it?

Great video

this is gold thanks mate

Not only the new shirt but the cup was also replaced by a bottle

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

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:)

How many times you gonna adjust your sleeves during the video? lol

The ending is like a console app lol

I didnt understand anything at the introduction, but decided to bear with u a moment and it paid off well!

Jesse? so you're being a developer now?

I was hooked and then bye bye😂😂😂😂

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

"All these problems can be solved with mocroservices!" If you say so

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

Thanks ! ❤❤❤

Nice ending

Thanks for sharing ForrestKnight! This is helpful: "Microservice architecture - A collection of services, that each serves a unique responsibility."

I get the feeling this is the type of dude who can accomplish everything I'm trying to do

LOL the goodbye at the end killed me

Meanwhile some of Microsoft and other tech giants most profitable applications live in a mono repo

thank you :)

So if I wanted to create my own bluetooth app for just my phone, I would have to make a server & address first. Then code the device to use the server I created?

Great explanation, no gimmicks. Very much appreciated 👍

Superb explanation, thank you for the video.

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.

w t h how you end it like that..... great video though

Wasted 11 minutes

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!

30% of the video is about promo! what a low quality channel

Amazing video, thank you

Thank you.

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.

The jetbrains ad was too long

Great one! Now do monorepo and micro frontends.

Use erlang

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.?

Thanks.

Very well articulated and to the point. Thank you

Wonderful job here❤❤

it look like all the WEP APP Architecture build on monolith?