Why do we use Node.js in our backend?

Ryan Dahl kicked off work on Node.js in 2009 on top of two years of research related to server-side web components. The journey of the runtime wasn’t a smooth ride at all but as of today the major component of its semantic versioning hit 18. The revolutionary premise of Node.js was “server-side JavaScript” because since…

Backend for Frontend – What is it?

Backend for Frontend design pattern – BFF for short while it’s definitely not “Best Friends Forever” ? – seems to get some hype lately. It’s nowhere a new thing: one of the first mentions were by SoundCloud guys back in 2015. Basically it’s a specialized case of a more generic API Gateway pattern. Let’s figure…

Why is there a big pay discrepancy between different software engineers?

From a client’s perspective it may be confusing to pick up an independent developer. That’s because prices for what seems to be similar work may be drastically different. For instance, it’s not uncommon for web development work to be priced in $20-200/hr range. How so? Why is there a big pay discrepancy between different software…

When to use microservices?

This is a follow up to an earlier article on microservice architecture implementation principles. It was promised back then to get back to the question of “when to use microservices”. A bit of history The overall architecture pattern of microservices was successfully implemented in 2010-ish. That was an endeavor on the part of a few…

Memory Layers Latency Difference

There’s such term as memory hierarchy in computer architecture. In simplistic terms it’s about structuring different memory/storage types based on response time. In software design & architecture memory hierarchy directly affects performance and may make or break design of a particular software system. Memory layers latency difference is very important to software design. Basics of…

Scalable Backend Secret Sauce

There’s an implementation principle of a scalable backend system which I find among the most important ones. It’s about minimization of compute resources footprint of a request handler for every possible request. This principle isn’t only applicable to handlers in request/response scenarios, e.g. REST or GraphQL APIs. For a session-based handler like a websocket handler…

Microservice Architecture Implementation Principles

Today on microservice architecture implementation principles. I intentionally don’t touch the topic of whether or not one should use microservice architecture for a particular project/company context in this article. That’s a big separate topic of its own and a story for another day. The following list consists of fundamental items which should be kept in…

Don’t rely on a pure technology expert…

…to do the right thing for your business Software development exploded worldwide during the last thirty years or so. Mass adoption of personal computing devices gave rise to the first wave of unprecedented investments into software development. Technology expert was a new dream career. Then it was World Wide Web and finally handheld computing devices.…

Enhanced GitFlow article is live!

We’ve been working on this article with Toptal Blog editorial team since this summer. It’s about an alternative to GitFlow approach to Git branching. Finally it’s live: https://www.toptal.com/gitflow/enhanced-git-flow-explained Check it out if you stuck with Classic GitFlow. It gives some fresh air in regards to version control in your projects.

Long-running transactions considered harmful

When working with ACID storages developers have a powerful tool at their disposal – transactions. Most RDBMS systems out there – think MySQL or PostgreSQL – are fundamentally ACID storages. Developers learn transactions as part of any basics course on RDBMSes. They seem pretty organic to underlying databases. One may get really surprised by the…