Since that was asked in the Kubernetes topic, I would recommend you to take a look at the management of Kubernetes services from the public providers (AKS from Azure, EKS from AWS, GKE from Google, Kubernetes Linode, IBM Kubernetes, etc.). For micro-services in the…
This is a pretty wide topic. Basically, we need this to be able to track changes (when it was changed, who did this and what actually was updated). Also, it brings such things as repeatability and automation to decrease the possibility of typos and misconfiguration.
I think you need to look for
1. Unifications. All aspects of the monitoring should be done by one or multiple tools. As an option, integration between tools should be possible.
2. Plug-in based or open architecture. Open Source will be a huge plus. In this case, you will…
Mainly, VMs are more "heavy" way (in terms of size, startup time and support), while containers are more "lightweight" and modern technology. But VMs could handle some scenarios that containers could not support. Also, VMs are theoretically more secured, because they provide…
Some recommendations
1. Be ready for the steep learning curve.
2. Use best practices in Terraform - try to keep Terraform and provider versions always updated, use modules, use remote state, use state locking.
3. Use only one method of managing infrastructure - don't mix…
Cloud agnostic approach (you can't reuse most of the code - resources are provider-specific, but you can use Terraform for interactions with various clouds), automation, modules re-usability, infrastructure as a code approach.
There are a set of open questions and decisions to prefer one or another cloud, just a few of that
1. Region availability (to store sensitive data like payments or PHI data locally) - both providers have a set of not overlapping regions.
2. Specific services - both…
