PracHub
QuestionsPremiumCoachesLearningGuidesInterview Prep
|Home/Software Engineering Fundamentals/Revolut

Explain DB concurrency, debugging slowness, DDD and CQRS

Last updated: Mar 29, 2026

Quick Overview

This question evaluates understanding of database concurrency control and isolation anomalies, backend performance investigation and diagnostic skills, and knowledge of architectural concepts DDD and CQRS, testing competencies in transaction semantics, operational troubleshooting signals, and architectural trade-offs.

  • medium
  • Revolut
  • Software Engineering Fundamentals
  • Software Engineer

Explain DB concurrency, debugging slowness, DDD and CQRS

Company: Revolut

Role: Software Engineer

Category: Software Engineering Fundamentals

Difficulty: medium

Interview Round: Technical Screen

## Backend fundamentals: concurrency, performance investigation, and architecture terms Answer the following backend questions: 1. **How do databases handle concurrency?** - What mechanisms prevent lost updates and ensure isolation? - How do isolation levels relate to anomalies (dirty read, non-repeatable read, phantom read)? 2. **If users report the service is slower than usual, how do you investigate?** - What signals do you check first? - How do you narrow down whether the bottleneck is CPU, DB, network, dependencies, or code changes? 3. **What are DDD and CQRS?** - Define each term. - When would you use them, and what are common pitfalls?

Quick Answer: This question evaluates understanding of database concurrency control and isolation anomalies, backend performance investigation and diagnostic skills, and knowledge of architectural concepts DDD and CQRS, testing competencies in transaction semantics, operational troubleshooting signals, and architectural trade-offs.

Revolut logo
Revolut
Feb 11, 2026, 12:00 AM
Software Engineer
Technical Screen
Software Engineering Fundamentals
4
0

Backend fundamentals: concurrency, performance investigation, and architecture terms

Answer the following backend questions:

  1. How do databases handle concurrency?
    • What mechanisms prevent lost updates and ensure isolation?
    • How do isolation levels relate to anomalies (dirty read, non-repeatable read, phantom read)?
  2. If users report the service is slower than usual, how do you investigate?
    • What signals do you check first?
    • How do you narrow down whether the bottleneck is CPU, DB, network, dependencies, or code changes?
  3. What are DDD and CQRS?
    • Define each term.
    • When would you use them, and what are common pitfalls?

Solution

Show

Comments (0)

Sign in to leave a comment

Loading comments...

Browse More Questions

More Software Engineering Fundamentals•More Revolut•More Software Engineer•Revolut Software Engineer•Revolut Software Engineering Fundamentals•Software Engineer Software Engineering Fundamentals
PracHub

Master your tech interviews with 7,500+ real questions from top companies.

Product

  • Questions
  • Learning Tracks
  • Interview Guides
  • Resources
  • Premium
  • For Universities
  • Student Access

Browse

  • By Company
  • By Role
  • By Category
  • Topic Hubs
  • SQL Questions
  • Compare Platforms
  • Discord Community

Support

  • support@prachub.com
  • (916) 541-4762

Legal

  • Privacy Policy
  • Terms of Service
  • About Us

© 2026 PracHub. All rights reserved.