Working in tech, it's not uncommon to default to navel gazing mode every now and then. Sometimes our focus can get a little too insular, so avoiding this folly requires regularly stepping out of the day-to-day grind to stay in the loop with what's happening in the Community. It's also a great way of understanding how the momentum of tech hype measures up to the reality of market adoption.
It's one of the things I really love about my job. I'm lucky in the sense that I have lots of opportunities - be it through speaking at events, hosting meetups or even via virtual gatherings, to get out there and talk to my peers. Sometimes, just providing a platform for people to simply talk about their issues and how they're attempting to tackle them can reveal a lot.
Take the example of an intro-level Docker workshop I hosted a few weeks back for beginners. As the evening progressed, I was struck by the similarities between how participants wanted to approach building their microservice architecture, and how this mirrored the practices among the vast majority of Cloud 66 for Docker users. Most of the workshop participants wanted to treat containers as a means to deploying their monolithic apps, which when compared with trends from Cloud 66 users, was pretty consistent.
In fact, roughly 70% of our customers are taking a monolithic containerization approach for multi-tenant deployments. While there's nothing wrong with that per se, it rather defeats the purpose of breaking down app components into smaller services for more agile deployments. Despite being fairly established now, it's yet another example of how technologies like Docker still require a lot of education around best-case adoption scenarios.
There's loads more we can all do in order to share best practices to help eachother get the most out of using Docker. It makes sense that not everybody has the luxury of starting with a green field project to test out their microservices architecture design choices. But only when we openly debate what it takes in a real world context to move legacy apps to microservices, can we begin to efficiently tackle the challenges of containerization.
And that's where I try and help. I'm a software developer first and foremost, but part of my role as a developer evangelist at Cloud 66 is to also share knowledge and tips for how we can improve the way we do things together. So if you're a dev who's just getting to grips with how to containerize your services using Docker, then next week's webinar session on "From Code to Docker Image" is the perfect intro.
We're hosting the webinar with our friends over at Codefresh, and you can expect me to cover pretty much all the components needed to get started with microservices, requisite dependencies you’ll need to consider and I'll even show you a practical implementation example with tips for deploying to production.
If you plan to join us, then please sign-up for the webinar and I look forward to seeing you then.