I work for a 40 year old private enterprise with a large Java 8 micro-service architecture. My current project is to facilitate the migration to Java 21.
As you point out, there needs to be a compelling business reason. In our case, we are migrating to K8s as well, which is easier to make the business case for.
Security helps make the case as well. Any enterprise using Java 8 and Spring Boot is riddled with CVEs.
Spring Boot 3 requiring Java 17 is what allowed the migration in two companies I’ve been, it’s much easier to sell it as security issue than tech debt.
These reasons all make sense to me. I find most engineers who care about the health of a system want to address technical debt.
The problem is convincing leadership addressing technical debt is important. Neglecting maintenance runs rampant at my organization. Maintenance is often viewed as adding no value to the business so the work is constantly deprioritized.
Can someone help me understand why keeping metrics in memory, consuming resources, and having Prometheus ping your spring-boot app every 10 seconds is good design? What happens to this design at scale when you have thousands of spring boot microservices and Prometheus has to ping each instance to collect metrics.
I have a lot of the same qualms and unhappinesses with the prom ecosystem. Also don't love how it sort of fiats that you have low-latency, quickly-consistent external service discovery to find out what to scrape.
It also seems like the prom ecosystem is still deciding how it wants to do push based metrics (you know...the pattern that has none of those problems) and that none of the tools in that area are especially good or mature.
> If you don't mind me asking, what medicine were you prescribed? What kind of topics do you go over in therapy?
First of, I suggest you talking to your doctor about the medicine. For me, I use Vyvanse 30mg, but the same medicine can have a much different impact on you.
I do recommend therapy and really opening up to your therapist. I started out with current struggles, how I felt and handled, and then I talked about past events, formative stuff from my childhood and teenage years.
I also covered topics about inadequacy and frustrations with how I manage my time, my attention and my energy.
Before each sessions I make a list of certain topics I want to cover and I use it as starter, then I let the therapist guide me through some stuff.
My wife and I tried a number of apps and settled on YNAB. We've been using it for a year now and the app is incredibly helpful. Fair warning, the learning curve is a little steep.
Fortunately, it supports syncing with the small credit union we belong to. It does NOT support some of our accounts like our retirement accounts, some credit cards like Apple and Sam's Club, but it supports enough to be convenient.
> Fair warning, the learning curve is a little steep.
Can you be a bit specific here? I've setup a trial account and so far nothing seems to challenging to me - perhaps this is because I'm used to envelope budgeting, or just haven't gotten to the more nuanced things yet?
Highly recommend WireGuard for this (see kilo for k8s specific that works with whatever network you have setup). Setting up a VPN that just works is super simple.
As you point out, there needs to be a compelling business reason. In our case, we are migrating to K8s as well, which is easier to make the business case for.
Security helps make the case as well. Any enterprise using Java 8 and Spring Boot is riddled with CVEs.