Hello Jason, This is a project dealing with Internet of Things/5G.
The plan was to cache millions of devices session information in memory for the frequently communicating things and to age out the infrequent things to the database. The in memory search would be done first, If cache hit did not occur, then it would goto the db for the devices that communicate infrequently (once a month, for example a smart meter). The cache will be up 7x24 all the time, just like DNS. Project is just starting, meaning that I do not have db load and spikes information as of yet. I created a micro service using django, REST API, using mariadb and postgres to start. The micro service runs in a docker container and will use K8s or Docker Swarm for orchestration. What would you recommend for an approach. I am currently just counting on the db (mariadb) to perform caching internally. I was about to run an experiment to compare my approach to just counting on the database. thx bk On Tuesday, August 7, 2018 at 8:53:44 AM UTC-4, Jason wrote: > > What other alternatives have you looked at with caching before this? How > long is your cache lifetime, how heavy is your db load, what spikes do you > have, what are your bottlenecks. > > There are two hard things in computer science: cache invalidation, naming >> things, and off-by-one errors. >> > > https://twitter.com/codinghorror/status/506010907021828096?lang=en > > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/6f2849c0-fb43-477b-911e-08c0c60e52b1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
