<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Architecture on Fernando Ruiz</title><link>https://www.fernandoux.com/tags/architecture/</link><description>Recent content in Architecture on Fernando Ruiz</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://www.fernandoux.com/tags/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Build vs. Buy in AI: Your Own Model or an API?</title><link>https://www.fernandoux.com/en/wiki/ai/build-vs-buy-models/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/ai/build-vs-buy-models/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 &lt;strong&gt;Build vs. buy in AI&lt;/strong&gt; is the decision to use a model through a third-party API (buy) or to host and operate an open model on your own or rented infrastructure (build). The right answer depends on token volume, the data the product handles, and the team&amp;rsquo;s technical capacity, not on which option sounds more serious.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-do-build-and-buy-mean"&gt;What do build and buy mean?&lt;/h2&gt;
&lt;p&gt;With &amp;ldquo;buy&amp;rdquo; you pay per use to a provider that maintains the model, the infrastructure and the upgrades. Your cost grows with every call. With &amp;ldquo;build&amp;rdquo; you host an open model, serve it with an inference engine, and pay for GPUs, people and operations. There is also a middle option: running an open model through a hosted inference provider that charges per token and runs the infrastructure for you. Many comparisons skip it. To understand how closed and open models differ, read [[open-vs-closed-models|open vs. closed models]].&lt;/p&gt;</description></item><item><title>RAG (Retrieval-Augmented Generation): Answers Grounded in Your Documents</title><link>https://www.fernandoux.com/en/wiki/ai/rag/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/ai/rag/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 &lt;strong&gt;RAG&lt;/strong&gt; (Retrieval-Augmented Generation) is a technique in which the system searches a collection of documents for relevant fragments and includes them in the request to the model, so the answer is grounded in those texts rather than only in what the model learned during training.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-is-rag"&gt;What is RAG?&lt;/h2&gt;
&lt;p&gt;RAG combines two parts. A &lt;strong&gt;retriever&lt;/strong&gt; searches your document base for the fragments most related to the question, usually by comparing [[embeddings|embeddings]]. A &lt;strong&gt;generator&lt;/strong&gt;, the [[what-is-an-llm|LLM]], writes the answer using the question and those fragments as context.&lt;/p&gt;</description></item></channel></rss>