Our tech stack

ababa.tech codes in the Typescript programming language. Every project of ours uses all of these technologies plus a bunch of smaller ones. Here is a little about each of them – what it does, why it is needed and why we use it.

The technologies we use in all our projects:

  1. Typescript (TS) – a programming language built on top of Javascript (JS). It is better than JS because it lets you use variable types. That greatly lowers the chance of bugs and speeds up coding. Counted together with JS, it has been the most popular programming language in the world for ten years now. We chose it precisely because it is so popular – the more widely used a language is, the less we “chain” our clients to ourselves. And it is not popular for nothing – it really lets you build serious systems comfortably and fast.

  2. React – a JS/TS library for building user interfaces. A library means there are ready-made pieces of code you do not have to write from scratch. That removes one of the most annoying parts of a developer’s job – writing scaffolding code (boilerplate) instead of code that actually does something. Boilerplate gives a system its skeleton and keeps it in line with the world’s best practices. Think of it as Lego bricks: your Lego house is built from them, and React is like a box full of all kinds of bricks. Still, React’s real value is not the library itself but the ecosystem built around it. Thousands of developers make countless bricks just for React. By the way, React was made by Facebook, so you can be sure it is not going anywhere! Another main reason why we and so many other developers use React is that building the visual side of a system with it is a relatively small headache. Without React, building a web project would be a lot harder.

  3. Node.js – a technology for running code written in Typescript or Javascript. Node.js lets us program the logic on the server: for example, when you click the “purchase” button, code running in Node.js carries out the transfer of money from you to the seller.

    On top of Node.js we add NestJS (more on it in the next point), which speeds up our coding. But Node.js itself is the core of the system’s logic.

  4. NestJS – a framework that makes Node.js work better. A framework is, you could say, a “more serious” version of a library. If a library is just a box of Lego bricks, a framework is a similar box that also comes with instructions on how to put the bricks together. Depending on the framework, those instructions can be gentle tips (as in React) or very strict rules. NestJS is a strict framework. It tells developers to code one way and not another. That means any developer who knows this framework can easily take over a project built by someone else. We value that a lot, because once again we do not lock our clients into a technology that only we understand.

  5. Git – simply put, Git is a process that sets how developers organise their code. It makes sure no code gets lost, shows the order in which things were coded and who did which part, and avoids conflicts when two developers work on the same spot. All of this (and more) is called version control. When a single developer works alone, it is not that important, but when several developers code at the same time, there is no way around it.

  6. PostgreSQL – a relational database (DB) that manages a system’s data. There are two main groups of databases – relational and non-relational. Simply put, you can picture relational ones as an Excel sheet and non-relational ones as a hierarchical tree. We work with the “Excel-like” kind, because these databases are more versatile. PostgreSQL is one of the most popular databases of this group, and its popularity keeps growing compared to alternatives whose use is slowly but steadily falling, e.g. MySQL.

    The other reason is much simpler – a database is usually picked out of a developer’s habit, experience and comfort. That is how we chose this one for building systems too: we are simply used to working with it.

  7. Docker – simply put, a program that packs code into a container and standardises how it is run. Picture a shipping container. Someone in China loads goods into a container, puts it on a truck, then on a train, then on a cargo ship. The ship sails to Lithuania, and here the same process runs in reverse. The key point – that container fits everywhere, on a Chinese ship and on a Lithuanian truck alike. Docker does the same, just for code. It lets the same code run on Windows, Linux, Mac and so on.

    We use it because without it every developer has a slightly different coding setup, and the code will not run on all of them without fixing extra problems. Docker solves that by packing the whole environment into a container.

  8. Digital Ocean (DO) – a server hosting platform. This is where we host every system we build, this website included. When you open one of our systems, you are actually visiting DO’s servers. Digital Ocean is much friendlier to developers than the alternatives from Amazon, Google or Microsoft. Its hosting is also cheaper than those alternatives. And finally, DO has loads of articles that help a developer solve a specific problem fast.

  9. Sass – an extension of CSS, the language styles are written in. CSS is in charge of a system’s whole look. The font colour, the spacing between lines, the background colour and hundreds of other settings are all configured with CSS. CSS is a very basic language and easy to learn, but it has quite a few shortcomings. Sass extends what CSS can do and speeds up coding N times.

  10. Redux – any app that uses React needs this technology. Redux is like a memory for React, because without it React remembers next to nothing. Imagine you are in an online shop and click the “Add to cart” button. Without Redux, the system would instantly forget you clicked it and could not add the item to your cart. Redux is also used for navigation. Say you clicked the link to the contact page in the menu and then hit the “back” button. Redux remembers where you were before and takes you back there.

    Without Redux or one of its alternatives, no bigger system can work properly. Tiny projects, like some primitive calculator, can get by, but if a system needs “navigation”, it needs Redux too.

  11. CircleCI – a platform that automates “putting” code onto the server. It speeds up a developer’s work a lot and lowers the chance of bugs.

    Without it, after writing the code in their notepad, a developer would have to put it into the testing environment by hand, test it, fix it in the notepad again, upload it to the testing environment again, make sure everything is OK and only then upload it to the “live” environment that the system’s users see. Hard to follow? Ha! That is exactly why we use CircleCI, which automates this whole process. It can test the system automatically, roll back an update if something went wrong, let the developers or the client know that an update went out, and so on.

  12. Sentry – a program that catches bugs. How it works is fairly tricky, but you can picture Sentry latching onto the core of the system like a virus (a good virus!) and, the moment some error happens, instantly alerting the developers that something is wrong. Sentry spots every crash, page that fails to load and freeze as soon as it happens, so developers can start fixing critical bugs sooner. In fact, thanks to this very technology, we sometimes fix a bug before our clients even notice it exists!

  13. Redis – a technology for serving selected items at lightning speed. This is usually called caching. Many people have heard the word from SEO specialists. Caching solves speed problems: for example, when lots of products have to load at once, or when you search for “computer” and only a few out of thousands of products have to be shown. That is exactly what Redis solves – it keeps information in a special memory from which the same information can be loaded really fast. You can picture Redis as the RAM in a computer, or as your “instinctive” memory when you touch a hot frying pan. Touch that pan and your hand just flies off it – in a similar way, Redis flies the information over to your computer.

  14. Nginx – a program for running a server. When we rent a server on Digital Ocean, we basically get a little folder on the internet, a bit like Google Drive. But for that folder to be able to carry a website, we need Nginx. It is a bit like an operating system that the system runs “on top of”. Well, to be precise, Node.js runs on Nginx, and NestJS runs on Node.js.

On this page we honestly tried to explain the technologies we use as simply as we could, but if it still seems complicated, do not worry – you do not need to know how to work with each of them, that is the developer’s job!

Still, knowing that such technologies exist comes in handy when you are choosing a development team to build your system.

Typescript (TS)

A programming language built on top of Javascript (JS). It is better than JS because it lets you use variable types. That greatly lowers the chance of bugs and speeds up coding. Counted together with JS, it has been the most popular programming language in the world for ten years now. We chose it precisely because it is so popular – the more widely used a language is, the less we “chain” our clients to ourselves. And it is not popular for nothing – it really lets you build serious systems comfortably and fast.

React

A JS/TS library for building user interfaces. A library means there are ready-made pieces of code you do not have to write from scratch. That removes one of the most annoying parts of a developer’s job – writing scaffolding code (boilerplate) instead of code that actually does something. Boilerplate gives a system its skeleton and keeps it in line with the world’s best practices. Think of it as Lego bricks: your Lego house is built from them, and React is like a box full of all kinds of bricks. Still, React’s real value is not the library itself but the ecosystem built around it. Thousands of developers make countless bricks just for React. By the way, React was made by Facebook, so you can be sure it is not going anywhere! Another main reason why we and so many other developers use React is that building the visual side of a system with it is a relatively small headache. Without React, building a web project would be a lot harder.