Category Archives: ActiveSpaces

TIBCO Activespaces – Best Practices –10. Physical Considerations

Physical Considerations Network considerations In general, just as with many other distributed systems, the network can have a large influence on performance: in many use cases and deployment scenarios there is a very good chance that a Space operation will need to wait for a network round trip time to elapse before it completes. Therefore, the  faster the network between

Read more

TIBCO Activespaces – Best Practices – 9. Persistence

Persistence Shared-all Persistence You can register more than one instance of the implementation of the shared-all interface on the same space. When more than one instance of the implementation of the shared-all persistence interface is registered, then onWrite and onRead operations are distributed amongst those instances. The most efficient deployment mode is when every seeder on the space registers an

Read more

TIBCO Activespaces – Best Practices – 7. API Considerations

API Considerations Threading Many ActiveSpaces API objects are thread safe (meaning that multiple threads can use them at the same time) The Metaspace object is thread safe: Metaspace connection is actually a process-wide resource. Use getMetaspace() to get more copies of the metaspace object as needed. Space objects are thread safe: Multiple threads can use the same space object at

Read more
« Older Entries