Windows Server AppFabric provides Distributed Caching features.
Windows Server AppFabric Caching features use a cluster of servers that communicate with each other to form a single, unified application cache system.
As a distributed cache system, all cache operations are abstracted to a single point of reference, referred to as the Cache Cluster.
In other words, your client applications can work with a single logical unit of cache in the cluster regardless of how many computers make up the cache cluster.
The primary components of the physical architecture consist of:
1. Cache Server
2. Cache Host Windows Service
3. Cache Cluster (Cluster of Cache Servers)
4. Windows Power Shell-Based Cache Administration Tool
5. Cluster Configuration Storage Location
6. Cache Client
The following diagram shows how all of these elements relate.
| Cache Client | Any application server that is running a cache-enabled application may be loosely referred to as the cache client. For an application to be cache-enabled, it must use the AppFabric caching assemblies and specify the appropriate application configuration settings programmatically or in an XML-based application configuration file |
| Cache Cluster | The cache cluster is a collection of one or more instances of the Caching Service working together in the form of a ring to store and distribute data. Data is stored in memory to minimize response times for data requests. The operations of the cache cluster are managed by a role, named the cluster management role |
| Cache Hosts | The AppFabric Caching Service is a Windows service that runs on one or more servers. |
| Cache Server | Each server that runs the Caching Service is referred to as a cache server. For each cache server, only one instance of the Caching Service can be installed. |
| Windows Power Shell-Based Cache Administration Tool | Windows Power Shell is the exclusive management tool for the Cache Service. Windows PowerShell cache administration cmdlets can be installed on any domain computer or on the cache servers themselves. This is done by installing the Cache Administration feature of AppFabric. You must have Administrator privileges on all of the cache servers for the tool to function properly. |
| Cluster Configuration Storage Location | Each time the cluster starts, it must retrieve configuration information from the cluster configuration storage location. The generic term "storage location" is used because the location is determined by how you choose to store the cluster configuration settings. |
Architecture Overview of App Fabric
The diagram below provides a high-level overview of the AppFabric system.
· Apps are deployed into a farm of AppFabric servers that share Workflow Instance Stores and Monitoring Stores (Databases).
· Distributed Cache provides unified data cache view to Apps while distributing and replicating data across multiple machines
The Windows Server AppFabric Cache stores Dot Net objects, scales seamlessly, and manages data location and redundancy by distributing the cache across a cluster of machines.
The developer can simply put data in the cache and retrieve it when needed - AppFabric handles all the underlying complexity for you.
Functional View
The diagram below illustrates key components of the AppFabric system and their functions from a single-machine view (one AppFabric Server view) in a typical setup.
Thus Windows Server AppFabric adds improved hosting capabilities to Windows Server to efficiently host all your WCF services, including WF Services.
Additionally, AppFabric provides common services that help you as a developer build scalable Web and composite applications.
There are many NFRs which are ultimately getting addressed with App Fabric. Some of them are :
· Reliability – Overall (pertains to system’s maturity, fault tolerance level, recoverability and product relevance duration)
· Reliability – Availability ( The fraction of the time when the system is operative and accessible to all it users)
· Reliability – Integrity ( The probability that a system will not be compromised such as to perform incorrectly or return incorrect results)
· Reliability – Security ( The probability that a system will not be compromised via access for read- write operations by unauthorized users or other software )
· Monitor ability : ( Ability to monitor run time - sessions, auditing of transactions )
· Stability ( a facet of performance, availability and manageability; devoid of memory leaks , dangling areas and other creeping issues)
· Availability –HA ( with Recoverability as a sub-requirement. Also MTBF – the mean time expected between two run time failures MTTR the mean time required to fix a bug after it is noticed at run time; software failover, hardware failover, standby hardware and so on ; strict ACID transactions, Tracing and Auditing; Business continuity against disasters; Recovery from malicious attacks )
Note:
AppFabric Caching requires less management; the "fabric" takes care of everything.
Adding new machines to the cache is handled in the AppFabric Configuration Wizard.
The cache takes a central configuration approach, so all the servers in the cache cluster know about each other.
You can choose to store this configuration in SQLServer or in a file share.
Distributed Cache
The Distributed Cache of App Fabric provides a distributed, in-memory application cache for developing scalable, available, and high-performance applications.
Distributed Cache Service runs across multiple machines and forms a tight cluster offering data replication and data consistency across multiple machines.
Distributed Cache Service can run on the same machine as the application code or run in a remote dedicated farm of machines.
How To Setup AppFabric Cache
Please check the link below.
Thanks & Regards,
Arun Manglick,
Project Manager - Forecasting
Mobile: 9158041782| 9850901262| Desk Phone: +912040265348 | http://www.synechron.com
SYNECHRON -
- 4,000+ professionals globally.
- USA | Canada | UK | The Netherlands | UAE | India | Singapore | Hong Kong | Japan
No comments:
Post a Comment