I would probably let the proxy node in DMZ run an akka-http server and publish a WebSocket endpoint. The worker node in private network would connect to it using akka-http client. This is probably the easiest way to stream messages from DMZ to private zone with backpressure and (some degree of) delivery guarantees. Akka Streams and Akka HTTP handle a lot of complexity for you and are preferred tool over low level TCP machinery. Of course if you need millisecond latencies and custom binary protocols, you need to get your hands dirty :)
Cheers, Rafał W dniu czwartek, 9 lutego 2017 11:32:55 UTC+1 użytkownik Christian Kaps napisał: > > Hi Rafał, > > Thanks for your answer! Maybe I implement an Akka TCP server which is > located in the DMZ and a TCP client which is located in the private > network. Is it possible that the client polls message in near real-time > from the TCP server? Am I right, that this is possible with Pull-reading as > described in the Throttling Reads and Writes > <http://doc.akka.io/docs/akka/current/scala/io-tcp.html#Throttling_Reads_and_Writes> > > section of the Akka TCP documentation? > > Best regards, > Christian > > Am Donnerstag, 9. Februar 2017 10:23:09 UTC+1 schrieb Rafał Krzewski: >> >> Hi Christian, >> >> Akka is very general toolkit and you can implement any communication >> architecture that you need with it. It offers excellent HTTP support and >> also low-level TCP and UDP communication and you can implement any standard >> or custom protocol on top of that. >> Akka Cluster however does not sound like something that would fit here: >> - it requires bidirectional connectivity among all nodes that are parts >> of the cluster >> - the network connecting the nodes is assumed to be trusted >> - Akka Cluster is useful when you need to create an Actor system so large >> that it does not fit on a single machine because of memory or processing >> power requirements (say, millions of entities interacting in real time) >> >> Cheers, >> Rafał >> >> W dniu czwartek, 9 lutego 2017 09:48:22 UTC+1 użytkownik Christian Kaps >> napisał: >>> >>> Hi, >>> >>> for a project we need a special type of server architecture. Because of >>> a customer compliance we cannot access the customers database server from >>> the DMZ. The server on which the database runs can access servers inside >>> the DMZ. In a similar project my employee has used a proxy like >>> architecture with an additional database server. The outer side writes >>> requests into this proxy database and the inner side polls this database >>> for requests and writes results to it. The outer side polls then for the >>> results. >>> >>> Is such a kind of architecture possible with Akka? Maybe with a cluster >>> like architecture? >>> >>> Outside(Public) | DMZ | Inside >>> Frontend Server | Backend Server | Database Server >>> >>> Best regards, >>> Christian >>> >> -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
