Going forward on scalability; databases as well might need to be scaled,
which one can do vertically by partitioning the database; or horizontally
by replicating it. both aproaches need to consider how databases can be
updated: one db only can be written to as well as read, and thus informs the others
when changes are made. Or all can be written to, where various conflicts might
arise with update, delete on a particular item.
To the rescue in all this: the cache; something that is often requested can be
stored in a cache for easy access. The cache can be temporal ie for a certain
number of secondswhile the fancy version includes an identifier: if the identifier changes,
one overrides the timer.
Caching can be done client-side or server-side.
No comments:
Post a Comment