TimeBase CE

Business Problem

Time-series data is foundational to both buy-side and sell-side financial services firms. The need for time-series data management systems is well understood and is well-served by products provided under commercial licenses. There are also many open-source time-series data systems but their uptake in financial services firms is less extensive, possibly due to insufficient performance and scalability or lack of appropriateness for financial services time-series data. There is constant demand to reduce total cost of operating technology stacks, whilst at the same time implementing changes to serve new opportunities or meet new obligations. Implementing change in a cost-effective manner has led to an increase in the use of cloud and open-source technologies, and less of a “one size fits all” approach.

Proposed Solution

Having been battle-tested in trading firms for over 10 years under a commercial license, TimeBase is now offered under an open-source license as TimeBase Community Edition”. TimeBase Community Edition was designed from inception for managing time-series data found in financial services.

The goal is to provide enterprise grade time-series data management and messaging capability which enables financial services firms to use with other open-source and commercial components to augment existing solutions, create new solutions.

TimeBase can be used, simultaneously, as a traditional time-series database and real-time data messaging/streaming server. Data structures (“streams”) are user-defined. There is a rich API for interacting (ingesting, streaming) with TimeBase, which provide the necessary hooks for data population and data utilization.

FINOS TimeBase CE Resources

Episode	Description
	Leveraging TimeBase Community Edition event-oriented time-series database to PowerCloud hosted analytical application.
	In this session, Matt will talk about TimeBase Community Edition and how the Open Source Community can leverage this technology to build their own analytical models, data visualizations, and unique applications.

Current State

History:

• 2006 – Timebase 1.0 (historical data analytics, SQL)
• 2010 – Timebase 2.0 (timeseries data base, live streaming)
• 2015 – Timebase 5.0 (Very large databases, HDFS)
• 2018 – IPC/UDP low latency mode (Timebase topics)
• 2019 – Cloud support (REST/WS, Docker, Kuber)
• 2021 – Timebase 6.0 Community Edition (open source)

Roadmap

1. Replace Apache Tomcat
2. TimeBase Cluster
3. NIO Support for network layer

Existing Materials

• TimeBase repository
• Web site
• Documentation

Build

Build the project with Gradle using this build.gradle file.

You will require the Java 11+ to build TimeBase:

Full clean and build of all modules

    $ ./gradlew clean build

Run

Start TimeBase using Docker

docker run --rm -d \
    -p 8011:8011 \
    --name=timebase-server \
    --ulimit nofile=65536:65536 \
    finos/timebase-ce-server:6.1

Usage example

https://kb.timebase.info/community/development/libs

Releases

The following file lists known Timebase CE vulnerabilities:

https://github.com/finos/TimeBase-CE/blob/main/CVE.md

Contributing

1. Fork it (https://github.com/finos/TimeBase-CE/fork)
2. Create your feature branch (git checkout -b feature/fooBar)
3. Read our contribution guidelines and Community Code of Conduct
4. Commit your changes (git commit -am 'Add some fooBar')
5. Push to the branch (git push origin feature/fooBar)
6. Create a new Pull Request

NOTE: Commits and pull requests to FINOS repositories will only be accepted from those contributors with an active, executed Individual Contributor License Agreement (ICLA) with FINOS OR who are covered under an existing and active Corporate Contribution License Agreement (CCLA) executed with FINOS. Commits from individuals not covered under an ICLA or CCLA will be flagged and blocked by the FINOS Clabot tool. Please note that some CCLAs require individuals/employees to be explicitly named on the CCLA. The EasyCLA bot will monitor all pull requests to ensure compliance.

Need an ICLA? Unsure if you are covered under an existing CCLA? Email [email protected]

Development Team

• Stuart Farr - Business
• Matthew Gorelik - Product Manager
• Aliaksei Vavilov - Delivery Manager
• Alex Karpovich - Chief Solution Architect / Main Developer / Maintainer
• Alexei Osipov - Solution Architect / Main Developer
• Andy Malakov - Solution Architect
• Raman Kisel - Backend Developer
• Daniil Yarmalkevich - Backend Developer
• Maxim Gadalov - Backend Developer
• Dzmitry Barkouski - Front-end Developer
• Vitalii Zavarskii - Front-end Developer
• Maksim Samusenka - Solution Architect (Integrations)
• Eugene Karankow - Backend Developer (Integrations)
• Polina Gurinovich - Front-end Developer (Integrations)
• Aliaksei Strakh - QA Automation
• Sergei Remsha - Technical Writer

License

Copyright © 2021 EPAM Systems, Inc.

Distributed under the Apache License, Version 2.0.

SPDX-License-Identifier: Apache-2.0