Purpose Built for Microservices
and Distributed Applications
Bigstep Container Service offers the ideal environment for building production-ready distributed applications based on Docker. It enables users to manage fleets of interconnected containers on a scalable, single-tenant bare-metal cluster that offers the lowest latency and the best performance-to-price ratio available on the market.
High Availability and Fault Tolerance
Every time faults are detected, the system recovers by immediately spawning the application in another container.
We use automation so you don't have to do anything manually. There is no host OS and no Docker platform to manage.
Applications that require low latency can benefit from our container service since it runs exclusively on a highly optimized bare metal infrastructure.
Databases are equally at home on our platform. Our Shared Drive enables not only persistent volumes but also sharing of data across containers.
All users have access to their own real-time containers and a set of physical servers that are assigned to a single user at a time.
High Consolidation Ratios
It is you rather than the cloud provider that gains the benefits of consolidating multiple containers on the same physical machines.
Frequently Asked Questions
Do I have access to the underlying hosts?
No, the hosts are under Bigstep’s automated management. However, you can choose the hardware configuration as well as add and remove nodes in the cluster.
How do I set up load balancing?
Enabling a service port to container port mapping on a ContainerArray enables round-robin load balancing on the respective service port that works for both TCP and UDP protocols. Check out the Technical Overview document for more details.
How does Bigstep handle networking?
We use our state-of-the-art Layer 2 network to add the physical interface to the docker bridge and we manage the cluster-wide IP allocation scheme, which enables direct container-to-container communication. This enables bare-metal bandwidth and latencies.
I typically use normal operating systems such as apt-get install in VMs. Why should I switch?
If your application is very simple and drives low traffic, you might not get much benefit out of containers but, in the majority of cases, applications tend to have multiple interconnected components, and managing all of them without some sort of automation is very risky.
What is a ContainerArray?
A ContainerArray is a group of identical Containers spawned from the same Docker image, that behaves the same; it can be identified through the service discovery mechanism and can do load balancing.