Check out AWS DynamoDB
Its a NoSql database service by Amazon. It has really generous free tier limits and good performance too.
25 GB of storage(approx)
25 Writes/Read per second capacity.
If you are storing posts from Vercel, you can allocate the full read/write capacity to just one table, or you can distribute that capacity across multiple tables. Note:
You would have to use aws-sdk to connect to DynamoDB directly without using API Gateway for zero charges.
Also storing data in table incurs zero data transfer charge, but pulling out data from table to does. The free tier limit for data transfer(out) is
I don't know about you but writing 25 entries to a table in one second is pretty good for me. I can store 25 articles in 1 second without paying a cent.
Writing is going to be pretty asymmetric, and 25 should be fine, except perhaps for the initial load. Reading though is going to be more problematic. One place I worked the initial page load was ~100 database reads.
You are right. Almost all databases are read heavy, rather than write heavy.
For a real database load that's exposed to public reads, you need to handle the scaling, or in other words, pay up.
Self-taught designer, developer, and musician. JS, CSS, React, Next, Vue, Node, and much more. Studying computer information systems at Mississippi College.
Check out AWS DynamoDB
Its a NoSql database service by Amazon. It has really generous free tier limits and good performance too.
If you are storing posts from Vercel, you can allocate the full read/write capacity to just one table, or you can distribute that capacity across multiple tables.
Note:
You would have to use aws-sdk to connect to DynamoDB directly without using API Gateway for zero charges.
Also storing data in table incurs zero data transfer charge, but pulling out data from table to does. The free tier limit for data transfer(out) is
25 ops/s? You could get that hosting something at home on an old box. An app could hit that with a single page load on one client.
I know. But, you've got 25 GB of storage.
It doesn't matter how much it is if you can't access the way you need to.
I don't know about you but writing 25 entries to a table in one second is pretty good for me. I can store 25 articles in 1 second without paying a cent.
Writing is going to be pretty asymmetric, and 25 should be fine, except perhaps for the initial load. Reading though is going to be more problematic. One place I worked the initial page load was ~100 database reads.
You are right. Almost all databases are read heavy, rather than write heavy.
For a real database load that's exposed to public reads, you need to handle the scaling, or in other words, pay up.
I've actually looked at hosting the server on my own machine, but I've decided not to open up my home network to potential invasion. 😃