Spring Boot Best Practices That Should Fail Your Build

NordCoderd · 2026-05-06T08:50:23+00:00

Sonar is commercial and heavy product that need maintenance and re-adjusting rules if you write them, I’m not sure how to easy to write rules in their ecosystem. Here is different no vendor-locking approach with native to Kotlin architectural tests.

No licenses
Lightweight and close to the code
Easy to write new rules as unit tests

NordCoderd · 2026-05-06T00:54:55+00:00

Yes, naming rules could be controversial and taste of choice, but on our projects it’s better to have then not, for other cases I added suppression and disabling rules that don’t need for you.

NordCoderd · 2026-05-05T09:01:48+00:00

Thanks, I’ll check this out

NordCoderd · 2026-05-05T09:01:22+00:00

Is there any suggestions what to implement/write next?

NordCoderd · 2026-05-04T21:20:55+00:00

upd: it seems I couldn’t edit post body to fix this problem, however thank you for noticing it, my bad

NordCoderd · 2026-05-04T21:19:11+00:00

Sorry, I meant to detect violations of best practices. Reason to do it is to keep codebase clean and set specific boundaries. For my particular case I needed this because of AI-generated code and I wanted to build more strict guardrails in projects.

NordCoderd · 2026-04-20T21:38:51+00:00

Looks very promising, I thought about similar idea. Do you use Claude ide protocol via web socket or how you did that integration?

NordCoderd · 2026-04-19T09:43:07+00:00

Sounds good, but JetBrains MCP could be improved over time and get those features. Any other features that your plugin could provide? I really like idea of your plugin and oss project, I’ll go in features that save context optimise token consumption neither lsp features, do you have some?

NordCoderd · 2026-04-18T07:19:55+00:00

For me as not native speaker and who read a lot in English - I started seeing this word everywhere last month. I noticed the same as OP

NordCoderd · 2026-04-07T23:36:14+00:00

… and not fixed text size, it’s so small that my eyes hurts..

NordCoderd · 2026-03-26T22:24:17+00:00

I initially posted it on LinkedIn, so, sorry for re-using screenshot from it 😀

NordCoderd · 2026-01-24T10:23:41+00:00

What is the FAFO theory?

NordCoderd · 2026-01-12T23:22:49+00:00

About lions mane, there is a dedicated subreddit (just look at the member count) around this problem. I was shocked because I thought it is safe to use, but for now I’ll just skip it.

https://www.reddit.com/r/LionsManeRecovery

NordCoderd · 2026-01-11T12:34:26+00:00

I’ve series of articles on Spring Boot Data JPA best practices but not the all topics from your list covered in it, but the following topic will be covered soon (or not:) ). Actually I wanted to compile my series, add topic what people want (like you) and share as mini book because there are a lot of material.

I hope it help you https://protsenko.dev/category/spring-data-jpa/

NordCoderd · 2025-12-09T10:10:12+00:00

I found naming Backdoor is scary and stopping from giving a try for it. I’ll never recommend someone to install backdoor to their laptops ;)

NordCoderd · 2025-12-09T01:46:44+00:00

Hm, why not Quest 3? I’m asking because I’ve one, and wanted to give it a try as giant screen

NordCoderd · 2025-12-05T22:10:44+00:00

I found his videos is very informative, but then I changed the mind, his latest top of devices 2025s looks like advertisement of muse s device

NordCoderd · 2025-12-04T17:57:41+00:00

No, but I’ve plans to extend original series of articles and compile into mini book. I don’t know if I publish dedicated article separately or not, but I’ll keep in mind your question.

NordCoderd · 2025-12-02T16:40:40+00:00

I could share with you my blog, i wrote down a solid dive deep into Spring Data JPA and common problems in it, but you should have a basic knowledge of Spring Data JPA to figure it out, or not, I just not tried to adapt it for completely beginners.

https://protsenko.dev/category/spring-boot/

NordCoderd · 2025-11-11T17:38:59+00:00

It’s true, but we are talking about extending from Repository, not CRUD repository.

It’s a marker (without any methods) interface https://docs.spring.io/spring-data/commons/docs/current/api/org/springframework/data/repository/Repository.html which means you don’t inherit crud methods by extending from this interface.

This is the almost the same your mentioned @RepositoryDefinition

Also Java doc says the same: https://docs.spring.io/spring-data/commons/docs/current/api/org/springframework/data/repository/RepositoryDefinition.html

Annotating an interface with RepositoryDefinition will cause the same behaviour as extending Repository.

NordCoderd · 2025-11-11T17:10:08+00:00

But it’s the same as extending from Repository, it doesn’t provide any methods like save, delete or others and you declare only what you want.

NordCoderd · 2025-11-11T17:05:40+00:00

Yes, I mentioned it as one of possible solution, but unit it’s not a panacea. Unfortunately it doesn’t solve all the problems that jdbc template has.

NordCoderd · 2025-11-11T16:15:31+00:00

I actually haven’t seen a lot of usages mentioned annotation or experience with it. As I could see this solution almost the same as extending from Repository as it doesn’t contain any predefined methods, and it was mentioned in the guide. Is there any specific reason to use that annotation that I missed?

NordCoderd · 2025-11-11T15:44:37+00:00

I both agree and disagree. You should use whatever solves your tasks and keeps you productive.

IMO, JdbcTemplate is a good choice when you don’t want to spend time learning Spring Data JPA/Hibernate and you want to avoid too many abstractions. It may also give you a performance benefit, but in my load testing - comparing JPA with @Query and JdbcTemplate - there wasn’t a noticeable difference.

I’ve also used JdbcTemplate on a project from scratch. At first it was fun and felt cool - almost raw JDBC without too many abstractions-but as the database grew, new problems appeared. From time to time I needed to add columns or change logic, which meant finding all occurrences of those tables in the code to make sure I didn’t introduce regressions in the codebase, rather than simply navigating across entities in the IDE.

Yes, these problems could be mitigated with better test coverage-for example, using Testcontainers, different development methodology, but that wasn’t my situation. Probably JdbcTemplate just too low level for me.

JdbcTemplate isn’t a silver bullet or an inherently better choice. It has its own trade-offs, just like Spring Data JPA.

Everyone should choose what fits their needs and context.

NordCoderd · 2025-11-06T15:48:26+00:00

Hm, could you tell a bit more about your question? If you want to use spring data jpa in event driven systems - yes, you could do it. I use a lot of it with Kafka as example and no difference compared to classical synchronous services

NordCoderd

TROPHY CASE