What guides are in the catalog?
The Enterprise RAG Architecture Guide walks through RAG, the approach that grounds large language model answers in an organization's own knowledge sources, across core components, permission and security design, and quality measurement; it was written for architects and CTOs evaluating or building an enterprise RAG system.
The Hybrid Cloud Workload Placement Guide structures the decision of which environment each application runs in — on-premises infrastructure, private cloud, colocation, or public cloud — weighing cost, performance, data classification, latency, licensing, and recovery objectives, and presents typical placement patterns.
- Enterprise RAG Architecture Guide: components, permission and security design, quality measurement
- Hybrid Cloud Workload Placement Guide: decision framework, placement criteria, typical patterns
How are the guides prepared?
Every guide is written to the same skeleton: a definition of the concept, the architectural or decision components, implementation steps, measurement topics, and frequently asked questions. The shared structure lets guides on different subjects read with the same flow.
Content is reviewed under a claim discipline: unverifiable figures, superlatives, and sales language do not enter the guides, and technical terms are matched one to one across the Turkish and English editions. The research methodology is a separate framework and is described on the Research and Guides page.
- Definition blocks are written to stand alone when quoted
- FAQ answers state the answer in the first sentence
- Measurement topics are limited to observable indicators
How should a guide be used?
A guide can be read end to end or used as a reference; section headings are phrased as questions, so the relevant part can be found directly.
During an evaluation or deployment, the implementation steps are followed in order, and the measurement topics serve as a separate checklist for judging the outcome.
- For a first encounter with the concept, the definition block and the opening section are a sufficient start
- For teams at the decision stage, the criteria and decision framework sections matter most
- Teams running a deployment use the implementation steps and measurement topics together
How are guides kept current?
Technology guides are not static documents; when a development affects a guide's scope, the guide is reviewed and the change is noted on its page.
Updates reassess the whole guide rather than appending to the existing text; recommendations that no longer hold are removed in the new revision.
- Content-changing updates are noted on the guide's page
- The scope of a change is briefly described in a revision note
- The catalog grows as new guides are published
