How does Kafka distribute messages across partitions?
Java
Have you worked with Spring Data and Hibernate? What performance issues did you solve?
Is implementing idempotent event processing an achievement for a senior, or is it something that is expected of them a priori?
Are there any other patterns for distributed transactions besides Saga?
There is a topic with 10 partitions. How many containers (consumers) are needed to read all partitions?
Tell about the levels of transaction isolation in databases.
What will happen if corePoolSize=5, maxPoolSize=10, queue=100, and initially 5 tasks are added, then 7 more?
What salary range are you considering?
What should be done if a second event source (second Kafka topic), also changing post ratings, appears?
What happens to working copies during git reset?
Tell me about the @ElementCollection annotation.
How is transaction integrity ensured when transitioning from monolith to microservices?
Задача по коду: Spring @Transactional и self-invocation (скриншот с кодом)
Is it possible to configure so that each instance of the microservice reads all messages from the topic? And how to distribute processing among pods in Kubernetes?
Is it possible to evaluate query performance without executing it?
Tell about the most complex/interesting task.
Have you worked with multithreading? What did you use?
If method A calls method B with @Transactional inside the same class — will a transaction open?
When changing a contract, is a new accrual added?
What inheritance strategies do you know in JPA? Which ones have you used?