Basically it leverage Amazon simple queue services by sending user data info asynchronous over http rest requests with the option of turning off the nagel algorithm to optimise TCP pipe connection wait times.
This code proves that we can audit user activity on wangle with Zero loss in performance.
This is done by recording user activity and then when the wangle app is inactive it will open a Asynchronous connection to push the user activity in a tiny message.
Once in Amazon SQS a background service in Amazon EC2 will then connect the messages and store them in Amazon S3 buckets. Another system then collects the messages from each user bucket to use for reporting or audit/police /investigation requests.
You can have my source code. I sent this to Wangle but they don't seem to be too excited about it, they pretty quiet.
I attached the source code as well. I am a cloud computing expert.
The interesting thing for me is I don't understand how data retention could delay the app as it can be done so easily with no performance issue or degradation.
Why did they have such a huge delay in something so trivial?
A message to the audit system is
Username
Sourceip
Destip
Time
Http url
It is so small and asynchronous means in its done in the background so the app runs smooth....
I'm concerned.... I wonder if they can at least show us commit history of source code so that as investors we have proof the app is in development in a professional source control repository.
