This paper is an overview of how capacity-driven Web services are defined and put into action. Because of the specificities of these Web services compared to regular (i.e., mono-capacity) Web services, the way they are looked into is different and occurs through four steps known as description, discovery, composition, and enactment. A Web service that is empowered with several capacities, that are in fact operations to execute, has to know which capacity out of several it has to choose and then, trigger at run-time. For this purpose, this Web service takes into account the requirements like data and network that are put on each capacity it was empowered with. A feasibility discussion on the implementation of capacity-driven Web services is presented in this paper, as well.