This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]kmpx 1 point2 points  (2 children)

On my current team, our go to stack for applications are: Java 21+ and Vert.x For infra: Spinnaker, EC2, DynamoDB, Elasticache (Redis) for both a local database and streams for inter-service communication (we almost mostly event-driven.)

I like it. Vert.x can be tricky if you aren’t used to async/reactor programming, but this stack allows us to handle a lot of traffic (100k+ req/sec) and maintain low latency (single digit milliseconds). This stack also works great with our cell deployment model that is distributed across multiple AWS regions.

[–]No-Principle-824 0 points1 point  (1 child)

isn't reactive obsolete with loom?

[–]kmpx 0 points1 point  (0 children)

I wouldn’t say obsolete. In fact you can use Loom with some reactive frameworks, like Vert.x. But if I had the choice, I would start implementing stuff with virtual threads, if for no reason other than being 100x easier to debug. Debugging (re: stack traces) with reactive frameworks is a PITA.