There is no proxy server actually.lompsa.com
connects over websockets directly to a FIMK instance we have on our server.
If for some reason the FIMK server is caught in a long and blocking process (of which there are plenty, just the nature of how crypto/blockchains - especially NXT/FIMK - 2.0s - operate) you will experience that as a non-responding website.
The most time the FIMK server blocks is on updating database indexes, of which there are again plenty.
Too much actually if you'd ask me.
But there is another dilemma to be solved first. NXT/FIMK are first in it's kind as compared to BTC where there is a user facing API that is much and much more complex than BTC's.
We have all sorts of database indexes to be able to have our client be responsive, while for BTC there only are a handful of indexes (they have no accounts, ae, dgs, aliases, all-sorts-of-searches etc) we have a multitude.
I believe in order to scale this has to change in two phases.
First phase is well on it's way as you know, here we've integrated the FIMK server blockchain download/upload/pop/push etc mechanism with an external database, in our case MySQL.
This MySQL database now holds a one-to-one real-time replica of the blockchain, this database includes all unconfirmed transactions.
The MySQL database is a multi-threaded powerful db solution which is suitable for use as a data backend for an internet facing server. You don't have to expect down time from that.
The second phase is to get rid of all the functionality exposed directly by the FIMK server that is not essential for it's p2p operations, the API size has really gone too far imo. When this is done we would have thrown out probably half of all code and we are able to drop many database indexes no longer in need of updating.
This of course has an effect on how individual people run their own FIMK server, while running the server itself remains fully possible of course, you can run it forge etc.. But what has to change is that you can no longer connect your client to your locally running server and expect your client to keep working the same way..
When the worst internal database indexes are dropped you can no longer use the backend as is without also running the replicated database, since only the replicated database will have all the (and much better performing mind you) search/indexes.
But since probably 99.99% of all FIMK users will be coming through one of our web portals I dont think thats a problem.
To still allow people to program against FIMK we of course must publish a powerful API from our webportals, one I believe will work much better than running your local FIMK server. As you know we have made big steps in that area when we've created our server framework (based on non-blocking Play!/Scala and which works with FIMK at tha java level) .