DynamoDB Module for Corona

Solar2D General Questions/Discussion
#1

Howdy,

If anyone is interested, I’ve put together a AWS DynamoDB module (V1). The DynamoDB module provides access to the low-level AWS DynamoDB API.

In the spirit of open-source, I’ve opted to release it as a module as opposed to a plugin, so that others can contribute to its refinement.

You can find the documentation, with install instructions, etc. here https://develephant.github.io/dynamodb-coronasdk/

I’m happy to answer questions regarding the module specifically, but I can’t give advice on using DynamoDB directly (though I’m available for consulting).

Enjoy!

-dev

#2

Hi there!

This is something i might use for my current project, once I’ve read up on it.

Thanks for sharing mate!

Anaqim

#3

hi, anaqim.

thanks for sharing your knowledge.

1 question.

never used noSQL databases, is there any advantage learning/using them if I already know SQL databases? creating complex databases on sql doesn’t scare me and returning data from them with “complex” queries also. just wanted to know if i’m missing something not going for noSQL route. 

regards,

Carlos.

#4

Hi Carlos,

Thats the part i need to read up on but unless i am mistaken, noSQL is more powerful than simple json tables but probably not on the level of SQLite3. Perhaps someone else know more about this.

The convenience is easy online access.

In Radiance we are using App42 (http://api.shephertz.com/) for storing the online presets.

It works well and if i dont recall wrong, its also noSQL.

App42 will btw give you much for free and have full documentaion with code examples, also in Lua.

Cheers!

#5

I use a mix of json storage and normal RI in MySQL and it is best of both worlds.  The only limitation is changing the json inline is a heavy string operation and should be avoided. But if you are only storing game state then SQL v noSQL makes no real difference.

NoSQL DBs were created for things like document storage and retrieval and they are better at that stuff then a pure SQL DB.

I just looked at http://api.shephertz.com/pricing.php and $300pcm gives a bandwidth of 50GB a month.  My DB is processing 30GB per hour so they would be prohibitively expensive.

#6

Thanks for your input sphere.

Since we upload out presets with image data, it works well on app24 for us.

30 GB per hour is a lot of data, may I ask where you get that hosted at a reasonable price?

#7

I pay $100 pa for a business account from http://one.com which comes with

  • 500 GB storage
  • 4 GB RAM
  • Multiple databases
  • Multiple domains**
  • SSL
  • SSH
  • 8 x CPU
  • Backup & Restore

There are a few limitations for really high bandwidth (like no more than 50 POSTs every 10 seconds) that I’ve had to work around.

But I highly recommend if you can write your own PHP and design MySQL databases

#8

Yeah I know one.com, they are good.

Writing own PHP though would be something brand new to me, so trying not to go there until i must

#9

Hi Develephant,

I’ve been checking out DynamoDB but dont seem to find the answer to the following question.

The free tier is limited to 25x4KB read per sec and 25x1KB write per sec.

What happens if my app requests/read more than that but only as a burst?

Will it be auto limited, or will I be billed extra for it?

Thanks for sharing your expertize on the subject :slight_smile:

Anaqim

#10

Hi there!

This is something i might use for my current project, once I’ve read up on it.

Thanks for sharing mate!

Anaqim

#11

hi, anaqim.

thanks for sharing your knowledge.

1 question.

never used noSQL databases, is there any advantage learning/using them if I already know SQL databases? creating complex databases on sql doesn’t scare me and returning data from them with “complex” queries also. just wanted to know if i’m missing something not going for noSQL route. 

regards,

Carlos.

#12

Hi Carlos,

Thats the part i need to read up on but unless i am mistaken, noSQL is more powerful than simple json tables but probably not on the level of SQLite3. Perhaps someone else know more about this.

The convenience is easy online access.

In Radiance we are using App42 (http://api.shephertz.com/) for storing the online presets.

It works well and if i dont recall wrong, its also noSQL.

App42 will btw give you much for free and have full documentaion with code examples, also in Lua.

Cheers!

#13

I use a mix of json storage and normal RI in MySQL and it is best of both worlds.  The only limitation is changing the json inline is a heavy string operation and should be avoided. But if you are only storing game state then SQL v noSQL makes no real difference.

NoSQL DBs were created for things like document storage and retrieval and they are better at that stuff then a pure SQL DB.

I just looked at http://api.shephertz.com/pricing.php and $300pcm gives a bandwidth of 50GB a month.  My DB is processing 30GB per hour so they would be prohibitively expensive.

#14

Thanks for your input sphere.

Since we upload out presets with image data, it works well on app24 for us.

30 GB per hour is a lot of data, may I ask where you get that hosted at a reasonable price?

#15

I pay $100 pa for a business account from http://one.com which comes with

  • 500 GB storage
  • 4 GB RAM
  • Multiple databases
  • Multiple domains**
  • SSL
  • SSH
  • 8 x CPU
  • Backup & Restore

There are a few limitations for really high bandwidth (like no more than 50 POSTs every 10 seconds) that I’ve had to work around.

But I highly recommend if you can write your own PHP and design MySQL databases

#16

Yeah I know one.com, they are good.

Writing own PHP though would be something brand new to me, so trying not to go there until i must

#17

Hi Develephant,

I’ve been checking out DynamoDB but dont seem to find the answer to the following question.

The free tier is limited to 25x4KB read per sec and 25x1KB write per sec.

What happens if my app requests/read more than that but only as a burst?

Will it be auto limited, or will I be billed extra for it?

Thanks for sharing your expertize on the subject :slight_smile:

Anaqim