I will be making the plunge in a production server environment soon, but I will be starting with my read only, or read intensive applications.
I have an elevation service, which has 600gb of binary files which are queried randomly. Since I have users from all over the world using the service at any one time, the heads on the drives must be flying all over the place. Perfect application for SSD's, even if they are poor at wear leveling, because it's a read-only application.
As far as database is concerned, I'll be holding off until I am sure I won't be screwed by the wear leveling. My database is currently sitting at 91% reads, but as we grow I can imagine that 9% writes can add up way quicker on the server than any amount of writes do on a persons desktop.
I have an elevation service, which has 600gb of binary files which are queried randomly. Since I have users from all over the world using the service at any one time, the heads on the drives must be flying all over the place. Perfect application for SSD's, even if they are poor at wear leveling, because it's a read-only application.
As far as database is concerned, I'll be holding off until I am sure I won't be screwed by the wear leveling. My database is currently sitting at 91% reads, but as we grow I can imagine that 9% writes can add up way quicker on the server than any amount of writes do on a persons desktop.