Sherbim

Backend + API

Ndertojme sistemet pas UI. API REST, GraphQL, WebSocket / SSE, perpunim background-job, integrime me sherbime third-party. Linja jone SaaS drejton ~50 endpoints prodhim ne Rails (Outsourcing, Finance) dhe Node/TypeScript (HRS, Logistics, Leads, CMS) — i njejti stack qe rekomandojme.

Rezultate konkrete

  • REST + GraphQL API — me versionim, te dokumentuara (OpenAPI), te autentikuara (OAuth2, JWT, API key).
  • Pipeline background-job — Sidekiq, BullMQ, Celery; cron + scheduled jobs.
  • Funksione real-time — WebSocket, Server-Sent Events, pub/sub permes Redis ose Kafka.
  • Integrime third-party — Stripe, SendGrid, Twilio, DocuSign, Salesforce, HubSpot, Airtable.
  • Trajtim webhook + retry — idempotency keys, dead-letter queues, replay tooling.
  • Migrime — migrime gjuhesh (Rails → Go, PHP → Node), upgrades framework (Rails 5→7, Node LTS), migrime database (MySQL → Postgres).

Me cfare punojme

Zgjedhim cfare i pershtatet ekipit tuaj. Nuk imponojme preferencat tona.

Languages

Node.js + TypeScript (deepest) · Ruby on Rails · Python (FastAPI, Django) · Go · Java/Kotlin (Spring) · Elixir/Phoenix (specialised)

Databases

PostgreSQL (default) · MySQL · MongoDB · Redis · DynamoDB · ClickHouse

Queues + jobs

Sidekiq (Ruby) · BullMQ (Node) · Celery (Python) · RabbitMQ · Kafka · AWS SQS

API patterns

REST (default) · GraphQL · tRPC · gRPC (internal RPC) · WebSocket · SSE

ORMs

Prisma (TypeScript) · ActiveRecord (Rails) · SQLAlchemy (Python) · Drizzle (TypeScript)

Testing

Vitest, Jest (Node) · RSpec, Minitest (Ruby) · pytest (Python) · Postman/Bruno + automation

Si punojme

01

Zbulim (1 jave)

Dizajn kontrate API, model te dhenash, mapim integrimi third-party. Output: spec OpenAPI + diagrame ERD.

02

Skema + scaffolding (1 jave)

Migrime database, shtrese model, seed data, auth baze. Asgje e ekspozuar ende ne bote — por themeli eshte i testueshem.

03

Ndertim endpoints (3-8 jave)

Route per route, me teste. Sekuence sipas dependency: read-only fillimisht, writes te dyta, integrime te treta.

04

Production hardening

Rate limiting, observability, log aggregation, on-call runbooks. Suite testesh integrimi Postman/Bruno per kontrolle te vazhdueshme shendeti.

Nga prodhimi yne

Merot Outsourcing API (Rails 7)

70+ kontrollore, JWT auth, Sidekiq per background jobs, integrime Stripe + DocuSign + SendGrid. Multi-product (admin / employer / employee) me akses me role.

Merot Logistics backend (Node + TS + Prisma)

Multi-tenant white-label SaaS — dergesa, COD, GPS, BullMQ per background sync, integrim Infobip SMS/WhatsApp.

Merot CMS (Node + TS + Prisma)

Content API headless qe i sherben merot.com + outsourcing blogs. Endpoints public read + admin write.

Nearshore delivery sipas tregut

Faqet e shteteve shpjegojne besimin, zonen kohore, compliance dhe pyetjet e delivery qe bleresit i bejne para zgjedhjes se partnerit software.

North Macedonia

Zhvillim softueri për kompani maqedonase: web aplikacione, aplikacione mobile, cloud sisteme, automatizim AI dhe integrime nga ekipet inxhinierike të Merot në Shkup.

Germany

Senior Balkan software teams for German companies: web, mobile, AI, cloud and integrations with EU timezone overlap, GDPR-aware delivery and DACH communication.

Austria

Nearshore web, mobile, cloud and AI engineering for Austrian SMEs and product teams. EU timezone, DACH communication, GDPR-aware delivery.

Netherlands

Senior React, mobile, backend, cloud and AI teams for Dutch SaaS and operations companies. English-first delivery, EU timezone and GDPR-aware workflows.

Switzerland

Senior Balkan software teams for Swiss companies: secure web, backend, cloud, AI and integrations with DACH communication and privacy-aware delivery.

Sweden

Nearshore web, mobile, backend, cloud and AI engineering for Swedish SaaS and operations teams. Senior delivery, EU timezone, clean handoff.

Denmark

Senior nearshore engineers for Danish product and operations teams: web, backend, mobile, cloud, AI and integrations with EU timezone overlap.

Ireland

Senior EU nearshore engineers for Irish SaaS, fintech and operations teams. Web, backend, mobile, AI and cloud delivery with English-first collaboration.

United States

Senior European software engineers for US companies: custom web apps, mobile apps, backend systems, cloud, AI workflows and integrations with practical US overlap.

Canada

Custom web, mobile, backend, cloud and AI engineering for Canadian companies. Senior European delivery, practical timezone overlap and clean handoff.

United Kingdom

Senior nearshore software engineers for UK companies: custom web apps, backend platforms, cloud modernization, AI workflows and integrations.

France

Nearshore product engineering for French companies: web apps, mobile apps, AI workflows, cloud systems and integrations with EU timezone delivery.

Belgium

Nearshore web, backend, cloud, mobile and AI engineering for Belgian companies operating across languages, regions and EU compliance expectations.

Modeli i angazhimit

Cmimi per backend varet nga data model, API surface, auth, permissions, integrime, reporting, infrastrukture, migration dhe support. Caktoni scoping call; punojme ne stack-un tuaj ekzistues kur kjo eshte praktike dhe japim oferte pasi kerkesat jane te qarta.
Cakto takim

Pyetjet me te shpeshta — Backend + API

Rails vs. Node vs. Go — cfare rekomandoni?

Si standard: Node + TypeScript per projekte te reja nen nje ekip 5-veteshe. Rails kur doni convention maksimal + speed-of-build per aplikacione CRUD. Go kur latency ka rendesi + ekipi juaj tashme drejton Go. Nuk imponojme stack — zgjedhim ate qe i pershtatet ekipit tuaj.

A shkruani teste?

Po — llojin qe mund ta mirembani realisht. Teste unit per logjike te paster, teste integrimi per siperfaqen API, teste end-to-end me kursim. Coverage nuk eshte qellim; saktesia eshte.

Database — Postgres apo dicka tjeter?

Postgres eshte standardi. MySQL kur e keni trasheguar. Mongo per te dhena vertet ne formen e dokumentit (rralle). DynamoDB / Cassandra kur keni tejkaluar shkallen Postgres (shume rralle per shumicen e klienteve).

Idempotency per webhooks?

Po — cdo webhook handler qe shkruajme eshte idempotent. Supozojme qe derguesi do te bej retry (sepse do te bej). Dead-letter queue per deshtime, replay tool per reprocess.

Background jobs — cili stack?

Sidekiq per Rails. BullMQ per Node. Celery per Python. Nuk rekomandojme reinventing — keto jane te pjekur.

GraphQL apo REST?

REST si standard — me e thjeshte per te debug, cache dhe rate-limit. GraphQL kur ekipi i klientit specifikisht e do (read-e thelle te ngjeshura me typing strict). Nuk do te imponojme GraphQL vetem per ta pasur.

Si trajtoni operacione long-running?

Background job me status polling endpoint, ose webhook callback kur eshte e plote. Shmangim te mbajme HTTP requests te hapura me gjate se 30 sekonda.

Po gRPC?

Perdoret nga brenda mes sherbimeve ku latency ka rendesi (p.sh. sherbimi yne PDF ben gRPC nen high load). Rralle i ekspozuar nga jashte — REST eshte me miqesor per klientet.

Le ta percaktojme projektin tuaj — Backend + API

Telefonate 60-minutëshe falas. Plan i shkruar 6-faqesh brenda 48 oresh.

Kontakt

Na tregoni cfare po ndertoni.

Pergjigje gjate orarit.

Pa spam.Direkt te ekipi Merot.