<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body><div><div style="font-family:Calibri,sans-serif;font-size:11pt">+1<br><br>Sent from my phone, so anticipate hilarious autocorrects</div></div><div dir="ltr"><hr><span style="font-family:Calibri,sans-serif;font-size:11pt;font-weight:bold">From: </span><span style="font-family:Calibri,sans-serif;font-size:11pt"><a href="mailto:aslak@redhat.com">Aslak Knutsen</a></span><br><span style="font-family:Calibri,sans-serif;font-size:11pt;font-weight:bold">Sent: </span><span style="font-family:Calibri,sans-serif;font-size:11pt">11/8/2016 8:10 AM</span><br><span style="font-family:Calibri,sans-serif;font-size:11pt;font-weight:bold">To: </span><span style="font-family:Calibri,sans-serif;font-size:11pt"><a href="mailto:tmancini@redhat.com">Todd Mancini</a></span><br><span style="font-family:Calibri,sans-serif;font-size:11pt;font-weight:bold">Cc: </span><span style="font-family:Calibri,sans-serif;font-size:11pt"><a href="mailto:alkazako@redhat.com">Alexey Kazakov</a>; <a href="mailto:almighty-public@redhat.com">ALMighty-public</a></span><br><span style="font-family:Calibri,sans-serif;font-size:11pt;font-weight:bold">Subject: </span><span style="font-family:Calibri,sans-serif;font-size:11pt">Re: [almighty] Cache solution for Almighty core</span><br><br></div></body></html><div dir="ltr">That's the beauty of immutable objects.. :)<div><br></div><div>-aslak-</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 8, 2016 at 1:36 PM, Todd Mancini <span dir="ltr"><<a href="mailto:tmancini@redhat.com" target="_blank">tmancini@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">There are only two hard things in Computer Science: cache invalidation<br>
and naming things.<br>
<br>
-- Phil Karlton<br>
<br>
Many of the worst bugs I ever struggled to fix had to do with caching.<br>
It is so very hard to get right in large, distributed, multi-tenant<br>
systems. Proceed with caution; don't optimize early. (and have flags to<br>
be able to turn it off 😉)<br>
<br>
Sent from my phone, so anticipate hilarious autocorrectsFrom: Alexey<br>
Kazakov<br>
Sent: 11/7/2016 7:15 PM<br>
To: ALMighty-public<br>
Subject: [almighty] Cache solution for Almighty core<br>
<div class="HOEnZb"><div class="h5">Hi all,<br>
<br>
At some point we will probably need some universal cache solution which<br>
we could use different types of objects in almighty core. I'm going to<br>
spend some time on researching in this area but there are a few<br>
questions I would like to discuss with the team.<br>
There are some solutions like Memcached or Redis which could be used but<br>
they require to have a server with the cache service (on a dedicated<br>
container?) where we could keep WIT, WI and any other artefacts which we<br>
want to access some value by a key. Some solutions like Memcached are<br>
pure in-memory some like Redis can be persistent but my biggest concern<br>
for now is what approaches are best for microservices world.<br>
In monolith world we could have a shared cache server. One DB - one<br>
cache service. But I'm not sure if it's worth having an internal<br>
dedicated cache server for each relevant microserver.<br>
Currently we are kinda building a monolith and a cache server could<br>
work. But how our cache system should evolve when we start<br>
splitting/introducing microservices in almighty-core? Is there any<br>
concept of shared cache between microservices or it's always hidden by<br>
the microservice implementation and the microservice just takes care of<br>
synchronization of its internal model/DB and uses some internal fully<br>
independent cache if needed.<br>
<br>
Any thoughts?<br>
<br>
______________________________<wbr>_________________<br>
almighty-public mailing list<br>
<a href="mailto:almighty-public@redhat.com">almighty-public@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/almighty-public" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/almighty-<wbr>public</a><br>
<br>
______________________________<wbr>_________________<br>
almighty-public mailing list<br>
<a href="mailto:almighty-public@redhat.com">almighty-public@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/almighty-public" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/almighty-<wbr>public</a><br>
</div></div></blockquote></div><br></div>