logging - What NoSQL solution is best to store Apache error_log and access_log? Cassandra or MongoDB? -


We have developed a PASS solution for PHP. Under this, we offer developers the ability to view Apache errors and log-in files through our APIs.

Currently we write logs in files on disk per disk (vhost).

Even with higher nodes and deployment, it does not scale well, even if the files are on distributed file system (Glastrephase), we want to switch to something better.

Especially for billing and statistical reasons, we do not always want to parse the log files.

Since collection of collection of mongodibi looks great for logging, we wanted to go with it. But it is revealed that they do not seem to work with auto-shading, what kind of things do we deteriorate for us because we expect that they read too much then they read.

The second option was the case, which I want because it is every node equal approach, but they have no such thing as a capsized collection.

One of the two solutions provides a specific feature that helps me make a decision, or I do not see it.

>

So do I want to know that someone has used one of the two systems for logging first? What are your experiences, can you give me some suggestions? Or are there other solutions that keep our needs better?

Neither two solutions provide a specific feature that helps me make a decision , Or I do not see it.

Honestly, we are going through this test with some serious log data (and so far, I mean, some of us are running late last night Were).

For me, these two specific attributes are: ease of use and proven scaling .

Ease of use

  • Mongodibi was easy in just a few hours from an active Mongo instance Together with the data imported from MySQL, and the whole map-less.
  • In the same period, the team sat around to compile the Java files to configure Cassandra to configure Hadop to run on the existing case implementation so that they can be mapped- Can reduce.

proven scaling

  • earning of mongoiboiba is still in beta in the next few weeks Ready to launch
  • Cassandra sharding is proven to be very great examples.

So I think the answer is really going to be specific, for my personal taste I honestly think that Cassandra is a more stable & amp; Proven product, but I also know from experience that learning and setup curve is a very steeper so it can be worth a little effort of both.


Comments

Popular posts from this blog

c# - sqlDecimal to decimal clr stored procedure Unable to cast object of type 'System.Data.SqlTypes.SqlDecimal' to type 'System.IConvertible' -

Calling GetGUIThreadInfo from Outlook VBA -

Obfuscating Python code? -