วีดีโอ

Since I'm unfamiliar with the GCP services and cloud infra - It's hard to understand what each service does in the video. It might be helpful to explain the purpose of each cloud service.

Excited to see where this goes :D

...and I'd recommend some eye drops, your eyes seem like they are either dried and a bit bloodshot from watching the screens for so long, or you smoked a doobie. Great advice, thank you!

Your channel randomly popped up on my recommended feed. I love the idea, the videos are great and I'll definitely watch more!😄Keep it up

Hey There, love your content ❤ I have an idea/suggestion, how do i contact you ?

100% agreed, good communication is the most important skill to have as a software developer.

GREAT JOB!

Thank God I found this mine of gold

Subscribed to the channel. I am going to take this challenge from today. Hopefully I will be able to catch up with your pace.

Just because you load balance requests to replicated monolith, it doesn't suddenly become equivalent to micro-services based application. It doesn't have to worry about network partition, graceful degradation, data denormalization and about a thousand of other things. If you think that micro-services are a solution to a technical issue you are wrong. They were invented to solve scaling of organizations. And since it's a technical solution to a human issue, they fail by definition. But of course, you can throw 200 engineers into a problem and eventually they'll manage to make it work. For any small company that's not ready to create a plethora of SRE, platform engineering and ops teams , going full micro-service based approach is a suicide.

helpful😊

bruh love form india

Why not use a hybrid model? If a module is taking too many resources, that module can be separated and used as a microservice, while other modules can be kept within a modular monolith architecture. This way, we can balance scalability and performance, ensuring that resource-intensive components are isolated for independent scaling, while simpler or less demanding parts of the application remain in the monolith for easier management. This approach combines the best of both worlds, reducing complexity and avoiding unnecessary overhead, while enabling flexibility for future scaling and system evolution.

Microservices are a scam

I always wonder how joins work with M/Services Let's say users service and Billing/Blogs and the fact that you can use Mongo for users and PG for other services. Assuming blog also has comments how do you handle joins and the F_key constraints I see a lot of network requests. Until I understand this I still believe small scale apps should be monoliths

Thus, the Modular Monolith is not a scam. Perfect. Thanks for a clickbatey title! The point behind the Modular Monolith is to start with it first, extracting parts into separate services along the way only when it's necessary. And it is not always necessary, per se, so you might not end up with a full-blown microservices zoo when following this path. And this is awesome, since usually you do not need to have everything distributed and eventually consistent since day 1. P.S. In Clojure (and some Python) we tend to use a so-called Polylith architecture for large multi-service projects. It's a glorified Modular Monolith with all the benefits of a monorepo and handy tooling for things like workspace consistency checks and incremental testing. You'll lose all or some of these, if you start building it another way around, splitting everything on all architectural levels (static source code, logical/functional components, deployment).

invest to a mic that reduce background echo - < just an advice