Darren Broemmer

Yeah. So there's a number of solutions here. I think one nice way to start is just to And here's where an abstraction does actually benefit you because you can put a facade in front of your service. And so maybe you start out with just actually just calling inline. You're just calling the class directly in your same Ruby process.

Yeah. So there's a number of solutions here. I think one nice way to start is just to And here's where an abstraction does actually benefit you because you can put a facade in front of your service. And so maybe you start out with just actually just calling inline. You're just calling the class directly in your same Ruby process.

But then that positions you so that when you do move it out to a service, you can swap that out and it's less of a problem. In terms of the domains, I personally like having the different subdomains Part of that, I guess, the product that I work with, EngineR, facilitates this pretty nicely where each of your apps within the same application just get different subdomains.

But then that positions you so that when you do move it out to a service, you can swap that out and it's less of a problem. In terms of the domains, I personally like having the different subdomains Part of that, I guess, the product that I work with, EngineR, facilitates this pretty nicely where each of your apps within the same application just get different subdomains.

But there's obviously different ways that you can do it. And you don't actually, you know, of course, you don't need to split that out because you could just use different URL paths to accomplish a similar goal. But if you get it into containers and you can segregate, then you get those benefits of the physical deployment also. So to me, I prefer to try to keep it simple.

But there's obviously different ways that you can do it. And you don't actually, you know, of course, you don't need to split that out because you could just use different URL paths to accomplish a similar goal. But if you get it into containers and you can segregate, then you get those benefits of the physical deployment also. So to me, I prefer to try to keep it simple.

Certainly, there's a couple different choices there. I mean, I would probably, if you can avoid... Putting messaging layers in between. If you can keep it simple, rest calls, unless you need to do something different, I probably would advocate for that. Keep it as simple as possible, but no simpler. But there's also other tools and frameworks that help you do that.

Certainly, there's a couple different choices there. I mean, I would probably, if you can avoid... Putting messaging layers in between. If you can keep it simple, rest calls, unless you need to do something different, I probably would advocate for that. Keep it as simple as possible, but no simpler. But there's also other tools and frameworks that help you do that.

I haven't worked with it in detail. AWS has Service Mesh, which helps you orchestrate all of these microservices. So there are things out there that will help you manage all of this. And probably those are worth it if you really get into large numbers.

I haven't worked with it in detail. AWS has Service Mesh, which helps you orchestrate all of these microservices. So there are things out there that will help you manage all of this. And probably those are worth it if you really get into large numbers.

If your enterprise is truly bought in and you're going across many different departments and many different organizations, that's probably when you look at something like that.

If your enterprise is truly bought in and you're going across many different departments and many different organizations, that's probably when you look at something like that.

Yeah, I had a similar reaction that Chuck had. If we get into the thousands, I'm completely with you. We've probably gone off the rails at that point.

Yeah, I had a similar reaction that Chuck had. If we get into the thousands, I'm completely with you. We've probably gone off the rails at that point.

I believe that's probably correct. I actually got to work with them a little bit when I was at AWS. They also are a bit of a snowflake because, I mean, there are very few companies or organizations that have the amount of resources that they have. Companies like Netflix, like Amazon, You know, there aren't very many folks that can put that many resources on it.

I believe that's probably correct. I actually got to work with them a little bit when I was at AWS. They also are a bit of a snowflake because, I mean, there are very few companies or organizations that have the amount of resources that they have. Companies like Netflix, like Amazon, You know, there aren't very many folks that can put that many resources on it.

And they have a vast amount of capability as well. I think for small and medium-sized business, you're looking at a different category and a different type of architecture. And it would probably not be good if you got into those numbers. I will say on the infrastructure cost point that you brought up, I think that would be true on... if you're on instances or virtual machines.

And they have a vast amount of capability as well. I think for small and medium-sized business, you're looking at a different category and a different type of architecture. And it would probably not be good if you got into those numbers. I will say on the infrastructure cost point that you brought up, I think that would be true on... if you're on instances or virtual machines.

However, containers are very efficient at this. You can put a lot more container processes on the underlying hardware, and you also get a lot of those other benefits that I mentioned. So I don't know that the infrastructure cost would be quite as bad as you think it is because the container processes are pretty lightweight. They can start up in milliseconds as opposed to...

However, containers are very efficient at this. You can put a lot more container processes on the underlying hardware, and you also get a lot of those other benefits that I mentioned. So I don't know that the infrastructure cost would be quite as bad as you think it is because the container processes are pretty lightweight. They can start up in milliseconds as opposed to...