Architecture
Guide on various building blocks of Impler, How they communicate and How Impler works?
Last updated
Guide on various building blocks of Impler, How they communicate and How Impler works?
Last updated
Impler is built upon scalable architecture to validate and process records of any size.
Separation of concern helps organizing code across various packages, libraries and apps. The idea is that app is divided into various parts, and each one is responsible for a spacific task.
Let's dive deep into building blocks of Impler.
Widget is the main app where import happens. Widget provides UI to upload, map, validate and reivew data files. Widget gets embedded into iframe using embed script. It communicates with API to accomplish file processing work.
Queue manager handles processing data. Once user completes file import, the command gets passed to Queue Manager app to start processing data and sending it to application in chunks.
Chunk contains chunked data along with import information. More information on Using Webhook
API keys are used to authenticate APIs happening from import widget. Additionally developers can integrate Impler into their application by manually calling Impler API.
SDKs removes the need of managing import widget manually. In case of missing SDK developer can take reference of HTML & JS Embedto embed widget into application.
If you have any questions, suggestions, or comments. Feel free to reach out to us over Discord. We’re constantly improving to deliver the best Data Importer for your product, and we value your input.
