{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Fullstack Ruby Podcast","title":"Designing Your API for Their API (Yo Dawg!)","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/e63b429b\"></iframe>","width":"100%","height":180,"duration":1688,"description":"It’s tempting to want to take the simplistic approach of writing “to the framework” or to the external API directly in the places where you need to interface with those resources, but it’s sometimes a much better approach to create your own abstraction layer. Having this layer which sits between your high-level business logic or request/response handling, and the low-level APIs you need to call, means you’ll be able to define an API which is clean and makes sense for your application…and then...","thumbnail_url":"https://img.transistorcdn.com/z1Z35J65srO9Mo7KW-Uagv-8SWlSysssQNN3In7xUqU/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS85ZThi/M2NiNzdhMmU1ZGUz/ODBiNjY4Zjg5NmI4/NDlkYS5qcGVn.webp","thumbnail_width":300,"thumbnail_height":300}