CloverETL Editions - Overview

		Community	Desktop	Enterprise Standard	Enterprise Corporate	Cluster
Price		$0	$4,000	Inquire	Inquire	Inquire
Includes CloverETL Designer		*		1	2	4
Contains complete set of transformation components
Ability to run graphs on a PC/Mac/Linux desktop
Supports Client / Server mode
Includes  CloverETL Server
CloverCare Support
Total CPU cores			n/a	4	16	-
Tracking of execution history
Parallel execution of multiple transformations
Improved thread management and graph pooling
Multi-user access/security
Scheduler
Workflows
File triggers/Message triggers
Launch services (Real-time ETL)
Clustering and distributed execution
Load balancing
Failover
Autoscaling

Total CPU cores

Number of processing units (CPU cores) as reported by Java Virtual Machine. For example, one physical dual core CPU is considered to be system with 2 CPU cores; one physical dual core CPU with hyperthreading is considered to be system with 4 CPU cores.

Tracking of execution history

Server automatically collects transformation logs and runtime statistics. Both logs and statistics are easily accessible for email distribution or trend monitoring strategies.

Parallel execution of multiple transformations

Any number of transformations can run simultaneously. Additionally supports starting multiple instances of one transformation with configurable maximum.

Improved thread management and graph pooling

Minimizes start-up time of transformations during real-time ETL calls by caching and pooling the transformations. Sub-sequent runs of cached transformations are much faster.

Multi-user access/security

Access to transformations, data, services and server configuration is protected by user security module. Communication between Server and its clients can be optionally secured by HTTPS protocol.

Scheduler

Internal scheduler lets you schedule transformations to run once or periodically on specific times. It supports advanced scheduling expressions similar to those provided by UNIX cron scheduler.

Workflows

Workflows simplify deployment of Server into operational environment and integration with you production support architecture. Server workflows allow sequencing jobs of several types: transformations, system scripts/batches, JMS messages, emailing tasks or internal Groovy scripts.

File triggers/Message (JMS) triggers

File triggers help to easily implement scenarios, where data is uploaded for ETL processing in form of files. Server can automatically observe change or arrival of a file then automatically trigger its processing.
Message triggers allow to triger pre-defined action (e.g. execute graph) upon receiving a message through observed message queue. Ideal for Enterprise Service Buse (ESB) and similar deployments.

Launch services (Real-time ETL)

Launch Services provide infrastructure for SOA-oriented and real-time ETL deployments. Transformations can be configured to be executed as web-services, while data and parameters are passed dynamically as part of the web-service call.

Clustering and distributed execution

Server clustering enables cooperation of multiple Server machines in a networked environment which brings both fail-over and scalability. It is also suitable for cloud deployments on public clouds (EC2, Rackspace, …) as well as in-house data centers.

Load balancing

Configurable load balancing rules together with automated performance monitoring lets you tune utilization of individual nodes operating in clustered environment.

Failover

Cluster performs automatic healthcheck monitoring of all nodes in cluster and in case of node failure redirects processing to remaining active nodes.

Autoscaling

New nodes can be dynamically added to a running cluster on demand. Suitable for operational environment such as Amazon EC2 that allow dynamic allocation of computational resources.