Can't manage redis connections dynamically

When you say 'Lumen is giving me a hard time' - do you have the same code working ok in the main Laravel app? If so you might want to post to their github issues page :-) I've never tried to change the config dynamically in lumen so can't be much help apart from that I'm afraid :-/

Yeah, so it's quite crazy actually... and I just figured this out: I can only write to a certain redis db in Laravel if that's the first interaction with the cache.

    Cache::get('any_key');
    \Config::set('database.redis.default.database', 2);
    Cache::put('laravel_key_db2', '2',1);  // Gets set in db 0, which is the one set in the config file

But this works nicely:

    \Config::set('database.redis.default.database', 2);
    Cache::put('laravel_key_db2', '2',1);  // Gets set in db 2

I'll submit a ticket... and maybe even try to fix it and make my first contribution to Laravel :) Let's see... But if someone has any ideas or suggestions in the meantime - please.. do let me know.

By the way... this doesn't happen in Lumen. Lumen always go to the database that was set in the config file.

Thanks

That's an odd one! Hope you get it fixed! :-)

Ive been into redis lately , but yours was way off beyond ive been tackling... But if u wan performance you should go to phpredis rather than the default predis if your using laravel but in your case lumen , i havent check lumen yet.

You can follow this guide if you intend to use phpredis than predis but off course you will be using laravel https://laracasts.com/discuss/channels/tips/tutorial-guide-installing-php-redis-on-fresh-install-homestead-with-php7

I also i heard that lumen is insanely fast can handle around 3400 request per sections based on taylor otwell benchmarking the framework.

I Also i hear also that if your just building an api choosing lumen would be the best option, coz its slim and fast. but if your gonna use session , cookie , going for laravel would be the best...

You Said By the way... this doesn't happen in Lumen. Lumen always go to the database that was set in the config file.

Pretty much is the same as laravel it is getting info on the config

The Only thing i can see to achieve this is make a service provider that can add/edit config file on the fly cause using different connection is already available

$redis->connect('127.0.0.1', 6379);

Anyway thats all i can help out >.<

Something pop out of my mind thinking what is the best approach to achieve this

Have you ever thought of using polymorphism?

Hi @elena have you tried the select( database# ) command? e.g.

Redis::command('select', 2);

The (laravel) RedisServiceProvider creates a singleton passing the settings ($app['config']['database.redis']).

As it's in a closure it won't actually be created till it's first use. Hence the behavior you are seeing. Once the PRedis client is created, I doubt that changing the config will make any difference.

Thanks masterpowers. I kind of hacked around it, but ended up liking the result better. I changed both the main app and the microservice to use namespaced redis keys, making use of the "prefix". All good now :)

That worked Mark! Thank you so much!

Redis::command('select', ['database'=>2]);

I was stuck until a bit ago, now I have 2 working solutions. Hmm... what do I do? :D Prefixes or databases?

Since we're grouping the clients by domain, anyway, I just ended up putting \Request::getHttpHost() in the configuration file itself in the main app. Super simple solution that works like a charm. Plus it's a nice way of organizing things, more visual than (integer) database names. And also -> one less thing to manage (no need to keep track of redis database number per company).

What do you think?

Following Code works for me

Redis::select(2)

I think there still might be a need to reset the predis connection. In our application we are forking a process and we'd like to have create a new connection per thread.