Skip to content
leo_gateway handles user’s requests. It can speak both of original REST-API and S3-API.
Erlang Logos Other
Pull request Compare This branch is 105 commits ahead of develop.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
include
priv
snmp
src
test
.gitignore
.travis.yml
LICENSE
Makefile
README.md
cuttlefish
dialyzer.ignore-warnings
rebar
rebar.config
rebar.config.develop

README.md

leo_gateway

Build Status

Overview

  • leo_gateway, LeoGateway is one of the core components of LeoFS. Main roles are described below.
  • The detail document is here.
  • leo_gateway uses rebar build system. Makefile so that simply running "make" at the top level should work.
  • leo_gateway requires Erlang R16B03-1 or later.

Architecture

LeoGateway consists of the fast HTTP-Server - Cowboy, the API handler and the cache mecanism. It provides the REST-API and Amazon S3-API. You’re able to easily access LeoFS with S3-Clients such as s3cmd, DragonDisk, program languages - Erlang, Java, Ruby, Python, Go and so on.

leo_gateway_architecture

A client requests an object or a bucket operation to LeoGateway then LeoGateway requests the message of operation to a storage-node.

A destination storage node is decided by the routing-table. It is called RING, routing-table which is generated and provided at LeoFS Manager and which is based on consistent-hashing.

Also, LeoGateway provides built-in support for the object-cache mechanism in order to realize Keeping high performance and reduction of traffic between LeoGateway and LeoFS Storage.

Sponsors

LeoProject/LeoFS is sponsored by Rakuten, Inc. and supported by Rakuten Institute of Technology.

Something went wrong with that request. Please try again.