Cloud-based distributed persistence and cache data model

A distributed cache data system comprising:

• a front-end client cache residing on a client machine;
• a back-end distributed file system comprising data cells capable of storing data in an unstructured format in clustered nodes, wherein each node comprises a plurality of data cells capable of storing data in an unstructured or structured format;
• a cache adapter comprising data cells capable of storing data in a structured format residing in the clustered nodes wherein the cache adapter is configured to reserve a designated portion of memory in at least two nodes to form a contiguous memory space spanning across the clustered nodes;
• and a lightweight application server comprising an application code embedded within the cache adapter;
• wherein the cache adapter comprises data cells configured to store data in a relational database table format;
• the cache adapter is configured to move data between the data cells in the cache adaptor and the distributed file system, wherein the data is persisted in the distributed file system;
• the cache adapter is configured to interface with the client cache at the front-end of the distributed cache data system and a distributed file system at the back-end of the distributed cache data system, wherein the distributed file system bi-directionally synchronizes with the client cache;
• the cache adapter is configured to provide an interface for external clients at the front-end of the distributed cache data system to access the data;
• the cache adapter is configured to bi-directionally communicate to the external clients via a web server, the cache adapter is configured to create at least one instance that has an upper limit in size, wherein when the instance reaches the upper limit, the cache adapter automatically creates a new instance;
• the cache adapter further comprising a storage map comprising a directory of a plurality of instances and a plurality of UserIDs stored on each instance,
• the lightweight application server is configured to analyze an incoming request of a user to determine an UserID;
• and
• based on the UserID and the Storage map, send the incoming request to a data cell that contains all user related data for the user,
• receive a response from the data cell and transmit the response to the front-end client cache;
• and the lightweight application server acts as a controller and is configured to ship the application code to a location of the data.