<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Lateeftosin on Medium]]></title>
        <description><![CDATA[Stories by Lateeftosin on Medium]]></description>
        <link>https://medium.com/@lateeftosin1999?source=rss-1b567dbf978------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*g1GhZuL56WkLw8KY.jpg</url>
            <title>Stories by Lateeftosin on Medium</title>
            <link>https://medium.com/@lateeftosin1999?source=rss-1b567dbf978------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 10:23:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lateeftosin1999/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Backend Architecture, Explained the Way I Wish Someone Explained It to Me]]></title>
            <link>https://medium.com/@lateeftosin1999/backend-architecture-explained-the-way-i-wish-someone-explained-it-to-me-7f2ce8663f3e?source=rss-1b567dbf978------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f2ce8663f3e</guid>
            <dc:creator><![CDATA[Lateeftosin]]></dc:creator>
            <pubDate>Wed, 10 Jun 2026 17:36:05 GMT</pubDate>
            <atom:updated>2026-06-10T17:36:05.811Z</atom:updated>
            <content:encoded><![CDATA[<p>When I first heard the word “backend,” it sounded like some mysterious thing only senior engineers understood. Then it clicked for me with one simple example: Amazon.</p><p>When you open Amazon, somebody has to remember your profile. Your order history. The items sitting in your cart from three weeks ago. Your search results. None of that lives on your phone or laptop, it lives somewhere else, and that somewhere else is the backend. In the simplest terms, <strong>the backend is the part of an application that manages and saves your data.</strong></p><h3>Two Computers Talking to Each Other</h3><p>Here’s something that sounds obvious but is actually the foundation of everything: any computer connected to the internet can send a message to any other computer connected to the internet.</p><p>Amazon has computers connected to the internet. You have a computer (or phone) connected to the internet. So your computer can communicate with Amazon’s computer.</p><p>In this relationship, your computer is called the <strong>client</strong>, and Amazon’s computer is called the <strong>server</strong>.</p><p>But here’s the catch, your computer can send messages out, but it can’t <em>receive</em> messages from the internet by default. A computer has to be programmed to listen for incoming messages. And that is exactly where backend programming languages come in.</p><p>Every backend language has features that turn an ordinary computer into a server, a machine that can receive messages from the internet and respond to them. The popular ones are JavaScript (Node.js), Python, Ruby, and Java.</p><h3>Frameworks and Packages: Why Nobody Writes Backends From Scratch</h3><p>Using a backend language by itself is honestly difficult. So in practice, developers lean on two tools.</p><p>The first is a <strong>backend framework</strong>. A framework helps you create a server with a lot less code. Each language has its favourite: JavaScript has Express.js, Python has Django, Ruby has Rails, and Java has Spring.</p><p>The second is <strong>packages</strong>. A huge amount of backend code has already been written by other people. code for doing calculations, talking to a database, handling user authentication, and so on. These reusable pieces of code are called packages, and to install and manage them we use a <strong>package manager</strong>. Again, every language has its own: npm for JavaScript, pip for Python, Bundler for Ruby, Maven for Java.</p><p>So instead of building everything yourself, you stand on the shoulders of thousands of developers who came before you.</p><h3>Where Does the Data Actually Live?</h3><p>Our server now exists, but we still need somewhere to <em>save</em> the data. user history, orders, cart items, or in Amazon’s case, every product ever sold on the platform.</p><p>That’s the job of a <strong>database</strong>. A database is simply a piece of software that stores and manages data. It usually runs on a separate computer, so our server needs a way to communicate with it. The most popular databases you’ll hear about are MySQL, PostgreSQL, and MongoDB.</p><h3>The Request,Response Cycle</h3><p>Now let’s connect everything. When the frontend (your browser or app) sends a message to the server, that message is called a <strong>request</strong>. The message the backend sends back is called a <strong>response</strong>. Together, this back-and-forth is known as the <strong>request, response cycle</strong>.</p><p>Here’s what a real request to create an order might look like:</p><pre>POST https://api.amazon.com/orders<br><br>{<br>  &quot;order&quot;: [<br>    {<br>      &quot;id&quot;: &quot;23456&quot;,<br>      &quot;name&quot;: &quot;Adidas&quot;,<br>      &quot;quantity&quot;: &quot;2&quot;<br>    },<br>    {<br>      &quot;id&quot;: &quot;23457&quot;,<br>      &quot;name&quot;: &quot;pencil&quot;,<br>      &quot;quantity&quot;: &quot;5&quot;<br>    }<br>  ],<br>  &quot;paymentMethod&quot;: &quot;creditCard1&quot;,<br>  &quot;deliveryAddress&quot;: &quot;address1&quot;<br>}</pre><p>Notice the structure: there’s a <strong>type</strong> (POST), a <strong>domain</strong> (api.onscript.xyz), and a <strong>URL path</strong> (/orders). The body of the request carries the actual data , in this case, the items being ordered, the payment method, and the delivery address.</p><h3>APIs and REST</h3><p>So how does the frontend know what requests it’s allowed to send? That’s defined by the <strong>API</strong> the Application Programming Interface. An API is the list of all the request types the backend allows: POST, GET, PUT, PATCH, DELETE, and so on.</p><p>APIs follow naming conventions, and the most popular one is <strong>REST</strong> (Representational State Transfer). Any API that follows REST conventions is called a REST API.</p><p>REST isn’t the only option, though. <strong>GraphQL</strong> is another convention that uses a single POST /graphql endpoint for all requests. There’s also <strong>RPC</strong> (Remote Procedure Call), which uses POST with more detailed, action-specific URLs.</p><h3>Putting It All Together</h3><p>So in my own terms, backend architecture is this: a client (your device) sends requests across the internet to a server. The server, built with a backend language, made easier with frameworks and packages receives those requests, talks to a database to save or fetch data, and sends back a response. The rules of that conversation are defined by an API.</p><p>That’s it. Behind every “Add to Cart” button is this exact cycle happening in milliseconds. Once you see it as two computers having a structured conversation, the backend stops being mysterious, it’s just the part of the app you can’t see, doing all the remembering.</p><h3>thank you for reading.</h3><blockquote>i hope i have been able to enlighten you more on backend architecture, explaining in my own term.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f2ce8663f3e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Title: Rust Ownership Explained: The Box Analogy That Finally Made It Click.]]></title>
            <link>https://medium.com/@lateeftosin1999/title-rust-ownership-explained-the-box-analogy-that-finally-made-it-click-edbd3ba44c4a?source=rss-1b567dbf978------2</link>
            <guid isPermaLink="false">https://medium.com/p/edbd3ba44c4a</guid>
            <dc:creator><![CDATA[Lateeftosin]]></dc:creator>
            <pubDate>Fri, 13 Feb 2026 07:14:58 GMT</pubDate>
            <atom:updated>2026-02-13T07:14:58.539Z</atom:updated>
            <content:encoded><![CDATA[<h4>Subtitle: If you can understand moving boxes, you can understand Rust.</h4><p>If you are learning Rust, you have probably hit The Wall. It’s called the Borrow Checker.</p><p>I tried reading the official book. I tried the examples. It didn’t click until I stopped thinking about computer memory and started thinking about a heavy cardboard box.</p><p>Here is the only analogy you need.<br>📦 The Moving Box</p><p>Imagine you are moving to a new apartment. You have one very heavy box.</p><p>1. Ownership (Unique)<br>You are the only one strong enough to carry it. If your friend wants it, you have to physically hand it over and let go. You can’t both hold it. This is Rust’s String.</p><p>2. Borrowing (Immutable)<br>You get tired. You let a friend hold it with you so you can stretch. You are both looking at the box. Neither of you can modify it. This is &amp;T.</p><p>3. Borrowing (Mutable)<br>You need to tape the box shut. You let one friend take it. They are the only one holding it. They add tape. You wait. This is &amp;mut T.</p><p>The Golden Rule:</p><ul><li>✅ Either one person is taping the box (mutable borrow).</li><li>✅ Or multiple people are looking at the box (immutable borrow).</li><li>❌ Never both at the same time.</li></ul><h3>See It In Code</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/707/1*Bttt6kqbgQ-yMTCq9jj3qA.png" /><figcaption>Moving Ownership (Passing the Box)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/703/1*6vtcwYc-PWuXPyHrKcR72A.png" /><figcaption>Borrowing (Peeking Inside)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/703/1*VBx8oA2gUE8GuRZiwdxBBw.png" /><figcaption>Mutable Borrow (Taping the Box)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/706/1*o5GHoe5mKsLA-7l0s0WpDw.png" /><figcaption>The Rule in Action (Preventing Disaster)</figcaption></figure><h3>Why Does This Actually Matter?</h3><p>This isn’t just academic theory. This is why Rust is the most loved language five years in a row.</p><p>1. No Null Pointer Dereferences<br>If you don’t own the data, the compiler guarantees the owner still exists. No more “object reference not set to an instance of an object.”</p><p>2. Fearless Concurrency<br>Data races happen when one thread writes and another reads at the same time. Rust says: “You can’t have both references at the same time.” This is checked at compile time, not at 3:00 AM in production.</p><p>3. Self-Documenting Code<br>When you see &amp;mut self in a function signature, you immediately know: &quot;This function changes the object.&quot; You don&#39;t have to read the body.</p><h3>The “Aha!” Moment</h3><p>The mistake most beginners make is fighting the borrow checker.<br>Don’t fight it. Listen to it.</p><p>Rust isn’t making programming harder. It’s making sure your boxes don’t break.</p><p>thanks for reading!!.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=edbd3ba44c4a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>