What if those chains handle thousands of massages per second?

Serious backend is indeed a stretchy term. And I agree with that point b2b java is common. But our b2b backend handles multiple thousands of massages per second. I find the bottleneck to be MySQL and RabbitMQ.

I think it makes sense for a serious backend to have load balancing and nginx cache and horizontal scaling. I reckon QPS doesn’t matter as much as you think it does.

I still don’t think that java would be considered niche. I rather think that C or C++ would be considered niche. It takes longer to develop, and is not memory safe so I don’t think that most backend systems should consider it.

Most developers are not going to create the next kubernetes. For me it is usually down to earth integrations. Take this file from s3, send as email and sftp here. Create API to proxy another API. Take messages from Kafka, put on rabbitMQ. Save messages from rabbitMQ to database.

I think Java is very strong with libraries. Especially with Spring Boot and camel. I don’t really see it as niche but more of a plain boring peanut butter sandwich. Boring. Unexciting. But works.

I am however trying to convince my boss to allow kotlin. Which has access to all the java libraries

I have a colleague like that too, and then the other camp that loves MySQL.

Why do you like postgres

Backend

Oh I know that feeling. But when you get the hang of it you will never go back

It can be quite overwhelming if nobody knows how to use git.

I know software teams that went back to share code on teams folders after having used git…

Please get a git course for all the developers

This took me a month to make. Moving from docker swarm to kubernetes.

“Containers are platform independent, and can run on anything” - yes… But…

Beautiful… Tomorrow someone runs in and asking for the consumer-service-aggregator-constructor-mapper that apparently everything relies on

Only one dude reviewed it. In one minute.

Minified?