Configuration Management is one of the best things you can have in your infrastructure. It gives you a clear picture of what and where things would be running, it gives you the capability to involve the software design principles in your infrastructure design. But there are times where you don’t actually need CM, because they come with some overhead. For organizations, who don’t want to adopt to a full-scale CM can use something like FSS ...continue reading.
When you start building your infrastructure, your servers cross communicate with each other which brings in lot of security risk. To reduce this risk you should have some way to organize/classify your servers. The idea behind this model is to define how critical is the server from the security point of view. Hence, this level model works very well.
| Server Class | Level | Description | Example |
| Public + Subnets behind | Level 0 | Any server in our infrastructure |
This is the first of the series of blog post on building peaceful and scalable infrastructure.
Every DevOps dream is to have a stable infrastructure so that he/she can sleep peacefully without having to worry about systems going offline. From my experience if you cover up following areas in your infrastructure. You can sleep peacefully.
The better you know your components in your infrastructure, the better you can design it. There are multiple ...continue reading.