Andrés
@andalm
Let the technical be tangible, free of any mystical aura ✨
Andrés
github.com
MEN WEREN’T REALLY THE ENEMY— THEY WERE FELLOW VICTIMS SUFFERING FROM AN OUTMODED MASCULINE MYSTIQUE THAT MADE THEM FEEL UNNECESSARILY INADEQUATE WHEN THERE WERE
Neil Strauss • The Game
Replication lag occurs when there is a delay between a write operation being executed on the primary (leader) node and the same operation being replicated to the secondary (follower) nodes.
Replication lag is a basic issue in leader-based replication systems that are made for better availability, scalability, and faster response times by spreading out read operations across replicas in different locations.
This led to a virtuous cycle: as more companies adopt Terraform, more developers start using it; those developers contribute to Terraform, fixing bugs, improving security, adding new features, creating new tools and extensions, etc.; that makes Terraform even more compelling, so even more companies adopt it, and the cycle continues. As a result,... See more
Yevgeniy Brikman • The future of Terraform must be open
GitHub - eon01/awesome-chatgpt: 🧠 A curated list of awesome ChatGPT resources, including libraries, SDKs, APIs, and more. 🌟 Please consider supporting this project by giving it a star.
github.com
Why is AWS losing market share to Microsoft and Google? Probably because cloud cost optimisation and shift towards new type of workloads is hitting the biggest player the most.
Around 40-50% of AWS revenue comes from EC2, the most basic compute offering. This is a higher share than for Azure and GCP. Computing is the easiest cost to optimize, therefore hurting AWS the most. Google Cloud with focus on Data/AI has been consistently taking the market share from AWS/Azure and will soon have 20% of the Cloud market.
The interesting function therefore is the red line, the one that adds the up-front invest to the potential liability. That's your total cost and the thing you should be minimizing. In most cases, with increasing up-front invest, you'll move towards an optimum range. Additional investment into reducing lock-in actually leads to higher total cost. The reason is simple: the returns on investment diminish, especially for switches that carry a small probability. If we make our architecture ever-so-flexible, we are likely stuck in this zone of over-investment. The Yagni (you ain't gonna need it) folks may aim for the other end of the spectrum - as so often, the trick is to find the happy medium.