Jenkins is, by far, the most used CI/CD tool in the market. That comes as no surprise since it’s been around for a while, it has one of the biggest open source communities, it has enterprise version for those who need it, and it is straightforward to extend it to suit (almost) anyone’s needs.
Viktor Farcic
Senior Consultant @ CloudBees, Barcelona, Barcelona Spain
"Viktor Farcic is a Senior Consultant at CloudBees and member of the Docker Captains group. He coded using a plethora of languages starting with Pascal (yes, he is old), Basic (before it got Visual prefix), ASP (before it got .Net suffix), C, C++, Perl, Python, ASP.Net, Visual Basic, C#, JavaScript, Java, Scala, etc. He never worked with Fortran. His current favourite is Go. His big passions are Microservices, Continuous Integration, Delivery and Deployment (CI/CD) and Test-Driven Development (TDD). He often speaks at community gatherings and conferences (latest can be found here). He wrote The DevOps 2.0 Toolkit: Automating the Continuous Deployment Pipeline with Containerized Microservices and the Test-Driven Java Development books. His random thoughts and tutorials can be found in his blog TechnologyConversations.com."
Website: https://technologyconversations.com
Information
Expertise
Orchestration (specifically Swarm Mode)
Docker for Mac
Docker for Windows
Docker for AWS
Docker for Azure
Networking
Programming Languages
Go
Java
Javascript
Scala
Operating Systems
Linux
Mac
Available For
Speaking Opportunities
Guest Blogging
Consulting
Blog Posts by Viktor Farcic
This article is part of the series that compare Kubernetes and Docker Swarm features.
Both Kubernetes and Docker Swarm have Ingress, and it might sound compelling to compare them and explore the differences. While that, on the first look, might seem like a right thing to do, there is a problem. Ingress works quite differently across the two.
This article is part of the series that compare Kubernetes and Docker Swarm features. Kubernetes Pods, ReplicaSets, And Services Compared To Docker Swarm Stacks Kubernetes Deployments Compared To Docker Swarm Stacks Kubernetes Ingress Compared To Docker Swarm Equivalent If you already used Docker Swarm, the logic behind Kubernetes Deployments should be familiar. Both serve the…
Starting from this article, we’ll compare each Kubernetes feature with Docker Swarm equivalents. That way, Swarm users can have a smoother transition into Kubernetes or, depending on their goals, choose to stick with Swarm.
isolated and immutable. Isolation provides reliability. Isolation helps with networking and volume management. It avoids conflicts. It allows us to deploy anything, anywhere, without worrying whether that something will clash with other processes running on the same server. Schedulers, combined with containers and virtual machines, provide the ultimate cluster management nirvana. That will change in the future but, for now, container schedulers are the top of the engineering accomplishments. They allow us to combine the developer’s necessity for rapid and frequent deployments with sysadmin’s goals for stability and reproducibility. And that leads us to Kubernetes…
The article that follows is an extract from the last chapter of The DevOps 2.2 Toolkit: Self-Sufficient Docker Clusters book. It provides a good summary into the processes and tools we explored in the quest to build a self-sufficient cluster that can (mostly) operate without humans. We split the tasks that a self-sufficient system should…
