What is the exact difference between Adapter and Proxy patterns?

Question

As I understood both Adapter and Proxy patterns make two distinct/different classes/objects compatible with each for communication. And both of them are Structural patterns. I am getting that both of them are pretty much similar with each other.

Can some one explain what exactly make(s) them different?

EDIT: I went through this question. But I'd rather like to have a close comparison between Adapter and Proxy.

Answer 1

Adapter:

1. It allows two unrelated interfaces to work together through the different objects, possibly playing same role.
2. It modifies original interface.

UML diagram:

You can find more details about this pattern with working code example in this SE post:

Difference between Bridge pattern and Adapter pattern

Proxy:

Proxy provide a surrogate or place holder for another object to control access to it.

UML diagram:

There are common situations in which the Proxy pattern is applicable.

1. A virtual proxy is a place holder for "expensive to create" objects. The real object is only created when a client first requests/accesses the object.
2. A remote proxy provides a local representative for an object that resides in a different address space. This is what the "stub" code in RPC and CORBA provides.
3. A protective proxy controls access to a sensitive master object. The "surrogate" object checks that the caller has the access permissions required prior to forwarding the request.
4. A smart Proxy provides sophisticated access to certain objects such as tracking the number of references to an object and denying access if a certain number is reached, as well as loading an object from database into memory on demand

For working code, have a look at tutorialspoint article on Proxy.

Key differences:

1. Adapter provides a different interface to its subject. Proxy provides the same interface
2. Adapter is meant to change the interface of an existing object

You can find more details about these patterns in sourcemaking articles of proxy and adapter articles.

Other useful articles: proxy by dzone

Answer 2

From here:

Adapter provides a different interface to its subject. Proxy provides the same interface.

You might think of an Adapter as something that should make one thing fit to another that is incompatible if connected directly. When you travel abroad, for example, and need an electrical outlet adapter.

Now a Proxy is an object of the same interface, and possibly the same base class (or a subclass). It only "pretends" to be (and behaves like) the actual object, but instead forwards the actual behavior (calculations, processing, data access, etc.) to an underlying, referenced object.

Extrapolating to the electrical analogy, it would be OK that the use of an adapter is visible to the client - that is, the client "knows" an adapter is being used - while the use of a proxy might more often be hidden, or "transparent" - the client thinks an actual object is being used, but it is only a proxy.