Skip to content
HPCC Systems big data solution, community edition
C++ ECL XSLT JavaScript Yacc C Other
Pull request Compare This branch is even with hpcc-systems:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
build_utils
charm
clienttools HPCC-13448 Source Code needs Marca Registrada next to HPCC Systems® Aug 4, 2015
cmake_modules
common
dali
deploy
deployment
docs
ecl
ecllibrary
esp Merge branch 'candidate-6.0.2' Apr 29, 2016
githooks
initfiles
lib2
misc
plugins
roxie
rtl
services Merge branch 'candidate-5.4.0' Aug 12, 2015
system
testing HPCC-15466 Regression Test Engine doesn't handle properly the test Apr 28, 2016
thorlcr Merge pull request #8590 from ghalliday/issue15486 May 4, 2016
tools
.gitattributes
.gitignore
.gitmodules
.travis.yml
BUILD_ME.md
CMakeLists.txt
CNAME
CONTRIBUTORS
FUTURE
LICENSE.txt HPCC-13448 Source Code needs Marca Registrada next to HPCC Systems® Aug 4, 2015
R-LICENSE.txt
README.md
VERSIONS Preparation for 6.0.0-beta1 release Sep 22, 2015
baseaddr.txt
build-config.h.cmake
sourcedoc.xml
version.cmake

README.md

Description / Rationale

HPCC Systems offers an enterprise ready, open source supercomputing platform to solve big data problems. As compared to Hadoop, the platform offers analysis of big data using less code and less nodes for greater efficiencies and offers a single programming language, a single platform and a single architecture for efficient processing. HPCC Systems is a technology division of LexisNexis Risk Solutions.

Getting Started

Architecture

The HPCC Systems architecture incorporates the Thor and Roxie clusters as well as common middleware components, an external communications layer, client interfaces which provide both end-user services and system management tools, and auxiliary components to support monitoring and to facilitate loading and storing of filesystem data from external sources. An HPCC environment can include only Thor clusters, or both Thor and Roxie clusters. Each of these cluster types is described in more detail in the following sections below the architecture diagram.

Thor

Thor (the Data Refinery Cluster) is responsible for consuming vast amounts of data, transforming, linking and indexing that data. It functions as a distributed file system with parallel processing power spread across the nodes. A cluster can scale from a single node to thousands of nodes.

  • Single-threaded
  • Distributed parallel processing
  • Distributed file system
  • Powerful parallel processing programming language (ECL)
  • Optimized for Extraction, Transformation, Loading, Sorting, Indexing and Linking
  • Scales from 1-1000s of nodes

Roxie

Roxie (the Query Cluster) provides separate high-performance online query processing and data warehouse capabilities. Roxie (Rapid Online XML Inquiry Engine) is the data delivery engine used in HPCC to serve data quickly and can support many thousands of requests per node per second.

  • Multi-threaded
  • Distributed parallel processing
  • Distributed file system
  • Powerful parallel processing programming language (ECL)
  • Optimized for concurrent query processing
  • Scales from 1-1000s of nodes

ECL

ECL (Enterprise Control Language) is the powerful programming language that is ideally suited for the manipulation of Big Data.

  • Transparent and implicitly parallel programming language
  • Non-procedural and dataflow oriented
  • Modular, reusable, extensible syntax
  • Combines data representation and algorithm implementation
  • Easily extend using C++ libraries
  • ECL is compiled into optimized C++

ECL IDE

ECL IDE is a modern IDE used to code, debug and monitor ECL programs.

  • Access to shared source code repositories
  • Complete development, debugging and testing environment for developing ECL dataflow programs
  • Access to the ECLWatch tool is built-in, allowing developers to watch job graphs as they are executing
  • Access to current and historical job workunits

ESP

ESP (Enterprise Services Platform) provides an easy to use interface to access ECL queries using XML, HTTP, SOAP and REST.

  • Standards-based interface to access ECL functions
Something went wrong with that request. Please try again.