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
Zbulim (1 jave)
Dizajn kontrate API, model te dhenash, mapim integrimi third-party. Output: spec OpenAPI + diagrame ERD.
Skema + scaffolding (1 jave)
Migrime database, shtrese model, seed data, auth baze. Asgje e ekspozuar ende ne bote — por themeli eshte i testueshem.
Ndertim endpoints (3-8 jave)
Route per route, me teste. Sekuence sipas dependency: read-only fillimisht, writes te dyta, integrime te treta.
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.
Nga vijne keto inxhiniere
Punesim direkt EOR ne dy tregje, keshillim per punesim ne kater te tjere.
Inxhiniere te larte nga Maqedonia e Veriut
Tregu yne i shtepise — burimi me i thelle. ~30,000 profesioniste IT. EOR direkt permes MEROT DOOEL Shkup.
Detaje ligji pune + pagash →Inxhiniere nga Kosova
Popullsia me e re ne Evrope, monedha EUR (pa rrezik FX). EOR direkt permes MEROT L.L.C. Prishtine.
Detaje ligji pune + pagash →Plus 4 tregje keshillimi
Shqiperia, Serbia, Bullgaria, Mali i Zi — keshillim per punesim + partnere lokale te verifikuar pagash. Shihni landing-un e plote outsourcing per trade-offs.
Outsourcing landing →Modeli i angazhimit
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.