IT Architecture Design
HighLoad • BigData • ML • Monolith • Microservices • SOA • Blockchain
We will help you build a new system from scratch or scale an existing one, using our accumulated experience in IT architecture development.
What You Get
An architectural concept of the product solution, that meets current and foreseeable future business and technical requirements. Represented in a specification document with architecture models.
Work Stages
Cost Estimation
All the cases are provided as examples. We work individually with every client and we do not have any uniform solutions.
Automated workstation
From €2000
An internal web site for the automatization of the company’s business processes — including several integrations with the internal systems.
Up to one thousand users (1k users).
15 modules.
Requirements elicitation and analysis.
Technology solution.
Architectural concept elaboration.
Product pre-estimation.
SIM card distribution service
From €4000
A system for retail outlets with a small number of business processes, a web interface, and an integration with the external systems.
Up to one hundred thousand users (100k users).
12 modules.
Requirements elicitation and analysis.
Technology solution.
Architectural concept elaboration (average level of detail).
Deployment plan.
Product pre-estimation.
Tender platform
From €13 500
A tender system with complex business logic and a large number of services with web and mobile interfaces.
More than one hundred thousand users (100k+ users).
30 microservices.
Requirements elicitation and analysis.
Technology solution.
Architectural concept elaboration (great level of detail).
Product pre-estimation.
Problem
- Product vendor delayed releases and updates (1 release per quarter).
- Users were often unable to log into their online banking account due to the failures in the software or data bus — the high cost of downtime.
- The monolithic architecture was based on several servers; complex client distribution reduces the app's availability.
- All expertise belonged to the product vendor, and the Bank had no access to it.
- As a result — financial losses due to long time-to-market and outdated functionality. Customer outflow. Unclear understanding of pricing from the vendor.
- New microservice architecture for the remote banking and new UX for the mobile app.
- Each microservice is dubbed and has its own database. Even if the microservice cluster is not available, all other functionality works. Monitoring system is configured to track errors.
- New microservice data storage system with asynchronous data update from the banking system helped to eliminate the bottleneck — data bus.
- Expertise improvement of the Bank's developers.
- The number of failures on the user side was reduced by five times.
- TTM was shortened from one release per quarter to several releases per week.
- Project expertise was shared with Bank specialists.
- The architecture helps easily support several versions of the mobile app at the same time.
- New app features can be implemented further, to improve the system according to the user feedback.
The old monolithic application is difficult to maintain and update. Oracle DBMS is subject to sanctions. Client was looking for an experienced backend and frontend contractor.
Problem
- The current system is difficult to maintain and update. The system modules have complex interconnection , and that leads to frequent update failures. While one module is being updated, the other one breaks.
- Sanctions — it is necessary to replace Oracle DBMS.
- Client was looking for an experienced backend and frontend contractor.
- System downtime costs: penalties and delivery delays.
- To provide a new version of MVP with monolithic architecture to test the solution. This allows us to evaluate the future system’s complexity and to ensure that the client will be able to support the system . This also allows step-by-step development and enhances system functionality.
- To develop a new frontend from scratch.
- To implement a lightweight Java middleware instead of a heavy bus.
- Ability to use mobile devices to consume services.
- Digital collaboration with partners.
- 3 weeks to design the architecture solution and 2 months to implement it.
Sales channels are inefficient and slow to develop. Hard to update the restaurant menu and application interface. All improvements are to be made via the vendor.
Problem
- Inefficient sales channels.
- Business loses money because of inefficient sales channels.
- Old technological stack (Flash).
- Unable to use all modern IT solutions for marketing needs due to the old technology used in the current service.
- Hard to update the restaurant menu and application interface.
- It is not possible to implement modern UX requirements.
- Any modification is done via the vendor.
- Overdue notifications about the application failure.
- Scaling as a cluster of central servers. Use main servers clustering for scaling needs.
- Each restaurant has its own dedicated server.
- New features to create flexible marketing reports.
- To make each restaurant independent from the main server.
- Application interface manageability.
- Application quick and easy update.
- A/B testing and CusDev support, fast elaboration of all marketing hypotheses.
- Instant response to business needs.