{"id":3303,"date":"2020-11-27T09:35:42","date_gmt":"2020-11-27T09:35:42","guid":{"rendered":"https:\/\/eluminoustechnologies.com\/blog\/?p=3303"},"modified":"2025-05-22T10:11:04","modified_gmt":"2025-05-22T10:11:04","slug":"adapter-design-pattern","status":"publish","type":"post","link":"https:\/\/eluminoustechnologies.com\/blog\/adapter-design-pattern\/","title":{"rendered":"Understanding Adapter Design Pattern with a Case Study"},"content":{"rendered":"

Have you ever thrown up your hands in frustration when after a hectic day of travel, you find your phone’s charger is incompatible with the power adapter in your hotel room?<\/p>\n

Yes!<\/p>\n

Then you can understand the feeling of a developer when issues arise during developing software whereby two objects with different interfaces in the code need to interact with each other.<\/p>\n

The challenge in both cases is to find a solution that costs less.<\/p>\n

i) In your case- buying a new compatible power adapter<\/em><\/p>\n

ii) In the developers’ case- reworking the code because the changes broke something.<\/em><\/p>\n

The real-time solution in each case is the power adapter; one is physical while the other is virtual.<\/p>\n

In this blog, we will understand the adapter design pattern and how it deals with incompatible class issues.<\/p>\n

\n
\n

Table of Contents<\/p>\nToggle<\/span><\/path><\/svg><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n