One of my big takeaways from this week was the "cattle, not pets" approach to compute resources. It encourages using and configuring servers and containers as easily replaceable units. It aligns with the containerization of test infrastructure that I've seen in industry. Powerful hardware can run multiple instances of isolated containers to make good use of performance advancements. What struck me most is that this isn't just an infrastructure choice — it forces software itself to be written differently, avoiding local state and hardcoded dependencies so any instance can be killed and replaced without issue. I am still learning about docker and its uses but I expect that I'll get more exposure to serverless architectures. I also think the practical implications of scaling to zero are interesting. I'll be reading more about it.
Subscribe to:
Post Comments (Atom)
CST438: Week 7 (Week 82)
One of the differences between Agile and Waterfall software development cycles is that the Agile is more flexible while Waterfall tends to b...
-
This week I learned that React is really powerful for building interactive web UIs. It ties state directly to what shows up on screen. Until...
-
This week we covered merge sort and though we didn't have a programming assignment I took some time to explore it. I watched some video...
-
What did I expect that a course in Software Engineering would cover? I figured that it would cover the design, development, validation, and ...
No comments:
Post a Comment