This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (18)
- # asami (3)
- # aws (10)
- # babashka (47)
- # beginners (343)
- # calva (36)
- # cider (4)
- # clojure (66)
- # clojure-europe (9)
- # clojure-nl (3)
- # clojure-uk (23)
- # clojurescript (30)
- # community-development (69)
- # conjure (1)
- # eastwood (9)
- # events (7)
- # fulcro (81)
- # graalvm (1)
- # malli (5)
- # meander (1)
- # off-topic (41)
- # pathom (15)
- # rdf (1)
- # reitit (6)
- # sci (57)
- # shadow-cljs (18)
- # spacemacs (4)
- # startup-in-a-month (1)
- # testing (2)
- # vim (1)
i just discovered the Mr. Robot tv show, it is entertaining, i imagine there are people that would fault it at every turn, but i am easily entertained, and ohhhh look at the mentally challenged cute little puppy !
@U0183EZCD0D thanks for the reply, good computer, sci-fi etc. is hard to find, i really liked the movie Archive, it's odd and has a super ending
Cool, will have to look into that one. Also check out the film Primer if you haven't already
I was not convinced at all for my part. I m surprise you like it guys. May need to re check
What would be good to handle rare 30x spikes in website traffic with a clojure back-end?
Saying 30x spike doesn't give enough information, you need to know request latencies(average or percentiles), an know what latency threshold is acceptable, and know where your bottleneck is to determine if you can just queue up extra requests
lol "concrete example" slide with a flesh eating worm from ... tremors? lol
the db fails first usually, so i'd look at indexes, SQL and plan some aggressive caching russian doll-style
with the right architecture (aka "shared nothing") clojure code can scale with more hardware and a load balancer
yeah i was thinking load balancer... it seems like an interesting porblam
I also like how with immutable data you don't have to do key expiry, because when the data changes the key changes
right on... right on... so if something is updated it sorta "percolates up" otherwise it stays cached? if i'm getting the gist
> The advantage of Russian doll caching is that if a single product is updated, all the other inner fragments can be reused when regenerating the outer fragment.
there are other similar techniques to hit the cache more often, like show everyone the same stuff and use client side js to update based on specifics - like for time, or lists "all but me"
Aha. Cool. Hmm... I'm wondering what "cache" looks like in clojureland...
memcache + client is the canonical way, but depending on case you may get away with plain RAM memory
I'm reading this research paper and do not understand the use of > in fMRI images ..... really off-topic to programming but maybe someone understands what that's for?