[dkarapetyan]

dockbit looks pretty interesting. The one thing that is always unclear about services like yours is how well it scales to hundreds of servers and how it integrates with other orchestration mechanisms/tools like fabric, salt, awscli, and other custom services and tools. I'd be interested in knowing more about how you're approaching that aspect since most places re-invent the same things over and over again internally.

The other issue is that what happens when you have downtime? Is my deploy train stopped because of it? How do I design things so that even though I use your service I still have fallback mechanisms?

[tair]

We're not PaaS and not hosting anything, only orchestrating, so scaling is not our biggest concern right now. All the integrations are run in one-off Docker containers, which we're managing in our internal Docker cluster. Up until now we've been adding integrations ourselves, but the plan is to open-source our integration framework and let anyone add support for their tools. It's going to be quite easy, we will most probably require only Dockerfile and a metadata file for us to build the pipeline UI.

Answering your downtime question, sure we will provide plans with SLAs and multi-AZs, but basically it's a similar situation when repository hosting provider, DNS, container registry, or another infrastructure service is unavailable. That being said, we'll definitely think of a way to provide a fallback mechanism. Thank you!