Thread 8

The Erlang programming language is an interesting approach to a solution for concurrent and parallel programming. It is interesting for so many different aspects and the first aspect would be that is a programming language that doesn't require the idea of sharing memory. This is a big change in paradigms , we have seen it in some old languages that the idea to share memory is a common one. Yet even if it is an old idea and a paradigm that is implemented in several languages , is hard to handle. It is true that we have certain objects that could help us to manage the memory and how different threads or programs can access shared resources. This sometimes can be difficult to understand and even sometimes hide some bugs that are hard to replicate and even solve them.  Another idea that Erlang deviates from is the idea of immutable variables or states. This is another old way to manage resources and make sure that we can keep the state of the program appropriately. We can notice that Erlang which is a programming language focused on concurrency , it completely  uses different paradigms that were implemented ages ago.  The third aspect that it can be replicated with different arquitectures or programs. Is the idea of workers and administrators. Which is a model that replicates on how a project in the real life would work, The workers are tasked with simple tasks and given the data or parameters on how to execute it's task. If anything wrong happens in that task it will tell the administrator that something wrong happened.  The administrator will decide what to do with this error and how to handle it. This makes Erlang a programming language that is focused on less error prone. Kubernetes is an example of a load balancer which it will balance the different information that comes to the the main node to it's separate children nodes. Just like as an Administrator in Erlang would work. Yet if something bad happens in a node, it will be in charge on creating a whole new node.