Differences between Striim Platform and Striim Cloud
Striim is available as two different products: Striim Platform and Striim Cloud.
Striim Platform is installed on your hardware or deployed on a virtual machine in AWS, Azure, or Google Cloud Platform. You must configure and manage it yourself.
Striim Cloud is a fully managed SaaS platform available on AWS, Azure, or Google Cloud Platform
In this documentation, when we say "Striim" without specifying Platform or Cloud, it applies to both.
The following features require multi-server clusters, so are available only in Striim Platform and Striim Cloud Mission Critical (see Introducing Striim Cloud Mission Critical), not Striim Cloud Enterprise.
deploying and running applications on multiple servers Adapting TQL applications for multi-server deployment
application failover when a server goes offline (see Continuing operation after server failover)
automatic redistribution of applications among servers when a server goes offline or comes back online (see Automatic load rebalancing)
Multi-server clusters in Striim Platform with servers on different subnets may suffer split brain (see Avoiding split brain). This is not an issue with Striim Cloud Mission Critical. (It is also not an issue with Striim Cloud Enterprise, since that supports only a single server.)
The following features are currently available only in Striim Platform, not in Striim Cloud:
the schema conversion utility (initial load wizards with Auto Schema Creation are supported in both Striim Platform and Striim Cloud)
using environment variables in adapter properties
reading from SQL Server 2008 directly, without using a Forwarding Agent
writing to SQL Server 2008
using Active Directory authentication with Azure SQL Database, Azure Synapse, or SQL Server
the SysOut adapter
using LDAP authentication
reading log files
file lineage
monitoring using JMX
creating custom Java functions
See also the known issues listed in Release notes.