low-code performance | VSoft archITekt

Is it possible to process 1.5 million cases in 47 minutes using a low-code platform?

When building complex management and decision-making solutions, we often need to download customer data. This includes, for example, information about the products they own and the transactions they perform. Simply downloading the data for solution is only the first step in the process. Next one is to verify the received records, interrelate them and calculate the relevant aggregates (indices, sums, etc.). Dedicated tools are used to streamline data feed and processing, for instance, receivables monitoring systems in a bank, based on the daily processing of tens of millions of data about customers, their payments and contact history. Streamlining feed processes works well if data processing is reliable and scalable as the business grows. When data is not processed within the set timeframe, a sequence of events, sometimes hard to manage quickly, begins. These range from a delay in operating units to generating outgoing correspondence based on outdated data and sending it to customers. As a result, the...

Data migration in 4 minutes and 30 seconds with the VSoft archITekt platform

Today, IT companies do not exist without specialised tools. These can be commercial solutions, open source, as well as those created internally. At VSoft, when creating systems for our customers, we rely on the internal low-code platform VSoft archITekt. This helps us to implement solutions faster, in a more flexible and optimal way. Over these 26 years, we have created dozens of systems for a variety of industries. A major success is that we create many of them together with our customers. We have developed procedures for working on projects simultaneously, so that such cooperation accelerates the intellectual and business growth of both teams. When executing dedicated projects, we practically always have to deal with data migration. It takes place once or iteratively several times - depending on the type, quantity and quality of the data. This time it was not easy, we migrated several thousand insurance policies from the old system to our VSoft Insurance Platform. The data to b...

Low-code: does performance matter?

"Begin with the end in mind" that’s the second one of “7 Habits of Highly Effective People” by Stephen Covey. Does it apply when implementing a low-code platform? In my opinion, yes, and very much so. I have recently had a talk with a potential customer who is having problems with a system based on low-code. The very construction and implementation of the system took place without any problems, but over time it turned out that the platform used is completely not adapted to the size of the business and is not able to support the required amount of data (although from the perspective of "traditional" systems, these volumes are nothing extraordinary). Unfortunately, this pattern is repeated relatively often. There are many manufacturers of low-code platforms who have focused only on the fancy user interface and the speed of building small applications. However, they often lack experience or an idea how to approach more complex systems that appear in large organizations. They promise nirvana and u...

Low-code solution for complex, high-performance systems? Sounds impossible. Or is it?

There is a stereotype that low-code platforms create software that is slow and limited in functionality. As with any stereotype, there is some truth to that, but not much. To find out what the reality is, at first, we need to start with how high-performance systems are built using general-purpose programming languages. Let’s get to the bottom of this and then confront it with what low-code has to offer. Is custom programming really such a great advantage compared to low-code solutions? Or is it a drawback? What makes software “slow”? What does "slow" really mean in terms of a typical enterprise application? By "typical" I mean a 3-layer classic: Web UI + service backend + databases. "Slow" can come from: Database queries being far from optimal - missing indexes, outdated statistics, bad join strategies etc. Unnecessary queries - missing caches or “chatty” algorithms assuming that fetching more data from database or external services is free and i...