A
agent_008_nl
Guest
I am not working for the customer where I thought about the exposed problem, so at the moment I have no need to dive into this. But in principle I would like to see a solution (the problem could arise again + it's a step to making microservices possible) along the lines described during the thread. In short, with some small extra's: I want a dataset to be available in memory, where f.e. validations reside (see previous threads where I explain some details about how an abl brms could work). This could be a separate abl session / service, name it f.e. a datacontainer. This dataset is updated when validations / validationmessages etc. are maintained in the database. When the dataset is updated a tweet (pub/sub) goes to all idle appserveragents (or persistent running validation services in separate abl/agent sessions), the dataset is copied to the validationservice and ready for use. Running appserver agents / validation services get a fresh copie after their current work is done and the datacontainer is updated. I rejected the shared temptable as proposed during the thread because running validations have to be completed before the dataset is refreshed. All this to give the validationservice the possibilty to work as quick as possible, without having to do extra work right before a validation is required. Of course it would be nice to be able to offer the dataset in a more language independent format (json?) to services written in another language.
Continue reading...
Continue reading...