![10 Data Science Myths Debunked [Infographic]](https://www.kdnuggets.com/wp-content/uploads/kdn-10-data-science-myths-debunked-feature.png?#)
/cdn.vox-cdn.com/uploads/chorus_asset/file/25835962/257511_Tech_Oligarchs_MHarris_LEDE.jpg)
3rd party REST API calls in repository pattern
For a long time, I’ve been using Repository pattern to abstract data access logic from actual business logic, always using SQL or noSQL databases as my data source. But how much valid is it, to abstract data access logic into repository, if our data source is a 3rd party REST api? Is there any other better architectural approach for this? (For my particular instance, I am developing a REST API to automate things on that 3rd party platform, and obviously I would need to do the CRUD operations to the data through that 3rd party REST API.)
For a long time, I’ve been using Repository pattern to abstract data access logic from actual business logic, always using SQL or noSQL databases as my data source.
But how much valid is it, to abstract data access logic into repository, if our data source is a 3rd party REST api?
Is there any other better architectural approach for this?
(For my particular instance, I am developing a REST API to automate things on that 3rd party platform, and obviously I would need to do the CRUD operations to the data through that 3rd party REST API.)
