

Official logo of Basque Country's public health care service: Osak

256_cta-background.webp

384_cta-background.webp

640_cta-background.webp

750_cta-background.webp

828_cta-background.webp

thumbnail_cta-background.webp

osakidetza-logo

Daar hebben wij de oplossing voor

Wilt u efficiënter werken? 



Atmosphere of azure electric sky, with water, slope,

1080_background.webp

1200_background.webp

256_background.webp

384_background.webp

640_background.webp

750_background.webp

828_background.webp

thumbnail_background.webp

atmosphere-water-sky-azure-electricity-astronomical-object-slope-electric-blue

1080_zen-logo-white.webp

1200_zen-logo-white.webp

256_zen-logo-white.webp

384_zen-logo-white.webp

640_zen-logo-white.webp

750_zen-logo-white.webp

828_zen-logo-white.webp

thumbnail_zen-logo-white.webp

zen-logo-white.webp

ZEN Software

1080_zen-logo-black.webp

1200_zen-logo-black.webp

256_zen-logo-black.webp

384_zen-logo-black.webp

640_zen-logo-black.webp

750_zen-logo-black.webp

828_zen-logo-black.webp

thumbnail_zen-logo-black.webp

západoslovenská energetika-logo

Agile Analytics

Websites & Apps Development

Tech Consultancy

ZEN DevOps Accelerator

Content and Commerce at any scale

ZEN Cloud Landing Zone

What We Do

About us

News

Contact

Success! You`ve been added to our email list.

Subscribe to our email list and we will keep you updated on DevOps and ZEN Software News and Trends

Subscribe to ZEN Software's  newsletter

The Kanban game at Crunchr



People sharing table for vision-care, fashion, and fun board game

table-human-black-fashion-eyewear-vision-care-sharing-chair

The [Kanban is a game](https://getkanban.com/) for professional software organisations that teaches your teams how to work in a kanban workflow. It takes a fictional software company and puts the team at the helm of the organisation.

The game teaches you the effects of certain flow decisions in your software operations, the need for proper quality control and collaboration.

Continuous Delivery 3.0 training



"Clothing, Table, Chair service event w/ unintelligible

clothing-table-furniture-desk-conference-room-table-chair-service-event

For the 6 week long NISI training Continuous Delivery 3.0 hosted at the Universiteit Utrecht I was guest trainer for the part of Continuous Integration.

[Source: Continuous Delivery - Course — NISI - Nederlands Instituut voor de Software Industrie ](https://nisi.nl/continuousdelivery/course)

For the 6 week long NISI training Continuous Delivery 3.0 hosted at the Universiteit Utrecht I was guest trainer for the part of Continuous Integration.



From monolith to microservices using the strangler pattern

c124f787-7a87-4c74-be31-7ab9bf204292.webp

The strangler pattern is a technique from Dave Farley’s ‘Continuous Delivery’ for transforming a monolithic software system into a microservices-based architecture. It involves gradually replacing parts of a big monolithic software system with smaller microservices, thus "strangling" the monolith over time until it is completely replaced. The name ‘strangler pattern’ is derived from the strangler vine that grows on another tree, using it as physical support, while also stealing sunlight and nutrients from it, which eventually kills the host plant.

The **strangler pattern** is a technique from Dave Farley’s ‘Continuous Delivery’ for transforming a monolithic software system into a microservices-based architecture. It involves gradually replacing parts of a big monolithic software system with smaller microservices, thus "strangling" the monolith over time until it is completely replaced. The name ‘strangler pattern’ is derived from the strangler vine that grows on another tree, using it as physical support, while also stealing sunlight and nutrients from it, which eventually kills the host plant.

Here are the steps to transform a monolithic software system to a microservices-based architecture using the strangler pattern:

1. **Identify the boundaries**: The first step is to identify the distinct boundaries within the monolith system that can be broken down into separate microservices. This could be done based on business capabilities, functional domains, or technical dependencies.
2. **Define the interfaces**: Once the boundaries have been identified, the next step is to define the interfaces between the microservices and the monolith. This involves specifying the data that will be exchanged between the microservices and the monolith and the APIs that will be used for communication. (tip: employ techniques from Domain Driven Design to guide this process)
3. **Implement the microservices**: With the interfaces defined, the next step is to start implementing the microservices one by one. This involves creating a new service that implements a small part of the functionality of the monolith and defining the API that will be used for communication.


4. **Route traffic to the microservices**: The next step is to route traffic to them once the microservices have been implemented. This could be done by gradually modifying the routing rules of the monolith to send traffic to the microservices instead of the monolith.
5. **Decommission the monolith**: As more and more traffic is routed to the microservices, the monolith becomes less critical. Eventually, when microservices have replaced all the functionality of the monolith, the monolith can be decommissioned.


The strangler pattern is a gradual and iterative process; it is important to start small and focus on the most critical parts of the monolith first. Over time, more and more functionality can be migrated to microservices until the monolith is no longer needed.

The story of the Ship of Theseus is a philosophical paradox that raises the question of identity over time. The story goes that the Athenians preserved the ship of Theseus in a dock as a memorial to their hero. As the years passed, the planks of the ship began to rot and were replaced one by one until no original plank remained. **The question then arises: is the ship that remains still the ship of Theseus, or is it a new ship entirely?**

Similarly, the strangler pattern involves gradually replacing parts of a monolithic software system with microservices until the original system has been fully replaced. The question then arises: is the resulting system still the same system as the original monolith, or is it a new system entirely?

In both cases, the identity of the original entity is called into question due to the gradual replacement of its constituent parts. In the case of the strangler pattern, the resulting system is still functionally the same as the original monolith, but it has been restructured into a new architecture.

Ultimately, the Ship of Theseus story and the strangler pattern illustrate the challenges of the gradual replacement of parts of a larger system (monolith/ship). Both cases raise questions about continuity and change. The strangler pattern is the best way to de-risk an otherwise extremely risky replacement operation of a monolith. When you carefully plan what parts of the monolith migrate in which order you can safely enjoy a transformation what would otherwise caused much heartache and stress.

Guest trainer multi-cloud at Young Mavericks



Smiling people in nature enjoy their property: jeans, trousers & wheels

smile-plant-jeans-trousers-property-window-wheel-people-in-nature

As part of the Data Science trajectory at Young Mavericks, ZEN Software provided an introduction to Multi-Cloud. How can you use cloud in Data Science and what choices are there in the field of Cloud as a toolset.

Scrum Training at TextKernel



Jeans-clad event-goers having fun, adapting to the window

jeans-trousers-window-post-it-note-t-shirt-adaptation-event-fun

Happy to kick start the software development teams at TextKernel with an introduction training Scrum. The training was interactive and we practiced a number of sprints, how to collaborate and estimate

Want to know more how your organisation can benefit from using Scrum or Agile? Contact us at ZEN Software and we’ll kick start your organisation too!

Happy to kick start the software development teams at TextKernel with an introduction training Scrum. The training was interactive and we practiced a number of sprints, how to collaborate and estimate


Security Awareness training




Learn the power of the Internet w/ desktop computer & monitor peripheral gadget

computer-personal-computer-peripheral-output-device-computer-monitor-desktop-computer-gadget-computer-monitor-accessory

Security awareness is very important when safeguarding the data of your customers. To improve the security awareness and have some fun at the same time we decided to hold a recurring training for all engineers and combine this with a shared hacking session.

Learn how to secure your software, learn how to program with security in mind and:


Security awareness is very important when safeguarding the data of your customers. To improve the security awareness and have some fun at the same time we decided to hold a recurring training for all engineers and combine this with a shared hacking session.

Learn how to secure your software, learn how to program with security in mind and:

try to break into the software you are creating yourself! fun!

After these trainings we were able to find a number of vulnerabilities and patch them before our customers faced any of the downsides of the vulnerabilities.

Continuous Delivery 3.0 training

Make Agile Work for You

Read more:

The Kanban game at Crunchr

Continuous Delivery 3.0 training

From monolith to microservices using the strangler pattern

Guest trainer multi-cloud at Young Mavericks

Scrum Training at TextKernel

Security Awareness training

Subscribe to ZEN Software's newsletter