I have a terraform setup right now but it’s super awkward and very slow. The goal is to be able to define settings using PKL which looks super interesting. Wanted to try it out for a while now.
So if I am understanding this correctly the challenges of setting up a secure linux VM and a container are more or less the same?
The point about multi-tenancy is absolutely understandable. Isn't this an old story from the PHP world with multi-tenancy? I think a good generalization is: don't run on multi-tenant systems if you do anything (!) critical (e.g. authentication or payments)?
But that of course disregards the fact that when people _can_ do something, they _will_ do it even though they shouldn't (like running E-Commerce systems in multi-tenant environments).
Another thought regarding isolation: aren't VMs essentially just running on one host as well? Is that why you said "VMs are _more_ isolated"?
Were they really that significantly more secure? You still needed to do regular maintenance on the underlying image, etc. Same with Docker. The only big difference I see is that yes, breaking out of a container is easier than out of a VM. But are there any other significant vectors I should be aware of?
IMHO personal growth of the founders/leaders is correlated with long-term success. A healthy organization should be able to adapt to changes in the market. The same is true for a healthy individual. And more importantly as leader(s) of an organization - because you must lead by example. E.g. if you have a healthy way to keep your ego in check or be aware of your flaws you will be able to notice issues in organizational structures; if you're willing to change when presented with new information so will the organization; if you micromanage everything you've fixed the speed of adaptation to your own - can be good - can be bad; if you need validation you will surround yourself with people that validate you no matter what; if you twist your reality so that you're always on top those lies will seep into the culture.
It's kind of like Conway's law but more like organizations design structures (communication, hierarchies, etc.) which mirror their leaders identity/character/personality/soul...
Microservices are indepently deployable modules. Thus the same principles of modular design in a monolith apply. So, yes, you're correct with the network part.
We create digital products for a diverse set of (pretty large) customers (automotive, logistics & banking). We strongly believe that technology should make lives easier. That is why we employ cross-functional teams and focus on short feedback loops and user experience.
Now we are looking for a DevOps engineer to support one of our big client projects that is used by a lot of people daily.
Instead of predicting what will (not) happen these were some of the challenges of the last six months:
* advise the teams during the introduction of resource requests & limits
* supporting the decision of resizing the Kubernetes clusters on the requirements and factoring in operational cost
* integrating Azure KeyVault & EventHub into our backend services
* introduce Ansible to provision virtual machines
* introduce PostgreSQL monitoring and support a resizing decision
* analyze and research an issue with a Docker update
Our working language is German. All levels of proficiency are welcome!
My take on it is that it boils down to the profession being so young. Since it's so young we have a lot of young developers ( < 10 years experience). Programming is an inherently complex task [0]. Couple that with Not-Invented-Here and favoritism of barely working solutions (meaning by businesses: [1]) and as a result you get extremely fluctuating stacks. Every piece of code written by others was never written with care [2] - that is the assumption at least because more often that not it's true. Everyone in their own right thinks that only their code works well and has some special properties but in the end you face the exact same problems: problems of design rather than implementation.
[1] https://www.cs.utexas.edu/users/EWD/transcriptions/EWD10xx/E...: the business community, which, having been sold to the idea that computers would make life easier, is mentally unprepared to accept that they only solve the easier problems at the price of creating much harder ones
Actually I don't think there will be more breaking changes than there were in the past due to the new release cadence. Mark Reinhold gave a great talk about the values they try to follow when moving the platform forward: https://m.youtube.com/watch?v=HpbchS5kmio
This applies to the new release cadence as well. But time will tell if they will achieve their goals.
I have a terraform setup right now but it’s super awkward and very slow. The goal is to be able to define settings using PKL which looks super interesting. Wanted to try it out for a while now.