Å·±¦ÓéÀÖ

“...my classical values make me advocate the triplet of erudition, elegance, and courage; against modernity's phoniness, nerdiness, and philistinism...many philistines reduce my ideas to an opposition of technology when in fact I am opposing the naive blindness to it's side affects - the fragility criterion. I'd rather be unconditional about ethical and conditional about technology than the the reverse.”
― Nassim Nicholas Taleb, The Bed of Procrustes: Philosophical and Practical Aphorisms

“In December one cannot afford to be fastidious; besides, one is actually less fastidious about everything in the winter. The keen air braces soul as well as body into robustness, and the food and the perfume disliked in the summer are perfectly welcome then.”
― Elizabeth von Arnim, Elizabeth and Her German Garden

“Resilience versus Robustness.
Typically when we want to improve a system’s ability to avoid outages, handle failures gracefully when they occur and recover quickly when they happen, we often talk about resilience. (�) Robustness is the ability of a system that is able to react to expected variations, Resilience is having an organisation capable of adapting to things that have not been thought of, which could very well include creating a culture of experimentation through things like chaos engineering.
For example, we are aware a specific machine could die, so we might bring redundancy into our system by load-balancing an instance, that is an example of addressing Robustness. Resiliency is the process of an organisation preparing itself to the fact that it cannot anticipate all potential problems. An important consideration here is that microservices do not necessarily give you robustness for free, rather they open up opportunities to design a system in such a way that it can better tolerate network partitions, service outages, and the like. Just spreading your functionality over multiple separate processed and separate machines does not guarantee improved robustness, quite the contrary, it may just increase your surface area of failure.”
― Sam Newman, Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith