DEV Community

How I built a Simple Sprint Dashboard with AWS Amplify

Pubudu Jayawardana on March 04, 2021

This article first appeared in Hashnode Intro This is how I built a simple sprint dashboard using VueJS and used Amplify for backend, f...

Read full post

Mel♾️☁️ • Aug 28 '23

Wooow .... this is soooo awesome!!! I sooo appreciate this @pubudusj absolutely great job.

This is an issue sometimes with some dev myself included .... the knowledge is there but we don't sit down and create something.

You have done that and kudos for an amazing work.

I really need to giddy up and create too. There is nothing cooler than creating stuff.

Pubudu Jayawardana • Aug 29 '23

Thanks for your kind words @softwaresennin
Totally agree that nothing cooler than creating stuff (and share it with the community)

enix79 • Mar 6 '21

Who is saying putting everything in one table is best practice? There are several reasons amplify creates a separate table for every @model object type:

You can query the objects of tables by the primary key. Keep in mind that the maximum amount of GSIs is 30 (and they are not free). In a complex model it might not be enough.
You can assign an object to other tables/objects, i.e. assign same address id to user (user private address) and company (company business address). Reusing same object keeps your data redundancy free and avoids duplicates, i.e. "My street 1"and "My stret 1".
You can set the authorization on your data more granular and convenient with @auth directive, which you didn't use in your project so far.

Alex Chan • Mar 10 '21

Many of the resources from github.com/alexdebrie/awesome-dyna... recommend single table design. Rick Houlihan in particular has some pretty convincing talks on why and how to achieve this.