Hari's Technical Space

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

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

Seeding and Leeching Remember that seeding and leeching is a “per space” state: a process can seed on one space and leech on another. Also remember that a leech is not limited in functionality compared to a seeder, it can make use of all of the Space operations. A Seeder contributes some of its resources to the scalability of the

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

Space Operations Operations on Keys You can use options in some space operations in order to do two things: Optimize response times and resource usage by: Combining operations You can do a put plus a lock or unlock operation in a single call and possibly in half the time if you do a put with a lock or unlock option