If we attentively look at IT industry at 2017, all of us will see “containers” and “Docker” as the top buzzwords ever. We started to package developed software in Docker containers in every field. We’re using containers everywhere. From small startups to huge microservices platforms. From CI platform to Raspberry Pi ARM-targeted research. From database management systems to….
The word we say almost everything and everywhere. The question we have to double check when implementing new feature. It’s a kind of work allows to sleep calmly. Yes, this is security.
Database question is probably must have the most reliable answer in all service questions. The more you ensured what to use and how to maintain – the more fast and reliable your system will be.
I`d compare backups with meditation on human body. You don’t actually see the benefits, but in long term backups keep you healthy. Because they verify your infrastructure have reserve sources. Meditation helps to overcome the hardest moments of your life throwing out dirty thoughts. The clear backup similarly helps engineer to go through some kind of disasters. Even disasters we couldn’t guess before it was happened.
It’s easy to manage Amazon solutions which don’t require any special operations skill. Set load balancer, speed up content delivery with Cloudfront, store enormous amounts of data in S3 in 2 clicks. But what if we wish to get into the bottom about idea how do they all work? Do they work right in our case?
Disclaimer: this is my cosplay on charity.wtf post based only on my personal experience.
Keep going with infrastructure improvement, I stayed some time on monitoring issue. Generally monitoring is inseparable component of DevOps workflow. It allows to clearly control each subject of maintained service.
Monitoring work is interesting as well as complicated. This field, like database, doesn’t have ready solutions for any kind of project. For each situation you have to figure out what metrics are special and what graphs you must check at first.
