aratno
AnyDB: An Architecture-Less DBMS for Any Workload
Experimentation Infrastructure at LinkedIn
- Use column-oriented storage for columns that are frequently scanned in analytical queries
- Automated index management, based on user-provided boundaries for write throughput, disk footprint, query latency
- Calibrated optimism for heap updates. AFAIK, current DBs are either optimistic (assume transactions are more likely to commit than rollback) and update the heap in-place, and write the old value elsewhere in case of rollback, or pessimistically write all updates in new, versioned tuples and let MVCC (and garbage collection) handle the rest. Would be interesting to see the performance improvement that could come from modeling commit / rollback outcomes and optimizing accordingly.
- Using variable-sized pages to reduce overhead for older pages, as a sort of light cold storage
Anyone know of any DBs that automatically tune these aspects?
Microservices: Architecture Nihilism in Minimalism's Clothes
The Snowflake Elastic Data Warehouse (2016) [pdf]
Latency and the Quest for Interactivity (1996) [pdf]
Technology and Courage (1996) [pdf]
Happy Eyeballs
AWS Chalice
Is there a readability metric for source code?
I’m imagining something like the Flesch-Kincaid test for source code: https://en.wikipedia.org/wiki/Flesch%E2%80%93Kincaid_readability_testsI’m assuming it would have to be language-specific.This is particularly interesting for contextualizing terse code, like Gocker shared here recently, which may have readability benefits in its brevity that is undone by use of obscure features and structure...
Some Virtualization Papers Worth Reading
The ecosystem is moving (2019) [video]
What does it mean for employees to "help implement the changes"?
What will you do if change does not happen?