Andrés
@andalm
Let the technical be tangible, free of any mystical aura ✨
Andrés
github.com
To some extent, we understand what led HashiCorp in this direction. They are trying to maintain a delicate balance: on the one hand, they are creating amazing value by providing high quality, free, open source software to a community of thousands of developers; on the other hand, they are trying to run a sustainable business, so they need to... See more
Yevgeniy Brikman • The future of Terraform must be open
In Elasticsearch, these partitions are known as shards . Each node of the Elasticsearch cluster can serve queries independently for the partition it manages, thereby increasing query throughput.
Improving query performance in ElasticSearch at scale
Therefore, we have joined forces with a number of other companies to create the OpenTF manifesto. The goal of the manifesto is to ensure Terraform remains truly open source — always.
To this end, the manifesto lays out the following two-step plan:
To this end, the manifesto lays out the following two-step plan:
- Ask HashiCorp to switch Terraform back to open source. The manifesto is a public request—a petition
Yevgeniy Brikman • The future of Terraform must be open
#dataengineering #softwarearchitecture #datascience #cloudcomputing #bigdata #datalake #datawarehouse #datamesh #streamprocessing #techleadership #ingenieriadedatos #arquitecturadesoftware… | Christian Acevedo
linkedin.com
The matrix differentiates between the cost of making the switch from the likelihood that you'll have (or want) to make the switch. Things that have a low likelihood and a low cost shouldn't bother you much while the opposite end, the ones with high switching cost and a high chance of switch, are no good and should be addressed. On the other diagonal, you are taking your chances on those options that will cost you, but are unlikely to occur - that's where you'll want to buy some insurance, for example by limiting the scope of change or by padding your maintenance budget. You could also accept the risk - how often would you really need to migrate off Oracle onto DB2, or vice versa? Lastly, if switches are likely but cheap, you achieved agility - you embrace change and designed your system for low cost of executing it. Oddly, this quadrant often gets less attention than the top left despite many small changes adding up quickly. That's our poor decision making at work: the unlikely drama gets more attention because what if!
