NodeBB and Wordpress should be hosted same machine or we can use speretaly them to integrate?

@cagatay they can co exist on the same server. There is integration available, but it really depends on what your requirements are.

@phenomlab I wanna create new subdomain as blog.domain.com and located in turkish server and hosted on. My nodebb hosted in hetzner vps and domain.com also.
My question is; blog.domain.com and domain.com can integrate each other or they should run at same server?

@cagatay the immediate issue I can think of here is latency. If you have a server (for example) in Germany and another in Turkey, then any interaction between the two of them will be much slower than it would be if they were on the same server.

If the transactional activity is for logins for example then this process would be much slower than it should be owing to the servers being in different geographical locations and that could be very noticeable to the user experience depending on where the login endpoint resides.

The performance will also be impacted depending on what is being transferred. Can you provide a bit more detail ?

@phenomlab I want to run the software running on two different machines integrated with each other. For example, when an article is written in wordpress, it should be shared in nodebb or the user who registered with nodebb should also be considered registered in wordpress.

@cagatay There is comments and post sharing for WordPress available in NodeBB. There is also SSO for WordPress (although I haven’t tested this). The question is who handles the registrations and login sessions - WordPress, or NodeBB?

@phenomlab i dont think who handles its just an idea for my web site. I m going to add blog system and share organic post on it for google mean (SEO). I think wordpress will handle.
So can you say clearly that system can work on 2 different location and machines?

@cagatay said in WordPress and NodeBB on different machines:

So can you say clearly that system can work on 2 different location and machines?

Technically, but they need to be in the same location, and same subnet. Anything outside of this will lead to performance problems and will cause you more issues than you will set out to solve.

I personally would not recommend this route as it will make support extremely difficult. There is also the cost angle. The traditional route here is to run both on the same machine which will eliminate the latency and performance issues, and will also keep the costs low.

@phenomlab thank you for information.