TimeBase Community Edition (WIP)

[stuartfarr]

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.

Current State

Summarize the history and current state of the project

Existing Materials

If materials already exist, provide a link to them that Foundation staff can access - if it's in a private GitHub.com repositories, you should invite the finos-admin user with R/O permissions to those repositories

Development Team

List out all of the current team members, including full name, affiliation, work email address, and GitHub.com username

Contribution process

Below is the list of tasks that FINOS Team and the contribution author go through in order to complete the FINOS contribution process.
Please do not edit these contents at contribution time!

FINOS Contrib POC

• Identify and Assign FINOS Contrib POC - James McLeod - @mcleo-d

Identify project meta (Lead: FINOS Contrib POC, Support: FINOS Marketing)

• Project Name
  • Assess current trademark status - @stuartfarr - Does Timebase CE have an existing trademark?
  • Define new project name (if applicable) - The project name has been confirmed as Timebase CE
  • Design new project logo (if applicable) - The existing project logo is demonstrated on https://timebase.info/ and in the comments below ... TimeBase Community Edition (WIP) #70 (comment)
  • Trademark new project name and logo (if applicable) - @stuartfarr - Is Timebase CE trademarked as a project name?
• Category and sub-category (for FINOS Landscape) - Timebase CE should be added to the models category of the FINOS Landscape - http://landscape.finos.org/
• Existing code or new Github repository - Timebase CE has an existing GitHub repository as demonstrated in comment TimeBase Community Edition (WIP) #70 (comment)
• Existing code releases (and which artefact repositories are used) - @avavilau to confirm with @maoo via @mcleo-d - see comment TimeBase Community Edition (WIP) #70 (comment)
• Team composition: lead maintainer and other maintainers - Timebase CE maintainers are @avavilau and @alex-karpovich as highlighted below
• Meetings (existing/yes/no) - no
• Meeting minutes, agenda, attendance tracking (existing/yes/no) - no // possible future scenario
• Continuous Integration (existing/yes/no) - yes - To be discussed with @avavilau and @maoo
• Documentation website (existing/yes/no) - yes - Currently exists as markdown and integrated into https://timebase.info/

Maintainers, contributors and CLAs (Lead: FINOS Contrib POC, Support: FINOS infra)

• For each maintainer identified in the previous step, collect: the following info:
  • TimeBase CE Lead Maintainer
    • Full name : Aliaksei Vavilau
    • GitHub username : @avavilau
    • Corporate email address : Aliaksei_Vavilau@epam.com
  • TimeBase CE Maintainer
    • Full name : Alex Karpovich
    • GitHub username : @alex-karpovich
    • Corporate email address : Aliaksandr_Karpovich@epam.com
• Identify other existing contributors (assuming there's a contribution history (eg Git history) - Project contributors all from EPAM Timebase team
• Check if maintainers and other contributors are all covered by FINOS CLA
• Engage with FINOS Legal team to figure out what’s needed to cover all maintainers and contributors with FINOS CLA
• Reach out to contributors and employers to coordinate CLA signatures - EPAM CCLA Status - https://github.com/finos/metadata/pull/732
• Invite GitHub usernames to GitHub FINOS Org - https://github.com/finos/metadata/issues/761
• Create <project-name>-maintainers GitHub team and invite users - https://github.com/finos/metadata/issues/762

Code validation (only if code is contributed) (Lead: FINOS Infra)

• The codebase doesn’t have HIGH or CRITICAL CVEs across direct and transitive libraries
• The codebase doesn’t have any unfriendly licenses across direct and transitive libraries
• (optional - if a build system is provided) The build process runs successfully
  • finos-admin is Admin of the GitHub repository to transfer
• The codebase doesn’t include any patent or copyright that conflicts with FINOS Governance and bylaws (to be validated with FINOS Legal team)
• The codebase complies with FINOS Project Blueprint
• All incubating criteria are checked and documented below

Voting (Lead: FINOS Infra)

• Assign issue to @mindthegab to trigger voting
• FINOS accepts the contribution (and the contribution process can move forward)

Code transfer (Lead: FINOS Infra)

• Rename https://github.com/epam/TimeBase to https://github.com/epam/TimeBase-CE
• Check GitHub repository transfer requirements:
  • finos-admin has Admin to all repositories to transfer
  • finos-admin ia allowed to transfer repositories out of the org
  • if the repository is owned by a user (and not an org), the user must be able to transfer the repository to finos-admin
• Transfer all code assets as GitHub repositories under github.com/finos
• Enable CLA Bot
• Alex - Merge project blueprint files from https://github.com/finos/timebase-ce to https://github.com/epam/TimeBase
• Alex - Update README.md to comply with template https://github.com/finos/software-project-blueprint/blob/main/README.template.md
  • Update project badge - Added by @mcleo-d Update Timebase Project README TimeBase-CE#175

Announcement (Lead: FINOS Contrib POC)

• Work with FINOS marketing to send out announcement to community@finos.org , checkout announcement template on https://finosfoundation.atlassian.net/wiki/spaces/FINOS/pages/83034172/Contribute
• Coordinate social media promotion with FINOS marketing
  • Post on FINOS social media
  • Post on LF social media
• EPAM to deliver SVG logo with TimeBase CE underneath, based on this template - https://github.com/finos/finos-landscape/blob/master/hosted_logos/git-proxy.svg
  • Added by @mcleo-d here https://github.com/finos/branding/blob/master/project-logos/active-project-logos/Timebase/timebase-logo-upright.svg

Infra setup (Lead: FINOS Infra)

• maoo - Delete https://github.com/finos/timebase-ce-tmp
• Add project to metadata
• Add identities, orgs and affiliations to metadata
• Add logo to FINOS landscape - Added by @mcleo-d to https://github.com/finos/branding/tree/master/project-logos/active-project-logos/Timebase
• Add project maintainers emails to finos-project-maintainers@finos.org list (Added Alex)
• Add project maintainers GitHub usernames to the project-maintainers Team
• Enable security vulnerabilities scanning (WhiteSource)
• Enable meeting attendance tracking

First Release

• Alex and mao - discuss about first public release
  • Update release coordinates to include finos

Onboarding and training

• Enable EasyCLA, disable CLA Bot
• FINOS Project Governance
• FINOS Project Lifecycle
• ODP Training

[avavilau]

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)​
2020 – Timebase 6.0 Community Edition (open source) and Clustering

TimeBase 6.0 is currently in progress, we are in the middle of moving project and CI/CD to GitHub from private repository.
Many TimeBase 6.0 features and many public materials are also work in progress

[avavilau]

Existing Materials:

• TimeBase repository
• Web site
• Documentation (work in progress)

[avavilau]

Development Team:

https://github.com/stuartfarr - Business
https://github.com/avavilau - Delivery Manager
https://github.com/alex-karpovich - Chief Solution Architect / Main Developer
https://github.com/alexei-osipov - Solution Architect / Main Developer
https://github.com/andymalakov - Solution Architect
https://github.com/Romkisel - Backend Developer
https://github.com/ypldan - Backend Developer
https://github.com/Maxim-Gadalov - Backend Developer
https://github.com/sizmestiev - C++ Developer
https://github.com/MitoZ - Front-end Developer
https://github.com/msamusenka - Solution Architect (Integrations)
https://github.com/ekarankow - Backend Developer (Integrations)
https://github.com/PolinaGurinovich - Front-end Developer (Integrations)
https://github.com/astrakh - QA Automation
https://github.com/sr-remsha - Technical Writer

[avavilau]

Contribution process

Contribution guidelines are work in progress and not yet defined.

[ColinEberhardt]

Thanks for raising this contribution proposal, TimeBase looks like an interesting and useful product for the FINOS members and the wider community.

Considering that this is already a commercial product, I would be grateful if you could elaborate on the differences between the open source community edition and the paid-for enterprise version? This type of arrangement can cause conflict, you will certainly wish to retain sales of your commercial edition, and as a result, I expect that you will 'hold back' certain product features. However, for the community edition to be a success (beyond being a teaser for the commercial edition), it needs to be a well-rounded and useful product in its own right.

Can you please share your thoughts on this?

[stuartfarr]

@ColinEberhardt, thank you for question; your comment is well made. You can see the differences here. But some additional comments and context: TimeBase's original mission was (and is) to provide high performance time-series data management for systematic/algorithmic trading firms as part of larger product suite we provide. Many such firms are small and want "out of the box" capability. As such, we bundled data (ingest) connectors for many trading venues and associated market data structures (streams). These are not part of TimeBase Community Edition because we want and expect a much wider set of use-cases which may or may not need these connectors. Another piece of relevant background is that TimeBase was built by a small software company called Deltix, acquired by EPAM in February 2020. We (old Deltix) had considered making an open source contribution years before but the support of EPAM has given us the confidence to finally do it! TimeBase Community is emphatically not a teaser for the commercial product which, outside of the differences noted, is the same core engine as the enterprise edition. This is an important topic, please let me know if this comment addresses it.

[mcleo-d]

Please find the differences between Community Edition and Enterprise Edition below ...

[avavilau]

@mcleo-d repository: https://github.com/DeltixInc/TimeBase

[avavilau]

• Aliaksei Vavilau and Alex Karpovich (maintainers)
• Rest of the team as members https://timebase.info/our-team.html

[avavilau]

TB Logo: https://timebase.info/assets/img/timebase-logo-new.svg

[mcleo-d]

Hey @stuartfarr - I'm currently updating the progression of the Timebase CE project contribution and was wondering if you have an update on inviting current Timebase customers to join the project contribution?

It would be great if you could supply an update in the issue comments below.

Kind regards,

James.

[mcleo-d]

Hi @stuartfarr, @avavilau and @alex-karpovich,

Can you ask the following Timebase team members to accept their invitation to the FINOS organisation on GitHub as part of the Timebase CE project contribution 👍

• @stuartfarr
• @andymalakov
• @alex-karpovich
• @alexei-osipov
• @Romkisel
• @alexey-ban
• @bmcgreal
• @MitoZ
• @sizmestiev
• @dpoguts
• @ypldan
• @astrakh
• @Ga2nibal
• @Sergei-Y
• @msamusenka
• @Maxim-Gadalov
• @ekarankow
• @PolinaGurinovich
• @Sateviss
• @EkaterinaRunets
• @sr-remsha

Many thanks,

James 🚀

[stuartfarr]

Hey @stuartfarr - I'm currently updating the progression of the Timebase CE project contribution and was wondering if you have an update on inviting current Timebase customers to join the project contribution?

It would be great if you could supply an update in the issue comments below.

Kind regards,

James.

There are a couple of new (TimeBase CE prospects) that I hoped we would be able to, but it looks like they are going to fall into 2021 now.

[mindthegab]

Thanks @stuartfarr and the team of contributors for putting this forward. I think we should proceed with the contribution validation and onboarding, and then use the socialization phase to garner more contributors.

@stuartfarr please let us know we can help once the project is contributed. Definitely existing prospects would be a great place to start to build a community.

Thanks!

[mcleo-d]

Thanks @mindthegab - I have setup a meeting with the TimeBase team for Monday 18th January at 2:30pm GMT to move forward with next steps 👍

James.

[mcleo-d]

The following update was received from @avavilau in the Timebase team ...

• We’ve created all the repositories for all dependencies.
• We’ve ported our CI scripts from gitlab pipelines to github workflows
• We’ve started publishing artifacts to maven. (docker/artifacthub/nuget in progress)
• We still need a bit more time to finish the process.

James.

[stuartfarr]

We are pleased to announce that our friends at crypto trading technology firm mainbloq will be the first consumer of TimeBase Community Edition.

[mdvx]

Absolutely thrilled to be working with TimeBase, we have big plans for this breakthrough technology. Can't wait to get started!

[mcleo-d]

Hi @mdvx - It's an absolute pleasure to meet you and look forward to working with you and the TimeBase team when the project hits the FINOS organisation 🚀

It would be great to catch up and talk about FINOS CCLAs so we can hit the ground running. Are you okay if @stuartfarr introduces us via email?

James.

cc @mindthegab @toshaellison @maoo @cm-howard

[mdvx]

Hi James Nice to meet you, looking forward to working together. Let me also Introduce you to Clay Cowdery who will be taking an active role in this deployment. All good with Stuart doing intros. Marc From: James McLeod ***@***.***> Sent: Thursday, April 1, 2021 6:51 AM To: finos/community ***@***.***> Cc: Marc Deveaux ***@***.***>; Mention ***@***.***> Subject: Re: [finos/community] TimeBase Community Edition (WIP) (#70) Hi @mdvx <https://github.com/mdvx> - It's an absolute pleasure to meet you and look forward to working with you and the TimeBase team when the project hits the FINOS organisation 🚀 It would be great to catch up and talk about FINOS CCLAs so we can hit the ground running. Are you okay if @stuartfarr <https://github.com/stuartfarr> introduces us via email? James. cc @mindthegab <https://github.com/mindthegab> @toshaellison <https://github.com/toshaellison> @maoo <https://github.com/maoo> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#70 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAUKUF3YVTTAMPHRBTB3GPTTGRFYVANCNFSM4R45EKGQ> . <https://github.com/notifications/beacon/AAUKUF2UWTODAQD2IG5AKJLTGRFYVA5CNFSM4R45EKG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGBRXRIY.gif>

[mdvx]

Hi Guys

anybody got a URL for the docker image?

@stuartfarr @mcleo-d

[mcleo-d]

Hi @mdvx

Apologies for the time taken to respond. Let me email @avavilau and @stuartfarr to see how close the TimeBase team is to making the contribution and we'll get right back to you.

James.

[mcleo-d]

Hi @kimmolinna

Thank you for meeting yesterday and for showing your initial interest in TimeBase CE as an open source alternative to KDB.

I'd like to introduce you to @stuartfarr and the TimeBase team who I'm sure will be in touch once the project is contributed to FINOS.

Have a great weekend and speak soon.

James.

[stuartfarr]

Hi @mdvx

Contribution to FINOS should be available in next 2 weeks: we will announce accordingly.

Thanks, Stuart

[stuartfarr]

Hi @kimmolinna

You may have seen that the TimeBase Community Edition (CE) contribution to FINOS is due early may.

In case you have not seen it, the site has information on TimeBase CE. But let me know if you have any questions.

Stuart

[mcleo-d]

Following a quick review of the TimeBase project prior to FINOS contribution, the issue below describes prerequisites needed within the open source project as outlined in the FINOS Contribution Compliance Requirements document.

• FINOS Review - Contribution Compliance Requirements for FINOS Contribution TimeBase-CE#1

[stuartfarr]

Hi @mcleo-d

Duly noted: TimeBase contribution will be ready 18th May but understood that subject to vulnerability scanning etc. for which we can provide @maoo the required access to the current EPAM/TimeBase repo.

[mcleo-d]

Hi @stuartfarr,

Thanks so much for your update. This is very exciting news! 🚀

Feel free to send me a link to the main Timebase repo when the project is ready for review.

James.

[mcleo-d]

@stuartfarr has confirmed TimeBase can move to the next stage of FINOS contribution alongside the completion of finos/TimeBase-CE#1 by the TimeBase team.

[maoo]

Hi @mcleo-d and @alex-karpovich ! I've raised finos/TimeBase-CE#174 as I noticed that NOTICE file was still not correct.

Any update on the TimeBase logo, so that we can complete the project onboarding and complete the contribution process?

Thanks!

[maoo]

Quick status update - The TimeBase code is now hosted to https://github.com/finos/TimeBase-CE - congratulations to the EPAM team!

To complete the contribution process, we'd also like to:

1. solve a logo visualization issue on https://landscape.finos.org/
2. release on Maven Central and Docker (although not mandated by FINOS standard contribution process)
3. LF Onboarding (@maoo)
   1. Enable LFX EasyCLA (EPAM already onboarded on EasyCLA)
   2. LFX Insights
   3. SFDC

[maoo]

Logo is fixed, see https://landscape.finos.org/

[maoo]

Project is registered in our internal systems, releases are done (soon README will be updated with badges).

Marking contribution as done, congrats to the EPAM team for this great contribution!