Employee Handbook Builder
Step-by-step handbook builder
Performance Review Builder
Build performance appraisals in minutes
Interview Question Builder
Fully compliant interview questions
Job Description Builder
Professional job descriptions in minutes
COBRA Notice Generator
Generate COBRA notices in 3 easy steps
Compare geographic salary data
Evaluate your companies HR practices
Steps to Success
Series of how-to guides
How-to articles and expert insight
Background & Drug Screening
Over 25 different screenings
Ask an HR Pro
Direct access to certified HR professionals
Sexual Harassment Prevention
Sexual harassment prevention training
Federal Holiday Calendar
Holidays that will impact bank services
Fully integrated Workers Comp insurance
Intelligent time clocks & apps
Wage & Tax Guide
Series of how-to guides
Payroll & Tax
Easy, accurate & worry free
Time & Attendance
Automate payroll and improve accuracy
Keep compliant, track success & analyze
Fully managed ACA compliance
HR360 & HR Hotline
Support, compliance and beyond
Find the talent you need to succeed
Transition candidates into employees
Engage and empower your employees
What is Caching
Caching helps applications perform dramatically faster and cost significantly less at scale
What is Caching?
In computing, a cache is a high-speed data storage layer which stores a subset of data, typically transient in nature, so that future requests for that data are served up faster than is possible by accessing the data’s primary storage location. Caching allows you to efficiently reuse previously retrieved or computed data.
How does Caching work?
The data in a cache is generally stored in fast access hardware such as RAM (Random-access memory) and may also be used in correlation with a software component. A cache's primary purpose is to increase data retrieval performance by reducing the need to access the underlying slower storage layer.
Trading off capacity for speed, a cache typically stores a subset of data transiently, in contrast to databases whose data is usually complete and durable.
RAM and In-Memory Engines: Due to the high request rates or IOPS (Input/Output operations per second) supported by RAM and In-Memory engines, caching results in improved data retrieval performance and reduces cost at scale. To support the same scale with traditional databases and disk-based hardware, additional resources would be required. These additional resources drive up cost and still fail to achieve the low latency performance provided by an In-Memory cache.
Design Patterns: In a distributed computing environment, a dedicated caching layer enables systems and applications to run independently from the cache with their own lifecycles without the risk of affecting the cache. The cache serves as a central layer that can be accessed from disparate systems with its own lifecycle and architectural topology. This is especially relevant in a system where application nodes can be dynamically scaled in and out. If the cache is resident on the same node as the application or systems utilizing it, scaling may affect the integrity of the cache. In addition, when local caches are used, they only benefit the local application consuming the data. In a distributed caching environment, the data can span multiple cache servers and be stored in a central location for the benefit of all the consumers of that data.
Caching Best Practices: When implementing a cache layer, it’s important to understand the validity of the data being cached. A successful cache results in a high hit rate which means the data was present when fetched. A cache miss occurs when the data fetched was not present in the cache. Controls such as TTLs (Time to live) can be applied to expire the data accordingly. Another consideration may be whether or not the cache environment needs to be Highly Available, which can be satisfied by In-Memory engines such as Redis. In some cases, an In-Memory layer can be used as a standalone data storage layer in contrast to caching data from a primary location. In this scenario, it’s important to define an appropriate RTO (Recovery Time Objective--the time it takes to recover from an outage) and RPO (Recovery Point Objective--the last point or transaction captured in the recovery) on the data resident in the In-Memory engine to determine whether or not this is suitable. Design strategies and characteristics of different In-Memory engines can be applied to meet most RTO and RPO requirements.