https://github.com/pocorall/syncmap

A lightweight distributed map for JSON object repository.
https://github.com/pocorall/syncmap

Last synced: about 2 months ago
JSON representation

A lightweight distributed map for JSON object repository.

• Host: GitHub
• URL: https://github.com/pocorall/syncmap
• Owner: pocorall
• Created: 2012-02-09T13:44:38.000Z (almost 13 years ago)
• Default Branch: master
• Last Pushed: 2012-02-10T11:34:11.000Z (almost 13 years ago)
• Last Synced: 2024-10-15T10:26:39.606Z (3 months ago)
• Homepage:
• Size: 145 KB
• Stars: 1
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
SyncMap is a Java library that provides lightweight JSON object maps for **synchronized client data**.

Suppose you have to write a feature similar to bookmark synchronization of Google Chrome. When a browser added a new bookmark, the browser notify it to a bookmark server. Then the server updates persistent repository(DB) and broadcast the update notification to all the clients listening the user's activity.

SyncMap is fit for this requirement. Client uses a SyncMap object as if it is an ordinary Map collection. All the works related to the synchronization is managed behind the scene. 



## Features

* Automatic Map synchronization between the clients

* Offline persistance

* Android ready

## Client example

Using SyncMap is no other than using ordinary Map object.

    Connection conn = ...	// acquiring connection. Will be explained later.

    Map map = conn.getMap("id.pocorall.bookmark");	// getMap() is a bloking operation.

    // Once SyncMap is acquired, no need to take care about synchronization.

    for(JSONObject obj: map.values()) {

    	System.out.println(obj);

    }

    // put() is a non-blocking op. i.e. the function returns immediately.

    map.put("http://somewhere.com", new JSONObject("{note:\"Favorate site!\"}")); 

Pretty simple :)

## Server example

## Connector example

## Persistent example

## Comparision to an alternative approach

If the client directly accessing remote DB, the client must hit remote DB for every data access which cause some delay due to network latency. client-side database cache will be less helpful because other client can update the data. Moreover, if you write an app for android, unstable wireless connection make the situation worse.