I really like that you mentioned Modular Monoliths and how to build them. Also the architecture test, they're are really underrated nowadays. They are pretty easy and fast to write, and you can copy-past them from project to project. Such important things you showed in this video, deserve to be in one of your courses! P.S.: I really like that the quality of your videos increases overtime. A good addition is the "table of contents" of the video, I really like it. Also, check your microphone, there is some background noise (ultrasound) at the beginning of the video.
That’s a good idea with the courses actually, I’ll probably revisit a couple of them this year at some point, I’ll add that to my notes. Noted on the mic, thanks.
Hi James, First, I want to thank you for your efforts-I really enjoy your videos! Second, I have a few questions, please. You mentioned that Azure ACR is serverless. Could you clarify what you mean exactly? You defined things like memory, etc., so how is it serverless? Could you explain that a bit more? Also, don’t you think it’s time to create a course on Dometrain for something like Cloudflare? 🤣
Great question. So the way I think about serverless is less about functions (Lambda, Azure Functions) and more about 'deploying my application with as little operational overhead as possible'. If I deploy a containerized applications to Azure Container Apps, as a developer all I care about is setting the memory and CPU and Azure handles the rest. As a developer, I don't need to care about the infra. Serverless purists would say serverless must scale to zero, which ACA can do as well to be fair. But I think about it more from the perspective of complexity/operational overhead. LOL, if Cloudflare had .NET support I definitely would.
Hey James! First of all, thank you for your great videos, I learned a LOT from them already. I do have one question regarding the arch testing: how does it compare to constraints set with things like NX?
@@serverlessjames Sorry, working with specific environments sometimes makes you forget not everyone may be familiar with the toolset :). I am talking about the NX Monorepo manager/build tool (nx.dev). It was meant to help manage monorepos, and has nice tools such as mentioned constraints (or Module Boundaries as they call it in docs). Their solution works based on linter, and working with it previously I was wondering how do both of those solutions compare. Obviously, introducing entire monorepo manager just for the sake of maintaining module boundaries does not make much sense, but aside of that might have some pros and cons compared to one another.
@@Buslowicz Ahh ok. In a typical monorepo you'd have multiple microservices inside the same repo... so if I understand correctly you'd use a tool like NX to enforce the microservice boundaries. But then you could use architecture tests inside a specific microservice to enforce how you want a specific service to be architected. I think they would work well together. NX == service boundaries ArchTest == code structure inside a service
Beautiful speech!
I really like that you mentioned Modular Monoliths and how to build them. Also the architecture test, they're are really underrated nowadays. They are pretty easy and fast to write, and you can copy-past them from project to project.
Such important things you showed in this video, deserve to be in one of your courses!
P.S.: I really like that the quality of your videos increases overtime. A good addition is the "table of contents" of the video, I really like it.
Also, check your microphone, there is some background noise (ultrasound) at the beginning of the video.
That’s a good idea with the courses actually, I’ll probably revisit a couple of them this year at some point, I’ll add that to my notes.
Noted on the mic, thanks.
@serverlessjames Great!
yes
Hi James,
First, I want to thank you for your efforts-I really enjoy your videos!
Second, I have a few questions, please. You mentioned that Azure ACR is serverless. Could you clarify what you mean exactly? You defined things like memory, etc., so how is it serverless? Could you explain that a bit more?
Also, don’t you think it’s time to create a course on Dometrain for something like Cloudflare? 🤣
Great question. So the way I think about serverless is less about functions (Lambda, Azure Functions) and more about 'deploying my application with as little operational overhead as possible'. If I deploy a containerized applications to Azure Container Apps, as a developer all I care about is setting the memory and CPU and Azure handles the rest. As a developer, I don't need to care about the infra.
Serverless purists would say serverless must scale to zero, which ACA can do as well to be fair. But I think about it more from the perspective of complexity/operational overhead.
LOL, if Cloudflare had .NET support I definitely would.
This might help actually - ruclips.net/video/ZKS4Oy3pMHc/видео.html
@@serverlessjames thank you bro
Hey James! First of all, thank you for your great videos, I learned a LOT from them already. I do have one question regarding the arch testing: how does it compare to constraints set with things like NX?
Thanks for the comment. What do you mean by NX sorry?
@@serverlessjames Sorry, working with specific environments sometimes makes you forget not everyone may be familiar with the toolset :). I am talking about the NX Monorepo manager/build tool (nx.dev). It was meant to help manage monorepos, and has nice tools such as mentioned constraints (or Module Boundaries as they call it in docs). Their solution works based on linter, and working with it previously I was wondering how do both of those solutions compare. Obviously, introducing entire monorepo manager just for the sake of maintaining module boundaries does not make much sense, but aside of that might have some pros and cons compared to one another.
@@Buslowicz Ahh ok. In a typical monorepo you'd have multiple microservices inside the same repo... so if I understand correctly you'd use a tool like NX to enforce the microservice boundaries. But then you could use architecture tests inside a specific microservice to enforce how you want a specific service to be architected. I think they would work well together.
NX == service boundaries
ArchTest == code structure inside a service
@@serverlessjames hmm interesting approach, I might need to try that :). Thank you!