I got a lot of little issues I would like to have fixed

🤷‍♂️

lol

wondering if someone could give a short answer to the following. I’ve built an application in the past using react/redux/aws-amplify/amazon-rds, but more recently have built an application with react/apollo/graphql-yoga/prisma. I am in love with the simplicity of yoga/prisma, but too enjoyed the ease of use (once u figure it out) of amplify and the native aws integrations. It seems as though amplify and maybe yoga (might be more prism with the code generation) are similar in what they do. could anyone elaborate on the differences a little more. like I can understand prism / yoga can be deployed on multiple platforms, and aws amplify is specifically aws. maybe this is too open ended if so lmk! thsnk!

I would think the differences would be huge

I don't think redux/apollo are necessarily comparable, amplify is kind of similar to prisma in ways, but almost more comparable to like firebase right

but it can do graphql

but yea amplify is AWS only, I mean thats a huge sticking point right there for what you choose

apollo uses redux internally(I think still does, it used to for sure) so thats why I don't find that very comparable

so afaik amplify now does do gql and has native lambda support, but what I have yet to do is mess with the ‘deploy yoga to lambda’ stuff so I’m only at like a 50% understanding of all of this. was trying to wrap my head around it some more

to be fair it has been a few months since I’ve worked with amplify so I am less knowledgable at the moment.

you can do serverless yoga

but I don't so I dont know much about it

yeah I’ll have to look into that some more then.

I actually ditched yoga

and I just use apollo-server

yoga to me, essentially was just an apollo-server wrapper, and it wasn't keeping up on versions, so I just switched to apollo-server, it didn't take long to do it

idk seems like there was some overlap and I just LOVE all of this new age tech so I’m just trying to make sense of it all before I go into my next application 🙂

cause they were essentially the same

will look into it some more thanks for the info!

sure, I would think the biggest difference is

owning your stack, being able to deploy it where you want

versus, not owning it(amplify)

and then there will be a bunch of nuanced differences from there

gotcha yeah. not that what I am building is enterprise or anything but being (or practice being) cloud agnostic is obviously a plus

prisma is just solving one problem(data layer), amplify is more of a kitchen sink

yeah often hear people b**** about lambda on aws and the vendor lock-in associated with it

yea, especially since lambda isn't cheap

I mean aws isn't cheap

lambda is relatively cheap