The presentation explores the design features of a mobile application architecture, using a bank employee application as an example. We will trace the path of solution construction: from mapping the subject field and Object-Oriented Design (OOD), which shaped the domain architecture (DDD), to the selection of integration methods, database, and non-functional aspects. As a result, we obtain a platform that, thanks to OOD, ontology, and API First, can easily integrate with the corporate ecosystem, scale, and evolve in line with business needs.

The talk will present the idea of how the initial business requirements can be represented as a set of business objects with a certain attribute composition or "marked the subject field". The result of this markup (ontology, graph or taxon) is proposed to be the basis of the solution architecture and used to select the architectural style (monolith, microservice, citadel), build a REST architecture, JSON RPC, and database table architecture. Also, the constructed graph will allow you to determine the synchronous or asynchronous nature of the interaction. 

In the talk, it is planned to present 4 patterns of solution architecture (microservice pipeline for production, building a system based on Rabbit MQ for tasks related to artificial intelligence, building a system based on Kafka for production tasks, the concept of an Open API for a Big Business company), built on the basis of an object-oriented approach.

You will learn about practical experience of analyst's work for TOP-5 Russian banks. In the Agile env it has become problematic to support “monolith” and recently large banks (as well as many big companies) are increasingly moving to a microservices architectural style. As a result, new demands have begun to be placed on analysts. The analyst is no longer a “tech writer” dealing with docs and preparation of mappings for adapters. He/she is now more of a “solution architect” and a central figure in the team, responsible both for solution selection and for setting development tasks.

The talk will cover the following topics:

• What are microservices from a methodological perspective and what artefacts require attention when analysing them. 
• Are microservices always a good thing, or are there cases where it is still better to leave a monolith?
• DDD, ontology as best practices.
• How to select and describe a solution so that it does not become an obstacle for subsequent refinement and integration.