Now that we've identified the core components of a WCF endpoint, the giant remaining question is: how do I make this service available to consumers? You are able to host your service in a variety of places, including:
Self-hosting: You can create a managed .NET application such as a Windows Form or Console application that acts as the host for your service. A self-hosted service can use any of the available WCF bindings but offers the least infrastructure for service hosting. This avenue is typical of demonstration or proof-of-concept scenarios and is not really considered enterprise grade.
Windows Service: You could choose to build a Windows Service that hosts your service in a more managed fashion. Also considered a form of self-hosting; it too can support the full range of WCF bindings. This is a bit better than manually building a service host because, through the Windows Services platform, you get more manageability and support for failure recovery, automatic startup...