We are an agile shop. We have pair programming, continuous integration, and continuous delivery to AWS. The pipeline runs RedHat. We have also have some CentOS.
Fedora is not a bone, it is a great way to know what is coming in RHEL. CentOS (which RedHat supports) is a great server distro for everyone.
The tension is stability versus the latest tech. RedHat purposely moves very, very slowly. The same can be said about Debian stable. As an admin I like slow moving targets. The problem is that developers want to use the latest stuff. So what does RedHat do about this? I think they are trying to solve it in two ways. First is their Software Collections. These are packages that site outside the base OS and are easy to pivot to the newer version. This allows for multiple versions of things like Python to be installed in parallel. Very handy!
Another thing that is helping quite a bit is Docker. RedHat is big on Docker. By packaging containers as apps, this allows a developer to easily control the dependencies outside of the OS that the app is running on. This makes everyone happy! Fedora is tracking some interesting tooling with Docker (geard, os-tree).
I like that RedHat tries to solve bigger problems than just packing and releasing a distro. They are trying to make things manageable (see FreeIPA, OpenLMI, RDO, CloudForms, oVirt)
Personally, I like RedHat. I like Debian. I run Fedora on my desktop and notebook. I maintain a CI/CD pipeline on RedHat at work. I never jumped on the Ubuntu bandwagon. It seems to me that Ubuntu has made quite a few more mis-steps in their short existence than RedHat has over the years. I get the feeling that a lot of people are just dropping back to Debian, which is just fine with me!
Thanks for this! Both you and the previous poster explaining BGP. So many people have misconceptions on how the Internet works. Then there is the added complexity of business.
I really proves nothing that Netflix over a VPN is faster than without a VPN. We already know Verizon-Level3 peering is saturated. Both sides have admitted it. It comes down to how to solve the problem. It is not a technical problem. It is a business problem
So what if Level3 offers to pay for the upgraded link. If the existing agreement is settlement-free upgrading the link will likely push the traffic exchange outside the agreement. So if Level3 starts sending more traffic than it received from Verizon, then they should pay Verizon for transit of that traffic. Verizon has probably told them that. Level3 comes back and says, "But we'll pay for the upgraded equipment." Verizon says, "So what? If the traffic isn't equal, then you pay." And on and on it goes. So, as stated above, the best thing to do is for Netflix to create peering connections with Verizon that have no expectation of equal traffic. They will have to pay Verizon for these connections.
This is NOTHING new people. This is how the Internet has always worked.