DL-29: The merge PR script should delete branches once the PR are merged

Author: Sijie Guo <sijieg@twitter.com>

Reviewers: Franck Cuny <franck.cuny@gmail.com>

Closes #24 from sijie/sijie/fix_merge_script
1 file changed
tree: e0f0b5fbe951182e675b46938d1c1f2b685cbe6b
  1. distributedlog-benchmark/
  2. distributedlog-client/
  3. distributedlog-core/
  4. distributedlog-example/
  5. distributedlog-protocol/
  6. distributedlog-service/
  7. distributedlog-tutorials/
  8. docker/
  9. docs/
  10. scripts/
  11. src/
  12. vagrant/
  13. .gitignore
  14. .travis.yml
  15. ChangeLog
  16. CONFIG.ini
  17. Dockerfile
  18. LICENSE
  19. NOTICE
  20. pom.xml
  21. README.md
  22. Vagrantfile
README.md

Build Status Coverage Status

Overview

DistributedLog (DL) is a high-performance, replicated log service, offering durability, replication and strong consistency as essentials for building reliable distributed systems.

High Performance

DL is able to provide milliseconds latency on durable writes with a large number of concurrent logs, and handle high volume reads and writes per second from thousands of clients.

Durable and Consistent

Messages are persisted on disk and replicated to store multiple copies to prevent data loss. They are guaranteed to be consistent among writers and readers in terms of strict ordering.

Efficient Fan-in and Fan-out

DL provides an efficient service layer that is optimized for running in a multi- tenant datacenter environment such as Mesos or Yarn. The service layer is able to support large scale writes (fan-in) and reads (fan-out).

Various Workloads

DL supports various workloads from latency-sensitive online transaction processing (OLTP) applications (e.g. WAL for distributed database and in-memory replicated state machines), real-time stream ingestion and computing, to analytical processing.

Multi Tenant

To support a large number of logs for multi-tenants, DL is designed for I/O isolation in real-world workloads.

Layered Architecture

DL has a modern layered architecture design, which separates the stateless service tier from the stateful storage tier. To support large scale writes (fan- in) and reads (fan-out), DL allows scaling storage independent of scaling CPU and memory.

Documentation and Getting Started

Getting involved

We feel that a welcoming community is important and we ask that you follow Twitter's Open Source Code of Conduct in all interactions with the community.

Authors

Thanks for assistance and contributions:

A full list of contributors can be found on GitHub.

License

Copyright 2016 Twitter, Inc.

Licensed under the Apache License, Version 2.0: http://www.apache.org/licenses/LICENSE-2.0