Personally, I think it is better to setup the deployer as a Java or .NET application because it provides better flexibility and extensibility. All the legacy CD feature should just work. You shouldn't need to upgrade the deployer service to have it work with SDL Web 8
Update to your 2nd Edition:
As of SDL Web 8, the old publishing framework has been deprecated in favor of a new one, and as a result, the Publishing Management node in the Administration tab of Content Manager Explorer is hidden by default. You can make it appear again by changing a configuration setting.
Procedure On the Content Manager server, navigate to the folder %TRIDION%\web\WebUI\Editors\CME\Configuration. Open CME.config for editing. Find the enablepublishingmanagement element and set its contents to true. Save and close CME.config. Restart the Content Manager Explorer Web site. Access the Content Manager Explorer Web site, select the Administration tab and confirm the presence of the Publishing Management node.
After you setup your java deployer app, make sure the httpupload url works in the browser. Then use the legacy feature and create a publication target with the deployer url tied to it. The transport service should automatically pick up. No need to install a microservice nor discovery service