Re: High Transaction Data Persistence Requirement across Different Process / Programs

[BrowserUk]

I think you need to clarify the operating environment and operational requirements of your question.

1. Is this 3 long running concurrent processes? Or with one or more transient (web-server-like) processes?
2. Is that a single 40-byte string? Or one 40-byte string per id? (If so, how many ids?)
3. You mention persistence. Is that persistence between connections? Or persistence across server outages?
4. Are the other two processes also Perl? Or C? Other?
5. Do all three need read-write access? Do you need coherency?
6. Many other questions that would be answered or avoided by a much clearer description of the actual purpose.

[Anonymous Monk]

Hi let me elaborate a bit MORE to get Better Suggestions from all Perl Monks

Platform Red Hat Linux 64 Bit 5. 4 with Perl 5.8

1. There are "A" number of Perl ProcessA running, which read from Linux QUEUE (ID - Amount - Details ) and make a Call to FCGI process B , Collect the response, based on the Response(Response gives Session ID for the ID )....TO 3

2. There is a FCCI process C , which is invoked by External systems for Session ID to provide value Success or Failure ..., which is read and Mapped to the DB with Session ID - Success/Failure

3 . The FCGI B after getting the response, based on the Session ID will query DB for the Session ID and Write in to a Linux Queue

All of these 3 Process are in Synchronous mode dependent on one another, we are trying to make this Asynchronous and achievable at high throughput. So to make the same , we need to share data across the 3 Process to remove the Database interaction

Coming to the Questions asked

1.These are Non stop running process , running in multiple instances

2.Mapping is required to be like Id- SessionID - Amount - Unit - Success/Failure - Number

3.Persistence - In terms of Data persistence across these processes on single server

4.All the 3 are perl Process

5. Yes worst case scenario need all the 3 to read write

6. Sorry for not being clear in my first description

[BrowserUk]

Sorry, I don't think I can help. I've read and re-read your description of the 3 processes, but I cannot make sense of the flow of initiation at all. Hopefully someone with more experience of clustered/cloud-based CC processing will be able to help.

Specifically I don't understand your nomenclature "process A ... make a s call to FCGI process B"? Are you saying that Process A makes an HTML connection to process B?

Nor do I understand "FCGI process C , which is invoked by External systems".

Basically, I'm out of my knowledge zone.

[Anonymous Monk]

Hi , Let me make a last try to make things clear

Process A , Process B and Process C are the 3 Process

Process A is a stand alone continuous running perl program which Reads from Linux named queues and process the Message . It picks up the message in the queue , and Makes a LWP call to a FCGI Process

This FCGI Process is Process B; FCGI is a persistent CGI process something like mod_perl, when the Process A makes this HTTP call to the FCGI process . This FCGI inturn again makes a HTTP Call gets back a HTTP 200 for it and Updates the Database ; and does a poll on the database tilll.....Basically we are making a Charging request to an asynchronous system

FCGI Process C that is running is invoked by the charging system after succesfull processing , this Updates the Database

Polling being done earlier ends here as the value is updated in the database; and the value is taken and written into a Linux named queue

Hopefully now I am little more clear ?