I was put in charge to write some extra tests in our framework covering our Docker registry endpoints. We created a framework around Locust.

Sometimes you need to run Docker containers in different circumstances, like on Raspberry Pi's or you have systems that are just wired differently (Alpine) and sometimes even a combination of those (Alpine on a BananaPi) and you do not always have everything laying around to reproduce it. So what do you do?

There was a problem on a server we did not control. It was managed by a third party and we only got a service account. Since things were down and I did not have full root access I got a bit annoyed waiting for them to respond back.

I decided to take matters into my own hands.

I just skimmed/read this article. It states that PHP is just as good as Rust/C/Java. That the opinion that it is bad is just 10 years out of date.

Speaking of learning the basic tools, I think I learned enough of running docker on multiple platforms that I now have a nice setup that is the perfect Docker image that fits as a very perfect boilerplate template to create all your future images with.

I wrote a piece on microservices and nanoservices and how that is not the way to move forward.

I recently skimmed / read this article. It is written by someone who has 25 years of experience in the field and 18 of those at Microsoft and currently operates as a Software Architect. It is not always relevant, but in this case I found it to be so.

I recently ran into the unsolvable issue that if you ran an npm audit on a React or Angular framework project, it would give back an error because of this CVE. Now the solution was to go to a lower dependency for one of the scripts, but that lower dependency had other high vulnerabilities and so you were in an endless cycle and could not fix it.

Recently I got the experience of using Docker on Windows Server to actually deploy a production running service. It was a fun experience for sure. I ran into three things that made it worthwhile to write down for posterity.

So I recently started using Spring WebFlux and Project Reactor as stated in this post. One more thing I came across as I was debugging why a certain job was not running was that if you do not catch all exceptions and do not have a doOnError statement it will just keep that thought hidden from you and all to itself.