I'm currently building a web application for my enterprise level business internship. This web application will track data from three different sources: a DB2 database, a SQL Dynamic database, and an existing API, and then marry them together.
I'm currently working on the SQL Dynamic side, and I was advised to use Entity Framework to streamline this process. From what I understand, EF is useful when creating local database contexts to perform queries against, generating SQL code, and when updating/inserting records to provide security and performance benefit. However, the SQL data that I need to marry will only be provided by a SELECT, and will be implementing a single stored procedure that will return the data I need.
I have already developed an API to access SQL stored procedures in C# (I was advised this would help them and myself greatly due to their DB infrastructure). I personally don't see the benefit of adding Entity Framework to this solution; in my view (which, take with a grain of salt as a result of my intern position), adding EF to this solution will only increase dependency on non-internal packages and increase complexity of maintenance in the future. I don't need to generate SQL code, and I don't need to insert records; I just need to pass parameters.
In a scenario like this, where I am passing parameters to a single stored procedure already housed in the SQL DB I'm accessing, where can Entity Framework benefit me? If it won't, are there any more convincing reasons I can provide to those above me to remove this dependency?