I am looking for best practices around the Unit of Work & Repository patterns. Our team is building a web app that for the first phase will be interacting directly with an EF backed database. For the second phase, this may be completely swapped out for a 3rd party platform that is backed by a RESTful api.For implementation, I was thinking of just standard UnitOfWork & Repository patterns, so we only need to re-implement those interfaces for the REST api when the time comes.Does this seem like an appropriate pattern for my scenario?
Unit of Work / Repository patterns with EF & RESTful service
c#;rest;entity framework;repository;unit of work