Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Tutum & Docker: Run, Container, Run

DZone's Guide to

Tutum & Docker: Run, Container, Run

Tutum (latin for safe/secure) is a Docker hosting platform for running containers in any cloud. Hear the story of how it began and how they joined the Docker organization.

· Cloud Zone
Free Resource

Are you joining the containers revolution? Start leveraging container management using Platform9's ultimate guide to Kubernetes deployment.

Today I’m thrilled to announce that Tutum and Docker are joining forces. To anybody that has been following these companies, the announcement may not come as a surprise. After all, the two teams are truly a match made in container heaven.

The Journey Thus Far

It’s hard to determine exactly when Tutum started.

Tutum (latin for safe/secure) was first conceived the Fall of 2012, as part of my graduate studies and master thesis at Carnegie Mellon University (Pittsburgh) and University of Hyogo (Japan). Tutum was then a security decision support system to help enterprises transition to the cloud securely.

In the Spring of 2013 we were given the opportunity to kickstart the project by Startup Chile. During this time we developed technology to test, measure and optimize the scalability and resiliency of applications in cloud environments. It was then we first learned about, and fell in love with Docker (v0.3).


The founders – who have been friends since elementary school.

In September of 2013, the founding team moved to Buenos Aires to participate in NXTP Labs. Buenos Aires, with its beautiful tree-lined streets, vibrant nightlife, and world-renowned beef, provided us with ample energy to bring Tutum to fruition. It was in the Argentine Capital, over a bottle of Malbec, that the team decided to go all-in with Docker (v0.6.3).

We envisioned a world where developers would be empowered to easily run any code, on any server, anywhere. Back then, PaaS (Platform-as-a-Service) solutions were simple but very constraining; IaaS (Infrastructure-as-a-Service) solutions were flexible, but complex to use. The team saw in Docker the opportunity to build a service both simple and flexible – the best of both PaaS and IaaS.

With a private beta and the world’s first Docker container scheduler fully functioning by December of 2013, our plans were quickly materializing. We soon arrived in New York City to participate in Techstars in the Spring of 2014. While not the most affordable city, NYC is a fantastic place to be for a startup. If like us, you’re working nights and weekends, you won’t have any problems getting your daily dose of freshly made [insert favorite food here], or finding an open gym to relieve stress at 4AM. Plus sharing a tiny apartment in Manhattan with your team is an unforgettable bonding experience unlike any other.


Tutum booth during Techstars Demo Day in NY.

After Techstars, the team established offices in New York City and Madrid. We raised a seed round of financing from supporting and inspiring investors (led by RTP Ventures andAzure Capital). The funding enabled us to focus on delivering the best product and experience to the thousands of developers from around the World that had signed up for our beta.

The team started growing very fast – before we knew it we had already doubled in size. This truly was the best team a founder could ever ask for. Together we’ve accomplished a tremendous amount. Since making Tutum publicly available less than a year ago, Tutum has successfully provisioned and scheduled over a million containers, for tens of thousands of users, across tens of thousands of servers running Docker. Tutum has become the best place to quickly and easily deploy and manage distributed applications across any infrastructure.

Picture
First biannual company retreat. Not in this picture: Maxime Heckel and Francisco Miranda.

Why Docker?

Over the past 2 years, there was never a doubt in our minds that we made the right decision in choosing Docker container technology to deliver our vision. Docker has built a truly transformational technology. From enabling developers to focus on their code, to empowering operations to be more efficient – in every engineer’s lifetime there will be a fundamental shift in perspective “before Docker” and “after Docker”.

But it’s not only about the technology. For Tutum, Docker is also about the community. Being one of the very first adopters, we’ve seen the community grow from just 5 players in the entire ecosystem to what it has become today. The willingness and selflessness with which the Docker community contributes to open-source is unlike anything we’ve seen. And from the awe in the face of a developer after their first “docker run…”, to the thousands of Docker open source projects available today from the community, the passion and admiration that this technology stirs up in every engineer is unquestionable.


Ben, Borja, Fernando and Solomon after the first DockerCon in San Francisco.

There is also the culture. Back during the Fall of 2013, the team at Docker reached out to us to chat about what we were building at Tutum. They wanted to understand our use case and how we were using Docker, as well as any issues we were facing. Seldom would anyone run into a company that is more passionate about learning and understanding their user’s needs, while solving hard technical problems, than Docker. The honesty and humility with which we were welcomed in each and every interaction with the Docker team from thereon was inspiring. Since the day we met, long before Docker was on the tip of everyone’s tongue, they encouraged us to build amazing technology ourselves.

The technology, the community, and the culture were all factors that positively influenced our decision to join forces with Docker. But above all those, there was the vision. It quickly became apparent that both companies were working towards the same unified vision.


Tutum joins the Docker family.

What’s next?

As part of Docker, the Tutum team will continue working on our shared vision and building technology to run any code, on any server, anywhere.

We are extremely happy with the results obtained during the beta of Tutum and the reception has surpassed any initial expectations. During the past 12 months, Tutum has become an essential part of the toolkit for thousands of developers and ops around the globe. Today the service enables teams of all sizes to quickly go from code to production, with built-in capabilities to build, test, deploy and manage any distributed application on any infrastructure. We’d like to take this opportunity to thank each and every one of our beta users for their support and feedback, which has proven invaluable in building Tutum.

As an engineering-led team, we’ll never stop improving the product with new and exciting features, many of which are already in the pipeline. But the true source of Tutum’s inspiration lies in its users. We’ve heard the requests to come out of beta loud and clear and our focus is to do so, while expanding the current integrations that we have with Docker Hub.

So, what does this mean for Tutum users?

It is all great news. Docker is fully embracing Tutum and its vibrant community. Together we’ll continue to innovate and advance the technology to build, ship and run your applications. Product development of Tutum will be accelerated with the help of the amazing engineering talent at Docker and thanks to the acquisition we are now better prepared to support each and every customer.

Once again, we thank all of our users and everyone who has helped us get here. We couldn’t have done it without you.

Stay tuned for more, we’re just getting started ;)

¡Saludos!

The Tutum Team

Additional Links:

Using Containers? Read our Kubernetes Comparison eBook to learn the positives and negatives of Kubernetes, Mesos, Docker Swarm and EC2 Container Services.

Topics:
docker ,cloud

Published at DZone with permission of Bryan Lee, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}