Darren Broemmer

You know, like an EC2 instance probably takes like between 30 and 60 seconds to start up. Whereas a container, let's say, let's round it off to a second. So you can scale those up and down really quickly and you can pack a lot more onto a physical cluster as well. So I don't know if that would be as much of an issue, but on the complexity front, I agree.

You know, like an EC2 instance probably takes like between 30 and 60 seconds to start up. Whereas a container, let's say, let's round it off to a second. So you can scale those up and down really quickly and you can pack a lot more onto a physical cluster as well. So I don't know if that would be as much of an issue, but on the complexity front, I agree.

There's some point where it becomes unmanageable. Yeah.

There's some point where it becomes unmanageable. Yeah.

Yeah, unless your databases are of pretty decent size, I would probably go the route you mentioned where if you're talking AWS, you have an RDS database and you can put multiple, not instances, multiple schemas on there, right? So at least you can segregate it that way. You know, if...

Yeah, unless your databases are of pretty decent size, I would probably go the route you mentioned where if you're talking AWS, you have an RDS database and you can put multiple, not instances, multiple schemas on there, right? So at least you can segregate it that way. You know, if...

Many of these microservices, if they have a smaller footprint, there's no real reason to have a different physical instance. You don't need to take that separation to the nth degree. Not to be too salesy, but the company, Engine Yard, also has a ScaleArc product, which is a database proxy, which is also a nice way to... actually get the three-tier architecture independence.

Many of these microservices, if they have a smaller footprint, there's no real reason to have a different physical instance. You don't need to take that separation to the nth degree. Not to be too salesy, but the company, Engine Yard, also has a ScaleArc product, which is a database proxy, which is also a nice way to... actually get the three-tier architecture independence.

Actually separate out your application tier from your database by connecting to the proxy, and then it can talk to all of these other databases, make them look like different connections, do intelligent caching and security controls for you. Again, if you get into larger number of databases, that might be something that's helpful.

Actually separate out your application tier from your database by connecting to the proxy, and then it can talk to all of these other databases, make them look like different connections, do intelligent caching and security controls for you. Again, if you get into larger number of databases, that might be something that's helpful.

But yeah, packing multiple database schemas on the same RDS cluster is actually pretty good strategy in a lot of cases, unless you have a really high volume or a really large size database.

But yeah, packing multiple database schemas on the same RDS cluster is actually pretty good strategy in a lot of cases, unless you have a really high volume or a really large size database.

Absolutely. So yeah, those two things that we've been talking about, the microservices and the containers, are most certainly independent. So like you were just saying, even with beautiful monolith, containers give you a lot of benefit. They give you this really fast scalability that you just talked about.

Absolutely. So yeah, those two things that we've been talking about, the microservices and the containers, are most certainly independent. So like you were just saying, even with beautiful monolith, containers give you a lot of benefit. They give you this really fast scalability that you just talked about.

And something we haven't even mentioned yet, it's actually pretty nice for development as well. So developing with containers is

And something we haven't even mentioned yet, it's actually pretty nice for development as well. So developing with containers is

really helps cut down on you know how many times how much time in my career have i spent getting my workstation my development environment set up the way that i want it and you know managing those things so using containers for development is really nice for that there's also some really nice tooling to help out there as well so We offer Dev Spaces.

really helps cut down on you know how many times how much time in my career have i spent getting my workstation my development environment set up the way that i want it and you know managing those things so using containers for development is really nice for that there's also some really nice tooling to help out there as well so We offer Dev Spaces.

There's also an open source Gitpod where you can, with a single click, bring up the online IDE. It's running based on the container that you define, and you can also do some simple automation. So for example, you can have it on startup, do your bundle install, start your rail server, it opens up a preview window inside of your online IDE, which is based roughly on VS Code.

There's also an open source Gitpod where you can, with a single click, bring up the online IDE. It's running based on the container that you define, and you can also do some simple automation. So for example, you can have it on startup, do your bundle install, start your rail server, it opens up a preview window inside of your online IDE, which is based roughly on VS Code.