Stateless tech is great fun. If it fails you rebuild it and everything is (mostly) okay again. Frontend and app tier containers, network devices, even compute hosts. There's lots of posts about these.
But state (and loss of) can be nightmarish and we mostly want to avoid it. We outsource database hosting to cloud providers, avoid touching SANs, hand-wave away schema change and rollback considerations when talking about our CI/CD pipelines.
Where are all the HN posters working on these things? I want to hear from you!
What are you working on?
If you write firmware for SAN arrays, how do you sleep at night with that sword dangling over your head?
Do you keep working on stateful tech because you love it or because it pays better?
What's the best and worst thing you've experienced?
0 comments
—
Ask HN: Where are all the stateful posters? Tell us what you're working on · HackerTrans
But state (and loss of) can be nightmarish and we mostly want to avoid it. We outsource database hosting to cloud providers, avoid touching SANs, hand-wave away schema change and rollback considerations when talking about our CI/CD pipelines.
Where are all the HN posters working on these things? I want to hear from you!
What are you working on?
If you write firmware for SAN arrays, how do you sleep at night with that sword dangling over your head?
Do you keep working on stateful tech because you love it or because it pays better?
What's the best and worst thing you've experienced?