Комментарии:
and on the AppSync topic, I do not think it's that bad, as long as you use Lambda Authorizers and Lambda Resolvers in order to outsource your authentication away from Cognito and avoid using VTL mapping templates.. AppSync has built in integration with ElastiCache which seems insane, I think it automatically handles DynamoDB Streams updates and cache invalidation
Ответитьhey Ben, what do you think about Elastic Beanstalk? It looks like a great solution for hosting monolithic apps without having to worry about containers, it has load balancing and monitoring baked in and it is super easy to deploy on a platform of your choosing
ОтветитьClouds are stealing data now a days also charging too much. Very difficult to learn and understand
ОтветитьCan you do an update on if you like AWS app sync in 2021?
ОтветитьSo far my experience is that it's great for the backend but the npm package aws-appsync is so outdated that is a pain to use on the FE.
ОтветитьFor me, I only use appsync as the api graphql schema definition conversion, so that i could standardize how the frontend dev call the api, instead of using rest. Then for the core stuff, it better to keep as microservices in container,.
Trick to use aws is, just use that you think make your life easier, if not, then just left it.
😅
I like Serverless Architecture, but I don't like AppSync because it lacks the flexibility that I am looking for. Although I use AppSync at work because it's required, personally, I would recommend FaunaDB. I'm using it for my personal projects, it's really really really awesome.
ОтветитьAppsync and amplify are literally the reason our PRODUCTION READY webiste can't launch since 3 weeks ago. It is REALLY frustrating
ОтветитьHe miss the timeout of 30 seconds which may hurt of some process take more than 30 seconds like download and could be an issue. But we also should realise graphql is not made for those kind of processes ideally.
ОтветитьYou can configure your AWS stack in code using CloudFormation
ОтветитьWell main bottleneck is Amplify cli not appsync. So you build infra with AWS CDK instead of amplify cli. Then its not only easy but also massively flexible.
ОтветитьI love this video.
Speaking from a production ready platform, its just a pain in the ass to use. I am still stuck with appsync, but will be moving my api to apollo.
Serverless still out in 2019?!!
It’s about to become old school 😀
Yeah amazon console is a mess, i'm with you, i prefer to configure my own kubernetes ecosystem with docker, make my yaml files is always fun to me. Scale a project is so fun when you make yourself... And get the ssl too, and why pay for aws hidden prices when kubernetes is so cheap? Severless guys are so stupid hahahahaha....
ОтветитьI think you're missing the whole point of using a cloud provider, managed services, and serverless - it does most of the mechanical devops work for you, as well as most of the mechanical, cookie-cutter, boiler plate backend development...
ОтветитьSeptember 2020. do you still feel the same way about serverless Ben?
ОтветитьWhen talking about serverless, do you mean the framework, AWS Lambda or just a concept in general?
ОтветитьGiven I don't want to get stuck at 80% of the project with Amplify and I don't have the expertise to model data without Amplify I'll stick with Firebase for now.
Ответить