To begin with, I’ll immediately make a reservation - it’s a superficial sign with web technologies and administration, so don’t blame for the stupidity of the question.

The bottom line is this: you want to create a site that interacts with the database. On the same platform, it is required to locate the daemon program on java , which interacts with this database and with various API's of third-party sites, and does this in 24/7 mode (it monitors database changes constantly + several more actions).

So, please clarify such nuances as:

  1. Select a language for the program. Is this critical, or is java quite suitable? (loads are not super-large, but multithreading is very likely)
  2. On which site to place this project? Is a simple hosting suitable here, or will you need a VPS (virtual server)?
  3. If you still need a separate server, what software will be needed for the operation?
  • 24/7 amused ... If it were 24/5 or 24/6, then you had to think, and when 24/7 it’s easier than simple :) - Barmaley

2 answers 2

Multithreading in your case is not only likely, but necessary for an adequate implementation. Therefore, java is the most reliable choice. To maintain the site, start with Tomcat - lots of examples and ready-made solutions. To select a hosting google "tomcat hosting".

  • one
    Only here is the thread model in Java and the serious (24/7) server things are difficult to use. Usually, almost all descriptions of multithreading in books are something quite perfect, some, seemingly unimportant, nuances of practical life are not considered. - IMHO with a not too large load (unfortunately, it is really checked only by practical operation) it is better to do a multi-process (and preferably without shared memory), rather than a multi-thread structure. (but Java is not very suitable here). In it, even in comparison with native threads, “failed” situations are much easier to handle. - avp
  • Well, who knows how. In the java-stream, I will intercept all exceptions and I will know that the stream has collapsed, but I cannot imagine how to monitor a separate process. And the fact that supposedly "the thread model in Java and a serious (24/7) server are difficult to combine" is an unsubstantiated insinuation. - rfq
  • Tomcat for such things is not very suitable. I would not risk betting on him. In the end, Tomcat is just the reference implementation of the JSP / Servlet container by some production attempts. Here we must take (if you live with Java) something from the category of WebLogic, WebSphere or JBoss. - Barmaley
  • one
    @avp correctly for the system to terminate the stream in which a software error was detected? I do not see the point. The error could have spread beyond the flow, it is better to restart the whole process. And even better, not to release semi-working programs into production than to masterly restart suspended subprocesses and then be proud of the fact that "we are able to do real things." - rfq
  • 2
    @rfq, I don’t dare to argue with arguments like “ it’s better to be healthy and rich ... ” - avp

I don’t even know how to answer such questions ... =)

  1. you can and Java, you can and PCP and Sharp, and rails, on what you know how to write and :)
  2. if Java - you need a server that will support it (few of them, such providers)
  3. server (software) depending on selected technologies
  • Thanks for the answer, 3. It meant software to run that same java daemon. At least in what direction to dig? - jekatigr
  • JVM, JRE, JDK - Gorets