Tools to choose and use!

Most probably many of you asked yourselves: To build from scratch or Not To build from scratch?

1. - To build!
2. - Not to build!
3. - To build!
4. - Not to build!

Hmm…  Hard to decide? Take a look on the diagram and decide!

Is there any Re Use in your answer? So you are one of those lucky bastards who can relax for a while and enjoy the cocktail

Re-use in all its beauty

Distributed platforms and frameworks aka Map-Reduce:

• Apache Hadoop is an open source software for reliable, scalable, distributed computing. It is allows to use simple programming models to support distributed processing of a large data sets across clusters of computers. The main components are HDFS (distributed file system), Hadoop YARN (framework for job scheduling resource management), Hadoop MapReduce (system for parallel large data sets processing).
  
• YARN is an aka second generation of MapReduce. The main idea behind its architecture is to split JobTracker’s resource management and job scheduling/monitoring into separate daemons. So that a Global Resource Manager and per-application AppManager were represented in the system.
  Architecture:
  
• Disco Project is a framework that is based on a MapReduce paradigm. It is on open Source Nokia Research Centre project which purpose is to serve handling of massive amount of data. According to the documentation it distribubed and replicates your data, schedules your jobs efficiently. Moreover, indexing of large amount of records is supported, so that real time querying is possible.
  Architecture:
  • Master adds jobs to the job queue and run them when nodes are available.
  • Client submit jobs to the master
  • Slaves are started on the nodes by master and spawn and monitor processes.
  • Workers do the jobs. Output location is notified to the Master.
  • Data locality mechanisms are applied once results are saved to the cluster.
  
• Spring Batch is an open source framework for batch processing. It is provide development of robust batch applications. It is built on Spring Framework. It supports logging, transaction management, statistics, restart, skip and resource management. Some optimization and partitioning techniques can be tuned in the system as well.
  Architecture:
  • Infrastructure level is a low level tool. It is provide an opportunity to batch operations together and retry if an error occurred.
  • Execution environment provides robust features for tracing and management of the batch lifecycle.
  • Core module is the batch-focused domain and implementation. It includes statistics, job launch, restart.
  
• Gearman is a framework to delegate tasks to another machines and processes that are more suited for it. Parallel execution of work is supported, as well as load balancing, multi language function calls.
  Architecture:
  • A client, a worker and a job server are the parts of the system.
  • The client creates jobs and sends them to job server.
  • Job server forward tasks to suitable workers.
  • Worker works and responds to the client through job server.
  • Communication with the server is established through TCP sockets.
  

Distributed platforms and frameworks aka Directed Acyclic Graph aka Stream Processing Systems:

• Spark a system that is optimized for data analytics to make it fast both to run and write. It is suited for in-memory data processing. Api is in Java and Scala. Purpose: machine learning and data mining, also general purpose is possible. It runs on Apache Mesos to share resources with Hadoop and other apps.
  
• Dryad is a general purpose runtime for execution data parallel apps. It is modeled as a directed acyclic graph (DAG) which defines the dataflow of the application and vertices that represents the operations that should be performed on the data. However, creation of a graph is quite tricky part. That is why some high-level language compilers were created. One of them is DryadLINQ.
• S4 and Storm
  are both for real time, reliable processing of unbounded stream of data. The main difference between Storm and S4 is the Storm guarantees messages to be processes even while failures occur, and S4 supports state recovery. More in the previous post.

Distributed Data Storage(DSS): 

• Key-Value
• Column Based
• SQL
• NewSQL
• bla bla bla…
• Latency
• Consistency
• Availability
• bal bla bla…

The problem of choosing the most suitable distributed storage system is quite tricky and require some reading in the field. Some information on Storage System with their deep review, from my previous project on Decentralized Storage Systems, can be found on my wiki. Also a brief review of come hot systems are represented in my previous post.

Actor Model Frameworks:

Is a  quite old computational model for concurrent computations that consist of concurrent digital computations called actors, that can react on the received messages: make local decisions, spawn other actors, send messages and design behavior for the next message that will be received. However this framework has some issues, that should be taken into account, if the decision to use this model is made – (a) scalability, (b) transparency, (c) inconsistency.
Actor Programming Languages are Erlang, Scala and other. This is one extra motivation to get to know closer those languages.
The most popular Actor Libraries:

• Akka
  • Language: Java and Scala
  • Purpose: Build highly concurrent, distributed, fault-tolerant event-driven application on the JVM.
  • Actors: Very lightweighted concurrent entities. They process messages asynchronously using an event driven receive loop.
• Pykka
  • Language: Python
  • Purpose: Build highly concurrent, distributed, fault-tolerant event-driven application.
  • Actors: It is an execution unit that executes concurrently with other actors. They don’t share state with each other. Communication is maintained by sending/receiving messages. On message, an actor can do some actions. Only one message is processed at a time.
• Theron
  • Language: C++
  • Purpose: Build highly concurrent, distributed event-driven application.
  • Actors: They are specialized objects that execute in parallel natively. Each of them has a unique address. Communication is dome by messaging. Each actor’s behavior defined in message handlers, which are user-defined private member functions.
• S4 - more in the Stream Processing Systems section.

Scheduling and Load Balancing:

• Luigi Scheduler
  • It is a python module that helps to build complex pipelines of batch jobs. Also it builds in a support for Hadoop. It is a scheduler that is open-sourced by Spotify and used within the company.
  • It is still quite immature and anyone can try hers luck to contribute to this scheduler that is written in Python.
• Apache Oozie
  • It is a workflow scheduler system to manage Apache Hadoop jobs.
  • It is a directed acyclical graph od actions.
  • It is scalable, reliable and extensible system.
• Azkaban
  • It is a batch job scheduler.
  • It helps to control dependencies and scheduling of individual pieces to run.
• Helix
  • It is a generic cluster management framework for automatic management of partitioned, replicated and distributed resources hosted on a cluster of nodes.
  • Features: (a) automatic assignments of resources to nodes, (b) node failure detection and recovery, (c) dynamic addition of resources and nodes to a cluster, (d) pluggable distributed state machine, (e) automatic load balancing and throttling of transactions
• Norbert
  • Provides easy cluster management and workload distiribution
  • It is implemented in Scala and wraps ZooKeeper, Netty and Protocol Buffers to make it easier to build applications.
  • Purpose: (a) Provide Group Management, change configuration, add/remove nodes. (b) Partitions workload by using software load balancing. (c) Provide asynchronous client/server RPC and notifications.

Replication:

• Bucardo is an asynchronous PostgreSQL replication
• And whatever others…

Consesnsus and stuff:

• ZooKeeper and ZooKeeper made easy by Curator
• DooZerd

Log Collection:

• Apache Kafka
  Distributed Pub/Sub messaging systems that supports:
  • Persistent messaging with constant time performance
  • High-throughput
  • Explicit support for message partitioning over servers and machine-consumers
  • Support for parallel data load into Hadoop
  It is a viable solution to provide logged data to offline analysis systems like Hadoop, but it is might be quite limited for building real-time processing. The system is quite similar to Scribe and Apache Flume as they all do activity stream processing, even though that the architectures are different.
  Architecture:
  
• Logstash

Message Passing Frameworks:

• *MQ
  • RabbitMQ
  • ZeroMQ
  • Apache ActiveMQ
• MPI
• OpenMP (share resources)

(De)Serialization for sending objects in the network safely:

• Avro
  • It is a data serialization system.
  • Provides: (a) rich data structures, (b) compact, fast, binary data format, (c) container file to store persistent data, (d) integration with dynamic languages. The schemas are defined with JSON.
  • Used by Spotify
• Protocol Buffer
  • Developed and Used by Google.
  • It encodes structured data in an efficient extensible format.
• Apache Thrift
  • Purpose: scalable cross-language services deployment.

Chasing for latency:

• This is exactly what is my project about. Moreover this niche is not very well developed and only a few crazy ppl dared to touch it:
• NASDAQ OMX and their GENIUM INET Trading System
• MySQL Cluster