WCF vs Web API vs NET Remoting. The functionality of the centralized server is exposed as a web-service through Windows Communication Foundation (WCF). There are other ways by which the remote functionality can be exposed such as .Net Remoting of Web API from Microsoft, but neither of them can offer interoperability, security and performance, all in one. Interoperability of the WCF is ensured by the way it publishes it is service and **data** contracts. The WSDL ensures a cross-platform communication, thus adding a high degree of flexibility to this component. Due to its flexibility we can configure the security aspect of the web-service to fit our needs. If configured correctly, the WCF service can ensure confidentiality, integrity, and authorization. Confidentiality and integrity can be guaranteed at transport level or at message level, or at both, without a significant performance penalty. The authorizations in WCF provide flexibility in the way we define the authorizations. New authorizations levels can be defined and configure by the developer, or the WCF service can use the windows accounts that accesses the service. In this case, the developer doesn't have to define the authorization roles, but it needs to configure the levels of authorization. This allows us to write optimized queries the return an optimal amount of data. The main disadvantage of LLBLGen is that it cannot be integrated in the IDE, and comes with it is own configuration environment. Morover, LLBLGen Pro is not free. The advantages of Entity Framework is that it can be fully integrated in the development environment and plus, is free. The backend database was built using Microsoft SQL Server.