https://docs.protegrity.com/anonymization/1.4.1/docs/about_anon/Recent content in About Protegrity Anonymization onHugoenMon, 06 Apr 2026 11:24:23 +0000https://docs.protegrity.com/anonymization/1.4.1/docs/about_anon/hide_intro_comm/Mon, 01 Jan 0001 00:00:00 +0000https://docs.protegrity.com/anonymization/1.4.1/docs/about_anon/hide_intro_comm/<p>An overview of the communication is shown in the following figure.</p> <p><img src="https://docs.protegrity.com/anonymization/1.4.1/docs/images/hide/hide_arch_comm.png" alt="" title="Protegrity Anonymization Communication"></p> <p>Protegrity Anonymization leverages several pods on Kubernetes. The first pod contains the Dask Scheduler. This pod connects to the Dask Worker pod over TLS. If Protegrity Anonymization requires more processing to work with the dataset, then based on the configuration, additional Dask Worker pods can be added. Protegrity Anonymization Web Server performs the processing using an internal Database Server for holding the data securely. The Protegrity Anonymization request is received by the Nginx-Ingress component. Ingress forwards the request to the Anon-App. The Anon-App processes the request and submits the tasks to the Dask Cluster. The Dask Scheduler schedules task on the Dask Workers The Anon-app stores the metadata about the job in the Anon-DB container. Next, the Dask Workers read, write, and process the data that is stored in the Anon-Storage, the request stream, or the Cloud storage. The Anon-Storage uses S3 bucket for storing data. The communication between the Dask Scheduler and the Dask Workers is handled by the Dask Scheduler. The Dask workers run on random ports.</p>https://docs.protegrity.com/anonymization/1.4.1/docs/about_anon/hide_intro_arch/Mon, 01 Jan 0001 00:00:00 +0000https://docs.protegrity.com/anonymization/1.4.1/docs/about_anon/hide_intro_arch/<p>Protegrity Anonymization is composed of the following main components:</p> <ul> <li><strong>Protegrity Anonymization REST Server</strong>: This core component exposes a REST interface through which clients can interact with the Protegrity Anonymization service. It uses an in-memory task queue and stores anonymized datasets and respective metadata on persistent storage. Protegrity Anonymization tasks are submitted to a queue and are handled in first-in first out fashion. It invokes the Dask Scheduler to perform the Protegrity Anonymization task.</li> </ul> <blockquote> <p><strong>Note:</strong> Only one anonymization task is executed at a time in Protegrity Anonymization.</p>