-- There are tables with the structure Employee id (PK) name salary dep_id(FK department.id) Department id (PK) name -- write a query that returns a list of all department names with the maximum salary in each department select d.name, COALESCE(MAX(e.salary), 0) from Department d left join Employee e on e.dep_id = d.id group by d.name
Was the transition from Java 17 stack to 21 a one-time switch, or do different services run on different versions?
What Spring Cloud components have you used?
Do you see a weakness or a growth point for yourself?
How to build an efficient index for a column with low selectivity (for example, status: new/running/finish), when only the 'new' status is important?
What are Bean and BeanDefinition in Spring?
What is the difference between HashMap and LinkedHashMap?
How was Spring Security used in the project?
What exactly did you tune in Kafka? Which specific parameters did you configure?
What does a 'self-signed' token mean? Why is a signature needed?
What test cases would you write for this method?
Can an anonymous class be replaced with a lambda function?
What is Spring? Why is it needed? What is DI and IoC?
Briefly tell about a project at [company] — what did you do there?
producer 1 consumer 4 partition 3 topic 1
/** * == ФТ == * Сервис обработки заказа получает заказ для обработки через Rest API. * Обработка в следующем: * - Проверить наличие товара на складе (вызывается внешний сервис по REST/HTTP). Если товара нет, то обработка заказа прекращается. * - Сохранить заказ в БД заказов * - Запустить дальнейшую обработку заказа (Processing, вызывается внешний сервис по REST/HTTP) * - Инициировать уведомления о новом заказе (Notification, вызывается внешний сервис по REST/HTTP) * * == НОТ == * - обработка должна быть такой, что если сохранить в БД заказ не удалось, то запускать заказ в обработку (processing) и инициировать уведомление (notification) не надо * - использовать для корреляции логов идентификатор заказа * - поддержать метрики 1) количество принятых заказов 2) количество успешно обработанных заказов * - сервис должен обрабатывать до 100 заказов в секунду */ const MaxItems = 9999 // ... (остальной код не переводится)
The client sees the old balance after a successful withdrawal yesterday. What could be the reason?
Do you know the difference between HTTP 1.1 and HTTP 2? Maybe even HTTP 3?
Tell me more about the project: stack, load, microservices, what you did
How did you solve the problem of duplicate messages in Kafka?
