Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 2 TIBCO ActiveSpaces Fundamentals : What is a Metaspace?

What is a Metaspace?
A metaspace is a virtual entity that contains spaces, which are containers that store the data used by applications.
A metaspace is:
The hosts and processes in the cluster share the same metaspace name and set of discovery transport attributes and work together by joining the same tuple spaces.
System spaces—Spaces defined by ActiveSpaces.
User spaces—User-defined spaces.
Multiple independent metaspaces can be deployed over a single network of hosts, each with a different set of members and spaces, and each identified by a name and a set of network transport attributes.
This means, for example, that changes to a space called clients in a metaspace named Dev have no impact on a space named clients in a metaspace named Prod. Since no single application can connect to two different metaspaces using the same metaspace name, metaspaces should always use different names.
To use ActiveSpaces, your application must first connect to a metaspace. When your application is connected to a metaspace, it can:
A metaspace is a virtual entity: it is created when the first process connects to it, and disappears when the last process disconnects from it. The metaspace grows or shrinks automatically as members connect to it and disconnect from it.
Initially, a metaspace contains only system spaces. As users create spaces in the metaspace, the definition of those spaces (along with other administrative data) is stored in system spaces.
If you implement the ActiveSpaces data persistence feature, you can persist data to local storage. However, space and field definitions are not persisted in existing spaces after the last metaspace disconnects from it.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved