Kubernetes, or k8s, is an important container orchestration platform. In this blog, I’ll describe creating a workable Kubernetes cluster implemented on a stack of four Raspberry Pi boards. In the end, I’ll have provided an outline of how I created it and I’ll show how to replicate a stateless app across Kubernetes pods running on the nodes โ the Pi boards.
When I heard that Groovy 4 is coming out, I decided to get ahead of it. I went online to explore what new features we were getting and how I could start using them in my own code.
This article will not be a full list of the new features of Groovy 4; there are simply too many for one post. This post will simply be my thoughts on a select few of those features and how I would plan to use them.
Let’s get started!
The steps described in this blog post allow for the adding of a Logic App on Azure to append rows to an Excel file. It took a lot of trial, and mostly error, to figure out how to describe what I wanted in the way that the Logic App would understand. Hopefully, the steps that I outlined in this blog post will save others the time it took me to come up with them.
Back in 2015 and 2016, I wrote two blogs that went step by step to develop a microservice/Netty architecture with fully working code called Whirlpool.
A lot has changed in the years since, so recently I decided to come back to the project, update it with the latest versions of Kafka and Netty, and add a React UI to it (rather than the vanilla JavaScript version it used before). In addition, I also added Windows Subsystem for Linux (WSL) scripts in addition to the Mac and Linux scripts that were there before and made all of the scripts more robust.
This blog will be about the work that went into all of those updates, plus a look at the new React UI. This provides an excellent view into what it takes to update an outdated microservices application implemented with Kafka (version .9 –>3.0) and Netty (4.1.3->5.0.0-alpha2), bringing all versions up to date and adding a React UI. By the end youโll be familiar with the latest versions of these frameworks, know some โgotchasโ to avoid, as well as understand how to integrate WebSockets into React.
This blog is about converting legacy code betterโusing architecture already in place, SOLID principles, and best practices.
Generally speaking, not having an architectural plan set up (or not using SOLID principles and best practices) can lead to passing the buck to the next generation of developers. We should all strive to push good code forward to get the latest and greatest out there. Starting with following the patterns in place at your job, or SOLID best practices, will make converting and upkeep way faster in the future.
This post contains a discussion of my experience in various software team environments. Throughout them all, we show that if SOLID patterns and best practices had been followed, then time spent converting code would have been less and code upkeep would have been easier down the line.