473 karma · joined March 14, 2011
There are some problems with no good solution, namely the signed parameters in Amazon's case. How do you sign JSON? Is there a "canonical" JSON format that will allow signing consistently, and verification? All the approaches I've seen are incompatible in some way.
Client-side SSL is another solution, but its much less flexible (i.e., token-generated requests wouldn't be easy)
(I'm not actually serious about the last bit).
However, this approach is less flexible and makes Akka more all encompassing in feel.
If the "fat cache" still lets you work in a disconnected state (such as iCloud would let you), I don't see this as a problem.
I've had non-ECC RAM systems destroy database tables leading to data loss.
Systems with ECC are either able to correct the error (and log it), or throw the alarm bells. Even discounting RAM bit flips, simple bad RAM can destroy your data. Having an ECC aware system (including getting Linux to check the EDAC or have the baseband monitor do so) has saved me many times from failing hardware.
FPGAs are not a silver bullet. If you can express your design using a GPGPU instruction set, then by all means please use that. Its going to be more efficient by an order of magnitude, from power consumption and especially cost.
High end FPGAs can easily run in the $30k for a single unit range (this is what NVidia is going to buy to simulate their latest design in hardware, its not likely going to end up in a shipping product). They are also relative power hogs. Their strength lies in highly concurrent systems, especially around data streaming from disparate interfaces to other interfaces, when you can't put enough I/O bandwidth into an existing processing solution.
GPUs are good at processing and will floor an FPGA there. They are relatively terrible at I/O.
For now, they are the low volume option (<1-10m units) if you need special interfaces. If all you are doing is number crunching a Gpgu would likely be a more effective option.
http://zeroturnaround.com/jrebel/
Works with pretty much anything JVM.
The abstraction breaker here is that your application often has a set of ideal GC settings, which need to be set. You cannot forget about the garbage collector when using the JVM.
This is an interesting twist especially with the 16GB devices which tend to actually be above 50%.