Topic: To store a state for service + rabbitmq
Hello. There is a certain service, the bus (rabbitq+masstransit) and messages. Initially I assumed that if suddenly service fell, at restarting all raw messages it takes from the bus (since msg ack at us will not be the message anywhere does not get to). Specifying requirements, it was clarified that the organization of interaction at us is constructed as follows - the message that it is necessary to begin some operation comes, I answer that started to process request. Further service falling after which I should recover a state (the processed message () is possible. Queue any more does not store the initial message (was ack.) . Sootv. I should organize unpretentious storage, on type what service of that processes etc.: id, service id, message body, process status something Can be necessary still. A question: as well as on what similar storage is better for organizing - mysql, nosql. There is something similar ? The task unpretentious, the decision for certain . Not one decade. It would not be desirable to invent a bicycle. In advance I thank.