Optimize parsers for large datasets

**Feature request**
It would be great to have encryption for routes.

**Use case**
Many users need this functionality for production deployments.

**Implementation idea**
Add a new config option `enable_encryption` with default `false`.

First reconcile the unrelated title about large datasets with the body’s request for route encryption, then locate how routes and configuration options are represented. The issue names no files, entry points, or tests; done criteria for the encryption behavior and its default still need to be established.

Written by the indexing model from the issue text.