We're updating the issue view to help you get more done.Learn more

Remove per-tenant Hazelcast configuration

The current Hazelcast topology creates a separate member for each tenant in a SiteWhere instance. While this offers some advantages such as data isolation, it does not scale well for many tenants, particularly when clustering many instances. Also, there are cases where the Hazelcast interface is passed into tenant scripts, which could allow for manipulating data such as the cache and making SiteWhere less secure. The tenant-specific Hazelcast instance will be replaced by a per-node instance, requiring some re-working of existing functionality (caching in particular), but making the system much more scalable in clustered scenarios.