d59644b96f
The full scope across this batch: POST /sessions key→token exchange, SessionStore dual-index with revoke_by_id, CLI Bearer injection (ONTOREF_TOKEN), ontoref setup --gen-keys, install scripts, daemon config form roundtrip, ADR-004/005, on+re self-description update (fully-self-described), and landing page refresh.
23 lines
1.4 KiB
Markdown
23 lines
1.4 KiB
Markdown
Why I Needed Rust: Finally, Infrastructure Automation I can sleep on
|
|
Description
|
|
|
|
In 2013, I started my journey with containers and deployment automation. I've encountered fundamental problems with infrastructure code: configuration sprawl, brittle scripts, complex state management, and deployments that fail silently in production, years of nightmares trying to solve it the wrong way.
|
|
|
|
Thanks to Rust. Now I finally sleep well.Why I Needed Rust: Finally, Infrastructure Automation I can sleep on
|
|
Description
|
|
This talk shares how.
|
|
|
|
Learn from decades of infrastructure experience:
|
|
|
|
• The evolution of infrastructure challenges (2013-2025)
|
|
• Why traditional approaches to IaC fall short at scale
|
|
• Type safety and memory safety as production reliability
|
|
• Building safe orchestration across multi-cloud and on-prem environments
|
|
• Real applications: Kubernetes, blockchain validators, disaster recovery
|
|
|
|
We'll explore concrete examples of what went wrong, why it went wrong, and how the Rust ecosystem can help solve infrastructure problems at scale.
|
|
|
|
For infrastructure engineers, SREs, platform teams, and Rust developers who've felt the pain of configuration drift, failed deployments, and infrastructure code that simply doesn't scale safely.
|
|
|
|
Suitable for: All experience levels. No advanced Rust knowledge required, this is about infrastructure problems and how Rust can help solve them.
|