[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"portal-settings:stajic:sr":3,"public-menus:all":38,"post:enterprise-grade-multi-tenant-architecture-for-an-international-platform:sr":221,"related:post:enterprise-grade-multi-tenant-architecture-for-an-international-platform:sr:1":852},{"statusCode":4,"data":5,"message":37},200,{"tenantId":6,"lang":7,"defaultLang":8,"siteUrl":9,"contactEmail":10,"brandName":11,"logoUrl":12,"siteName":11,"siteDescription":13,"ogImage":10,"robotsIndex":14,"socialLinks":10,"reservedSlugs":10,"seoPolicy":15},"stajic","sr","de","https:\u002F\u002Fstajic.de",null,"Stajic Platform","\u002FLogo_Planet.svg","Stajic Portal",true,{"branding":16,"relatedContent":17,"crossDomainLinks":18},{"logoUrl":12},{"enabled":14},[19,22,25,28,31,34],{"url":20,"label":21,"isActive":14,"showInFooter":14,"includeInSameAs":14},"https:\u002F\u002Ffigure.rocks","figure.rocks",{"url":23,"label":24,"isActive":14,"showInFooter":14,"includeInSameAs":14},"https:\u002F\u002Floving.rocks","loving.rocks",{"url":26,"label":27,"isActive":14,"showInFooter":14,"includeInSameAs":14},"https:\u002F\u002Fbazify.com","bazify.com",{"url":29,"label":30,"isActive":14,"showInFooter":14,"includeInSameAs":14},"https:\u002F\u002Fbazify.de","bazify.de",{"url":32,"label":33,"isActive":14,"showInFooter":14,"includeInSameAs":14},"https:\u002F\u002Fbazify.at","bazify.at",{"url":35,"label":36,"isActive":14,"showInFooter":14,"includeInSameAs":14},"https:\u002F\u002Fbazify.ba","bazify.ba","Portal settings resolved",[39,45],{"id":40,"name":41,"location":42,"isActive":14,"isDefault":43,"items":44},1,"main-navigation","header",false,[],{"id":46,"name":47,"location":48,"isActive":14,"isDefault":14,"items":49},4,"main-menu","sidebar",[50,66,79,93,103,118,133],{"id":51,"title":52,"url":60,"target":61,"icon":62,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":64,"portfolioId":10,"children":65},"item-18",{"de":53,"en":54,"es":55,"fr":56,"it":54,"ru":57,"sr":58,"zh":59},"Startseite","Home","Inicio","Accueil","Главная","Почетна","首页","\u002Ffull-stack-web-developer-munich-performance-seo-and-maintainable-builds","_self","i-lucide-home","page",111,[],{"id":67,"title":68,"url":75,"target":61,"icon":76,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":77,"portfolioId":10,"children":78},"item-22",{"de":69,"en":69,"es":70,"fr":69,"it":71,"ru":72,"sr":73,"zh":74},"Vision","Visión","Visione","Видение","Визија","想象","\u002Fueber-uns-webdesign-muenchen-webaplikation","i-lucide-eye",113,[],{"id":80,"title":81,"url":89,"target":61,"icon":90,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":91,"portfolioId":10,"children":92},"item-19",{"de":82,"en":83,"es":84,"fr":83,"it":85,"ru":86,"sr":87,"zh":88},"Leistungen","Services","Servicios","Servizi","Услуги","Услуге","服务","\u002Fservices-dienstleistungen-muenchen","i-lucide-wrench",116,[],{"id":94,"title":95,"url":99,"target":61,"icon":100,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":101,"portfolioId":10,"children":102},"item-23",{"de":96,"en":96,"es":96,"fr":96,"it":96,"ru":97,"sr":97,"zh":98},"Blog","Блог","博客","\u002Fblog","i-lucide-book-open",112,[],{"id":104,"title":105,"url":114,"target":61,"icon":115,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":116,"portfolioId":10,"children":117},"item-32",{"de":106,"en":107,"es":108,"fr":109,"it":110,"ru":111,"sr":112,"zh":113},"Neue Technologien","New Technologies","Nuevas tecnologías","Nouvelles technologies","Nuove tecnologie","Новые технологии","Нове технологије","新技术！","\u002Fneue-webtechnologien","i-lucide-sparkles",122,[],{"id":119,"title":120,"url":129,"target":61,"icon":130,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":131,"portfolioId":10,"children":132},"item-20",{"de":121,"en":122,"es":123,"fr":124,"it":125,"ru":126,"sr":127,"zh":128},"Kontakt","Contact us!","Contacto","Contact","Contatto","Контакт","Контактирајте нас","联系我们！","\u002Fcontact","i-lucide-mail",115,[],{"id":134,"title":135,"url":144,"target":61,"icon":145,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":146,"portfolioId":10,"children":147},"item-21",{"de":136,"en":137,"es":138,"fr":139,"it":140,"ru":141,"sr":142,"zh":143},"Unsere Arbeit","Our Work","Nuestro trabajo","Nos réalisations","I nostri lavori","Наши работы","Наши радови","文件夹","\u002Fportfolio","i-lucide-briefcase",114,[148,161,175,191,206],{"id":149,"title":150,"url":144,"target":61,"icon":159,"isActive":14,"type":63,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":146,"portfolioId":10,"children":160},"item-24",{"de":151,"en":152,"es":153,"fr":154,"it":155,"ru":156,"sr":157,"zh":158},"Alle Projekte","All Projects","Todos los proyectos","Tous les projets","Tutti i progetti","Все проекты","Сви пројекти","所有项目","i-lucide-grid-3x3",[],{"id":162,"title":163,"url":171,"target":61,"icon":172,"isActive":14,"type":173,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":10,"portfolioId":10,"children":174},"item-29",{"de":164,"en":165,"es":166,"fr":167,"it":168,"ru":169,"sr":170,"zh":143},"Local Roots, Global Reach","Local Roots - Global Reach","Empresa local ","Entreprise locale","Azienda locale","Местная компания","Локално предузеће глобално тржиште","\u002Fportfolio\u002Flocal-roots-global-reach-communication-media-systems-for-modern-business","i-lucide-globe-2","custom",[],{"id":176,"title":177,"url":186,"target":61,"icon":187,"isActive":14,"type":188,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":10,"portfolioId":189,"children":190},"menu-2916d060-8681-482a-af9a-c107a8bc30d8",{"de":178,"en":179,"es":180,"fr":181,"it":182,"ru":183,"sr":184,"zh":185},"Von Rohdaten zu verifizierbarem KI-Kontext: Eine praktische Architektur für agentenbereite Informationen","From Raw Data to Verifiable AI Context:","De datos sin procesar a contexto de IA verificable: una arquitectura práctica para información lista para agentes","Des données brutes au contexte d'IA vérifiable : une architecture pratique pour des informations prêtes pour les agents","Dai dati grezzi a un contesto IA verificabile: Un'architettura pratica per informazioni pronte per gli agenti","От необработанных данных к верифицируемому контексту ИИ: практическая архитектура информации, готовой для агентов","Od sirovih podataka do proverljivog AI konteksta: Praktična arhitektura za informacije spremne za agente","从原始数据到可验证的 AI 上下文：面向智能体就绪信息的实用架构","\u002Fportfolio\u002Ffrom-raw-data-to-verifiable-ai-context-a-practical-architecture-for-agent-ready-information","i-lucide-database","portfolio",22,[],{"id":192,"title":193,"url":202,"target":61,"icon":203,"isActive":14,"type":188,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":10,"portfolioId":204,"children":205},"menu-e2061cd7-ff53-49d5-a0e8-3d49090577c0",{"de":194,"en":195,"es":196,"fr":197,"it":198,"ru":199,"sr":200,"zh":201},"Präsenzplattformen — Unternehmenskommunikation","Presence Platforms — Enterprise Communication","Plataformas de presencia — Comunicación empresarial","Plateformes de présence — Communication d'entreprise","Presence Platforms — Comunicazione aziendale","Платформы присутствия — Корпоративные коммуникации","Presence platforme — Poslovna komunikacija","Presence 平台 — 企业通信","\u002Fportfolio\u002Fpresence-platforms-enterprise-communication-that-wins-without-competing","i-lucide-badge-percent",21,[],{"id":207,"title":208,"url":217,"target":61,"icon":218,"isActive":14,"type":188,"productId":10,"categoryId":10,"shopCategoryId":10,"articleId":10,"pageId":10,"portfolioId":219,"children":220},"menu-a781582e-e90d-418e-b8c9-b070bc37c37e",{"de":209,"en":210,"es":211,"fr":212,"it":213,"ru":214,"sr":215,"zh":216},"Maximierung des POS-ROI durch Konsistenz","Maximizing POS ROI Through Consistent","Maximizar el ROI del POS a través de constante","Maximiser le ROI du PDV grâce à la cohérence","Massimizzare il ROI del POS attraverso costante","Максимизация ROI POS за счет последовательного","Maksimizacija POS ROI-ja kroz dosledno","通过持续最大化 POS 投资回报率","\u002Fportfolio\u002Ffrom-vision-to-value-maximizing-pos-roi-through-consistent-ci-creation-and-strategic-branding","i-lucide-briefcase-business",11,[],{"statusCode":4,"data":222,"message":851},{"id":223,"title":224,"slug":225,"content":226,"contentJson":227,"excerpt":445,"featuredImage":446,"featuredImageAlt":447,"featuredImageCaption":10,"featuredImageTitle":10,"featuredImageCopyright":10,"featuredImageAuthor":10,"featuredImageSourceUrl":10,"featuredImageLicense":10,"featuredImageIsAiGenerated":43,"status":448,"publishedAt":449,"createdAt":450,"updatedAt":451,"seoLocalePaths":452,"categories":460,"author":500,"translations":505},"381","Višezakupna arhitektura korporativnog nivoa za međunarodnu platformu","enterprise-grade-multi-tenant-architecture-for-an-international-platform","\u003Ch1>Loving Rocks\u003C\u002Fh1>\n\u003Ch2>Arhitektura sa više zakupaca (multi-tenant) poslovnog nivoa za međunarodnu platformu za venčanja\u003C\u002Fh2>\n\u003Cp>\u003Cb>Loving Rocks\u003C\u002Fb> je međunarodna platforma za venčanja projektovana kao \u003Cb>sistem sa više zakupaca, više jezika i izolovanim podacima\u003C\u002Fb>, dizajniran za dugoročnu skalabilnost, operativnu stabilnost i širenje tržišta. Iz perspektive IT rukovodstva, platforma prati principe koji se obično nalaze u SaaS arhitekturama poslovnog nivoa, a ne u tradicionalnim veb-sajtovima sa sadržajem.\u003C\u002Fp>\n\u003Chr class=\"my-8\">\n\u003Ch2>1. Arhitektonska filozofija\u003C\u002Fh2>\n\u003Cp>Osnovni arhitektonski cilj Loving Rocks-a je \u003Cb>kontrolisana skalabilnost bez rizika po druge zakupce\u003C\u002Fb>.\u003C\u002Fp>\n\u003Cp>Umesto izgradnje monolitnog sistema sadržaja sa jednom bazom podataka, platforma usvaja:\u003C\u002Fp>\n\u003Cul>\u003Cli>strogu \u003Cb>izolaciju zakupaca\u003C\u002Fb>\u003C\u002Fli>\u003Cli>\u003Cb>nezavisno vlasništvo nad podacima\u003C\u002Fb>\u003C\u002Fli>\u003Cli>centralizovanu aplikativnu logiku\u003C\u002Fli>\u003Cli>predvidivo operativno ponašanje tokom rasta\u003C\u002Fli>\u003C\u002Ful>\n\u003Cp>Ovo omogućava platformi da se skalira kroz više domena, zemalja, jezika i pravnih konteksta bez strukturnog refaktorisanja.\u003C\u002Fp>\n\u003Chr class=\"my-8\">\n\u003Ch2>2. Model sa više zakupaca (Izolacija zakupaca po dizajnu)\u003C\u002Fh2>\n\u003Cp>Loving Rocks je implementiran kao \u003Cb>pravi sistem sa više zakupaca\u003C\u002Fb>, a ne kao zaobilazno rešenje sa deljenom tabelom.\u003C\u002Fp>\n\u003Ch3>Ključne karakteristike\u003C\u002Fh3>\n\u003Cul>\u003Cli>\u003Cb>Jedna baza podataka po zakupcu\u003C\u002Fb>\u003C\u002Fli>\u003Cli>Nema deljenih podataka zakupaca na sloju za perzistenciju\u003C\u002Fli>\u003Cli>Kontekst zakupca se rešava na nivou zahteva (domen \u002F lokalizacija \u002F konfiguracija)\u003C\u002Fli>\u003C\u002Ful>\n\u003Ch3>Prednosti\u003C\u002Fh3>\n\u003Cul>\u003Cli>\u003Cb>Izolacija podataka po podrazumevanoj vrednosti\u003C\u002Fb>: kvar, oštećenje ili pogrešna konfiguracija kod jednog zakupca ne može uticati na druge.\u003C\u002Fli>\u003Cli>\u003Cb>Bezbednost i usklađenost\u003C\u002Fb>: GDPR specifičan za zakupca, pravni tekstovi i politike zadržavanja podataka obrađuju se nezavisno.\u003C\u002Fli>\u003Cli>\u003Cb>Operativna fleksibilnost\u003C\u002Fb>: rezervna kopija, obnavljanje, migracija ili dekomisioniranje mogu se izvršiti po zakupcu bez uticaja na druge.\u003C\u002Fli>\u003Cli>\u003Cb>Spremnost za buduću monetizaciju\u003C\u002Fb>: podržava premium zakupce, white-label implementacije i skupove funkcija specifičnih za region bez grananja koda.\u003C\u002Fli>\u003C\u002Ful>\n\u003Cp>Ovo je ista strategija izolacije koja se koristi u zrelim SaaS platformama poslovnog nivoa.\u003C\u002Fp>\n\u003Chr class=\"my-8\">\n\u003Ch2>3. Strategija sloja podataka\u003C\u002Fh2>\n\u003Cp>Svaki zakupac radi na svojoj \u003Cb>sopstvenoj posvećenoj bazi podataka\u003C\u002Fb>.\u003C\u002Fp>\n\u003Ch3>Posledice (namerne)\u003C\u002Fh3>\n\u003Cul>\u003Cli>Nema spajanja podataka između zakupaca\u003C\u002Fli>\u003Cli>Nema globalnih tabela sadržaja\u003C\u002Fli>\u003Cli>Nema vektora slučajnog curenja podataka\u003C\u002Fli>\u003C\u002Ful>\n\u003Ch3>Pregled strukture\u003C\u002Fh3>\n\u003Cul>\u003Cli>\u003Cb>Šema sadržaja\u003C\u002Fb>: članci, vodiči, kategorije, tagovi, metapodaci\u003C\u002Fli>\u003Cli>\u003Cb>Šema lokalizacije\u003C\u002Fb>: jezički normalizovan sadržaj, prevodi, metapodaci specifični za lokalizaciju\u003C\u002Fli>\u003Cli>\u003Cb>Šema konfiguracije zakupca\u003C\u002Fb>: mapiranje domena, omogućeni jezici, brendiranje, pravne stranice\u003C\u002Fli>\u003C\u002Ful>\n\u003Cp>Ovaj pristup menja malo povećanje složenosti infrastrukture za \u003Cb>dugoročnu sigurnost i predvidivost\u003C\u002Fb>.\u003C\u002Fp>\n\u003Chr class=\"my-8\">\n\u003Ch2>4. Internacionalizacija na nivou platforme\u003C\u002Fh2>\n\u003Cp>Internacionalizacija se ne tretira kao funkcija frontenda, već kao \u003Cb>osnovna sposobnost platforme\u003C\u002Fb>.\u003C\u002Fp>\n\u003Ch3>Trenutne mogućnosti\u003C\u002Fh3>\n\u003Cul>\u003Cli>\u003Cb>8+ podržanih jezika\u003C\u002Fb>\u003C\u002Fli>\u003Cli>Skladištenje sadržaja svesno jezika\u003C\u002Fli>\u003Cli>Lokalizovani URL-ovi i metapodaci\u003C\u002Fli>\u003Cli>Pravne stranice i stranice privatnosti specifične za tržište\u003C\u002Fli>\u003C\u002Ful>\n\u003Ch3>Tehničke implikacije\u003C\u002Fh3>\n\u003Cul>\u003Cli>Prebacivanje jezika ne duplira logiku sadržaja\u003C\u002Fli>\u003Cli>SEO signali (metapodaci, struktura) generišu se po lokalizaciji\u003C\u002Fli>\u003Cli>Novi jezici se mogu omogućiti bez uticaja na postojeće zakupce\u003C\u002Fli>\u003C\u002Ful>\n\u003Cp>Ovo izbegava uobičajeni anti-pattern „prevedenog korisničkog interfejsa preko sadržaja na jednom jeziku“.\u003C\u002Fp>\n\u003Chr class=\"my-8\">\n\u003Ch2>5. Model isporuke frontenda\u003C\u002Fh2>\n\u003Cp>Frontend je optimizovan za \u003Cb>performanse, predvidivost i SEO stabilnost\u003C\u002Fb>.\u003C\u002Fp>\n\u003Ch3>Ključni principi\u003C\u002Fh3>\n\u003Cul>\u003Cli>Pre-renderovan HTML za primarni sadržaj\u003C\u002Fli>\u003Cli>Minimalan JavaScript tokom izvršavanja\u003C\u002Fli>\u003Cli>Nema nepotrebne SPA složenosti\u003C\u002Fli>\u003Cli>Potpuno responsivan izgled\u003C\u002Fli>\u003C\u002Ful>\n\u003Cp>Iz perspektive CTO-a, ovo obezbeđuje konzistentno vreme učitavanja globalno, nizak operativni rizik, čistu separaciju između isporuke sadržaja i poslovne logike, kao i odličnu indeksabilnost pretraživača na svim tržištima.\u003C\u002Fp>\n\u003Chr class=\"my-8\">\n\u003Ch2>6. Zašto je arhitektura sa više zakupaca važna (perspektiva CTO-a)\u003C\u002Fh2>\n\u003Cp>Za platformu namenjenu međunarodnom poslovanju, \u003Cb>dizajn sa više zakupaca nije opcija\u003C\u002Fb>.\u003C\u002Fp>\n\u003Cp>Bez toga, rast uvodi spajanje između tržišta, pravni rizik, operativnu krhkost i uska grla u skaliranju.\u003C\u002Fp>\n\u003Cp>Sa odabranom arhitekturom, Loving Rocks dobija:\u003C\u002Fp>\n\u003Cul>\u003Cli>\u003Cb>horizontalnu skalabilnost\u003C\u002Fb>\u003C\u002Fli>\u003Cli>\u003Cb>regionalnu nezavisnost\u003C\u002Fb>\u003C\u002Fli>\u003Cli>\u003Cb>jasne granice vlasništva\u003C\u002Fb>\u003C\u002Fli>\u003Cli>\u003Cb>održivost poslovnog nivoa\u003C\u002Fb>\u003C\u002Fli>\u003C\u002Ful>\n\u003Cp>Ovo čini platformu pogodnom ne samo za isporuku sadržaja, već i za buduće integracije, partnerstva i white-label slučajeve upotrebe.\u003C\u002Fp>\n\u003Chr class=\"my-8\">\n\u003Ch2>7. Pregled arhitekture na visokom nivou\u003C\u002Fh2>\n\u003Cp>Logički slojevi arhitekture:\u003C\u002Fp>\n\u003Cpre class=\"code-block\">\u003Ccode>┌──────────────────────────────┐\n│          Frontend            │\n│  (Pre-rendered, responsive)  │\n└──────────────┬───────────────┘\n               │\n┌──────────────▼───────────────┐\n│     Application Layer        │\n│  - Tenant resolution         │\n│  - Localization logic        │\n│  - Content orchestration     │\n└──────────────┬───────────────┘\n               │\n┌──────────────▼───────────────┐\n│      Tenant Databases        │\n│  - One DB per tenant         │\n│  - Isolated schemas          │\n│  - Independent lifecycle     │\n└──────────────────────────────┘\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cb>Ključno pravilo dizajna:\u003C\u002Fb> Zakupac nikada nije svestan postojanja drugog zakupca.\u003C\u002Fp>\n\u003Chr class=\"my-8\">\n\u003Ch2>8. Operativna stabilnost i upravljanje rizikom\u003C\u002Fh2>\n\u003Cp>Sa operativne tačke gledišta, platforma podržava:\u003C\u002Fp>\n\u003Cul>\u003Cli>povratak na prethodno stanje na nivou zakupca\u003C\u002Fli>\u003Cli>prozore za održavanje na nivou zakupca\u003C\u002Fli>\u003Cli>rezervne kopije na nivou zakupca\u003C\u002Fli>\u003Cli>kontrolisano uvođenje promena\u003C\u002Fli>\u003C\u002Ful>\n\u003Cp>Kvarovi su \u003Cb>izolovani, vidljivi i reverzibilni\u003C\u002Fb>, što je fundamentalni zahtev preduzeća.\u003C\u002Fp>\n\u003Chr class=\"my-8\">\n\u003Ch2>Zaključak\u003C\u002Fh2>\n\u003Cp>\u003Cb>Loving Rocks\u003C\u002Fb> nije tradicionalni veb-sajt za venčanja. To je \u003Cb>međunarodna platforma za sadržaj sa više zakupaca\u003C\u002Fb> izgrađena na arhitektonskim principima preduzeća: izolovane baze podataka, dizajn sa prioritetom jezika, skalabilan bek-end, frontend fokusiran na performanse i dugoročna operativna sigurnost.\u003C\u002Fp>\n\u003Cp>Ova arhitektura pruža čvrstu osnovu za održivi rast, regionalno širenje i buduću evoluciju platforme bez akumulacije tehničkog duga.\u003C\u002Fp>",{"time":228,"blocks":229,"version":444},1769731200000,[230,233,237,241,244,247,250,253,262,265,267,270,273,277,283,286,293,296,298,301,304,307,313,316,322,325,327,330,333,336,343,346,352,355,357,360,363,366,373,376,378,381,384,387,390,397,400,402,405,408,412,415,417,420,423,430,433,435,438,441],{"data":231,"type":42},{"text":232,"level":40},"Loving Rocks",{"data":234,"type":42},{"text":235,"level":236},"Arhitektura sa više zakupaca (multi-tenant) poslovnog nivoa za međunarodnu platformu za venčanja",2,{"data":238,"type":240},{"text":239},"\u003Cb>Loving Rocks\u003C\u002Fb> je međunarodna platforma za venčanja projektovana kao \u003Cb>sistem sa više zakupaca, više jezika i izolovanim podacima\u003C\u002Fb>, dizajniran za dugoročnu skalabilnost, operativnu stabilnost i širenje tržišta. Iz perspektive IT rukovodstva, platforma prati principe koji se obično nalaze u SaaS arhitekturama poslovnog nivoa, a ne u tradicionalnim veb-sajtovima sa sadržajem.","paragraph",{"data":242,"type":243},{},"delimiter",{"data":245,"type":42},{"text":246,"level":236},"1. Arhitektonska filozofija",{"data":248,"type":240},{"text":249},"Osnovni arhitektonski cilj Loving Rocks-a je \u003Cb>kontrolisana skalabilnost bez rizika po druge zakupce\u003C\u002Fb>.",{"data":251,"type":240},{"text":252},"Umesto izgradnje monolitnog sistema sadržaja sa jednom bazom podataka, platforma usvaja:",{"data":254,"type":261},{"items":255,"style":260},[256,257,258,259],"strogu \u003Cb>izolaciju zakupaca\u003C\u002Fb>","\u003Cb>nezavisno vlasništvo nad podacima\u003C\u002Fb>","centralizovanu aplikativnu logiku","predvidivo operativno ponašanje tokom rasta","unordered","list",{"data":263,"type":240},{"text":264},"Ovo omogućava platformi da se skalira kroz više domena, zemalja, jezika i pravnih konteksta bez strukturnog refaktorisanja.",{"data":266,"type":243},{},{"data":268,"type":42},{"text":269,"level":236},"2. Model sa više zakupaca (Izolacija zakupaca po dizajnu)",{"data":271,"type":240},{"text":272},"Loving Rocks je implementiran kao \u003Cb>pravi sistem sa više zakupaca\u003C\u002Fb>, a ne kao zaobilazno rešenje sa deljenom tabelom.",{"data":274,"type":42},{"text":275,"level":276},"Ključne karakteristike",3,{"data":278,"type":261},{"items":279,"style":260},[280,281,282],"\u003Cb>Jedna baza podataka po zakupcu\u003C\u002Fb>","Nema deljenih podataka zakupaca na sloju za perzistenciju","Kontekst zakupca se rešava na nivou zahteva (domen \u002F lokalizacija \u002F konfiguracija)",{"data":284,"type":42},{"text":285,"level":276},"Prednosti",{"data":287,"type":261},{"items":288,"style":260},[289,290,291,292],"\u003Cb>Izolacija podataka po podrazumevanoj vrednosti\u003C\u002Fb>: kvar, oštećenje ili pogrešna konfiguracija kod jednog zakupca ne može uticati na druge.","\u003Cb>Bezbednost i usklađenost\u003C\u002Fb>: GDPR specifičan za zakupca, pravni tekstovi i politike zadržavanja podataka obrađuju se nezavisno.","\u003Cb>Operativna fleksibilnost\u003C\u002Fb>: rezervna kopija, obnavljanje, migracija ili dekomisioniranje mogu se izvršiti po zakupcu bez uticaja na druge.","\u003Cb>Spremnost za buduću monetizaciju\u003C\u002Fb>: podržava premium zakupce, white-label implementacije i skupove funkcija specifičnih za region bez grananja koda.",{"data":294,"type":240},{"text":295},"Ovo je ista strategija izolacije koja se koristi u zrelim SaaS platformama poslovnog nivoa.",{"data":297,"type":243},{},{"data":299,"type":42},{"text":300,"level":236},"3. Strategija sloja podataka",{"data":302,"type":240},{"text":303},"Svaki zakupac radi na svojoj \u003Cb>sopstvenoj posvećenoj bazi podataka\u003C\u002Fb>.",{"data":305,"type":42},{"text":306,"level":276},"Posledice (namerne)",{"data":308,"type":261},{"items":309,"style":260},[310,311,312],"Nema spajanja podataka između zakupaca","Nema globalnih tabela sadržaja","Nema vektora slučajnog curenja podataka",{"data":314,"type":42},{"text":315,"level":276},"Pregled strukture",{"data":317,"type":261},{"items":318,"style":260},[319,320,321],"\u003Cb>Šema sadržaja\u003C\u002Fb>: članci, vodiči, kategorije, tagovi, metapodaci","\u003Cb>Šema lokalizacije\u003C\u002Fb>: jezički normalizovan sadržaj, prevodi, metapodaci specifični za lokalizaciju","\u003Cb>Šema konfiguracije zakupca\u003C\u002Fb>: mapiranje domena, omogućeni jezici, brendiranje, pravne stranice",{"data":323,"type":240},{"text":324},"Ovaj pristup menja malo povećanje složenosti infrastrukture za \u003Cb>dugoročnu sigurnost i predvidivost\u003C\u002Fb>.",{"data":326,"type":243},{},{"data":328,"type":42},{"text":329,"level":236},"4. Internacionalizacija na nivou platforme",{"data":331,"type":240},{"text":332},"Internacionalizacija se ne tretira kao funkcija frontenda, već kao \u003Cb>osnovna sposobnost platforme\u003C\u002Fb>.",{"data":334,"type":42},{"text":335,"level":276},"Trenutne mogućnosti",{"data":337,"type":261},{"items":338,"style":260},[339,340,341,342],"\u003Cb>8+ podržanih jezika\u003C\u002Fb>","Skladištenje sadržaja svesno jezika","Lokalizovani URL-ovi i metapodaci","Pravne stranice i stranice privatnosti specifične za tržište",{"data":344,"type":42},{"text":345,"level":276},"Tehničke implikacije",{"data":347,"type":261},{"items":348,"style":260},[349,350,351],"Prebacivanje jezika ne duplira logiku sadržaja","SEO signali (metapodaci, struktura) generišu se po lokalizaciji","Novi jezici se mogu omogućiti bez uticaja na postojeće zakupce",{"data":353,"type":240},{"text":354},"Ovo izbegava uobičajeni anti-pattern „prevedenog korisničkog interfejsa preko sadržaja na jednom jeziku“.",{"data":356,"type":243},{},{"data":358,"type":42},{"text":359,"level":236},"5. Model isporuke frontenda",{"data":361,"type":240},{"text":362},"Frontend je optimizovan za \u003Cb>performanse, predvidivost i SEO stabilnost\u003C\u002Fb>.",{"data":364,"type":42},{"text":365,"level":276},"Ključni principi",{"data":367,"type":261},{"items":368,"style":260},[369,370,371,372],"Pre-renderovan HTML za primarni sadržaj","Minimalan JavaScript tokom izvršavanja","Nema nepotrebne SPA složenosti","Potpuno responsivan izgled",{"data":374,"type":240},{"text":375},"Iz perspektive CTO-a, ovo obezbeđuje konzistentno vreme učitavanja globalno, nizak operativni rizik, čistu separaciju između isporuke sadržaja i poslovne logike, kao i odličnu indeksabilnost pretraživača na svim tržištima.",{"data":377,"type":243},{},{"data":379,"type":42},{"text":380,"level":236},"6. Zašto je arhitektura sa više zakupaca važna (perspektiva CTO-a)",{"data":382,"type":240},{"text":383},"Za platformu namenjenu međunarodnom poslovanju, \u003Cb>dizajn sa više zakupaca nije opcija\u003C\u002Fb>.",{"data":385,"type":240},{"text":386},"Bez toga, rast uvodi spajanje između tržišta, pravni rizik, operativnu krhkost i uska grla u skaliranju.",{"data":388,"type":240},{"text":389},"Sa odabranom arhitekturom, Loving Rocks dobija:",{"data":391,"type":261},{"items":392,"style":260},[393,394,395,396],"\u003Cb>horizontalnu skalabilnost\u003C\u002Fb>","\u003Cb>regionalnu nezavisnost\u003C\u002Fb>","\u003Cb>jasne granice vlasništva\u003C\u002Fb>","\u003Cb>održivost poslovnog nivoa\u003C\u002Fb>",{"data":398,"type":240},{"text":399},"Ovo čini platformu pogodnom ne samo za isporuku sadržaja, već i za buduće integracije, partnerstva i white-label slučajeve upotrebe.",{"data":401,"type":243},{},{"data":403,"type":42},{"text":404,"level":236},"7. Pregled arhitekture na visokom nivou",{"data":406,"type":240},{"text":407},"Logički slojevi arhitekture:",{"data":409,"type":411},{"code":410},"┌──────────────────────────────┐\n│          Frontend            │\n│  (Pre-rendered, responsive)  │\n└──────────────┬───────────────┘\n               │\n┌──────────────▼───────────────┐\n│     Application Layer        │\n│  - Tenant resolution         │\n│  - Localization logic        │\n│  - Content orchestration     │\n└──────────────┬───────────────┘\n               │\n┌──────────────▼───────────────┐\n│      Tenant Databases        │\n│  - One DB per tenant         │\n│  - Isolated schemas          │\n│  - Independent lifecycle     │\n└──────────────────────────────┘","code",{"data":413,"type":240},{"text":414},"\u003Cb>Ključno pravilo dizajna:\u003C\u002Fb> Zakupac nikada nije svestan postojanja drugog zakupca.",{"data":416,"type":243},{},{"data":418,"type":42},{"text":419,"level":236},"8. Operativna stabilnost i upravljanje rizikom",{"data":421,"type":240},{"text":422},"Sa operativne tačke gledišta, platforma podržava:",{"data":424,"type":261},{"items":425,"style":260},[426,427,428,429],"povratak na prethodno stanje na nivou zakupca","prozore za održavanje na nivou zakupca","rezervne kopije na nivou zakupca","kontrolisano uvođenje promena",{"data":431,"type":240},{"text":432},"Kvarovi su \u003Cb>izolovani, vidljivi i reverzibilni\u003C\u002Fb>, što je fundamentalni zahtev preduzeća.",{"data":434,"type":243},{},{"data":436,"type":42},{"text":437,"level":236},"Zaključak",{"data":439,"type":240},{"text":440},"\u003Cb>Loving Rocks\u003C\u002Fb> nije tradicionalni veb-sajt za venčanja. To je \u003Cb>međunarodna platforma za sadržaj sa više zakupaca\u003C\u002Fb> izgrađena na arhitektonskim principima preduzeća: izolovane baze podataka, dizajn sa prioritetom jezika, skalabilan bek-end, frontend fokusiran na performanse i dugoročna operativna sigurnost.",{"data":442,"type":240},{"text":443},"Ova arhitektura pruža čvrstu osnovu za održivi rast, regionalno širenje i buduću evoluciju platforme bez akumulacije tehničkog duga.","2.28.2","Loving Rocks je platforma za venčanja poslovne klase, dizajnirana sa istinskom više-zakupnom arhitekturom, izolovanim bazama podataka po zakupcu i ugrađenom internacionalizacijom za globalnu skalabilnost, bezbednost i dugoročnu operativnu stabilnost.","\u002Fuploads\u002F2026\u002F01\u002Fenterprise-grade-multi-tenant-architecture-for-an-international-platform-1769789121298-b6v7ak.webp","enterprise-grade-multi-tenant-architecture-for-an-international-platform-1769789121298-b6v7ak","PUBLISHED","2026-01-30T12:04:00.000Z","2026-01-30T16:04:05.940Z","2026-02-20T20:42:52.562Z",{"en":453,"de":454,"sr":455,"es":456,"it":457,"ru":458,"zh":459},"\u002Fblog\u002Fenterprise-grade-multi-tenant-architecture-for-an-international-platform","\u002Fde\u002Fblog\u002Fenterprise-grade-multi-tenant-architecture-for-an-international-platform","\u002Fsr\u002Fblog\u002Fenterprise-grade-multi-tenant-architecture-for-an-international-platform","\u002Fes\u002Fblog\u002Fenterprise-grade-multi-tenant-architecture-for-an-international-platform","\u002Fit\u002Fblog\u002Fenterprise-grade-multi-tenant-architecture-for-an-international-platform","\u002Fru\u002Fblog\u002Fenterprise-grade-multi-tenant-architecture-for-an-international-platform","\u002Fzh\u002Fblog\u002Fenterprise-grade-multi-tenant-architecture-for-an-international-platform",[461,465,469,473,476,480,484,488,492,496],{"id":462,"name":463,"slug":464},39,"Enterprise Delivery OS","enterprise",{"id":466,"name":467,"slug":468},108,"Procjena isporuke","delivery-assessment",{"id":470,"name":471,"slug":472},45,"Referentni model: Digitalna platforma","digital-platform",{"id":101,"name":474,"slug":475},"Overview","overview-digital-platform",{"id":477,"name":478,"slug":479},52,"Referentni model: Isporuka i promjene","delivery-and-change",{"id":481,"name":482,"slug":483},47,"Principi","principles",{"id":485,"name":486,"slug":487},48,"Sposobnosti","capabilities",{"id":489,"name":490,"slug":491},79,"Playbook: Učvršćivanje sigurnosti","security-hardening",{"id":493,"name":494,"slug":495},49,"Kontrole i dokazi","controls",{"id":497,"name":498,"slug":499},80,"Pristup i identitet","access-and-identity",{"id":501,"login":502,"email":503,"displayName":504},"20","rooth8233","","Aleksandar Stajić",[506,718],{"lang":507,"title":508,"content":509,"contentJson":510,"excerpt":717},"en","Enterprise-Grade Multi-Tenant Architecture for an International Platform","{\"time\":1769731200000,\"blocks\":[{\"data\":{\"text\":\"Loving Rocks\",\"level\":1},\"type\":\"header\"},{\"data\":{\"text\":\"Enterprise-Grade Multi-Tenant Architecture for an International Wedding Platform\",\"level\":2},\"type\":\"header\"},{\"data\":{\"text\":\"\u003Cb>Loving Rocks\u003C\u002Fb> is an international wedding platform engineered as a \u003Cb>multi-tenant, multi-language, data-isolated system\u003C\u002Fb>, designed for long-term scalability, operational stability, and market expansion. From an IT leadership perspective, the platform follows principles commonly found in enterprise SaaS architectures rather than traditional content websites.\"},\"type\":\"paragraph\"},{\"data\":{},\"type\":\"delimiter\"},{\"data\":{\"text\":\"1. Architectural Philosophy\",\"level\":2},\"type\":\"header\"},{\"data\":{\"text\":\"The core architectural goal of Loving Rocks is \u003Cb>controlled scalability without cross-tenant risk\u003C\u002Fb>.\"},\"type\":\"paragraph\"},{\"data\":{\"text\":\"Instead of building a monolithic, single-database content system, the platform adopts:\"},\"type\":\"paragraph\"},{\"data\":{\"items\":[\"strict \u003Cb>tenant isolation\u003C\u002Fb>\",\"\u003Cb>independent data ownership\u003C\u002Fb>\",\"centralized application logic\",\"predictable operational behavior under growth\"],\"style\":\"unordered\"},\"type\":\"list\"},{\"data\":{\"text\":\"This allows the platform to scale across multiple domains, countries, languages, and legal contexts without structural refactoring.\"},\"type\":\"paragraph\"},{\"data\":{},\"type\":\"delimiter\"},{\"data\":{\"text\":\"2. Multi-Tenant Model (Tenant Isolation by Design)\",\"level\":2},\"type\":\"header\"},{\"data\":{\"text\":\"Loving Rocks is implemented as a \u003Cb>true multi-tenant system\u003C\u002Fb>, not a shared-table workaround.\"},\"type\":\"paragraph\"},{\"data\":{\"text\":\"Key characteristics\",\"level\":3},\"type\":\"header\"},{\"data\":{\"items\":[\"\u003Cb>One database per tenant\u003C\u002Fb>\",\"No shared tenant data at the persistence layer\",\"Tenant context resolved at request level (domain \u002F locale \u002F configuration)\"],\"style\":\"unordered\"},\"type\":\"list\"},{\"data\":{\"text\":\"Benefits\",\"level\":3},\"type\":\"header\"},{\"data\":{\"items\":[\"\u003Cb>Data isolation by default\u003C\u002Fb>: a failure, corruption, or misconfiguration in one tenant cannot affect others.\",\"\u003Cb>Security & compliance\u003C\u002Fb>: tenant-specific GDPR, legal texts, and retention policies are handled independently.\",\"\u003Cb>Operational flexibility\u003C\u002Fb>: backup, restore, migration, or decommissioning can be performed per tenant without impacting others.\",\"\u003Cb>Future monetization readiness\u003C\u002Fb>: supports premium tenants, white-label deployments, and region-specific feature sets without branching the codebase.\"],\"style\":\"unordered\"},\"type\":\"list\"},{\"data\":{\"text\":\"This is the same isolation strategy used in mature enterprise SaaS platforms.\"},\"type\":\"paragraph\"},{\"data\":{},\"type\":\"delimiter\"},{\"data\":{\"text\":\"3. Data Layer Strategy\",\"level\":2},\"type\":\"header\"},{\"data\":{\"text\":\"Each tenant operates on its \u003Cb>own dedicated database\u003C\u002Fb>.\"},\"type\":\"paragraph\"},{\"data\":{\"text\":\"Consequences (intentional)\",\"level\":3},\"type\":\"header\"},{\"data\":{\"items\":[\"No cross-tenant joins\",\"No global content tables\",\"No accidental data leakage vectors\"],\"style\":\"unordered\"},\"type\":\"list\"},{\"data\":{\"text\":\"Structure overview\",\"level\":3},\"type\":\"header\"},{\"data\":{\"items\":[\"\u003Cb>Content schema\u003C\u002Fb>: articles, guides, categories, tags, metadata\",\"\u003Cb>Localization schema\u003C\u002Fb>: language-normalized content, translations, locale-specific metadata\",\"\u003Cb>Tenant configuration schema\u003C\u002Fb>: domain mapping, enabled languages, branding, legal pages\"],\"style\":\"unordered\"},\"type\":\"list\"},{\"data\":{\"text\":\"This approach trades a small increase in infrastructure complexity for \u003Cb>long-term safety and predictability\u003C\u002Fb>.\"},\"type\":\"paragraph\"},{\"data\":{},\"type\":\"delimiter\"},{\"data\":{\"text\":\"4. Internationalization at Platform Level\",\"level\":2},\"type\":\"header\"},{\"data\":{\"text\":\"Internationalization is not treated as a frontend feature, but as a \u003Cb>core platform capability\u003C\u002Fb>.\"},\"type\":\"paragraph\"},{\"data\":{\"text\":\"Current capabilities\",\"level\":3},\"type\":\"header\"},{\"data\":{\"items\":[\"\u003Cb>8+ supported languages\u003C\u002Fb>\",\"Language-aware content storage\",\"Localized URLs and metadata\",\"Market-specific legal and privacy pages\"],\"style\":\"unordered\"},\"type\":\"list\"},{\"data\":{\"text\":\"Technical implications\",\"level\":3},\"type\":\"header\"},{\"data\":{\"items\":[\"Language switching does not duplicate content logic\",\"SEO signals (metadata, structure) are generated per locale\",\"New languages can be enabled without touching existing tenants\"],\"style\":\"unordered\"},\"type\":\"list\"},{\"data\":{\"text\":\"This avoids the common anti-pattern of “translated UI over single-language content”.\"},\"type\":\"paragraph\"},{\"data\":{},\"type\":\"delimiter\"},{\"data\":{\"text\":\"5. Frontend Delivery Model\",\"level\":2},\"type\":\"header\"},{\"data\":{\"text\":\"The frontend is optimized for \u003Cb>performance, predictability, and SEO stability\u003C\u002Fb>.\"},\"type\":\"paragraph\"},{\"data\":{\"text\":\"Key principles\",\"level\":3},\"type\":\"header\"},{\"data\":{\"items\":[\"Pre-rendered HTML for primary content\",\"Minimal runtime JavaScript\",\"No unnecessary SPA complexity\",\"Fully responsive layout\"],\"style\":\"unordered\"},\"type\":\"list\"},{\"data\":{\"text\":\"From a CTO perspective, this ensures consistent load times globally, low operational risk, clean separation between content delivery and business logic, and excellent search engine indexability across markets.\"},\"type\":\"paragraph\"},{\"data\":{},\"type\":\"delimiter\"},{\"data\":{\"text\":\"6. Why Multi-Tenant Architecture Matters (CTO Perspective)\",\"level\":2},\"type\":\"header\"},{\"data\":{\"text\":\"For a platform intended to operate internationally, \u003Cb>multi-tenant design is not optional\u003C\u002Fb>.\"},\"type\":\"paragraph\"},{\"data\":{\"text\":\"Without it, growth introduces cross-market coupling, legal risk, operational fragility, and scaling bottlenecks.\"},\"type\":\"paragraph\"},{\"data\":{\"text\":\"With the chosen architecture, Loving Rocks gains:\"},\"type\":\"paragraph\"},{\"data\":{\"items\":[\"\u003Cb>horizontal scalability\u003C\u002Fb>\",\"\u003Cb>regional independence\u003C\u002Fb>\",\"\u003Cb>clear ownership boundaries\u003C\u002Fb>\",\"\u003Cb>enterprise-grade maintainability\u003C\u002Fb>\"],\"style\":\"unordered\"},\"type\":\"list\"},{\"data\":{\"text\":\"This makes the platform suitable not only for content delivery, but also for future integrations, partnerships, and white-label use cases.\"},\"type\":\"paragraph\"},{\"data\":{},\"type\":\"delimiter\"},{\"data\":{\"text\":\"7. High-Level Architecture Overview\",\"level\":2},\"type\":\"header\"},{\"data\":{\"text\":\"Logical architecture layers:\"},\"type\":\"paragraph\"},{\"data\":{\"code\":\"┌──────────────────────────────┐\\n│          Frontend            │\\n│  (Pre-rendered, responsive)  │\\n└──────────────┬───────────────┘\\n               │\\n┌──────────────▼───────────────┐\\n│     Application Layer        │\\n│  - Tenant resolution         │\\n│  - Localization logic        │\\n│  - Content orchestration     │\\n└──────────────┬───────────────┘\\n               │\\n┌──────────────▼───────────────┐\\n│      Tenant Databases        │\\n│  - One DB per tenant         │\\n│  - Isolated schemas          │\\n│  - Independent lifecycle     │\\n└──────────────────────────────┘\"},\"type\":\"code\"},{\"data\":{\"text\":\"\u003Cb>Key design rule:\u003C\u002Fb> A tenant is never aware of another tenant’s existence.\"},\"type\":\"paragraph\"},{\"data\":{},\"type\":\"delimiter\"},{\"data\":{\"text\":\"8. Operational Stability & Risk Management\",\"level\":2},\"type\":\"header\"},{\"data\":{\"text\":\"From an operations standpoint, the platform supports:\"},\"type\":\"paragraph\"},{\"data\":{\"items\":[\"tenant-level rollback\",\"tenant-level maintenance windows\",\"tenant-level backups\",\"controlled rollout of changes\"],\"style\":\"unordered\"},\"type\":\"list\"},{\"data\":{\"text\":\"Failures are \u003Cb>contained, observable, and reversible\u003C\u002Fb>, which is a fundamental enterprise requirement.\"},\"type\":\"paragraph\"},{\"data\":{},\"type\":\"delimiter\"},{\"data\":{\"text\":\"Conclusion\",\"level\":2},\"type\":\"header\"},{\"data\":{\"text\":\"\u003Cb>Loving Rocks\u003C\u002Fb> is not a traditional wedding website. It is a \u003Cb>multi-tenant, international content platform\u003C\u002Fb> built with enterprise architectural principles: isolated databases, language-first design, scalable backend, performance-focused frontend, and long-term operational safety.\"},\"type\":\"paragraph\"},{\"data\":{\"text\":\"This architecture provides a solid foundation for sustained growth, regional expansion, and future platform evolution without technical debt accumulation.\"},\"type\":\"paragraph\"}],\"version\":\"2.28.2\"}",{"time":228,"blocks":511,"version":444},[512,514,517,520,522,525,528,531,538,541,543,546,549,552,558,561,568,571,573,576,579,582,588,591,597,600,602,605,608,611,618,621,627,630,632,635,638,641,648,651,653,656,659,662,665,672,675,677,680,683,685,688,690,693,696,703,706,708,711,714],{"data":513,"type":42},{"text":232,"level":40},{"data":515,"type":42},{"text":516,"level":236},"Enterprise-Grade Multi-Tenant Architecture for an International Wedding Platform",{"data":518,"type":240},{"text":519},"\u003Cb>Loving Rocks\u003C\u002Fb> is an international wedding platform engineered as a \u003Cb>multi-tenant, multi-language, data-isolated system\u003C\u002Fb>, designed for long-term scalability, operational stability, and market expansion. From an IT leadership perspective, the platform follows principles commonly found in enterprise SaaS architectures rather than traditional content websites.",{"data":521,"type":243},{},{"data":523,"type":42},{"text":524,"level":236},"1. Architectural Philosophy",{"data":526,"type":240},{"text":527},"The core architectural goal of Loving Rocks is \u003Cb>controlled scalability without cross-tenant risk\u003C\u002Fb>.",{"data":529,"type":240},{"text":530},"Instead of building a monolithic, single-database content system, the platform adopts:",{"data":532,"type":261},{"items":533,"style":260},[534,535,536,537],"strict \u003Cb>tenant isolation\u003C\u002Fb>","\u003Cb>independent data ownership\u003C\u002Fb>","centralized application logic","predictable operational behavior under growth",{"data":539,"type":240},{"text":540},"This allows the platform to scale across multiple domains, countries, languages, and legal contexts without structural refactoring.",{"data":542,"type":243},{},{"data":544,"type":42},{"text":545,"level":236},"2. Multi-Tenant Model (Tenant Isolation by Design)",{"data":547,"type":240},{"text":548},"Loving Rocks is implemented as a \u003Cb>true multi-tenant system\u003C\u002Fb>, not a shared-table workaround.",{"data":550,"type":42},{"text":551,"level":276},"Key characteristics",{"data":553,"type":261},{"items":554,"style":260},[555,556,557],"\u003Cb>One database per tenant\u003C\u002Fb>","No shared tenant data at the persistence layer","Tenant context resolved at request level (domain \u002F locale \u002F configuration)",{"data":559,"type":42},{"text":560,"level":276},"Benefits",{"data":562,"type":261},{"items":563,"style":260},[564,565,566,567],"\u003Cb>Data isolation by default\u003C\u002Fb>: a failure, corruption, or misconfiguration in one tenant cannot affect others.","\u003Cb>Security & compliance\u003C\u002Fb>: tenant-specific GDPR, legal texts, and retention policies are handled independently.","\u003Cb>Operational flexibility\u003C\u002Fb>: backup, restore, migration, or decommissioning can be performed per tenant without impacting others.","\u003Cb>Future monetization readiness\u003C\u002Fb>: supports premium tenants, white-label deployments, and region-specific feature sets without branching the codebase.",{"data":569,"type":240},{"text":570},"This is the same isolation strategy used in mature enterprise SaaS platforms.",{"data":572,"type":243},{},{"data":574,"type":42},{"text":575,"level":236},"3. Data Layer Strategy",{"data":577,"type":240},{"text":578},"Each tenant operates on its \u003Cb>own dedicated database\u003C\u002Fb>.",{"data":580,"type":42},{"text":581,"level":276},"Consequences (intentional)",{"data":583,"type":261},{"items":584,"style":260},[585,586,587],"No cross-tenant joins","No global content tables","No accidental data leakage vectors",{"data":589,"type":42},{"text":590,"level":276},"Structure overview",{"data":592,"type":261},{"items":593,"style":260},[594,595,596],"\u003Cb>Content schema\u003C\u002Fb>: articles, guides, categories, tags, metadata","\u003Cb>Localization schema\u003C\u002Fb>: language-normalized content, translations, locale-specific metadata","\u003Cb>Tenant configuration schema\u003C\u002Fb>: domain mapping, enabled languages, branding, legal pages",{"data":598,"type":240},{"text":599},"This approach trades a small increase in infrastructure complexity for \u003Cb>long-term safety and predictability\u003C\u002Fb>.",{"data":601,"type":243},{},{"data":603,"type":42},{"text":604,"level":236},"4. Internationalization at Platform Level",{"data":606,"type":240},{"text":607},"Internationalization is not treated as a frontend feature, but as a \u003Cb>core platform capability\u003C\u002Fb>.",{"data":609,"type":42},{"text":610,"level":276},"Current capabilities",{"data":612,"type":261},{"items":613,"style":260},[614,615,616,617],"\u003Cb>8+ supported languages\u003C\u002Fb>","Language-aware content storage","Localized URLs and metadata","Market-specific legal and privacy pages",{"data":619,"type":42},{"text":620,"level":276},"Technical implications",{"data":622,"type":261},{"items":623,"style":260},[624,625,626],"Language switching does not duplicate content logic","SEO signals (metadata, structure) are generated per locale","New languages can be enabled without touching existing tenants",{"data":628,"type":240},{"text":629},"This avoids the common anti-pattern of “translated UI over single-language content”.",{"data":631,"type":243},{},{"data":633,"type":42},{"text":634,"level":236},"5. Frontend Delivery Model",{"data":636,"type":240},{"text":637},"The frontend is optimized for \u003Cb>performance, predictability, and SEO stability\u003C\u002Fb>.",{"data":639,"type":42},{"text":640,"level":276},"Key principles",{"data":642,"type":261},{"items":643,"style":260},[644,645,646,647],"Pre-rendered HTML for primary content","Minimal runtime JavaScript","No unnecessary SPA complexity","Fully responsive layout",{"data":649,"type":240},{"text":650},"From a CTO perspective, this ensures consistent load times globally, low operational risk, clean separation between content delivery and business logic, and excellent search engine indexability across markets.",{"data":652,"type":243},{},{"data":654,"type":42},{"text":655,"level":236},"6. Why Multi-Tenant Architecture Matters (CTO Perspective)",{"data":657,"type":240},{"text":658},"For a platform intended to operate internationally, \u003Cb>multi-tenant design is not optional\u003C\u002Fb>.",{"data":660,"type":240},{"text":661},"Without it, growth introduces cross-market coupling, legal risk, operational fragility, and scaling bottlenecks.",{"data":663,"type":240},{"text":664},"With the chosen architecture, Loving Rocks gains:",{"data":666,"type":261},{"items":667,"style":260},[668,669,670,671],"\u003Cb>horizontal scalability\u003C\u002Fb>","\u003Cb>regional independence\u003C\u002Fb>","\u003Cb>clear ownership boundaries\u003C\u002Fb>","\u003Cb>enterprise-grade maintainability\u003C\u002Fb>",{"data":673,"type":240},{"text":674},"This makes the platform suitable not only for content delivery, but also for future integrations, partnerships, and white-label use cases.",{"data":676,"type":243},{},{"data":678,"type":42},{"text":679,"level":236},"7. High-Level Architecture Overview",{"data":681,"type":240},{"text":682},"Logical architecture layers:",{"data":684,"type":411},{"code":410},{"data":686,"type":240},{"text":687},"\u003Cb>Key design rule:\u003C\u002Fb> A tenant is never aware of another tenant’s existence.",{"data":689,"type":243},{},{"data":691,"type":42},{"text":692,"level":236},"8. Operational Stability & Risk Management",{"data":694,"type":240},{"text":695},"From an operations standpoint, the platform supports:",{"data":697,"type":261},{"items":698,"style":260},[699,700,701,702],"tenant-level rollback","tenant-level maintenance windows","tenant-level backups","controlled rollout of changes",{"data":704,"type":240},{"text":705},"Failures are \u003Cb>contained, observable, and reversible\u003C\u002Fb>, which is a fundamental enterprise requirement.",{"data":707,"type":243},{},{"data":709,"type":42},{"text":710,"level":236},"Conclusion",{"data":712,"type":240},{"text":713},"\u003Cb>Loving Rocks\u003C\u002Fb> is not a traditional wedding website. It is a \u003Cb>multi-tenant, international content platform\u003C\u002Fb> built with enterprise architectural principles: isolated databases, language-first design, scalable backend, performance-focused frontend, and long-term operational safety.",{"data":715,"type":240},{"text":716},"This architecture provides a solid foundation for sustained growth, regional expansion, and future platform evolution without technical debt accumulation.","Loving Rocks is an enterprise-grade wedding platform designed with a true multi-tenant architecture, isolated databases per tenant, and built-in internationalization for global scalability, security, and long-term operational stability.",{"lang":7,"title":224,"content":226,"contentJson":719,"excerpt":445},{"time":228,"blocks":720,"version":444},[721,723,725,727,729,731,733,735,738,740,742,744,746,748,751,753,756,758,760,762,764,766,769,771,774,776,778,780,782,784,787,789,792,794,796,798,800,802,805,807,809,811,813,815,817,820,822,824,826,828,830,832,834,836,838,841,843,845,847,849],{"data":722,"type":42},{"text":232,"level":40},{"data":724,"type":42},{"text":235,"level":236},{"data":726,"type":240},{"text":239},{"data":728,"type":243},{},{"data":730,"type":42},{"text":246,"level":236},{"data":732,"type":240},{"text":249},{"data":734,"type":240},{"text":252},{"data":736,"type":261},{"items":737,"style":260},[256,257,258,259],{"data":739,"type":240},{"text":264},{"data":741,"type":243},{},{"data":743,"type":42},{"text":269,"level":236},{"data":745,"type":240},{"text":272},{"data":747,"type":42},{"text":275,"level":276},{"data":749,"type":261},{"items":750,"style":260},[280,281,282],{"data":752,"type":42},{"text":285,"level":276},{"data":754,"type":261},{"items":755,"style":260},[289,290,291,292],{"data":757,"type":240},{"text":295},{"data":759,"type":243},{},{"data":761,"type":42},{"text":300,"level":236},{"data":763,"type":240},{"text":303},{"data":765,"type":42},{"text":306,"level":276},{"data":767,"type":261},{"items":768,"style":260},[310,311,312],{"data":770,"type":42},{"text":315,"level":276},{"data":772,"type":261},{"items":773,"style":260},[319,320,321],{"data":775,"type":240},{"text":324},{"data":777,"type":243},{},{"data":779,"type":42},{"text":329,"level":236},{"data":781,"type":240},{"text":332},{"data":783,"type":42},{"text":335,"level":276},{"data":785,"type":261},{"items":786,"style":260},[339,340,341,342],{"data":788,"type":42},{"text":345,"level":276},{"data":790,"type":261},{"items":791,"style":260},[349,350,351],{"data":793,"type":240},{"text":354},{"data":795,"type":243},{},{"data":797,"type":42},{"text":359,"level":236},{"data":799,"type":240},{"text":362},{"data":801,"type":42},{"text":365,"level":276},{"data":803,"type":261},{"items":804,"style":260},[369,370,371,372],{"data":806,"type":240},{"text":375},{"data":808,"type":243},{},{"data":810,"type":42},{"text":380,"level":236},{"data":812,"type":240},{"text":383},{"data":814,"type":240},{"text":386},{"data":816,"type":240},{"text":389},{"data":818,"type":261},{"items":819,"style":260},[393,394,395,396],{"data":821,"type":240},{"text":399},{"data":823,"type":243},{},{"data":825,"type":42},{"text":404,"level":236},{"data":827,"type":240},{"text":407},{"data":829,"type":411},{"code":410},{"data":831,"type":240},{"text":414},{"data":833,"type":243},{},{"data":835,"type":42},{"text":419,"level":236},{"data":837,"type":240},{"text":422},{"data":839,"type":261},{"items":840,"style":260},[426,427,428,429],{"data":842,"type":240},{"text":432},{"data":844,"type":243},{},{"data":846,"type":42},{"text":437,"level":236},{"data":848,"type":240},{"text":440},{"data":850,"type":240},{"text":443},"Post erfolgreich abgerufen",{"items":853,"source":938,"manualIds":939,"manualMatchedIds":940},[854,861,868,875,882,889,896,903,910,917,924,931],{"id":855,"slug":856,"title":857,"excerpt":858,"featuredImage":859,"publishedAt":860},"484","what-is-an-ai-platform-architect-models-data-runtime-security-and-operations","Šta je arhitekta AI platforme? Modeli, podaci, izvršno okruženje, bezbednost i operacije","Arhitekta AI platforme projektuje višekratno upotrebljive AI temelje kroz modele, provajdere, pretragu, agente, identitet, bezbednost, evaluaciju, opservabilnost i operacije.","\u002Fuploads\u002F2026\u002F10\u002Fwhat-is-an-ai-platform-architect-models-data-runtime-security-and-operations-1791477229171-ou3zcc.webp","2026-10-08T12:32:00.000Z",{"id":862,"slug":863,"title":864,"excerpt":865,"featuredImage":866,"publishedAt":867},"481","generative-ai-explained-models-retrieval-tools-and-applications-are-not-the-same-thing","Generativna veštačka inteligencija objašnjena: modeli, pretraga, alati i aplikacije nisu ista stvar","Generativna AI je više od modela. Saznajte kako se modeli, pretraga, alati, kontekst, okruženja i aplikacije uklapaju u produkcione AI sisteme.","\u002Fuploads\u002F2026\u002F10\u002Fgenerative-ai-explained-models-retrieval-tools-and-applications-are-not-the-same-thing-1791475411822-pp0dvz.webp","2026-10-08T12:00:00.000Z",{"id":869,"slug":870,"title":871,"excerpt":872,"featuredImage":873,"publishedAt":874},"361","model-view-controller-mvc","Model-View-Controller (MVC): Strukturna okosnica modernih veb aplikacija","Model-View-Controller, obično skraćeno kao MVC, ostaje jedan od najtrajnijih arhitektonskih obrazaca u razvoju softvera. On timovima pruža praktičan način da razdvoje poslovnu logiku, prezentaciju i interakciju korisnika kako bi aplikacije ostale lakše za izgradnju, proširenje, testiranje i održavanje. Ovaj članak objašnjava šta je MVC, zašto je i dalje važan, gde se uklapa u današnje veb stekove i kako se povezuje sa širom arhitekturom platforme, kvalitetom isporuke, strategijom migracije i operativnom zrelošću.","\u002Fuploads\u002F2026\u002F03\u002Fmodel-view-controller-mvc-1774872805793-0bjubu.webp","2023-04-12T12:57:00.000Z",{"id":876,"slug":877,"title":878,"excerpt":879,"featuredImage":880,"publishedAt":881},"383","canonical-architecture-url-design-resolver-logic-api-scalability-specification","Kanonska Arhitektura, Dizajn URL-a, Logika Rezolvera, Specifikacija API-ja i Skalabilnosti","Geografski zasnovana arhitektura za otkrivanje za višekorisničke portale. Definiše kanonske URL adrese, logiku razrešavanja, strategiju keširanja i geo model za čitanje bez sprezanja sa CMS-om ili refaktorisanja baze podataka. Dizajnirano za SEO stabilnost, skalabilnost i buduća proširenja poput rezervacija i mapa.","\u002Fuploads\u002F2026\u002F01\u002Fcanonical-architecture-url-design-resolver-logic-api-scalability-specification-1769890763607-7rghbp.webp","2026-01-31T06:12:00.000Z",{"id":883,"slug":884,"title":885,"excerpt":886,"featuredImage":887,"publishedAt":888},"382","a-practical-monorepo-architecture-next-js-platform-admin-fastify-api-prisma-and-nginx","Praktična monorepo arhitektura sa Next.js, Fastify, Prisma i NGINX","Istražite praktičnu monorepo arhitekturu koristeći Next.js, Fastify, Prisma i NGINX, ističući integraciju i tok rada iz stvarnog sveta.","\u002Fuploads\u002F2026\u002F01\u002Fa-practical-monorepo-architecture-next-js-platform-admin-fastify-api-prisma-and-nginx-1769885526116-q1100n.webp","2026-01-31T08:18:00.000Z",{"id":890,"slug":891,"title":892,"excerpt":893,"featuredImage":894,"publishedAt":895},"451","test-dev-enterprise","Sveobuhvatni vodič za Test DEv Enterprise Stajic.de: Arhitektura i najbolje prakse","Istražite arhitektonske principe, prednosti i tehničke detalje upravljanja okruženjem za razvoj i testiranje nivoa preduzeća pomoću Test DEv Enterprise Stajic.de.","\u002Fuploads\u002F2026\u002F05\u002Ftest-dev-enterprise-1779534260081-r4dvxn.webp","2026-05-22T23:01:00.000Z",{"id":897,"slug":898,"title":899,"excerpt":900,"featuredImage":901,"publishedAt":902},"480","when-should-an-ai-stop-trusting-its-own-knowledge-the-retrieval-trigger","Kada bi AI trebalo da prestane da veruje sopstvenom znanju? — Okidač za pretragu","AI model ne zahteva pretragu za svako pitanje. Važan problem je znati kada njegovo interno znanje više nije dovoljno. Okidač za pretragu je praktična granica odlučivanja koja određuje kada AI sistem treba da prestane da se oslanja isključivo na znanje modela i pribavi spoljne dokaze pre odgovaranja.","\u002Fuploads\u002F2026\u002F09\u002Fwhen-should-an-ai-stop-trusting-its-own-knowledge-the-retrieval-trigger-1790574991244-f4rpyg.webp","2026-09-28T01:49:00.000Z",{"id":904,"slug":905,"title":906,"excerpt":907,"featuredImage":908,"publishedAt":909},"459","ollama-is-not-the-product-building-production-ready-open-llm-applications","Ollama nije proizvod: Izgradnja aplikacija spremnih za produkciju sa otvorenim LLM-ovima","Pokretanje lokalnog modela pomoću Ollama-e je jednostavno. Izgradnja Open-LLM aplikacije spremne za produkciju je teža: zahteva RAG, kontrolu pristupa, apstrakciju provajdera, evaluaciju, logovanje, disciplinu puštanja u rad i kontrolisani aplikativni sloj oko modela.","\u002Fuploads\u002F2026\u002F06\u002Follama-is-not-the-product-building-production-ready-open-llm-applications-1782679361640-h0usqf.webp","2026-06-28T16:39:00.000Z",{"id":911,"slug":912,"title":913,"excerpt":914,"featuredImage":915,"publishedAt":916},"445","qwen-3-6-in-production-release-runbook-ai-rollback-and-llmops-versioning","Qwen 3.6 u produkciji: Runbook za izdavanje, AI rollback i LLMOps verziranje","Qwen 3.6 nije samo još jedna nadogradnja modela. To je istovremeno događaj objavljivanja, scenario povratka na prethodnu verziju i problem verziranja. Ovaj članak objašnjava kako Qwen 3.6 treba tretirati u produkciji kroz LLMOps disciplinu, sledljivost promptova i modela, kontrolisano uvođenje i spremnost za povratak na prethodnu verziju zasnovanu na dokazima.","\u002Fuploads\u002F2026\u002F02\u002Fnew-qwen-3-5-plus-1771515512741-dcbi9p.webp","2026-05-04T02:49:00.000Z",{"id":918,"slug":919,"title":920,"excerpt":921,"featuredImage":922,"publishedAt":923},"497","how-far-is-an-ai-claim-from-the-evidence-evidence-distance","Koliko je tvrdnja o AI udaljena od dokaza? — Udaljenost dokaza","Nisu svi podržani odgovori podjednako blizu svojim dokazima. Udaljenost dokaza je praktičan način da se opiše koliko transformacija, sažetaka, pretpostavki i koraka zaključivanja razdvaja tvrdnju AI od direktno proverljivih dokaza.","\u002Fuploads\u002F2026\u002F10\u002Fhow-far-is-an-ai-claim-from-the-evidence-evidence-distance-1792095863209-3c1mog.webp","2026-10-15T00:23:00.000Z",{"id":925,"slug":926,"title":927,"excerpt":928,"featuredImage":929,"publishedAt":930},"485","enterprise-ai-architecture-what-changes-when-ai-enters-a-company","Enterprise AI arhitektura: Šta se menja kada AI uđe u kompaniju","Enterprise AI arhitektura objašnjava kako AI menja korporativne sisteme kroz autoritet podataka, identitet, dozvole, provajdere, rizik, upravljanje, evaluaciju, usklađenost i operacije.","\u002Fuploads\u002F2026\u002F10\u002Fenterprise-ai-architecture-what-changes-when-ai-enters-a-company-1791478161363-czrwaq.webp","2026-10-08T10:48:00.000Z",{"id":932,"slug":933,"title":934,"excerpt":935,"featuredImage":936,"publishedAt":937},"498","can-evidence-survive-the-ai-pipeline-the-evidence-preservation-chain","Može li dokaz preživeti AI proces? — Lanac očuvanja dokaza","Dokazi mogu biti tačni na izvoru i ipak postati nepouzdani nakon parsiranja, normalizacije, deljenja na delove, pronalaženja i sastavljanja konteksta. Lanac očuvanja dokaza prati da li identitet, poreklo, obim i značenje preživljavaju ceo AI proces.","\u002Fuploads\u002F2026\u002F10\u002Fcan-evidence-survive-the-ai-pipeline-the-evidence-preservation-chain-1792096396174-urdg9z.webp","2026-10-15T16:31:00.000Z","fallback",[],[]]