A practical guide to Docker and µService: What you need to know to avoid suffering
You *never* know when or where something will break when it comes to updating a software stack, but one thing is certain: It *will* break! Here, Davide Fiorentino lo Regio shares a few solutions on issues like unconnected servers, vLAN issues and more “so that others don’t have to suffer like I did!”
It takes months to update everything in a software stack and you *never* know when or where something will break (but you *know* it will). Sounds familiar?
In this session, Davide Fiorentino lo Regio goes over what tools and technologies that he used in order to build a stable and reliable environment of Web and Standalone Applications. He dives into dockerizing applications, managing images, system configurations, experimental features as well as running and scaling those containers.
Here’s what he learned during that long journey, whether it’s how to talk with all the stakeholders involved or how to split a monolith from an architectural/deployment point of view.
Along the way, he ran into many obstacles. Some people were unaware of existing and future issues, others had superficial or no knowledge at all of those “alien” tools. Other hurdles included vLANs issues, unconnected servers, and even people asking for Docker images for everything. He shares with us the solutions to these issues and more “so that others don’t have to suffer like I did!”