Arenadata QuickMarts
- quick data marts;
- e-commerce and finance;
- monitoring and analysis of structured logs and events;
- time series data;
- web and mobile application analytics.
A successful architectural pattern is to use Arenadata QuickMarts as a layer for fast data analysis. In this paradigm, an OLTP database is used to record transactional data into its row-based model, and Arenadata QuickMarts serves advanced analytical queries leveraging its column-oriented model to answer complex aggregates on the millisecond scale.
Additionally, Arenadata QuickMarts provides a wide range of engines to store and process data, as well as a rich toolkit of built-in functions for fast data analysis.
Arenadata QuickMarts is great as a data source for machine learning algorithms. It can be integrated with open-source Yandex CatBoost algorithm. Some of the main features of this competitive library are: default parameters (without customization) provide great results, categorical features do not require preprocessing, quick computation, high accuracy without overfitting, and lastly, efficient predictions.
Arenadata QuickMarts is an excellent choice for quick storing e-commerce data such as business transactions, user behavior and advertising data, and building flexible BI reports on top of it.
Arenadata QuickMarts is optimized for storing and querying time series data. It’s a good choice for analyzing data from financial markets or IoT devices.
Arenadata QuickMarts is a good choice to collect log data from different sources for further analysis. Fast query execution provides an easy-to-use interface for collecting facts, gathering metrics, or building event processing on top of it.
- support a strategy for distributing data across physical tables;
- increase insertion speed;
- balance load on ClickHouse/ADQM nodes.
- high speed of data transmission;
- automatic data schema generation;
- flexible partitioning;
- support for push-down operators;
- support for batch operations.
- connection pooling;
- load balancing and fail-over;
- limited support for modifying data in a source (INSERT) and support for scripts.
- limit HTTP access by a list of allowed IP addresses/IP masks;
- authorize users safely – Chproxy can map users submitting requests to users of the ADQM cluster without exposing real usernames and passwords used in ADQM;
- check health of cluster nodes and prevent requests from being sent to unavailable nodes.
Compare with
Compare with
A single tool for managing the lifecycle of all Arenadata products.
ADCM is installed with one command and only requires Docker.
Management console Cluster, node, backup, and update management.
User management.
AWS product management via a web interface.
Region and cluster size selection.
Monitoring management.
Automated deployment and configuration.
Allows cluster management.
User, role, and resource management.
Azure cloud web interface.
Resource and volume management.
Ability to build dashboards based on data.
Web interface with the ability to manage backups and monitoring.
Detailed documentation in Russian and English languages for all services, their installation, configuration, and operation.
Available in the public domain.
“Product comparison” section is relevant on the date of 30.06.2023.
- Added support for Ubuntu
- Added JAVA_HOME in cluster config
- Implemented multiple LDAP servers
- Implemented rolling upgrades
- Implemented rolling restarts
- Increased ClickHouse version
- Added the adqm-clickhouse-copier package
- Implemented support for SSL between ZooKeeper and ADQMDB
- Added log output for non-starting services
- Increased ClickHouse version
- Increased ZooKeeper version
- Introduced the Prometheus-based monitoring service
- Introduced new Grafana dashboards
- Added the jdbc bridge log path setting
- Implemented CA certificate support for inter-server communications
- ClickHouse errors are now displayed in ADQM jobs
- Increased ClickHouse version to 23.3.2.37-lts
- Implemented support for the gRPC network interface
- Extended data storage configuration options
- Added new sections to the configuration page of the ADQMDB service instead of the Storage Configuration parameter
- Implemented the ability to define requirements for the complexity of user passwords
- Added the Encryption codecs for tables section
- Added support for RedOS
- Increased ClickHouse version to 22.8.12.45-lts
- Added support for Astra Linux
- Added support of Kerberos authentication
- Implemented support for SSL in the Chproxy service
- Implemented the ability to install ClickHouse Keeper as a separate service
- Implemented a set of improvements to increase the security at the level of interaction between cluster hosts, SSL support, Chproxy and ClickHouse interaction
- Refactored the Configuration page of the ADQMDB service in the ADCM interface: improved descriptions of some parameters, deleted the external_dictionaries_path and external_dictionaries parameters from the Other section, and moved the Other section to the end of the page
- Extended a set of pre-checks before an ADQM cluster installation
- Implemented the concurrent_threads_soft_limit parameter that allows you to limit the number of query processing threads
- Added the Disable SElinux and Disable Firewalld options to the cluster configuration page in the ADCM interface
- Excluded the Baje proxy service from ADQM
- Added Alt Linux version check before installing ADQM
- Added the Chproxy service
- Fixed an error occurred when upgrading ADQM on Alt Linux
- Fixed incorrect switching of a cluster status from upgradable to installed during the cluster upgrade
- Changed ADQM package names so that they differ from names of ClickHouse packages
- Increased ClickHouse version to 22.3.2.2-lts
- Added support for Alt Linux 8.4 SP
- Added the ClickHouse Keeper component
- Expanded management options for built-in logging tools
- Added checks of monitoring services installed in an Enterprise Tools cluster before importing monitoring settings into an ADQM cluster
- Fixed: ADQM bundle upgrade could lead to loss of cluster configuration data if the Default cluster topology field was set to an incorrect cluster topology (for example, shards and/or replicas were unsorted or a shard/replica identifier contained a space)
- Implemented the Reinstall status-checker action for a cluster in the installed state. It runs the status-checker deployment scripts for services as well as for Docker containers
- Added the Advanced configuration parameters section to the Configuration page of the ADQMDB service
- Fixed the Baje proxy service installation error
- Fixed an error with offline installation of the ZooKeeper package
- Increased ClickHouse version to 21.8.8.29-lts
- Added the ability to map roles from an LDAP directory to ADQM roles and assign these roles to authenticated users
- Implemented the Expand and Shrink actions for the Monitoring Clients service
- Added support for Alt Linux 8.2
- Added retries to check JDBC bridge
- Changed the logic of adding the log_queries parameter to the default settings profile in the users.xml file
- Added support for RHEL
- Included checking of component versions to the Check action
- Fixed an issue with importing the HTTP Mirror service of an Enterprise Tools cluster into an ADQM cluster
- Increased ClickHouse version to 21.3.11.5
- Increased ClickHouse version to 21.3.4.25-lts
- Implemented the ability to install ADQM without Internet access
- Fixed a Zookeeper service error occurred when performing the Expand action
- Fixed an issue with skipping ADQMDB dashboards when installing monitoring
- Fixed an issue with loading more than one Avro-formatted message from Kafka into a ClickHouse table
- Increased ClickHouse version to 20.8.13.15-lts
- Implemented the ability to use an LDAP server for user authentication
- Added Zookeeper check after installation
- Fixed an issue with installing an ADQM cluster when using the external ZooKeeper
- Fixed an error in the users.xml file: the same IP address was duplicated in the networks list
- Increased ClickHouse version to 20.8.11.17-lts
- Added parameters to configure a default user and a default settings profile
- Implemented creation of macros for multiple cluster topologies
- Deleted the Create user and Delete users buttons
- Increased ClickHouse version to 20.8.4.11-lts
- Increased ClickHouse version to 20.3.20.6-lts
- Increased ClickHouse version to 20.8.2.3-stable
- Added the ability to specify Kafka configuration parameters
- Increased ClickHouse version to 20.3.13.130-lts
- Added the following parameters to the Configuration page of the ADQMDB service in the ADCM interface: Cluster Configuration, Storage Configuration, User policy, query_log
- Added the ability to specify a username and password for replicas in the remote_servers section of the config.xml configuration file
- Fixed: incorrect minimum version for an upgrade
- Increased ClickHouse version to 20.3.10.75
- Fixed Zookeeper service check error occured when performing the Check action for a cluster
- Refactored the ADQM bundle
- Increased ClickHouse version to 19.14.11.16-lts
- Added support for Alt Linux
- Divided the ADQM bundle into the Community and Enterprise versions
- Updated EULA for the Community version
- Added a window to sign the license agreement after downloading the bundle
- Added the Clickhouse JDBC Bridge component to the ADQMDB service
- Implemented the ability to use an external ZooKeeper