How confident are you that your model for this is correct? Hundreds of millions of records is a lot for one table... in some cases, it may be beneficial to part

How confident are you that your model for this is correct? Hundreds of millions of records is a lot for one table... in some cases, it may be beneficial to partition such a table even in a normal relational database. That being said, if this is an application with complex calculations and a very simple data structure, you should note that the biggest issue is creating indexes to find the records that must participate in a particular calculation quickly. RDBs are very good at building indexes, typically and I would personally be inclined just to use mySQL with data partitioned across multiple tables (perhaps with the same schema) backed up to S3 and with calculations run in EC2. You could also create a custom data structure for this if you are into low level pain. What is your application?