Skip to content

Node.js Development

Backends, interfaces and automation with Node.js – in the same language as your frontend.

dectria builds backends with Node.js and TypeScript: REST and GraphQL APIs, integration layers to existing systems, document generation and automation. We have used Node.js in backend projects since dectria was founded.

For Raiffeisen Rechenzentrum, we built a security handbook with Active Directory sign-in and PDF generation on Node.js; for Raiffeisen Informatik Center Steiermark, a portal based on Node.js and MariaDB.

Because frontend and backend are written in TypeScript, they share types and validation – and the same team can work on both sides.

Official website Michael Jauk Your contact Michael Jauk Contact for backend & architecture

What is Node.js – and when is it worth it?

Node.js is a runtime that executes JavaScript and TypeScript on the server. It is designed to handle many concurrent inputs and outputs efficiently – typical for APIs, integrations and services that wait on databases and other systems.

Node.js is worth it for APIs, integration layers and automation, especially when the frontend is also written in TypeScript. It is less worth it for compute-heavy tasks such as image processing or numerical calculations, or when your team and platform are firmly committed to .NET or Java.

Capabilities

What We Build with Node.js

REST & GraphQL APIs Express / Fastify / NestJS TypeScript in the Backend Database Access (PostgreSQL / MariaDB / SQL Server) Active Directory & LDAP PDF Generation & Document Processing Third-Party System Integration Background Jobs & Queues CLI Tools & Automation pnpm & Monorepos

Use Cases

Typical Use Cases

APIs for Web and Mobile Apps

Backends that provide data for web applications and apps – with authentication, roles and documented interfaces.

Integration into Existing IT Landscapes

Integration layers to Active Directory, SQL Server and existing systems that connect modern interfaces with established IT.

Documents & Automation

Automatic generation of PDFs and letters, data synchronization between systems and recurring tasks as scheduled jobs.

References

Projects with Node.js

RRZ Security Handbook
Web Application

Raiffeisen Rechenzentrum (RRZ)

RRZ Security Handbook
RICS Portal
Web Application

Raiffeisen Informatik Center Steiermark (RICS)

RICS Portal
View all references

FAQ

Node.js FAQ

Why does dectria use Node.js in the backend?
Because frontend and backend then speak the same language: types and validation are shared, and developers work on both sides without switching. For APIs and integrations that mostly wait on databases and other systems, Node.js is also very efficient.
Which Node.js frameworks does dectria use?
We choose the framework per project: NestJS for larger backends with a lot of business logic, Express or Fastify for lean APIs and single services. For web applications with their own server logic, we often use Next.js, which includes API endpoints.
Is Node.js suitable for enterprise applications?
Yes. We run Node.js applications in the banking sector with Active Directory sign-in and strict security requirements. What matters is less the runtime than clean architecture, tests, monitoring and regular dependency updates.
How does dectria connect Node.js to Active Directory and existing systems?
For sign-in, we use LDAP or, with Entra ID, OpenID Connect. We connect existing databases such as SQL Server or MariaDB directly through an ORM, and other systems through their interfaces. We encapsulate the integration in a separate layer, so replacing the legacy system later does not affect the rest of the backend.

Every project starts with a conversation.

Let us talk about your individual needs and goals.

Start a project