Best Practice Configurations
Once you have decided to use PoolParty, it is time to find the configuration that best suits your needs. A key to this is the so-called multi-tiering, which is the use of PoolParty licenses on a distributed infrastructure.
Along your data lifecycle, several activities take place in parallel and are highly interdependent: Development, testing, staging and production – to name a few. These activities impact the performance, risk, security, and availability of your taxonomy or knowledge graph itself or its associated applications. Managing these dependencies is a key factor in smooth operations, cost efficiencies, and reduced operational risk.
Operate PoolParty in a multi-tier enviroment helps to minimize operational issues and achieve maximum earned value with PoolParty deployment. The decoupled software instances allows to decouple risks, prevent stand-stills and increases data security. For example, separating the development and test environments can increase the validity of test runs, as it can also help to layout the test environment closer to the realities of the production environment.
Recommended Multi-tier PoolParty Configuations
Over the years, we have gained deep insights into how our customers develop, test, deploy, maintain, and reuse taxonomies within their specific frameworks. Based on this, we can now recommend best practice configurations.
PoolParty ranks above the industry average for integration capability.
SoftwareReviews is a research service that collects unbiased reviews of software vendors capabilities and measures them across companies in the industry. Aside from the features referenced in the chart, PoolParty also got over 80% scores in Automation of Metadata and APIs and Integration capabilities.