دانلود رایگان مقاله انگلیسی درک قابلیت اطمینان نرم افزار در صورت بی ثباتی زیرساخت - IEEE 2017

Cloud computing has brought with it the utilization of off the shelf, commodity hardware that has higher failure rates than the systems that have been used in enterprises for the last several decades. Coupled with increasingly complex, highly-distributed, constantlychanging data center environments that can no longer be treated as deterministic systems, this forces us to change the way that we view the stability of that infrastructure. Our aim is to provide digital solutions that remain stable in the face of this infrastructure uncertainty and we achieve this by utilizing specific design patterns and operational practices. At the core of the new way of working is a philosophical view that change is the rule rather than the exception. US entertainment company Netflix has fully embraced this new mindset and this served them well during a major outage experienced by their cloud infrastructure provider, Amazon Web Services (AWS). In this piece, we study how Netflix was able to avoid any significant impact while many other well established, technically savvy AWS users were not.

Conclusion

The events of September 20, 2015 were quite catastrophic for quite a number of well-established, highly trafficked web sites, yet Netflix viewed it as “a brief availability blip”. For them the recovery was rapid and low ceremony and their users experienced little disruption. This is not attributed to luck, rather, Netflix deeply understands what it means to run software in the cloud. They recognize that the software architectures of the last decades do not work well in the cloud, an environment that is constantly changing and is more distributed than ever before. They’ve invested in understanding and even defining new cloud patterns and have implemented frameworks and toolsets that allow them to manage the added complexity and even exploit the advantages that extreme distribution can bring. Moving to the cloud is not merely a matter of deploying existing software into Internet accessible data centers. Cloud-native software is defined by how you compute, not about where you compute. Writing software for the cloud demands that we treat change as the rule, rather than the exception. It is this that allows us to produce software that runs more reliably than the infrastructure that it is deployed to.