The BASE acronym was defined by Eric Brewer, who is also known for formulating the CAP theorem. The CAP theorem states that a distributed computer system cannot guarantee all of the following three properties at the same time: Consistency Availability Partition tolerance A BASE system gives up on consistency. Basically available indicates that the system does guarantee availability, in terms of the CAP theorem. Soft state indicates that the state of the system may change over time, even without input. This is because of the eventual consistency model. Eventual consistency indicates that the system will become consistent over time, given that the system doesn't receive input during that time. Brewer does admit that the acronym is contrived: I came up with [the BASE] acronym with my students in their office earlier that year. I agree it is contrived a bit, but so is "ACID" -- much more than people realize, so we figured it was good enough.
Here is what the above code is Doing:
1. We’re creating a new instance of the Flask class.
2. We’re then creating a route called /hello. This is the URL that will trigger our function.
3. We’re then defining a function called hello_world, which returns the string “Hello, World!”.
4. Finally, we’re telling our app to run.