What is the problem with calling REST directly from a Kafka consumer?
Java
If we make a positive decision, when will you be able to join us?
Why did you decide to cache the client specifically in Redis?
Which of these options do you personally like more?
How much was the latency reduced?
And if all services write such messages to Kafka, and the load is quite high — hundreds of thousands of messages per second, how would you organize the audit in this case?
How would you organize auditing of service calls, for example, Service A was called a million times, Service B — a hundred times in a day. How would you solve this task?
Do you solve more practical tasks or do you have to solve some technological problems?
Would it be suitable to read a message from Kafka, asynchronously write to a neighboring service, and commit after the service responds?
Can you tell me about the reason for transitioning from "IC Philosophy of IT" to PSB and why you are currently looking for a job again?
What tasks do you enjoy solving?
If not using a database and Spring wrapper — can the receipt of messages be separated in the same way?
Who prepared such configurations, as it was arranged in your team?
Considering that contract tests are described in JSON format, there is a runner that runs a set of tests for the specified endpoint, and this should be done for all systems with each release (about 160 thousand releases per year) — how would you organize integration with a large number of systems, including accounting systems, via API?
Are you familiar with the equivalent system 'Sbermoc', a platform for emulating execution of integrations (REST, MQ, Kafka) for a bank?
How is memory cleanup handled in Rust (since there is no garbage collector)?
What was unsatisfactory in the initial situation that led to this task?
What was the last book or article related to your work that you read?
Was it GVT or GVS?
How does HTTPS work? What is SSL? How does TLS differ from Mutual TLS?