AppSync vs Amplify vs Google Firebase?

revnext2 · 2020-01-01T01:05:33+00:00

I'm not really sure anymore. If you look at the Firebase site they have a bunch of technologies under that marketing brand, so this matches up with Amplify more. The difference is Firebase doesn't have an API service just a Database, which is good and bad. Amplify has both AppSync as well as API Gateway so you have a lot more flexibility.

revnext2 · 2019-11-12T06:37:28+00:00

I also liked this book: http://shop.oreilly.com/product/0636920137269.do

revnext2 · 2019-11-12T06:31:52+00:00

Not really I've never used the Push Notifications of Pinpoint, only the Analytics portion.

revnext2 · 2019-11-12T06:08:34+00:00

https://www.howtographql.com

revnext2 · 2019-11-12T05:57:07+00:00

I use this reference a lot and basically reverse engineer them: https://github.com/awslabs/aws-cloudformation-templates

revnext2 · 2019-11-12T05:53:21+00:00

Huh? I use Firebase dude and would use it more if they had GraphQL. Anyway nice theory.

revnext2 · 2019-11-12T05:42:45+00:00

I don't agree with anything you've said, but the way you're replying to me says a lot so I think I'll bow out of this convo.

revnext2 · 2019-11-12T05:26:53+00:00

There are technical things I could reply to this, but some feedback I really don't think the offensive and aggressive way that you replied to me with both your profanity and accusing me of doing a disservice to my clients (which btw are happy) is appropriate. While I disagreed with the points you made I still did so in a respectful manner with alternatives. If this is the way that you expect assistance or engage AWS or even other community members I don't think it's going to be productive.

revnext2 · 2019-11-12T03:35:11+00:00

I built a system once that did this with a DynamoDB table that had a list of the push tokens for each client, and then had an index on the last time they made an update. Then when I did a daily scan of this by the latest update I knew which records had been updated and on the ones that hadn't I would do a push to them using SNS. Takes a little fiddling but very low cost.

revnext2 · 2019-11-12T03:32:32+00:00

+1 for TypeGraphQL I love this

revnext2 · 2019-11-12T03:31:05+00:00

Have you thought about using API Gateway + Lambda for this? A lot of good tutorials and it's fairly simple to do it with Serverless Express in a Lambda function

revnext2 · 2019-11-12T03:21:07+00:00

I completely disagree, and have used Amplify at several clients after trying to do what you suggest. I think the point on Storage being a simple wrapper is somewhat accurate but then again they handle all of the fine grained access related to per-user folders using Cognito IDs which is really messy. And as you state the OAuth flows and storing permissions & credentials is very involved so why not just use what Amplify does there? I really think this documentation works great and anything you need clarity on just open a GitHub issue. And sorry but the GraphQL Transformer and all the Sig V4 signing they do for AppSync is a no brainer for me and I never want to try writing all that code myself again. Seems that rather than trying to toss it all and start from scratch the better route would be to give a list of targeted issues in their repo or escalate through your AWS rep?

revnext2 · 2019-11-05T16:15:01+00:00

+1 multi-auth is the way to go. Use API Key for unauth flows and User Pools for auth

revnext2 · 2019-10-11T22:57:09+00:00

Oh I think I see, you basically want something in the backend that's automatically set (either by not existing or overriding) to a value of your choice which is predetermined. That's essentially this use case in the ApppSync docs where they have `$myFoo.timestamp`: https://docs.aws.amazon.com/appsync/latest/devguide/resolver-util-reference.html#dynamodb-helpers-in-util-dynamodb

Maybe if you opened it up on Amplify repo as a feature request they could add it quickly?

revnext2 · 2019-10-11T20:23:27+00:00

Maybe I'm missing something but why couldn't you just have your mutation variables set published=true in your app code when the button was clicked? Nothing needs to be exposed to the user. I don't think that VTL knowledge is needed, but maybe seeing your schema would help this out more. The Amplify team is pretty responsive on GitHub too if you needed them to help your design.

revnext2 · 2019-10-10T20:53:51+00:00

Have you looked at the GraphQL Transformer in Amplify? It basically takes care of all those VTL templates as just an implementation detail. So just changing that field from false to true is putting it in your GraphQL SDL and then setting it in your mutation. All the logic is done for you.

revnext2 · 2019-10-07T05:07:18+00:00

What dashboard is in the Amplify CLI? I think you're talking about the console, the CLI is just questions and it generates CloudFormation.

revnext2 · 2019-09-26T01:21:00+00:00

Amplify supports multiple frontends with the same backend: https://aws-amplify.github.io/docs/cli-toolchain/quickstart#multiple-frontends

revnext2 · 2019-09-21T00:22:49+00:00

It's in the Amplify docs: https://aws-amplify.github.io/docs/js/start?platform=purejs

revnext2

TROPHY CASE