<?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 Ediel Queiroz on Medium]]></title>
        <description><![CDATA[Stories by Ediel Queiroz on Medium]]></description>
        <link>https://medium.com/@edielqueiroz?source=rss-b799035c5342------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*b-94R0bABcT9v2v7vccOYw.png</url>
            <title>Stories by Ediel Queiroz on Medium</title>
            <link>https://medium.com/@edielqueiroz?source=rss-b799035c5342------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 15:05:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@edielqueiroz/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[Databases Need Layer-7 Intelligence]]></title>
            <link>https://medium.com/@edielqueiroz/databases-need-layer-7-intelligence-a3e5f946b21a?source=rss-b799035c5342------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3e5f946b21a</guid>
            <category><![CDATA[java]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[proxy]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[database]]></category>
            <dc:creator><![CDATA[Ediel Queiroz]]></dc:creator>
            <pubDate>Sat, 14 Feb 2026 19:06:23 GMT</pubDate>
            <atom:updated>2026-02-14T19:06:23.951Z</atom:updated>
            <content:encoded><![CDATA[<h3>Databases Need Layer-7 Intelligence — Open J Proxy Delivers</h3><h3>What is a Layer 7 Proxy?</h3><p>A Layer 7 proxy operates at the application layer (Layer 7) of the OSI model. Because it functions at this level, it is aware of application-layer protocols such as HTTP and HTTPS, including their headers, paths, and cookies.</p><figure><img alt="An illustration of the OSI model show all the layer enumarated from 1 to 7 and highlighting the layer 7" src="https://cdn-images-1.medium.com/max/1024/1*qpQ3mAf1Q3hinoqZmJzHjA.png" /><figcaption><strong>The OSI Model</strong></figcaption></figure><h3>Layer 4 vs. Layer 7 Proxy</h3><p>While Layer 7 proxies operate at the application layer, Layer 4 proxies operate at the transport layer of the OSI model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*myyGgWDGQKnNIuMy_VWYbg.png" /><figcaption><strong>Layer 4 x Layer 7 Proxy</strong></figcaption></figure><p>A Layer 4 proxy is based on TCP/UDP protocols, and its routing decisions rely on IP address + Port. Because they operate at a lower layer, Layer 4 proxies are typically faster and lighter than application-layer proxies. However, Layer 7 proxies benefit from application-layer awareness, making them more &quot;intelligent&quot; by leveraging resources such as paths, headers, and cookies to empower their operation.</p><h3>When SQL meets a Layer 7 Proxy</h3><p>With modern application architectures, it is very common to experience increased pressure on databases, especially in Microservices and Service-Based Architectures. This happens because although applications and architectures have evolved to embrace new software delivery models such as cloud computing and containerization, the way they interact with databases has largely remained the same.</p><p>Typically, a set of services maintains its own connection pool. As services scale horizontally, their connection pools scale as well, creating an excessive number of database connections.</p><p>To go beyond a simple pass-through proxy that merely forwards raw TCP/UDP connections, a database proxy must take advantage of the application layer. When database connectivity is combined with a Layer 7 proxy, it becomes significantly more intelligent. Understanding application protocols such as HTTP, HTTPS, and gRPC enables the proxy to inspect SQL statements and make intelligent routing decisions.</p><p>Moreover, drivers such as JDBC operate at the application layer. Therefore, it is logical for the proxy to operate at this layer as well.</p><h3>Open J Proxy (OJP)</h3><p>Open J Proxy (OJP) is a Type 3 JDBC driver and a Layer 7 proxy server designed to sit between Java applications and relational databases.</p><p>As a Layer 7 proxy, OJP understands both JDBC and gRPC protocols, enabling key capabilities such as:</p><ul><li>Intelligent load balancing</li><li>Automatic failover</li><li>Backpressure</li></ul><p>This protocol awareness also enables advanced mechanisms, including:</p><ul><li>Slow query Segregation</li><li>Multinode deployment</li><li>XA distributed transactions</li><li>Telemetry and monitoring</li></ul><p>Application protocol awareness allows OJP to inspect and make intelligent decisions rather than simply forwarding requests from the application to the database.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sXckjBtUiA9YRmpJQFL7SA.png" /><figcaption><strong>Application Protocol Awareness</strong></figcaption></figure><p>Through its own implementation of the JDBC driver, OJP provides intelligent client-side load balancing and automatic failover while leveraging a multiplexed gRPC connection to the OJP Server. This approach significantly reduces network connection overhead.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*WBRtPwbIq6j9YUkAyulOlA.gif" /><figcaption><strong>OJP Design</strong></figcaption></figure><p>Another pivotal characteristic of OJP is its virtual connection management model.</p><p>Virtual connections are lightweight connections that act as &quot;stubs&quot; to connect to the OJP Server, which in turn creates a physical database connection only when required, (for example, when executing a query or update). When an application creates a new JDBC connection, the driver initially establishes a virtual connection until a query is executed.</p><p>This design allows an application to create thousands of virtual connections while maintaining only a single gRPC connection per OJP Server.</p><h3>Conclusion</h3><p>As distributed architectures continue to evolve toward microservices and cloud-native deployments, database connectivity remains one of the most critical — and often overlooked — bottlenecks. Traditional Layer 4 proxies and client-side connection pools lack application protocol awareness, limiting their ability to optimize routing, manage backpressure, or react intelligently to query behavior.</p><p>Open J Proxy (OJP) addresses this gap by introducing true Layer 7 intelligence into the database access layer. By operating at the application layer through its Type 3 JDBC driver and gRPC-based proxy server, OJP gains visibility into JDBC semantics and query execution patterns. This enables intelligent load balancing, automatic failover, slow query segregation, virtualized connection management, and support for advanced capabilities such as XA distributed transactions and multinode deployments.</p><p>The virtual connection model combined with multiplexed gRPC communication significantly reduces connection overhead while preserving scalability and resilience. Instead of scaling connection pools linearly with application instances, OJP enables a more efficient and controlled interaction model between applications and relational databases.</p><p>OJP is an open-source initiative designed to bring modern traffic intelligence principles to database connectivity. Developers, architects, and contributors interested in improving database scalability, observability, and resilience are encouraged to explore the project, review the architecture, and participate in its evolution:</p><p>Website: <a href="https://openjproxy.com/">https://openjproxy.com</a></p><p>GitHub: <a href="https://github.com/Open-J-Proxy/ojp">https://github.com/Open-J-Proxy/ojp</a></p><p>Community feedback, contributions, and real-world experimentation are essential to advancing Layer 7 database proxying. If you are building distributed systems and looking to modernize database connectivity, OJP is a project worth evaluating and contributing to.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3e5f946b21a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>