Versions Compared

Old Version 7

changes.mady.by.user Andrew Ralph Feller

Saved on

compared with

New Version Current

changes.mady.by.user Jaromir Hamala

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The following distributed ticket registries are available depending on the version of CAS you are deploying:

Ticket Registry

Version

Description

JBoss Cache

3.0.6

Uses JBoss Cache to store and replication information between servers over TCP / UDP

Memcached

3.3.0

Uses Memcached to store information and third-party patch to replication information

Ehcache3.5.0Uses Ehcache to store and replication information between servers over TCP / UDP

Option 3:Persistent ticket registry

...

The following persistent ticket registries are available depending on the version of CAS you are deploying:

Ticket Registry

Version

Description

JPA

3.2.1

Uses JPA framework (Hibernate, OpenJPA, TopLink, EclipseLink) to store information in datastore

Summary

Every CAS deployer should spend some time reviewing the options availble for ticket registries in reference to their organizational needs and resources available to support the costs.

Ticket Registry

Type

# of Machines

Version

Pros

Cons

Default

Standalone

1

N / A

  • Quick and easy
  • Data lost when server goes down

JBoss Cache

Distributed

2+

3.0.6

  • Replication options (TCP/UDP, unicast/multicast)
  • Data is somewhat resilient; improved availability
  • Data lost when all servers go down
  • Network chatty
  • CAS servers aware of one another

Memcached

Distributed

2+

3.3.0

  • Light-weight alternative to JBoss Cache
  • Separate process from CAS
  • Data is somewhat resilient; improved availability
  • Data lost when all servers go down
  • Network chatty
  • Requires third-party patch
  • Limited replication options (question)
  • Comprehensive data retrieval impossible
  • CAS servers aware of one another
EhcacheDistributed2+3.5.0
  • Data is somewhat resilient; improved availability
  • CAS servers aware of one another
  • Network chatty

JPA

Persisent

1+

3.2.1

  • Separate process from CAS
  • Data is very resilient; highest availability
  • CAS servers are not aware of one another
  • Datastore availability must be ensured
  • Datastore can be bottleneck