sruffatti

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.

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.

I second YNAB. It played a significant role in my financial responsibility in terms of budgeting and saving. YNAB is an excellent product.

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.

If you don't mind me asking, what medicine were you prescribed? What kind of topics do you go over in therapy?

I was not familiar with envelope budgeting or zero-based budgeting.

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.

YNAB does have an API https://api.youneedabudget.com/

My wife and I are considering switching banks to have more reliable integration with YNAB.

Bump! This sounds very interesting.