Why is scalability in a microservices architecture better than in a monolith?
Middle+
200
System Analyst
2753
0
What changes are required in the API when adding promo codes?
Middle
200
What rule was applied for ATM write-offs, and was the ATM's economy considered?
Middle+
200
What is the difference between GET and POST methods?
Middle
200
Is it possible to design services so that all methods use only POST?
Middle
200
What data will be transferred from one bank to another?
Middle+
200
Do you have to independently design integrations or is it done jointly with a developer/architect? What kind of integrations: internal or external?
Middle
200
There is a task to split a monolith into microservices. One of the services may not respond, leading to data inconsistency. How to safeguard?
Middle
200
Write the physical database tables for a catalog service (books, authors, genres, price).
Middle
200
Who is responsible for functional requirements, and who for non-functional ones?
Middle
200
What is the main problem with the system description structure - Incorrect separation of functions - System requirements are incomplete - System boundaries are not described clearly enough - Requirements description is unclear - Requirements for functions are described unclearly - System functions are described incompletely
Middle+
200
Do you have more experience in run activities or in change? Specifically in software development and production?
Middle
200
Where are we sending the event from and to, and how to determine if it is valid (has passed)?
Middle
200
What did you enjoy doing on the last project with unified accounting and inventories?
Middle
200
Is there anything else about caching that needs to be considered?
Senior
200
Have there been sprints in your work?
Middle
200
What ways of scaling databases do you know?
Senior
199
* No centralized notification history; * Users complain about duplicates and delays; * No unified SLA, metrics, or control center. Goal Design a new Notification Platform that: * Aggregates events from various sources (CRM, Support, Security); * Routes them by type and channel (email, SMS, Telegram, push); * Ensures uniform templates, logging, and observability; * Supports SLA (p95 ≤ 3 seconds for delivery); * Allows for future scaling and channel expansion. Candidate task 1. Define the functional requirements of the system. 2. Describe the non-functional requirements (reliability, performance, error handling). 3. Create a context diagram (C4 Level 2). 4. Add a sequence diagram, for example, sending a message from a source.
Middle+
199
Can you hear me?
Middle
199
What types of requirements have you had to work with?
Middle+
199