How to Scale Web Applications

👨‍💻 Learn Test-Driven Development with Laravel!
tddwithlaravel...
Sign up to 30 Days of Laravel 👉🏻 30daysoflarave...
👨‍💻 Sign up to my newsletter and receive PHP, JS and Laravel news in a weekly-basis:
subscribe.mate...
🎉 Party up:
/ mateusjatenee
/ mateusjatenee
/ mateusguimaraes
Thanks for watching!

[@marioniko4714]

great vid, people need to realize this is the kind of stuff that matters when talking about scale, not just the req/sec your js framework can handle.

Ty!

[@kurshadqaya1684]

Wow. It is first time I see something like that. It is unique. Everybody talks about microservices and blah blah. But before switching to microservices, very few people talk. Good for you!

Yup! Glad you liked it.

[@TonyMessias]

Great video! One thing worth mention is that the model will likely change when we're switching from a sync vs. async approach. For instance, the Order approach, if it was sync, we could create the Order model only after the credit card processing succeeded (or maybe just commit the transaction then). But if you're going *async*, you'd probably need to create a *pending Order* that would be sent to the ProcessOrder job, which would run in background, and would update the Order and notify the customer afterward... something like that. So, going from sync to async (and vice versa, I guess) causes domain changes too.

100%! Error handling would massively change too. Appreciate the comment dude. Thanks for adding some info!

[@cwell549]

Great video! How would you use docker to containerize something like this?

Thanks! I’d just set up individual containers for each service. In production, caching/DB would likely be managed, so one less thing to worry about. 👍

[@MT87840]

Great video, go ahead Mateus!

Thank you!