4 ms·
The real problem here is PHP/MySQL, not the dynamicism per se. A blogging platform based on Rhino (EcmaScript) on JVM hosted on virtualized server (or in cloud
by ilyak 17y ago
The real problem here is PHP/MySQL, not the dynamicism per se.
A blogging platform based on Rhino (EcmaScript) on JVM hosted on virtualized server (or in cloud) would easily resist slashdot effect.
And using file-based storage it would be storage-friendly, too.
And nobody prevents you from using external editor for WordPress, even.
- jrockway 17y agoFile-based storage may be "storage-friendly", but it isn't retrieval-friendly. For example, finding the list of all tags your blog uses requires a linear scan over every document in the system. Not fast. (Visit http://blog.jrock.us/ http://blog.jrock.us/. It does this. It takes a long time to load.)
- ilyak 17y agoYou can cache cache that in-memory! Because you've got a persistent app server.
- jrockway 17y agoHow do you know when to invalidate the cache without doing a scan over all the files? (Answer: hope your filesystem updates the directory change time when a file inside changes, or that your app server is inotify-ed of the change. Both are more complicated than querying a database. If I used KiokuDB for Angerwhale, it would only take me one key lookup for things that currently involve traversing the directory tree. Caching is nice, but it is not the solution to all problems.)
- ilyak 17y agoYou know when you update your data. Therefore, you invalidate your cache when you update your data. Timestamps help alot if you're paranoid, also.
- leej 17y agowhat? a (dynamic) cms resist /. easily on a virtualized host? can you please explain it more?
- ilyak 17y agoWhy not? Serving pages fully off cache. How many hits per second is slashdot effect? We could count. I think slashdot effect mostly happens because database (mysql, generally) locks down, and we're removing that bottleneck by going into file-based storage and in-memory caching.