Soft state: With Soft start, the copies of a data item may be inconsistent and the state of the system may change over time, even without input because of the ‘‘Eventual Consistency’’. ‘‘The soft state mode should be utilized for applications built on legacy functionality in the backend, particularly when the functionality includes initial loading/caching of large sums of information for a single request. By using soft state, the resources/functionality which has been loaded during the initial load can be reused for the subsequent requests of the service’’ [8]. Eventually consistent: The updates propagate, when there are no updates over a certain period of time defied for a particular application. Hence, the systems where BASE is the key requirement for reliability, the potential of the data changes essentially slows down.