# Introducing MLDOCK 🎉

As Data Scientists, docker can be both a huge enabler and a huge headache. And if you're developing machine learning with a goal of deploying to production, you might find that MLOps and Data Ops take up a huge chunk of your time.

Questions like .. "Which server, where to serve, how to maintain the code, how to maintain the model..." become huge set of hurdles to overcome. Nevermind the challenges of validating experiments, analyzing performance and generating insights for better algorithms. 🔬

That is why we built MLDOCK. To support the development of machine learning and enable you to get more models to production, faster and easier. AT MLDOCK our goal is to provide tools that help you "Build local, Deploy everywhere". 🐳, so that you:

  • ✔️ Spend more time validating ⚖️, experimenting ⚗️ and getting new features in to production :
  • ❌ lose far less hours ⏱ struggling with bash scripts
  • ✔️ Combine MLDOCK with any open-source platform or tool 🔨 to achieve your Machine learning goals 🎯.
  • ❌ lose far less energy ⚡️ wrangling your machine learning assets.
  • ✔️ Think less about docker 🤔, push ⬆️ ☁️ more models to production.
  • ❌ use far less effort 💪 converting development code in to code that runs in production.

# Where does MLDOCK fit in?

Below are the typical components of the production machine learning workflow.

ml-development-workflow

MLDOCK focuses on the problems associated with building an ML container and deploying it. This is achieved by providing a development environment where you can iterate in developing the training and prediction code. And then when you're happy, MLDOCK provides tooling to build and push your MLDOCK model container to the cloud container registry of your choice.

ml-development-workflow

MLDOCK supports this movev from build to deploy by providing:

  1. Quick start container templates (red)
  2. Docker-based development (blue)
  3. Cloud SDK enabled to interact with cloud registry (yellow)

mldock features development phase

A key thing to note is that development (shown blue) is an iterative process. Where tweaking your scripts to work may mean building and running many times. But no worries, MLDOCK is here to make it as painless as possible.

# Develop locally, deploy Everywhere

We focused on build local first approach. Starting with a command line tool that uses the docker engine and tools but packs in ml focused conveniences so you don't have to write any new bash commands and code.

build-with-mldock