If you're working on cloud-native apps and containers, you probably already noticed that, amid all features that containers offer, they added somehow a new later of complexity to the development workflow! We spend a great amount of time building container images, pushing them across registries, updating Kubernetes manifests, redeploying the
How many times did you run a desktop application in containers?! probably never, or the idea could've crossed your mind few times before at most. We all used and familiar with using containers to run different non-UI and headless applications and environments. But I never thought I'll need such a
There are considerable benefits of using, building and deploying small container images (small attack surface, faster updates, less network costs ...), and when it comes to lightweight distributions, Alpine Linux is by far the favorite choice. However, Java developers might find issues while running their containerized applications on alpine as stated
While admitting all the goodness it offers, Java developers still args that containers added a new layer of abstraction and made local development a bit more difficult: Writing a Dockerfile, setting up Docker daemon, waiting for builds to complete, fixing errors if any, then finally get our new unit of
Containers are nowadays everywhere. In this day and age, either you're using Docker or considering adopting it. Containers are lightweight and provide a consistent & portable software environment for applications to easily run and scale anywhere. They've made a huge impact on the way we architect, develop and ship our software.