The service read data from Kafka, enriched it with data from Redis — and then what did it do?
Golang
What happened when you rolled back the index, rewrote the query, and then applied the same index again?
What do you do with this data next?
The resume mentions that you implemented tracing — can you tell us more?
Personally, I tested that Postgres reorders columns and the optimizer doesn't care in which order you write the query — it will reorganize it as needed. What do you think?
And what was done for central logging?
What is the approach to the libraries used — do all commands use the same mock library or are there no restrictions?
How did you initially understand the problem from the metric, and what did you do next?
// Implement autocomplete for movies: // by entering the first 3+ letters, output the top-3 matches alphabetically. // ["macarthur", "interstellar", "intrusion", "macao", "into the abyss", "internship"] // me -> [] // mac -> ["macao", "macarthur", "machinist"] // int -> ["internship", "interstellar", "into the abyss"] // interstellar -> ["interstellar"] // intr -> ["intrusion"] // intrusion -> ["intrusion"] // into -> ["into the abyss"] // stellaris -> [] package main func main() {}
Why did you use Redis instead of in-memory cache?
How were duplicates filtered out? Couldn't duplicates be identified by ID? Why enrich data from Redis?
When validation passes — do we record it in the database or send it further to Kafka?
Can you tell about idempotency? How did you implement it? How did it work?