<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Observability on dplabs — Software Engineering &amp; Technology Consultancy</title>
		<link>https://dplabs.tech/tags/observability/</link>
		<description>Recent content in Observability 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/observability/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>
			<item>
				<title>AI Engineering Is Software Engineering</title>
				<link>https://dplabs.tech/blog/ai-engineering-is-software-engineering/</link>
				<pubDate>Mon, 09 Mar 2026 00:00:00 +0000</pubDate>
				<guid>https://dplabs.tech/blog/ai-engineering-is-software-engineering/</guid>
				<description>&lt;p&gt;There&amp;rsquo;s a tendency to treat AI features as different from other software. Different enough that normal engineering practices don&amp;rsquo;t apply, or apply differently, or can be deferred. This tendency produces AI systems that are unreliable, unobservable, expensive to operate, and difficult to improve.&lt;/p&gt;&#xA;&lt;p&gt;AI systems built with the same engineering discipline as other distributed systems are more reliable, cheaper to operate, and easier to improve. The disciplines aren&amp;rsquo;t different. The application is.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Spring Boot Observability: Metrics, Tracing, and Logs That Actually Help</title>
				<link>https://dplabs.tech/blog/spring-boot-observability/</link>
				<pubDate>Mon, 31 Mar 2025 00:00:00 +0000</pubDate>
				<guid>https://dplabs.tech/blog/spring-boot-observability/</guid>
				<description>&lt;p&gt;Spring Boot 3.x has strong observability support built in. Spring Boot Actuator, Micrometer for metrics, Micrometer Tracing (built on OpenTelemetry), and structured logging all work out of the box with minimal configuration.&lt;/p&gt;&#xA;&lt;p&gt;The gap between &amp;ldquo;instrumented&amp;rdquo; and &amp;ldquo;observable&amp;rdquo; is wider than it looks. Adding dependencies and enabling endpoints is instrumentation. Being able to answer &amp;ldquo;why are 3% of requests failing between the payment service and the inventory service, and since when?&amp;rdquo; is observability.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
