scholarly journals Data Synchronization Model for Heterogeneous Mobile Databases and Server-side Database

2018 ◽  
Vol 9 (1) ◽  
Author(s):  
Abdullahi Abubakar ◽  
Shuib Basri ◽  
Rohiza Ahmad ◽  
Abdul Rehman
Keyword(s):  
Data Synchronization ◽  
Mobile Databases ◽  
Server Side ◽  
Synchronization Model

scholarly journals DATA SYNCHRONIZATION MODEL TO IMPROVE THE SUPERVISION OF LAND OWNERSHIP FOR CITIZENS TOWARDS THE INDONESIAN AGRARIAN REFORM AGENDA

2021 ◽  
Vol 58 (2) ◽  
pp. 1673-1680
Author(s):  
AGUS SEKARMADJI Et al.
Keyword(s):  
Property Rights ◽  
Agricultural Land ◽  
Agrarian Reform ◽  
Land Ownership ◽  
Data Synchronization ◽  
Case Study Approach ◽  
Online System ◽  
Study Approach ◽  
Synchronization Model

The change of ownership and control of agricultural and non-agricultural land for all Indonesian people is a mandate of Article 7, 10 and 17 of Act Number 5 Year 1960 under the Indonesian Agrarian Reform. In practice, however, people can own property rights beyond the stipulated limit. The article aims to improve a fair distribution of land through the proposed model of supervision and property rights land tenure reforms. The data synchronization developed through an online system can be the tool to improve the supervision and management of land ownership and tenures. The methods used are the statute approach, socio-legal approach, and case study approach. The statute approach analysed existing statutes regarding land and land rights in Indonesia, the result is further observed in practice through the socio-legal approach by observing the data and figures in local regions. The case study approach reviews past judgments in the matter to examine the consistency and sufficiency of prevailing laws and policy and the direction of its developments. This study found that there is still an ineffective implementation of the law resulting in people having lands more than their limit. The proposed data synchronization model developed through an online system can solve this problem by harmonizing data in local regions with the existing data at the Civil Registry Office and the Tax Office. This study provides an essential contribution to the existing literature of Indonesian Agrarian Reform as well as a guideline for policymakers.

Technical Considerations for Building a Landslide Tracker Mobile App

2021 ◽  
Author(s):  
Ramesh Guntha ◽  
Maneesha Vinodini Ramesh
Keyword(s):  
High Performance ◽  
Monsoon Season ◽  
Performance Testing ◽  
Mobile App ◽  
Mobile Databases ◽  
Synchronization Mechanism ◽  
Server Side ◽  
Repeated Calls ◽  
The World ◽  
Client Side

<p>Substantially complete landslide inventories aid the accurate landslide modelling of a region’s susceptibility and landslide forecasting. Recording of landslides soon after they have occurred is important as their presence can be quickly erased (e.g., the landslide removed by people or through erosion/vegetation). In this paper, we present the technical software considerations that went into building a Landslide Tracker app to aid in the collection of landslide information by non-technical local citizens, trained volunteers, and experts to create more complete inventories on a real-time basis through the model of crowdsourcing. The tracked landslide information is available for anyone across the world to view. This app is available on Google Play Store for free, and at http://landslides.amrita.edu, with software conceived and developed by Amrita University in the context of the UK NERC/FCDO funded LANDSLIP research project (http://www.landslip.org/).</p><p>The three technical themes we discuss in this paper are the following: (i) security, (ii) performance, and (iii) network resilience. (i) Security considerations include authentication, authorization, and client/server-side enforcement. Authentication allows only the registered users to record and view the landslides, whereas authorization protects the data from illegal access. For example, landslides created by one user are not editable by others, and no user should be able to delete landslides. This validation is enforced at the client-side (mobile and web apps) and also at the server-side software to prevent unintentional and intentional illegal access. (ii) Performance considerations include designing high-performance data structures, mobile databases, client-side caching, server-side caching, cache synchronization, and push-notifications. The database is designed to ensure the best performance without sacrificing data integrity. Then the read-heavy data is cached in memory to get this data with very low latency. Similarly, the data, once fetched, is cached in memory on the app so that it can be re-used without making repeated calls to the server every time when the user visits a screen.  The data persists in the mobile database so the app can load faster while reopening. A cache-synchronization mechanism is implemented to prevent the caches' data from becoming stale as new data comes into the database. The synchronization mechanism consists of push-notifications and incremental data pulls. (iii) Network resiliency considerations are achieved with the help of local storage on the app. This allows recording the landslides even when there is no internet connection. The app automatically pushes the updates to the server as soon as the connectivity resumes. We have observed over 300% reduction in time taken to load 2000 landslides, between the no-cache mode to cache mode during the performance testing. </p><p>The Landslide tracker app was released during the 2020 monsoon season and more than 250 landslides were recorded through the app across India and the world.</p>

Design and Implementation of Configurable RFID Middleware for Mobile Devices

2014 ◽  
Vol 1049-1050 ◽  
pp. 1836-1839
Author(s):  
Da Wei Xu ◽  
Li Ping Yang ◽  
Xiao Ming Chen
Keyword(s):  
Mobile Devices ◽  
High Efficiency ◽  
Data Synchronization ◽  
Massive Data ◽  
Web Interface ◽  
Server Side ◽  
Low Energy Consumption ◽  
Device User ◽  
Platform Independence ◽  
Rfid Middleware

RFID middleware for massive data focused on the performance of server-side processing to bring pressure on the issue, a new for mobile devices can be flexibly configured RFID middleware (SMM). SMM can be used for mobile devices, has a better platform independence , can be deployed with multiple operating systems ; abstract objects by device , user via the user interface (UI) and a standard Web interface to control and manage a variety of mobile devices . Meanwhile, SMM also provides data synchronization. Experimental results show that, SMM has low energy consumption; high efficiency advantages can effectively reduce server stress and improve system performance.

Progressive Data Synchronization Model for Mobile Devices

2012 ◽  
Vol 4 (3) ◽  
pp. 1-20
Author(s):  
Mehdi Adda
Keyword(s):  
Mobile Devices ◽  
Data Access ◽  
Data Synchronization ◽  
Context Information ◽  
Mobile Data ◽  
Fine Grained ◽  
Disconnected Operation ◽  
Current State ◽  
Remote Server ◽  
Synchronization Model

Mobile data synchronization is an important technique used to replicate or synchronize data between a mobile client and a remote server. It helps overcome unstable wireless networks and support the disconnected operation. The current state of mobile data synchronization is most successful at transparently synchronizing all data. Generally, once a synchronization feature enabled, data is automatically synchronized without offering a fine grained and customizable synchronization policy. Furthermore, the context information, such as localization, date, device overload and resource consumption, type and quality of the connection, etc., are not equally taken into account or not considered at all. One solution is to develop a synchronization model that rely on a fine grained and flexible synchronization policy and where context information is considered as first-class citizen. This article puts forward a new model of data synchronization in mobile devices based on progressive data access schema.

Multi-Layer Control and Graphical Feature Editing Using Server-Side Rendering on Ajax-GIS

2010 ◽  
Vol 130 (1) ◽  
pp. 146-153 ◽  
Author(s):  
Takeo Sakairi ◽  
Takashi Tamada ◽  
Katsuyuki Kamei ◽  
Yukio Goto ◽  
Hideo Nakata
Keyword(s):  
Server Side ◽  
Layer Control

Dynamic Load-balancing and Control for Server-Side Rendering on Ajax-GIS

2013 ◽  
Vol 133 (4) ◽  
pp. 891-898
Author(s):  
Takeo Sakairi ◽  
Masashi Watanabe ◽  
Katsuyuki Kamei ◽  
Takashi Tamada ◽  
Yukio Goto ◽  
...  
Keyword(s):  
Load Balancing ◽  
Dynamic Load ◽  
Dynamic Load Balancing ◽  
Server Side ◽  
And Control

DYNAMIC REST SERVICES ORCHESTRATION USING THE KNOWLEDGE BASE

2019 ◽  
Author(s):  
Kostyantyn Kharchenko
Keyword(s):  
Knowledge Base ◽  
Service Oriented Architecture ◽  
Main Idea ◽  
The Real ◽  
Server Side ◽  
Service Oriented ◽  
Services Orchestration ◽  
Client Side ◽  
Abstract Operation ◽  
Microservice Architecture

The approach to organizing the automated calculations’ execution process using the web services (in particular, REST-services) is reviewed. The given solution will simplify the procedure of introduction of the new functionality in applied systems built according to the service-oriented architecture and microservice architecture principles. The main idea of the proposed solution is in maximum division of the server-side logic development and the client-side logic, when clients are used to set the abstract computation goals without any dependencies to existing applied services. It is proposed to rely on the centralized scheme to organize the computations (named as orchestration) and to put to the knowledge base the set of rules used to build (in multiple steps) the concrete computational scenario from the abstract goal. It is proposed to include the computing task’s execution subsystem to the software architecture of the applied system. This subsystem is composed of the service which is processing the incoming requests for execution, the service registry and the orchestration service. The clients send requests to the execution subsystem without any references to the real-world services to be called. The service registry searches the knowledge base for the corresponding input request template, then the abstract operation description search for the request template is performed. Each abstract operation may already have its implementation in the form of workflow composed of invocations of the real applied services’ operations. In case of absence of the corresponding workflow in the database, this workflow implementation could be synthesized dynamically according to the input and output data and the functionality description of the abstract operation and registered applied services. The workflows are executed by the orchestrator service. Thus, adding some new functions to the client side can be possible without any changes at the server side. And vice versa, adding new services can impact the execution of the calculations without updating the clients.

Sign in / Sign up

Export Citation Format

Share Document