At times it happens that the need of a real time data sharing is different from that of a batch processing. The APIs can work in both real time manner and in the batch processing. When the data is required in real time basis such as getting the leads from the website or sending an update on the patient’s health to doctor’s app, we make use of the services that are quick and have lowest response time. These APIs are written in the manner that can handle the exceptions with ease and are easy to be read and understood by the development team on the other side. In the batch processing, the batches of the data are created and a scheduled task is made to run on the pre-defined timings. These pre-defined timings could be hourly, daily, weekly or monthly. A fine example is fetching the data from the Attendance registers on the daily basis. With the batch processing, we reduce the load on the server at transfer the data at the non-working hours of the organisation.
When creating an API for the core applications, we work closely with the developers of the core applications to make sure that all the data is seamlessly shared and the transaction is complete in one go. Any exception arising due to the in the integration is handled so as to keep the data in sync.
These integrations often help in achieving higher levels of Automation and reduces the workload of the end-users and thereby eliminating the probability of the errors that occur with the human intervention. In one of the example, the details of the patient was copied from ERP to the core applications by the users and often resulted in delays and human errors. After integrating it with the help of JSON based APIs, the data was transferred from ERP application to the Core application seamlessly and eliminated any possibility of the Human error.