Do you know what it really takes to put your code in production?
Software deployment and orchestration is too much about abstraction and "black boxes". But I've always liked having full ownership of my code, so I'm on a mission to uncover these boxes.
I'm building my homelab to try out and learn industry-grade infrastructure practices. But what equipment should I start with? Here's what I found out.
There are so many homelab possibilities, with so many different levels of experimentation intended.
>Software deployment and orchestration is too much about abstraction and "black boxes".
So true, what are the alternatives, and how do you know if they are any good without trying them out?
OTOH, some (usually dangerous) things are often advised "don't try this at home" :)
Analogously I think some of the times what software pros call a "homelab" is so they can try things that might be too "dangerous" if they tried it at their employer.
>what equipment should I start with?
I think you answered your own question, "affordable" :)
I would add, so affordable that you can acquire duplicate hardware. Then while emulating a "modern" dev environment at home like you have in mind, also in parallel build a functional equivalent from the ground up based on bare metal using the duplicate hardware without black boxes at all.
Do you know what it really takes to put your code in production?
Software deployment and orchestration is too much about abstraction and "black boxes". But I've always liked having full ownership of my code, so I'm on a mission to uncover these boxes.
I'm building my homelab to try out and learn industry-grade infrastructure practices. But what equipment should I start with? Here's what I found out.
Good article.
There are so many homelab possibilities, with so many different levels of experimentation intended.
>Software deployment and orchestration is too much about abstraction and "black boxes".
So true, what are the alternatives, and how do you know if they are any good without trying them out?
OTOH, some (usually dangerous) things are often advised "don't try this at home" :)
Analogously I think some of the times what software pros call a "homelab" is so they can try things that might be too "dangerous" if they tried it at their employer.
>what equipment should I start with?
I think you answered your own question, "affordable" :)
I would add, so affordable that you can acquire duplicate hardware. Then while emulating a "modern" dev environment at home like you have in mind, also in parallel build a functional equivalent from the ground up based on bare metal using the duplicate hardware without black boxes at all.
See where those converge ;)