Multi-tenant
Retail API
One Spring Boot service. Four brands. Forty stores. JWT-resolved tenants, dynamic Informix routing, two Tomcats behind Nginx.
Custom B2B systems. ERP integration. Industrial Android. B2B · ERP · Android.
One Spring Boot service. Four brands. Forty stores. JWT-resolved tenants, dynamic Informix routing, two Tomcats behind Nginx.
Goods-in on a handheld, not a cart-mounted desktop. Native barcode, ZPL through Citizen / Brother SDKs. Offline queue, optimistic UI.
HQ ↔ 40 stores ↔ central warehouse. Goods-receipt, transfers, invoices. OCR for legacy fax-quality scans. e-invoicing every 30 minutes.
A dozen self-hosted n8n flows. COD reconciliation, O365 triage, e-invoicing, SMS proxy, backup alerting. Versioned in git, every run observable.
HP DL380 Gen8 from scratch. ZFS mirror on enterprise SSDs for the Informix VM. Separate ZFS pool for backups. LACP to a MikroTik CRS326.
A small working slice in a real environment. Not a 60-page Miro board.
No proxy. The person reading your schema is the person you reply to.
Spring Boot over the framework du jour. Postgres over the latest distributed thing.
Every system we've built is still in production. We maintain or hand over cleanly.
Mobile games, consumer social — not us. Small list, on purpose.
Fixed-price for defined slices. Day rate for ongoing. If it can be an email, it will be.
Marko. Faculty of Mathematics, University of Mladenburg. Sysadmin → backend → CTO. Currently CTO of a 40+ store retail group across Serbia, BiH, Montenegro.
VemidSoft is the side that takes outside work. Small client list on purpose. Direct line, every time.