/3blades

:control_knobs: 3Blades entry point.

BSD 3-Clause "New" or "Revised" LicenseBSD-3-Clause

slack in

3Blades

Overview

3Blades meta package for installation and docs.

3Blades was born to accelerate modern data science. Import data, use Notebook servers for exploratory data analysis, create visualizations and publish trained machine learning models as RESTful endpoints in their native languages. All from one location!

There are two options available:

  • Online: free signup and no credit card required.
  • On-premise: free community version available. Pro version adds more goodies and support services.

And yes, 3Blades is open source, BSDv3 licensed!

Some features...more to come!

  • A quick way to manage Notebook servers among team members.
  • Connect to a variety of data source containers, including Spark, either as local containers or via SSH.
  • Automate common tasks with cron jobs, such as train/test splits.
  • Publish trained models as RESTful APIs, secured with user API tokens, in their native language.
  • Create and share visualization dashboards to tell your data story.

We would love to hear from you if you have a feature request. If you have something in mind, feel free to open a feature request in our roadmap repo.

Repos

Main frontend and backend will be merged into one repo, once rewrite has been completed. For now, they are maintained independently:

Other software artifacts:

  • Log service: obtaines and optionally exports syslogs from docker containers. Also used for log streams in UI.
  • NBViewer: for .ipynb shares.
  • Notifications service: updates service and container statuses.
  • Reverse proxy: used to route traffic correctly to each micro service and user server environments.
  • Statistics service: used to log basic run stats for user services (stop/start datetimes, file outputs, etc).

User container servers:

  • Core server: parent server for job-server, model-server and notebook-server.
  • Job server: server to run scheduled jobs, useful for recurring and batch processes.
  • Model server: server to publish models as RESTful endpoints, in their native language.
  • Notebook server: notebook server used for exploratory data analysis.

Infrastructure elements:

  • Docker Swarm
  • NFS
  • PosgreSQL
  • Redis
  • RabbitMQ
  • SMTP

Currently we are using AWS to manage as many of the above services as possible.

  • Compute: EC2
  • Networking: VPC
  • PosgreSQL: RDS
  • Redis: Elasticache
  • Storage: EBS, S3, EFS
  • SMTP: SES

Other services:

RabbitMQ: CloudAMQP

DevOps

## Documentation

Copyright and license

Copyright © 2016-2017 3Blades, LLC. All rights reserved, except as follows. Code is released under the BSD 3.0 license. The README.md file, and files in the "docs" folder are licensed under the Creative Commons Attribution 4.0 International License under the terms and conditions set forth in the file "LICENSE.docs". You may obtain a duplicate copy of the same license, titled CC-BY-SA-4.0, at http://creativecommons.org/licenses/by/4.0/.