There are any number of ways to connect with the DB. ODBC, REST api, jdbc, nodejs,... It really comes down to your requirements.

I'm not sure there is such a thing as 'typical' in terms of Eclipse installation. Whether you get egit or not depends very much on the edition you are downloading/installing.

In short:
a container is a sandbox that runs a single process. This in turn can spawn off other processes. For us, that is isc-main, which will take care of running on the necessary processes (write daemons etc). But as soon as that first process goes away, the container is being closed
In a classical VM a complete machine is being simulated. Which in turn stars up a complete OS and not just a single process context.
There are plenty of articles that explain the difference in more detail (for example: https://blog.netapp.com/blogs/containers-vs-vms/)
(It's important to notice that on some OSes[windows + macos] docker is 'cheating' by creating a hidden linux VM to run the docker images)

While we do share our nameday Fabian!=Sebastian ;)

As Mike already said, pretty much it comes down to the specifics of your site and code. There aren't any big changes between 2014.1.2 and the current version, so I wouldn't expect much coding work. The majority of work is probably going to be your testing of the procedure and the resulting upgraded test environment. We are more than happy to discuss your upgrade plan and help with any issues you might encounter, feel free to contact the WRC and we'll go from there!
Best,
Fab

Just as a quick follow up, this seems to happen if you had installed the standalone Atelier client and subsequently install a full eclipse into the same directory. This will lead to a conflict between a couple of jar, leading to the errors as shown above. Doing a clean fresh install of eclipse solves it.

So you're saying you don't want to just use xpath for that?

seeing that that would be handled by the webserver, I don't see how there would need to be explicit support from ISC.

If you're saying you'll fork things. How often are you going to update from the source repo? (i.e. you didn't fork the latest version of yape)

Aside from the security concerns already raised (you should never direct accept user input), I feel the whole approach violates the statelessness of a REST architecture?
Thoughts?

Best guess:

your server responds to ICMP but HTTP.

Please clarify if you need more details.

Great! And thanks for sharing your solution!