We have several decoupled systems. These systems provide public APIs that are consumed by mobile applications and other client applications.
Now we need these systems for internal communication with each other during some calls (for some reason). I am torn between possible solutions.
Making Secure API Calls
Hosting an ASP.NET internal web API for each system so that they can provide data and functionality to each other.
- Advantage: Low grip. As long as the structure of the API call does not change, systems can evolve independently.
- Disadvantage: Very slow. An HTTP request is deadly slow compared to a database request. This can seriously affect the speed of our public calls.
Inter-Solution Link Repository Projects
Exchange and inclusion of a repository database (data access) between several projects.
- Advantage: Very fast. Getting the relevant data will be extremely fast, as it will just be a query to the database.
- Disadvantage: High grip. The rebuild and release on system A probably means the same for system B, as they will share common code.
None of these solutions seem perfect.
Is this a task for WCF?
source
share