cheeseri'm for anything to get less redises in the world. :)
dreamrealwell, thisis another one
dreamrealbut the positioning is interesting
* GreenResponse joined #java
cheeseryeah. kinda reminds me of redpanda in that sense.
* sepult joined #java
* kusanagi joined #java
* jamezp joined #java
* rvalue joined #java
Tenchiis redis not multithreaded?
ParaClassically no.
Tenchilol
ParaSeveral multithreaded redis forks and thingies exist.
* Tenchi has never used/needed/justified redis
ParaRedis' speed comes from avoiding concurrency performance impact. It's kinda its whole point.
* Tenchi has seen N-billion cobbled together thingies using redis
dreamrealI have never been happy using redis. I'd choose it about four years before dynamo, though.
dreamrealI guess to me redis can't decide what it actually is. memcached sucks but at least it knows it's only a cache and is a poor bandaid; redis acts like it's pretending to be something it's not.
dreamreal(I don't use memcached either, FWIW.)
Tenchii was just going to mention memcached but no idea if the kids would even know what that is
ParaRedis is a key-value store at its core. People using it as a cache are kinda missing half of the point, but it is an usecase, sure.
dreamrealTenchi: I fear they do.
Tenchibut yeah, seeing the adoption of redis back in the day reminded me of the adoption of memcached even backer in the day
ParaRedis is basically a data primitive, so reading through its API and commands should give you building blocks which you then figure out if they help you or not.
Tenchiseeing the adoption of mysql even backer backer in the day
Tenchi(the network attached spreadsheet)
ParaAhh, reminds me of one sysadmin interaction from ages ago.
Tenchibacker backer in the day the mysql manual said "foreign keys arent supported because they slow everything down"
ParaOur service started returning garbage to users. So we do some debugging, weird, there's a cache here. Ask ops. "We installed memcached." "Why?" "Because your service was slow." "But we have autoscaling?" "Well yes, but we wanted to test memcached." "Okay, well now our user database is fucked because of cached results."
javabotdreamreal's title: "Jordan Lord's "Three Constraints Before Building" | bytecode.news"
* agnivn joined #java
* Drixtan joined #java
* X-Scale joined #java
* julemand101 joined #java
* yaboishady joined #java
* julemand101 joined #java
* yaboishady joined #java
* stfstfm_ joined #java
* stfstfm joined #java
* sa02irc joined #java
* stfstfm_ joined #java
* ferdna joined #java
* TomyWork joined #java
* magla joined #java
* agnivn joined #java
* agnivn joined #java
* Cyp joined #java
* X-Scale joined #java
* agnivn joined #java
* stfstfm joined #java
* agnivn joined #java
* x1bncwn joined #java
* Nnavd joined #java
* nmourey joined #java
* mindCrime joined #java
jreicherdreamreal: re that "unpopular opinion", how would it apply to the cache that might be used by a database engine itself, so it doesn't have to hit storage?
jreicher(And this is not distributed either, for most databases)
* kathadris joined #java
dreamrealIf it's the database, it's not really a sidecache
jreicherWhat would you call it, from the engine's point of view? To itself the engine is just another application.
dreamrealWhich engine? the database engine?
jreicherYes
dreamrealWell, an internal cache is an aspect *of the engine*, I don't think it'd see it as external to itself