Barbarian is the world's best cloud-first, cloud-agnostic in-memory big data system founded on Apache Hadoop for enterprise-ready parallel distributed data processing at scale.
Read more at: https://barbarians.io/
Docs at: http://docs.barbarians.io/
The Barbarian Data System is an in-memory, parallel, distributed (MPP) data warehousing engine designed to be deployed to Kubernetes clusters, offering Apache Hive for powerful and flexible SQL based analytics. Barbarian includes an integrated in-memory filesystem and can run in three modes of operation.
- As an in-memory, standalone data warehousing system
- As a data warehousing system backed by an external storage system like Amazon S3
- In a hybrid mode, where primary storage is the external storage system, with common paths mounted to the in-memory filesystem
Barbarian includes compelling features including Apache Hive LLAP and Tez, with transactional tables enabled by default.
Barbarian's integrated Ignite in-memory distributed parallel filesystem is resilient to node failure with replication enabled by default.
Barbarian has no single points of failure.
Barbarian is offered with the Apache v2.0 software license.
Barbarian can be deployed to your Kubernetes cluster with just two commands:
helm repo add barbarians http://charts.barbarians.io/barbarian
helm install barbarians/barbarian
This repo contains the configuration files and build scripts for the Barbarian Hadoop Distribution ZooKeeper container image.
The latest release of the ZooKeeper container image is based on the following Apache Foundation software releases:
- Apache Zookeeper 3.5
| Release | Notes |
|---|---|
| 0.1 | Prelease 1 |
| 0.2 | Barbarian Data System r2 |
| -- | -- |
See .codefresh
This image is designed to be run as a part of the Barbarian Hadoop distribution - a Kubernetes based platform for data processing at scale, founded on free software developed by the Apache Software Foundation.
The image includes support for the following features:
- Zookeeper
- Zookeeper health check monitoring
- Loadbalancer-based client access
- Pod anti-affinity