OmniRoute/docs/i18n/ha/docs/reference/RELAY_BACKEND_STRATEGY.md

Relay Backend Strategy (Hausa)

🌐 Languages: 🇺🇸 English · 🇪🇹 am · 🇸🇦 ar · 🇦🇿 az · 🇧🇬 bg · 🇧🇩 bn · 🇨🇿 cs · 🇩🇰 da · 🇩🇪 de · 🇬🇷 el · 🇪🇸 es · 🇪🇪 et · 🇮🇷 fa · 🇫🇮 fi · 🇫🇷 fr · 🇮🇪 ga · 🇮🇳 gu · 🇮🇱 he · 🇮🇳 hi · 🇭🇷 hr · 🇭🇺 hu · 🇦🇲 hy · 🇮🇩 id · 🇳🇬 ig · 🇮🇹 it · 🇯🇵 ja · 🇬🇪 ka · 🇰🇭 km · 🇮🇳 kn · 🇰🇷 ko · 🇱🇹 lt · 🇱🇻 lv · 🇮🇳 ml · 🇮🇳 mr · 🇲🇾 ms · 🇲🇹 mt · 🇲🇲 my · 🇳🇵 ne · 🇳🇱 nl · 🇳🇴 no · 🇮🇳 or · 🇮🇳 pa · 🇵🇭 phi · 🇵🇱 pl · 🇵🇹 pt · 🇧🇷 pt-BR · 🇷🇴 ro · 🇷🇺 ru · 🇱🇰 si · 🇸🇰 sk · 🇸🇮 sl · 🇷🇸 sr · 🇸🇪 sv · 🇰🇪 sw · 🇮🇳 ta · 🇮🇳 te · 🇹🇭 th · 🇹🇷 tr · 🇺🇦 uk-UA · 🇵🇰 ur · 🇺🇿 uz · 🇻🇳 vi · 🇳🇬 yo · 🇨🇳 zh-CN · 🇹🇼 zh-TW

---

Taƙaitaccen bayani

Yanzu OmniRoute yana goyon bayan hanyoyin relay guda uku don /api/v1/relay/chat/completions:

• ts: Yi amfani da relay na TypeScript kai tsaye a cikin tsari guda.
• bifrost: Tilasta amfani da gateway na Bifrost.
• auto: Fifita Bifrost idan yana samuwa, sannan komawa TypeScript idan an samu gazawa.

Lokacin da kake aiki da yawan buƙatu sosai (adadi mai yawa na tokens/rana, tare da zirga-zirga kusan ba tare da yankewa ba), mafi kyawun dabara ita ce a sanya hanyar fallback a sarari kuma cikin sauri, domin hanyar da ake yawan amfani da ita kada ta taɓa makalewa saboda sidecar da ya daina aiki.

Halayen hanyoyin aiki

• ts
  • Mafi ƙarancin rikitarwar gudanarwa.
  • Duk routing da validation suna gudana a cikin Node.
  • Babu dogaro da sidecar don kasancewar sabis.
• bifrost
  • Tilasta duk buƙatu su bi ta gateway na sidecar.
  • Babu fallback ta atomatik.
  • Yana da amfani ne kawai idan an tabbatar da lafiyar sidecar da latency ɗinsa.
• auto
  • Ana amfani da sidecar idan ana iya isa gare shi kuma an kunna shi.
  • Ƙoƙarin da ya gaza yana haifar da headers na fallback sannan ya mayar da zirga-zirga zuwa TS, domin lokacin samun nasarar buƙata ya kasance cikin iyaka.
  • Wannan hanya ita ce mafi aminci ga production idan uptime ya fi tsauraran routing ta sidecar kaɗai muhimmanci.

9router da CLIPROXYAPI a yau

9router da CLIPROXYAPI dukansu haɗaɗɗun tsare-tsare ne waɗanda a tarihi suka samar da hanyoyin dacewa ga upstream providers.

• 9router hanya ce da aka saka a ciki don sarrafa upstream da halayen dacewa.
• CLIPROXYAPI gada ce ta proxy API don zirga-zirga irin ta CLI / SDK.
• Ana daidaita Bifrost a matsayin hanyar waje idan kana buƙatar wata keɓantacciyar tsallakewa mai kama da sidecar da kuma local dispatch mai ƙarancin latency.

Idan a halin yanzu kana kwatanta 9router/CLIPROXYAPI:

• Ka bar request signing, binciken allowlist, da matakan manufofin DB a cikin hanyar API kafin miƙa aikin.
• Idan workflow yana buƙatar tsauraran halayen sidecar da ƙarancin sauyin lokaci ga kowace buƙata, yi amfani da OMNIROUTE_RELAY_BACKEND=bifrost.
• Idan kana buƙatar juriya ta sidecar tare da raguwa cikin sauƙi yayin aukuwar matsala, yi amfani da OMNIROUTE_RELAY_BACKEND=auto.

Yarjejeniyar iyakar backend

Tsayayyar iyakar samfur ita ce relay API na OmniRoute, ba aiwatarwar dashboard ba. Dashboard na Next.js na iya girkawa, daidaitawa, da sa ido kan local services, amma routing na buƙatu ya kamata ya shiga ta relay API sannan a miƙa shi a bayan wannan iyaka.

Zaɓuɓɓukan backend na dogon lokaci:

• Ci gaba da riƙe relay na TypeScript a matsayin hanyar manufofi da fallback da ke gudana cikin tsari guda. Auth, allowlists, daidaita buƙatu, lissafi, da binciken aminci su ci gaba da kasancewa a nan kafin kowane miƙa aiki zuwa backend.
• Yi amfani da Bifrost a matsayin sidecar na Tier-1 da aka fi so don babban throughput idan deployment yana buƙatar ƙarancin sauyin routing, juyawar provider daga wuri guda, ko scale-out a tsakanin replicas na OmniRoute da yawa.
• Ci gaba da riƙe 9router da CLIPROXYAPI a matsayin ayyukan dacewa da aka saka a ciki. Suna gudana a matsayin local processes da ake sa ido a kansu, kuma suna da amfani idan halayen provider/CLI nasu su ne adapter da ake so, amma bai kamata su zama tsohon routing engine na Tier-1 ba.
• Kada a sa dashboard ya tura arbitrary service URLs zuwa hanyar da ake yawan amfani da ita. URLs da UI ya bayar bayanan configuration ne; lambar routing ya kamata ta nemo backends da aka yi wa rajista kuma aka tabbatar da lafiyarsu daga saitunan ɓangaren server da matsayin supervisor.
• A yau, fi son loopback HTTP don supervised services saboda managed processes sun riga sun samar da APIs masu dacewa da HTTP, route guard zai iya bincikar iyakar, sannan ana iya ganin halayen gazawa/fallback a cikin request logs. Ƙara SDK ko socket transport a nan gaba zai dace ne kawai idan yana rage p99 routing latency a zahiri ba tare da raunana keɓancewa ko ma’anar fallback ba.

Saboda haka, ga deployment mai babban throughput sosai, zaɓin tsoho shi ne auto tare da kunna Bifrost: yi amfani da Go sidecar a hanyar da ake yawan amfani da ita yayin da ake kiyaye fallback na TypeScript don tabbatar da adadin nasara. Yi amfani da bifrost kawai idan tsauraran halayen sidecar kaɗai sun fi raguwa cikin sauƙi muhimmanci.

Jagora don babban throughput

Don RPM/RPS mai yawa mai ɗorewa da tsauraran SLO na nasara:

1. Yi amfani da auto tare da cooldown mai amfani da telemetry na gazawa.
2. Bar upstream validation da binciken API-key a iyakar hanyar TypeScript.
3. Kunna takamaiman headers/counters domin tsarin faɗakarwarka ya ga yawan fallback da dalilansa.
4. Daidaita sidecar timeouts su gaza da sauri, maimakon jira har abada.
5. Kula da lafiyar service auto-restart da telemetry loop domin fallback ya kasance abin da ba kasafai yake faruwa ba.

Saitin asali da ake ba da shawara

• OMNIROUTE_RELAY_BACKEND=auto
• BIFROST_ENABLED=1
• Ci gaba da kunna binciken API keys, allowlist, sanitizer, da rate-limit a cikin route handlers (kullum suna gudana kafin downstream forwarding).
• Fitar da fallback metrics daga reverse proxy da request logs naka domin a iya ganin katsewar sidecar cikin minti ɗaya.

Yarjejeniyar provider plugin

Ya kamata sidecars su shigo da provider metadata ta cikin provider plugin manifest mai aminci ga JSON maimakon dogaro da abubuwan cikin TypeScript executor. Duba Provider Plugin Manifest don yarjejeniyar cancantar sidecar da matakan migration.