network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 3 months |
| seen | Mar 15 '12 at 6:18 | |
| stats | profile views | 4 |
|
Jul 7 |
awarded | Nice Question |
|
Feb 13 |
awarded | Supporter |
|
Feb 13 |
awarded | Scholar |
|
Feb 13 |
accepted | Highly Concurrent Storage System |
|
Feb 10 |
awarded | Editor |
|
Feb 10 |
revised |
Highly Concurrent Storage System deleted 84 characters in body |
|
Feb 10 |
comment |
Highly Concurrent Storage System Thank you for your response. You are correct. My problem is similar to algorithmic trading platform but different too. we have tried the RDBMS route and it could not scale. I need a storage that can scale and does not have the complexity of OLAP systems as our size of data is just growing and once we get to more TB on three tables, RDBMS will just create lots of locking and similar issue. I am hoping that a nosql option could satisfy such requirements. Any thoughts on that? |
|
Feb 9 |
awarded | Student |
|
Feb 9 |
comment |
Highly Concurrent Storage System I mean, I can not use DynamoDB or some technology that are only available in a public cloud like amazon or azure and so on. |
|
Feb 9 |
asked | Highly Concurrent Storage System |
