How business goals shape the architecture of future IT systems: a guide for entrepreneurs

Hello, I’m Maxim from Sailet. We specialize in custom software development, have been working since 2017, completed numerous interesting projects, talk about automation, and are developing our own ECM (Enterprise Content Management) system.

Previously, I wrote about mistakes in the public sector and how to avoid them. Now let's return to business and continue exploring problems that arise even at the start. One of the most common issues is incomplete disclosure.

Yes, this problem really exists. Entrepreneurs often withhold information about the actual scope and tasks of their projects, aiming to reduce initial costs. This leads to inadequate assessment of requirements and selection of unsuitable architecture, resulting in significant additional expenses in the future.

Real Case Study:
— We need to develop a system for processing applications, something like a specialized CRM.
— How many users will there be? What are the timelines? And other questions.
— There will be around 100 users, maybe more, but not significantly. Three months for development. Two months later:
— Can we add 800 companies with 15,000 users to the platform?
— With the current resources, no.
— Why? We asked you about server specifications and the platform.
— We provided data for up to 500 people with some reserve.
— But we need 15,000.

Actual Data:
1. According to research by the Standish Group, 31% of IT projects are canceled before completion, and 52% exceed budget.
2. A report by McKinsey shows that 45% of large IT projects experience budget overruns of 50% or more.

Consequences:

• This leads to choosing an architecture that cannot scale or adapt to future requirements. Be prepared to update your system every year or never finish it at all.
• Due to the necessity of changes and optimizations already during operation, development costs increase.
• Unsuitable architecture may not handle increased load. «Why is everything so slow?»

The contractor must clearly understand the REAL goals and tasks of the business to at least choose the right IT system architecture that will be maximally effective.

It’s IMPORTANT to discuss all usage scenarios and future plans from the very beginning. You pay the contractor for their expertise and solution generation. So provide accurate information to ensure those solutions are correct. This simple step can save you a lot of money.

We've covered the basics; now let's move on to technical aspects. Here's a brief overview.

The architecture of an IT system is its foundation, determining its components, their interactions, and operational principles. Properly designed architecture ensures stability, performance, and scalability of the system.

Poor architecture causes pain... lots of pain... an overwhelming amount of pain… Of course, I'm primarily talking about time and money, not to mention nerves, stress, missed opportunities, and, yes, plenty of pain. I hope I've conveyed just how much pain we'll be dealing with here.

In one project, poor architecture ended up costing the client six times the original estimate and required a complete overhaul of a system that was already 70% complete.

Monolithic Architecture
The entire system is developed as a single unit where all components are tightly coupled with each other.

• Pros: Simplicity in development and deployment.
• Cons: Difficulties in scaling and updating.

Often used for MVPs, small platforms, internal portals, etc., typically supporting up to 10k users.


Microservices Architecture
The system is divided into independent services, each responsible for its own part of functionality. Imagine a set of separate applications interacting with each other.

• Pros: Easy to scale and update. If one service needs changes, it doesn't affect others.
• Cons: Complexity in managing and configuring interactions between services.

Definitely excessive at the start, but definitely ideal at scale. If you have 5k+ users immediately, it's essential.


Service-Oriented Architecture (SOA)
The system consists of services with shared interfaces. It's like different parts of your system could “talk” to each other through standardized protocols.

• Advantages: Flexibility in integration. Easy to add new services.
• Disadvantages: Requires careful planning and management to ensure all parts work harmoniously.

Commonly found in ecosystems and super apps, such as EGOV, Kaspi, etc.


Used for very large systems.
Now, remember that when designing a system, the following parameters are considered:

• Load: The number of users and volume of data.
• Speed and Reliability: Response time and resilience to failures.
• Scalability: Ability to expand without losing performance.

And that's why understanding the goals and business tasks is crucial. What's the plan for this IT system? Who's it for? How many users? What happens next? What key tasks should it solve? Where do we grow? Etc.

We can certainly assist with all of this. To get started, submit a request using the link below. Please note that we only work with qualified clients, and this consultation is free.