In a perfect world, we would prefer to implement microservices to be stateless. This stateless approach eliminates a lot of problems towards maintaining the storage for the applications data. However, we are not in a perfect world. At most time, applications need to deal with data and keep them on storage for long term references. We need persistent storage solution so that the applications data can survive containers (or systems) restart or crash. Kubernetes provides this type of storage support in the concept of volumes. We are going to look at how can we configured storage for Kubernetes on Raspberry Pi 4.
Modernize the Payment Platform Based on Event-Driven Architecture – Part 2
In my previous post, I briefly talked about event-based architecture for payment platform modernization and why the modernization is important to the industry. In this post, we will dive into details of the key capabilities to consider for the payment platform modernization. The capabilities covered in this post may not be the complete list but it definitely serves as a good start.
K8s on RPi 4 Pt. 2 – Proven Steps to PXE Boot RPi 4 with Ubuntu
Follow these steps to easily setup PXE boot Raspberry Pi 4 with Ubuntu Server 20.04. PXE boot enables Raspberry Pi to run faster compared to SD card.
K8s on RPi 4 Pt. 1 – Deciding the OS for Kubernetes RPi 4
Running Kubernetes (K8s) on Raspberry Pi 4 with Ubuntu Server 20.04. The true reason why I choose Ubuntu instead of Raspberry Pi OS
A True Atomic Microservices Implementation with Debezium to Ensure Data Consistency
Typical microservices outbox pattern implementation requires developers to manually create the outbox event table and write the codes to send the data from the outbox table to the respective messaging platform. Debezium Outbox Event Router together with Outbox Quarkus Extension take cares of this and enforce a standard approach to do this with declarative implementation. This allows the developers to focus on business logic implementation and achieve faster application delivery.