Chaos Engineering has been a topic that has intrigued me for quite some time. My first encounter with this concept started in an SRE meetup hosted by the folks at Atlassian (back when the pandemic wasn’t a thing). While my current role doesn’t require me to work on these aspects of development, tasks that aren’t our responsibility more interesting, aren’t they?
As I might not be able to paraphrase it better, here’s a definition from principlesofchaos.org:
“Chaos Engineering is the discipline of experimenting on a system to build confidence in its capability to withstand turbulent conditions in production.”
While designing modern applications, the term ‘cloud-native architecture’ is often showcased as the desired trait for applications that you migrate or build on cloud platforms. But what exactly does being cloud-native mean? Let’s delve deeper and hope to understand this paradigm.
On an abstract level, a cloud-native application should be able to make the best use of modern cloud platforms. Compared to traditional on-prem infrastructure, the cloud offers a great deal of flexibility with the concept of ‘X’ as a service. However, it also brings along a different set of architectural constraints that software architects would have to deal with.
A lot of times, programmers looking forward to prototyping their projects are faced with a common dilemma, “Which framework or library to choose?”
Choosing the right tech stack is essential in designing a well-architected solution. While there are a plethora of advantages that emerging tools and technologies bring along, they also make the process of finding our niche more convoluted. For example, there have been times where I would simply google ‘Angular vs React’, see a random youtube video comparing the two, and finally start coding my project on ‘Vue.js’. …
An inquisitive Software Engineer & Cybersecurity Enthusiast