HackerTrans
TopNewTrendsCommentsPastAskShowJobs

PlumpyGER

no profile record

Submissions

The Cost of Accidental Complexity

backendhance.com
2 points·by PlumpyGER·قبل سنتين·0 comments

How a Release Failed

buttondown.email
2 points·by PlumpyGER·قبل 3 سنوات·2 comments

Java Bean Validation Is an Anti-Pattern (2022)

backendhance.com
4 points·by PlumpyGER·قبل 3 سنوات·1 comments

Laziness Prevails

buttondown.email
3 points·by PlumpyGER·قبل 3 سنوات·0 comments

Goodbye Performance Issues: How Project Loom Eliminates Asynchrony

backendhance.com
1 points·by PlumpyGER·قبل 3 سنوات·0 comments

Microservices are hard

code-held.com
267 points·by PlumpyGER·قبل 4 سنوات·343 comments

comments

PlumpyGER
·قبل 3 سنوات·discuss
This is amazing! Thanks for the effort!

I missed the original thread, but would be happy when you include my blog as well :) RSS Feed (en): https://backendhance.com/en/blog/index.xml RSS Feed (de): https://backendhance.com/blog/index.xml
PlumpyGER
·قبل 3 سنوات·discuss
https://backendhance.com/blog/

I started this blog in 2019 and wrote around 50 articles. I focus on backend engineering on the jvm and all the surrounding. The blog was formerly called "code-held" and when I started to work as a freelancer earlier this year I migrated the content. I publish in German and English.

My favorite posts are:

Microservices are a Big Ball of Mud - https://backendhance.com/en/blog/2022/microservices/ (was also featured at HN some while ago)

Don't Use The Builder Pattern in Kotlin - https://backendhance.com/en/blog/2021/dont-use-builder-in-ko...

How To Load A Shared Library From A Subfolder In Jenkins - https://backendhance.com/en/blog/2020/jenkins-local-shared-l...

RSS Feed (en): https://backendhance.com/en/blog/index.xml RSS Feed (de): https://backendhance.com/blog/index.xml

I publish every week now.

When you are interested in more opinionated content (infotainement) you might enjoy my newsletter as well: https://backendhance.com/newsletter/

In the newsletter I share some easy to consume inspiration twice a week.
PlumpyGER
·قبل 4 سنوات·discuss
The problem with standardizing these things is, that it makes them hard to change. A breaking change in the way you deploy must also work for all other solutions - otherwise you immediately loose your standardization. And this will happen eventually. For all this different kind of problems it is near impossible to avoid inconsistency and force rules on them.

So, imo you either have a (very) large organization with independent teams that work on independent services and give them the freedom for everything - or you develop a proper modulized monolithic software and extract services only as a last resort. I would avoid to use a microservice architecture with a small team of developers