|| at Dec 8, 2012 at 7:57 pm
El sábado, 8 de diciembre de 2012 19:20:13 UTC, Kyle Lemons escribió:
I need to handle a massive quantity of images (for then to create static
web pages using that information). The images will be into the file system
but I'll use a database to hold information associated to them (i.e. width,
Now well, I could build a specific system in Go using an array of structs
or a map, instead of using a RDBMS; Redis could be another option. The
disadvantage of use Go jut like Redis is that all DB has to be in memory.
Go isn't a database and has no set semantics.
Yes, I know, I already had written a little DB in Go to handle local
information of my disks.
Who says that you can't use an on-disk index with Go? Especially with an
SSD to help out, you could probably devise a very efficient combination of
in-memory and on-disk indices into an extremely large number of images.
That's a good idea. I was looking distributed filesystems like Ceph, Lustre
and Moose FS, but a distributed database like Riak does everything more