Timeline for Is caching data between independent but interacting systems okay?
Current License: CC BY-SA 3.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
S Jun 5, 2017 at 14:52 | history | suggested | Winter | CC BY-SA 3.0 |
Improved grammar
|
Jun 5, 2017 at 13:55 | review | Suggested edits | |||
S Jun 5, 2017 at 14:52 | |||||
Jun 5, 2017 at 12:57 | history | edited | Christophe | CC BY-SA 3.0 |
edited tags; edited title
|
Jun 5, 2017 at 12:54 | answer | added | Christophe | timeline score: 2 | |
Jun 5, 2017 at 10:31 | answer | added | Zalomon | timeline score: 0 | |
Jun 5, 2017 at 10:16 | comment | added | Mathematics | @Zalomon You are right we are not caching logic... in fact it's the code... we will only going to cache data | |
Jun 5, 2017 at 10:02 | comment | added | Zalomon | How do you cache some logic? you may inform Product X that you created a user in Product Y's active directory? I guess that you can log that fact so Product X is aware of the change or create the user on its own AD if needed, otherwise I'm not sure of what you mean. | |
Jun 5, 2017 at 8:30 | comment | added | Mathematics | @Zalomon it can be a table but they won't necessarily replicate each other, Thus some logic will be involved e.g. creating a active directory user etc.. so it's not just db sync | |
Jun 5, 2017 at 8:25 | comment | added | Zalomon | You mean that each product has a table where it receives updates regarding data from the other product? | |
Jun 5, 2017 at 7:57 | history | asked | Mathematics | CC BY-SA 3.0 |