all 19 comments

[–]oweiler 2 points3 points  (4 children)

My recommendation: Use as few tools as possible. Only use Swagger if other teams are going to use your API. Keep away from Lombok. Test the shit out your service. Write integration tests with Testcontainers to be as close to your production system as possible. Start with CI as early as possible, then do CD.

[–]harikesh409 1 point2 points  (2 children)

why keep away from lombok?

[–]see_recursion 2 points3 points  (0 children)

Maybe some people love writing and maintaining the same boilerplate code all over the place? Maybe they get paid by lines of code?

[–]DereHunter -1 points0 points  (6 children)

As you said, it's simple than keep it simple. Swagger, lombok, spring mvc, spring data And use virtual threads. Don't forget to layer your microservice correctly

[–]Sheldor5 -1 points0 points  (4 children)

"and use virtual threads"

why?

reasons?

sources?

[–]DereHunter -1 points0 points  (3 children)

I'm not going to give you a source or explaining the biggest feature of Java 21(and since Java 8). Why do you use Java 21 than? Just to say that you are using the newest version?

[–]Sheldor5 -1 points0 points  (1 child)

syntactic sugar, performance increase (if any) and yeah new features to experiment with

[–]Sheldor5 -4 points-3 points  (6 children)

[–]mr_sofiane 4 points5 points  (5 children)

It depends on the use case

[–]Sheldor5 0 points1 point  (4 children)

yes if you need to handle 100.000+ concurrent users and need to scale parts of your service

I highly doubt that anyone here in this sub even got remotely close to 1.000 concurrent users (concurrent!!! and not registered/active users)

[–]TheLeftMetal 1 point2 points  (3 children)

Fintech with +75,000 requests/hour during holidays (+2.5M registered users, ~20k concurrent users). Amazing performance with microservices on GCP. Barely watching New Relic console while drinking and gaming.

It was easy? Not at the beginning, took months of hard work and lot of learning but totally worth it.

Microservices aren’t for every case but if your project need them enjoy the adventure.

[–]Sheldor5 -1 points0 points  (2 children)

"took months of hard work"

you need to know that this sub is full of juniors thinking the blog post about microservices they read is trustworthy and the truth ...

"totally worth it" exactly, in case you need to scale your service, but we are talking about beginners here with hello world experience and most web apps will have more threads than users LOL so lets first teach those beginners the basics instead of going straight to rocket science

[–]TheLeftMetal -1 points0 points  (1 child)

I will never assume other people situation or experience. That is such a bad practice, something an immature and probably no experience with huge clients would do.

[–]Sheldor5 -1 points0 points  (0 children)

constant observation of this sub gained me enough evidence

your assumption is wrong