Category: Architecture

In this short tutorial I will show how to build a business application with the Business Process Modelling Notation – BPMN. This approach differs from the usual data-centric approach as we focus on process management instead of data processing.

Data Processing vs. Process Management

When we follow the classic approach building a Data-Centric Business Application, we usually first design a data schema. The data schema defines what kind of data can be managed. The application allows us to create new data sets, edit existing data and of course search for data.

In a Process-Centric Business Application we instead first try to answer the question how data should be processed to give each actor the best access to information to reach a specific business goal. And this kind of question becomes more and more important in our today’s rapidly evolving business landscape. BPMN offers the perfect approach to model a workflow with its business goals from the beginning to the end. BPMN models can be created with various tools like for example the Open Source BPMN designer Open-BPMN.

The big advantage of BPMN is that it does not only give all stake holders a clear understanding about the process, a BPMN 2.0 Model can also be executed by a suitable process engine. This “low-code” or “model-driven” approach leads to a much more flexible way to implement business applications. Of course, data still plays an important role and workflow engines allow us to manage business data in various ways. So let’s see how this works…

In this short tutorial I will explain how to run a Docker container with GPU support. This becomes important if you want to run AI applications such as the Imixs-AI project within a local Docker environment or in a Kubernetes Cluster. This short tutorial is based on Debian 12 (Bookworm) and the usage of a NVIDA graphic card. I assume that you already have installed Debian and the Docker engine. Read the official install guide about how to install the Docker engine on Debian.

The term “workflow engine” is not clearly defined in software development and therefore we would like to give a brief overview of different aspects and types of workflow engines in the following blog post.

If you take a look at the Github page awesome-workflow-engines, you will find an impressive number of open source workflow engines. But not all of these engines solve the same problem. The idea behind the term ‘workflow’ can be very different and so the functionality of a workflow engine. In general a workflow is a series of tasks or activities that are required to complete a specific process. Such a process can involve multiple people, teams, microservices or even other IT systems. Thus, it becomes clear that when comparing Workflow Engines, various aspects must be taken into account.

When you hear about Kubernetes for the first time these days, you might get the impression that Kubernetes has a lot to do with AWS or Azure. If you read blogs or tutorials about Kubernetes or even if you join conferences, AWS and Azure is everywhere. It seems like a stupid idea not to believe that Kubernetes is based on these Internet platforms and can exist outside them.

But Kubernetes is far away from being a product or internet service that is only offered by Amazon or Microsoft. Rather, Kubernetes is an open source platform which is supported and developed by the Linux Foundation. Many people are working on the concepts for this open platform on a daily basis. And the goal of Kubernetes is to provide an open and powerful platform for operating container-based applications and Microservices.

It was never a walk in the park to setup and operate a stable and highly available cloud environment consisting of many servers. With Kubernetes companies and organizations should be enabled to run a server infrastructure for container-based applications by there own. Google has published his own experiences in this area and handed it over to the Linux Foundation in order to share that knowledge with others. And it was never the goal to make a product or put organizations in a dependent situation. On the other hand, it is a big business for companies like Microsoft and Amazon to offer their services based on the concepts of Kubernetes. Binding customers to their platforms is the new way of licencing. And they do a lot of marketing to succeed.

Build Your Own Cluster

Believe it or not, you can set up your own Kubernetes cluster and run it successfully in just a few hours. The concepts of Kubernetes provide many solutions for the problems that normally arise when operating large server environments. The result will be a stable and sustainable cloud infrastructure that you can control yourself.

Of course, Kubernetes is a complex system of many different building blocks. It takes time to get used to it. But today there are also a lot of concepts available to achieve success quickly. So don’t hesitate and take control of your personal cloud platform.

If you like, you can take a look at our open source project ‘Imixs-Cloud‘, which shows a simple and stable approach for the operation of a Kubernetes cluster.

In this blog I will explain how to setup and customize Wildfly to run your Jakarta EE application on Kubernetes. We use this setup in our own Open Source project to run modern Jakarata EE applications on Kubernetes. You can find this project on Github.

Wildfly is Jakarta EE 8 compatible and includes the latest Eclipse MicroProfile in version 3.3. It provides a modern application framework out of the box to simplify the development of web applications and microservices. All runtime services minimize the heap allocation and applications are starting very fast with a minimum of memory.