<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Vendor-Lock-In on dplabs — Software Engineering &amp; Technology Consultancy</title>
		<link>https://dplabs.tech/tags/vendor-lock-in/</link>
		<description>Recent content in Vendor-Lock-In on dplabs — Software Engineering &amp; Technology Consultancy</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 06 Apr 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://dplabs.tech/tags/vendor-lock-in/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Building AI Features Without Losing Control of Your Architecture</title>
				<link>https://dplabs.tech/blog/ai-features-architecture/</link>
				<pubDate>Mon, 06 Apr 2026 00:00:00 +0000</pubDate>
				<guid>https://dplabs.tech/blog/ai-features-architecture/</guid>
				<description>&lt;p&gt;AI features are getting added to production systems quickly — often quickly enough that the usual architectural discipline gets skipped. The integration is direct: OpenAI SDK in the service, API calls scattered through business logic, prompts hardcoded in the calling code.&lt;/p&gt;&#xA;&lt;p&gt;This works for a proof of concept. At production scale, with real operational requirements, it creates a class of problems that are expensive to fix after the fact.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-vendor-lock-in-problem&#34;&gt;The Vendor Lock-in Problem&lt;/h2&gt;&#xA;&lt;p&gt;Directly using the OpenAI SDK, the Anthropic SDK, or any provider&amp;rsquo;s client library throughout your codebase creates tight coupling to that provider&amp;rsquo;s interface. When you want to:&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
