Is Heimdall Data an APM (Application Performance Monitoring) product?
How is Heimdall Data used as a transparent cache?
The operational elegance of the Heimdall Data solution is that it does not require any application code changes. This is ideal for those deploying 3rd party applications (e.g. HR, manufacturing, finance) requiring performance optimization and high availability. Installation is takes 5 minutes.
For application developers, cache policies are typically coded into their application code. This creates inefficiencies: 1) Trial and error of what to cache, and 2) Longer development cycles. The Heimdall Data cache solution provides custom recommendations on exactly what to cache, taking out the guesswork for application owners.. With Heimdall’s “One-click optimization”, caching policies are immediately enabled without any programming, and can be disabled just as fast.
But we already cache at the business object and web level. Does Heimdall Data still add benefit?
Absolutely. Working alongside the application caches and web caches, the Heimdall cache provides additional for performance benefits, particularly for dynamic content. Application level caches may have constrained parameters (e.g. per session) limiting the caching required for optimal performance. Because Heimdall caches at the data access layer, it sees the unrestricted flow traffic going to the database and optimizes performance that other cache systems will not be able to detect.
Web level caching is static content. And, one can only start streaming static content once the dynamic pieces have been generated. It is that dynamic content from the database that Heimdall optimizes.
Can Heimdall Data be deployed in the Amazon Web Services?
Heimdall Data is ideal for cloud deployments as it offloads database traffic, improving performance & reliability while saving cloud usage costs. Amazon RDS provides ease of database management, reliability, and scalability from a backend perspective. However, it is not application aware.
Heimdall Data ensures that upon a database failure, the application remains online. With our additional performance optimization and security features, Heimdall Data provides “Application Resiliency” for Amazon RDS deployments.
What makes the Heimdall Data High Availability failover unique compared to Oracle and existing load balancing solutions?
- The Heimdall Data HA failover solution is database vendor neutral. For customers who deploy multiple data sources, Heimdall can be used as a common platform for automated database failover. Heimdall Data supports databases such as MySQL, PostgreSQL and Oracle. Additionally, customers do not have to purchase piecemeal solutions as Heimdall is a platform for supporting 1) SQL optimization, 2) Automated failover and 3) SQL security.
- Solutions in the market today (e.g. TCP load balancer) are not application aware. The TCP load balance may successfully failover to a redundant database, but if the application time out and be forced to reconnect. The Heimdall Data Resiliency Platform is application aware insuring that upon a database failover, the application connection will be maintained and is at top performance.
- Heimdall Data can automate the failover on the master node for disaster recovery. We do not support database replication or slave promotion.
How is Heimdall Data different from middleware (IBM, Oracle, Microsoft, , Tibco)?
How is Heimdall Data different from Hibernate ORM (Object-Relational Mapping) framework?
Heimdall is a SQL optimization platform that supports caching, security, and high availability. Heimdall Data can work together with Hibernate and make your environment more scalable and higher performing.
In a SQL context, Hibernate requires the user to program to its APIs. Hibernate can interface with grid caches and manipulate SQL queries. Heimdall Data can do the same but is deployed transparently, requiring zero application code level changes. Heimdall is much easier to manage and deploy. Moreover, the performance of Hibernate is no comparison to that of Heimdall Data. Heimdall was architected to increase application performance and offer a platform of services (i.e. SQL optimization, HA, and security)
How much CPU and RAM load does Heimdall take up on the application server?
Is Heimdall Data suitable for deployments in the cloud?
What is the pricing model for Heimdall Data?
Our Web Application Firewall is used protect against SQL attacks.
SQL injection attacks trick the application into performing adversely. Because this form of attack is dependent the application behavior, there are cases where the WAF or application does not see such an attack. Hence, the Heimdall solution will act as a last line of defense for SQL data leakage.