Auto-translation used

How business goals shape the architecture of a future IT system

In an attempt to save money, entrepreneurs often say that they need to develop a small IT system, specifically keeping silent about the real tasks, scale and goals. This article will help you understand how a clear definition of business goals and objectives affects the architecture of a future IT system. 

You will learn why it is important to be frank at the planning stages, what architectural approaches exist, and how they relate to business goals. And most importantly, what is the price of a mistake?

Hi, I'm Maxim from Sailet. We specialize in custom development, have been working since 2017, have completed many interesting projects, talk about automation and develop our EDMS.

Earlier I wrote about mistakes in the public sector and how to avoid them. Now let's get back to business and continue to sort out the problems that are still at the start. One of the most frequent is understatement.

Yes, such a problem does exist. Entrepreneurs often keep silent about the real scale and objectives of projects, in an effort to reduce initial costs. This leads to an insufficient assessment of requirements and the choice of an unsuitable architecture, which entails significant additional costs in the future.

The real case:

- We need to develop a system for accepting applications, something like a profile CRM.

- How many users will there be? What are the deadlines? and other 100,500 questions.

- There will be about 100 users, maybe more, but not much. 3 months for development.

After 2 months:

- Tell me, can we bring 800 companies with 15k users to the platform?

- With the current resource, no.

- why? We asked you for the server and platform specifications.

- We have given data for 500 people with a margin.

- But we need 15,000.

Real data:

  • According to a Standish Group study, 31% of IT projects are cancelled before completion, and 52% exceed the budget.
  • The McKinsey report shows that 45% of large IT projects experience budget overruns of 50% or more.

The consequence:

  • This leads to the choice of an architecture that is not able to scale or adapt to future requirements. Get ready to update the system every year or not finish it at all.
  • Due to the need for changes and optimizations already in operation, development costs increase.
  • An unsuitable architecture may not be able to handle the increased load. “Has everything been working for a long time?"

The contractor must clearly understand the REAL goals and objectives of the business in order to at least choose the right architecture of the IT system that will be as effective as possible. 

It is IMPORTANT to discuss all use cases and future plans from the very beginning. You pay the contractor for the experience and generation of solutions. So provide real information so that the decisions are correct. This simple thing will save you a lot of money.

We've sorted out the basics, let's get to the technical points. A brief educational program.

The architecture of an IT system is the foundation that defines its components, their interaction and principles of operation. A properly designed architecture ensures the stability, performance and scalability of the system. 

The wrong one provides pain... a lot of pain... a lot of pain… Of course, I'm talking about time and money first of all, not counting nerves, stress, lost profits and a lot of pain… I hope I managed to convey how much this pain will be.

In one of the projects, it cost the customer x6 from the original plan and a complete redesign of the system, which was completed by 70%.

Monolithic architecture

The whole system is developed as a single whole, where all components are closely connected to each other.

  • Advantages: Ease of development and deployment.
  • Cons: Difficulties of scaling and updates.

It is often used for MVP, small platforms, internal portals, etc. Usually up to 10k users.

Microservice architecture

The system is divided into independent services, each of which is responsible for its own part of the functionality. Imagine a set of separate applications that interact with each other.

  • Advantages: Ease of scaling and updates. If one service needs to be changed, it does not affect the rest.
  • Cons: The complexity of managing and configuring interaction between services.

Definitely redundant at the start, but definitely perfect at scale. If the users are from 5k at once, then it is mandatory.

Service-oriented Architecture (SOA)

The system is built from services with common interfaces. It's as if different parts of your system could "talk" to each other through standardized protocols.

  • Advantages: Flexibility of integration. It is easy to add new services.
  • Disadvantages: It requires careful planning and management so that all parts of the system work harmoniously.

Often in ecosystems and superpaths, such as EGOV, Kaspi, etc. Very big ones.

Now, let's remember that the following parameters are taken into account when designing the system:

  • Load: The number of users and the amount of data.
  • Speed and reliability: Response time and fault tolerance.
  • Scalability: The ability to expand without loss of performance.

And for this, it is important for us to understand the goals and business objectives. What is the plan for this IT system? For whom? How many users are there? What will happen to her next? What are the key tasks to solve? Where are we growing up? Etc. 

We can definitely help everyone with this. To do this, you need to submit a request via the link. We don't do it for everyone, only after qualification, because it's free.

If you want to avoid pain, stress, and loss, be honest from the very beginning. Speak honestly about your goals and objectives. Fix the 3 basic rules:

  • Share real plans and forecasts with the contractor. This will help you choose the right architecture and avoid cost overruns.
  • Think a few steps ahead. Plan for scaling and consider possible changes.
  • Contact professionals who can offer optimal solutions for your project. Well, how about it)

Please write in the comments the topics about automation/development/programming/digitalization that you are concerned about and we will definitely tell you about them.

Comments 0

Login to leave a comment