<snip/> > >> 3. Is there some component or function, which allows > >> Phoenix to supervise the status of its blocks? > > > >no. > > hm - ok. > So, what would you recommend me, if I will have a couple of > serverside apps+servers (A, B and C), each in its own > block, where at least one of them (A) will depend on all > the others. > Let's say one of them (B) doesn't respond to any requests > anymore, because of some internal problem. > Do I need a fourth hosted app (D) to manage this situation, > e.g. like that: have (D) be notified that (B) is not OK, > and have (D) consequently initiate a restart of (B)? > Is such an approach tolerable in a server framework? Or > isn't this a rather generic problem scenario that should be > handled on a framework level? > Any advice, recommendations and/or hints welcome!
hmm. It is not too clear to me what you are thinking about. If you are talking about truely seperate services (like mail server, web server), you want them to be isolated from each other and not have the web server wonder how the mail server is doing, so you'll definately have an extra 'something' (server, cronjob, custom phoenix version, your (D)) if you want to monitor their status. If you are talking about separate but very intimately related services (like a StorageService depending on the availability of a DatabaseService), what you'll want to do is put those into the same server application, and have phoenix handle the dependency stuff. There's a lot of gray area in the middle where it is difficult to give a straight answer. The scenario you describe above could be a good way to handle your use case, or you might be better off doing it completely differently. While this is a generic problem, finding a generic solution is difficult and complex, which is why phoenix doesn't offer one. cheers, - Leo -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
