WCF - Windows Service API
Budget: $1,500 – $3,000 USD
We are looking to have two APIs developed utilizing WCF. These APIs should be written in VB.NET.
The first API will sit on the same machine as an on-premise SQL Express instance. It will act as the data access layer and be the single point of entry of the data. Calls to the API will be on the same network via TCP. It should also allow 3rd party developers access to the data via HTTP and that access should be secure. The API will access the SQL Express database via Windows Authentication. The API will be hosted in a Windows Service and should be discoverable on the network.
The second API will sit on a machine on the same network. It will be identical to the first API except it will not have 3rd party and/or HTTP access and it will include a discoverability call that will look for the first APIs address and store it. The second API will also make announcements that the first API is listening for.
Here is an idea of how requests for data will flow:
> Software application consumes second API and asks for data.
> Second API knows the address of the first API and contacts it for data.
> First API returns data to second API which in turn returns data to the application via service reference.
There will only be one instance of the first API.
There will be many instances of the second API.
When building this project, all efforts should be made to have appropriate separation of concerns, as well as, security.
You can use the Adventure Works database for any models.
We want this built the right way. Please do not apply if you do not have experience in WCF building APIs.
The first API will sit on the same machine as an on-premise SQL Express instance. It will act as the data access layer and be the single point of entry of the data. Calls to the API will be on the same network via TCP. It should also allow 3rd party developers access to the data via HTTP and that access should be secure. The API will access the SQL Express database via Windows Authentication. The API will be hosted in a Windows Service and should be discoverable on the network.
The second API will sit on a machine on the same network. It will be identical to the first API except it will not have 3rd party and/or HTTP access and it will include a discoverability call that will look for the first APIs address and store it. The second API will also make announcements that the first API is listening for.
Here is an idea of how requests for data will flow:
> Software application consumes second API and asks for data.
> Second API knows the address of the first API and contacts it for data.
> First API returns data to second API which in turn returns data to the application via service reference.
There will only be one instance of the first API.
There will be many instances of the second API.
When building this project, all efforts should be made to have appropriate separation of concerns, as well as, security.
You can use the Adventure Works database for any models.
We want this built the right way. Please do not apply if you do not have experience in WCF building APIs.