This document introduces Easteros, a new forecasting analytics platform. It describes Easteros' architecture which uses cloud-based data warehouses and Hadoop clusters to run jobs. Easteros aims to provide simple gateways for users to submit and monitor jobs without needing to setup or maintain clusters. It uses a router service to automatically select clusters and submit jobs, making the big data software easier for analysts and scientists to use.
2. History
≒ No
friendly
gateways
to
access
historical
forecas3ng
snapshot
(input,
interim,
output,
etc.)
≒ No
friendly
gateways
to
submit
ad-足hoc
queries
(troubleshoo3ng)
and
new
algorithms
≒ SLA
ETLs
are
hard
to
launch
and
maintain
≒
2
3. Architecture
3
Cloud
Based
Data
Warehouse
Hadoop
(EMR)
Clusters
EASTEROS: Router
service
EASTEROS: Analy.c
Portal
/
CLI
4. Why
Easteros?
≒ Simple
gateways
for
job
submission
and
monitoring
Access
to
each
snapshot
of
pipeline
run
≒ Separate
the
big
data
soGware
stack
from
users
(analysts,
scien3sts,
retail
in-足stock
managers)
4
5. Easteros鐚Router
service
≒ Users
perspec3ve
REST-足ful
service
to
run
Hive
and
Hadoop
jobs.
Auto
select
the
proper
EMR
Clusters
based
on
cluster
load
Users
doesnt
need
to
setup
and
maintain
clusters
Sophis3cated
users
can
provide
clusters
con鍖gs
Check
job
logs
periodically
(鍖ush
to
S3
every
5
minutes)
5
6. Easteros鐚Router
service
≒ SDE
perspec3ve
Spin
up
new
clusters
automa3cally
Override
site-足speci鍖c
hive/hadoop
con鍖gura3ons
6