How is the Heimdall Proxy Unique?

Read/Write splitting with ACID Compliance
Auto scaling while keeping state
Active Directory/LDAP integration
Check out our webinar.

Read/Write Split with Strong Consistency

Queries are routed to the writer/reader instances without code changes. We load balance across readers for better utilization. Users receive the most up-to-date data with our replication lag detection. Check out Google Cloud Blog.

Query Caching

Automated Query Caching: Reduces latency, result sets are cached to the storage of your choice (e.g. Redis) Automated invalidation is supported to guarantee fresh data. Deployment requires zero code changes.

Connection Pooling

Connection Pooling: Multiple client connections are associated to a database connection. Limit backend connections per user and per database.

Connection Multiplexing: Backend connections are established for only active, non-idle queries. The net result is lower total memory, and reduced database costs. Check out our Google Cloud Blog.

Connection Pooling and LDAP/Active Directory Video

Active Directory / LDAP Policy Enforcement

Most likely, your database is not regulatory compliant. Also, databases do not work with LDAP user groups. We centralize authentication for users to your organization’s LDAP; with Just-in-time provisioning and one-click reports of who has access. Check out the Heimdall Database Access Gateway.

Technical Resources

Google Blog: Automated Query Caching, no code changes

Google Blog: Read/Write Split with ACID Compliance

Google Blog: Connection Pooling

Google Marketplace: Free Trial