We are kind of evaluating the cons and pros between Ignite and Redis.
On official documents, it is said Ignite is partially Redis compliant. With that said, some commands / function come with limitations on the documents. Are there other unsupported features / known issues that Ignite-Redis does not clarify on the document?
Thanks in advance.
The commands listed on the docs page should work.
You can also check out known issues that mention Redis.
If you find that something else doesn't work, please report it to user#ignite.apache.org.
Related
I want to use MassTransit bus with RabbitMQ. But I am not able to find a simple example. I am looking for example which will get me started.
What I have tried.
googled: But most the examples are using MSMQ or they using too many configuration options.
GitHub: I looked a the GitHub for MassTransit (https://github.com/MassTransit/MassTransit/tree/master/src/Samples) But the example here is heavily loaded. It's very hard to understand for beginners.
Reading docs: I have started reading docs but it will take some time before I finish it. I am hoping if someone shares a link to simple example which will get me started.
Please provide your suggestion.
Here's a simple, good pub-sub example using MassTransit and RabbitMQ both.
http://looselycoupledlabs.com/2014/06/masstransit-publish-subscribe-example/
In case the article link does not work, here's the link to the source code:
https://github.com/dprothero/MtPubSubExample
Thanks to the author of course!
MassTransit implements a lot of concepts and provides great many features with a very small surface API. There's no simple way to describe everything it does, because the problems it helps to solve are not simple, but an example can be made small.
Have a look at this sample I have for testing throughput:
https://github.com/et1975/Throughput-Test
The only "extra" that one might find unnecessary is Dependency Injection integration. You'd want one in most cases, but it does hide how certain bits interact.
Look at https://groups.google.com/forum/?fromgroups#!forum/masstransit-discuss for more help.
Cheers,
ET.
I am very much new to activemq. I was trying to use activemq broker for subscribe/publish messages. But as for lack of experience I have no idea how to do it or if its really possible to do it. I googled a lot but unfortunately there is no suitable example for this type of functionality. So I was hoping may be someone here can put some light on it. Can any one here can give me some example of how to do it? or may be some link to online documentation. I have already tried apache activemq broker documentation. But it was not helpful, or may be I dont have that much experience to take help from it.
What you are interested in is done using topics. The reason that you haven't necessarily seen a description of it on the ActiveMQ site is that it's a foundational thing that is assumed that readers know about.
If you are looking at an introduction into messaging using Java, the best place is Oracle's JMS tutorial. Afterwards take a look at the code in the examples directory of an ActiveMQ installation. Alternatively, ActiveMQ in Action is a great book to get you heading in the right direction.
If you are using a language other than Java, ActiveMQ supports the STOMP protocol for which there are a large number of implementations in various languages.
Hope that helps.
I'm looking for articles and references that give an overview of 'queueing' (I'm probably not even using the right term here). I'm hoping for an introductory styled guide through a world of Redis, RabbitMQ, Celery, Kombu, and whatever other components exist that I haven't read about yet, and how they fit together.
My problem is I need to queue up background tasks for issued by my Django website, and every blog and article I read recommend different solutions.
Lots of options available to you, and your choice will likely come down to personal preference and what dependencies you feel comfortable installing.
I'll give a vote for Redis. I evaluated RabbitMQ, ActiveMQ, HornetQ, and Redis and found Redis to offer the best mix of ease of installation, simplicity, and performance.
It's technically not a message queue, but the push/pop primitives for the list types provide atomic queue-like operations, so it can effectively be used as a queue. It has worked well for us.
One python specific project on top of Redis you might look at:
http://richardhenry.github.com/hotqueue/tutorial.html
Very simple. But again, all the other options, like Celery, are viable too.
RabbitMQ has a good introduction here: http://www.rabbitmq.com/getstarted.html There's examples in Python, even.
HornetQ has a very good documentation, and it's simple to install.
You can find the documentation at www.hornetq.org, and you would have several examples available with the distribution.
I keep seeing references to the idea that "CouchDB may not be the best tool in every situation." This is good to know, but unfortunately also applies to every technology.
What would be much more helpful is a description of how CouchDB was tried on a project and subsequently abandoned for a traditional SQL database.
If you've tried CouchDB on a project and later gone back to a SQL database, what factors played the biggest role?
You might want to check out the following articles, which describe a few examples:
Why CouchDB Sucks
Stack Overflow - When to use CouchDB vs RDBMS
When to use CouchDB, when not to...
Top 10 Reasons to Avoid the SimpleDB Hype
Does CouchDB supports referential integrity?
There’s a good CouchDB post-mortem from Sauce Labs here:
http://sauceio.com/index.php/2012/05/goodbye-couchdb/
And another from Signal here:
http://blog.signalhq.com/2012/01/24/getting-off-the-couchdb/
Its marketing slogans "Relax, it's easy" and "CouchDB bult for the Web" - it's not true.
Because:
It's not easy. Ha-ha, writing map/reduce for every query is easy, really? Did someone who advocates it actually tried this approach, on something real I mean, not just two-weekends-blog app?
Some common web-app tasks is hard to do with CouchDB (try to get Post with its Comments Count in one query or Tag Cloud (top N tags, not just counts of tags) to see it for Yourself.
So, CouchDB has very interesting and unique features, but its marketing is wrong. It's not for a general web app, it's a nice but a very specialized tool.
P.S. More details http://alex-craft.com/blog/2013/a-little-about-cochudb-and-comparison-with-mongodb
you might find this page useful http://www.mongodb.org/display/DOCS/Comparing+Mongo+DB+and+Couch+DB
Ubuntu stopped using CouchDB for UbuntuOne, because it failed to deliver its promises, even for small load: https://lists.ubuntu.com/archives/ubuntu-desktop/2011-November/003474.html
I'm very impressed with my initial tests with db4o. However, i'm wondering just how many enterprise class websites are out there powered by db4o, i couldn't see any on the main website?
I can't see any reason why db4o should not be used. There appears to be decent enough support for transactions and ways to handle concurrency for example.
Anyone got a list of websites i could look at?
See:
http://developer.db4o.com/Projects/html/projectspaces/gaabormarkt.html
A particular search engine used to be powered by db4o (I say "used to" because I haven't talked to the author about this since a long time).
http://www.rel8r.com/
The author is Travis Reeder.
Although I cannot see websites specifically, here is a list of Open Source Projects from the db4o website:
http://developer.db4o.com/ProjectSpaces/view.aspx/Open_Source_Products