# adapter pattern Published articles for adapter pattern. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How Lovable Migrated lovable.dev from Next.js to TanStack Start DevFeed: [How Lovable Migrated lovable.dev from Next.js to TanStack Start]() Original publisher: [Read original article]() Author: Alexandre Zajac Published: 2026-08-24T15:30:50Z Content type: article Language: en Sources: [Hungry Minds]() Topics: [Next.js](), [Development](), [Software Engineering](), [dogfooding](), [Vercel](), [TypeScript]() Tags: [adapter-pattern](), [development](), [dogfooding](), [framework](), [next-js](), [software-engineering](), [trends](), [typescript](), [vercel]() ### AI overview The article describes Lovable's migration of lovable.dev from Next.js on Vercel to TanStack Start. It outlines a gradual rollout using parallel routing and feature flags, route grouping, shared framework-agnostic code, adapters, and AI-assisted migration. ### Source excerpt PLUS: Semantic layer at PostHog 🏗, AliExpress fingerprinting 🔎 , Git serving rebuilt at Datadog 📈 ## Generics vs. Interfaces DevFeed: [Generics vs. Interfaces]() Original publisher: [Read original article]() Published: 2022-12-16T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Go Language](), [Binance](), [backends](), [Code]() Tags: [adapter-pattern](), [api](), [api-server](), [business-logic](), [decoding](), [decoupling](), [encoding](), [function](), [generics](), [go](), [go-api-server](), [gorm](), [http](), [interfaces](), [reusable-code](), [solid](), [solid-principles](), [transactions](), [video]() ### AI overview A video explains how generic functions and adapter functions can reduce code duplication and decouple business logic from API server handlers in Go. It demonstrates HTTP handlers, GORM database transactions, performance evaluation with PPROF, and generic data encoding and decoding. ### Source excerpt Introduction In this video, Paulo shows the benefit of leveraging generic functions to write less code that does more. He starts by walking you through an API server he initially wrote that makes use of Go's default HTTP handlers with a sprinkle of GORM to manage database transactions. He then refactors that code by introducing the concept of adapter functions. Paulo's approach consists of decoupling his business logic with his API code. To achieve this, he defines an adapter function that will establish a bridge between his business logic and API server handlers. This proves to be an effective way to abstract request processing and handling. This approach also promotes code reusability because the business logic is loosely coupled with the API service invoking it. ## The Difference Between An Adapter And A Wrapper DevFeed: [The Difference Between An Adapter And A Wrapper]() Original publisher: [Read original article]() Author: Keegan Rush Published: 2017-01-30T00:00:00Z Content type: tutorial Language: en Sources: [The Coded Self]() Topics: [Code](), [interfaces](), [Programming](), [Library]() Tags: [adapter-pattern](), [bridge](), [compatibility](), [interface](), [interfaces](), [library](), [object](), [programming](), [third-party](), [toolbox]() ### AI overview This article explains the difference between the adapter pattern and wrappers. Adapters bridge incompatible interfaces by transforming input, while wrappers encapsulate code to simplify and constrain its interface, often around external libraries. ### Source excerpt The adapter pattern and wrappers each solve common but distinct problems. Their common usage and similarities in implementation, however, can lead to confusion. Both terms seem to be used interchangeably when in fact there are a few key differences. The adapter pattern and wrappers are two very useful tools and you can benefit from having them properly labeled in your toolbox. Definition Adapter: An adapter allows code that has been designed for compatibility with one interface to be compatible with another. An adapter accomplishes this by transforming the input meant for Interface A into compatible input for Interface B. It is a bridge between two existing interfaces. Wrapper: A wrapper encapsulates and hides the complexity of other code. The most common use of a wrapper is in the Facade pattern. Third-party code can be hard to use due to the fact that the exposed interface is made to accommodate many use cases. When you are only concerned about a subset of the features or the exposed interface, or you find that using the library is hard or tedious, then what you need is to wrap it in a simpler, more constrained interface. Differences Intention: The end product may look similar but the intention is different. A wrapper as used in the Facade pattern is intended to simplify an interface to an external library. An adapter is intended to bridge the disconnect between one interface and another. You may look at a new library that you wish to use and write a wrapper to simplify and streamline its use. You may look at an interface, internal or external, that your existing code needs to conform to, and write an adapter to do that. Composition: A wrapper contains another object and wraps around it. It has the the sole responsibility of moving data to and from the wrapped object. An adapter doesn't necessarily contain or simplify an object, although this can be a secondary benefit of using adapters. An adapter transforms input to make it match the input required by another in