Відео

Very nice introduction to the world of MACH.

hey thanks for the video - I would just give you a piece of advice, music while you're speaking and drawing graphs seriously impedements learning. Hope that helps and thanks for your very clear explanation :)

PWA already dead and lost it is google supprort...

Nicely presented - thank you John!

Great explanation! music playing in the video makes it hard to hear sometimes :(

I need a web developer

Best video i have seen, love this please do more and keep the analogies going! thank you

I agree with you, but you are also kind of wrong only due to why software architects ROYALY mess up about MSA: chopping up APIs by entity. Architects don't tend to make the same mistakes with other applications. If its a website, then those will be logically split by.. by what the website IS. If its a batch application, then the batch had to be named something. It has a purpose. It has BOUNDARIES inherent in it's application description. APIs don't necessarily have those boundaries and thus are the primary painpoint in MSA: how to define the boundaries of an API. When you have the goal to have microservices, but don't have multiple logical API boundaries, architects all seem to make the titanic mistake of separating a perfectly cohesive API by Entity, like a UserService, AccountService, SubscriptionService, etc. These might just be database tables and the architect decides that each table needs it's own service. And even if you can define an API's boundary CAN you separate them, or is there something tightly coupling them? If that is going to be a problem to decouple them, do you really NEED to? But when the goal is to have microservices, and you don't yet have a justification for more than one API, people foolishly choose to define boundaries around silly things. A website can be a single application with well defined boundaries, but it somehow needs to call 30 different APIs all defined around a single entity each....

I love the way you explained that. !

Your videos are amazing. I like it but your video has the same problem I am a new subscriber to your channel. Can I talk with you? You'd be glad that just now I’ve liked your UA-cam Channel. Cos, your content was really awesome. But unfortunately, there are not much views and subscribers. I noticed that your video SEO score is too weak according to your needs. Because of that, your video is not reaching your target audience. You will be glad to hear that I can help you increase your SEO score so that it is top on the first page of UA-cam which will increase your subscribers and views organically.

Hernandez John Hall Melissa Walker Jose

Great explaination!

Taylor Mark Young Richard Perez Gary

Data centers r replaced by Cloud services. Cloud native.

Thanks so much.. I found it helpful

great presentation

Nice

Liked! Thank you so much

Thank you for the thorough explanation!

Thank you for the clear explanation. Your help is much appreciated!

Characteristics: Discoverable Installable Linkable Network independent - can work offline Progressively enhanced Re-engageable - push notification or updates Responsively Designed Secure - HTTPS Enablers: Manifest file Service worker Https Core architecture

Thank you, this is very valuebale content and differenciate.

Permanent liver damage because I took a shot every time this guy said PeeDoubleA

Natives apps sound good at first glance but they are just a way for putting odorless odorless shit in Your device. Performance, Support & Even long term mantienability those are quirks of HTML they are mature and work fine out of the box. On the otherside there is Flutter and React Natives. Lack of Support. Everything You See can stop working on weeks leaving along performance and stability. Wish makes me wonder how mucho of a diferencia is between those programmers and this ones fron today. It's plain view for how business shit on everything that means to be honestly good.

I've removed many apps to replace them with pwas. The best one I've seen is xbox's cloud gaming system, which is almost 100% interchangeable between native and web. Another really good one is Audible.

Pee Double You Eh? Nice video man! ♥

If you’re in B2B, PWA makes way more sense. For consoomers, native seems better, but I would also do a PWA for those who don’t want to deal with the BS of getting the app, updating it, etc..

great video

very well explained

Loved it!

Nice explanation

Maybe just maybe If PWA's are able to catch up with Native apps. Hopefully, FirefoxOS can try to relaunch again

To be honest I use both. I only use Native apps when offline when need to

thank you

I feel so happy when I come searching for some boring stuff e and get IRON MAIDEN somehow!!!! UP THE IRONS!!!

beautifully explained, thank you

okok

Pros of native app is that millions of users can use it all together at once without worrying about internet bandwidth. While PWA requires powerful server for hosting if the creator expects millions of users.

Don't quite see the benefits described here in terms of reducing complexity, because you haven't really reduced the overall complexity as such, you've just moved it out of the front end. But you still have to do all the mapping and aggregation of multiple calls in the BFF. The real advantage is separation of concerns -- all that complexity (aggregating and mapping data from multiple services) is isolated into its own service.

Piii-dabbllyu-eeh

Wow, that's a really great explanation!

It was an interesting review, your 9 points framework show great insights about each technology, great job.

i was polling entire youtube to finally find this simple one. You need webhooks to tell us back.

Stop using PeeDoubleEEE say peweea much shortener )

The analogy at beginning was amazing. Thank you!

Thank you very much.

Still don't see the point of this. From your explanation, what I can get is that the bff acts like a mapper between the client and api, you said it helps separating different frontend clients concerns but still I can do that without bff. Sounds like a fancy term, to augment the complexity of applications where the tradeOff for that is pretty small (higher frontend costs, higher latency, because of batching) vs (a mapper / adapter, that by the way could be contained in the frontend itself, if the only reason for its existance is mapping values, and also you get a smaller bundle size maybe.

So instead of an external program requesting information at regular intervals, the web hook exists internally and upon a condition send that information to the external system for greater efficiency. Correct?

👻 👽

P-W-Eh! 😜