简体   繁体   English

Express Amplify Serverless/GraphQL 与 Express 服务器端后端

[英]Express Amplify Serverless/GraphQL vs Express Server-Side backend

What are the pros and cons of using Amplify Express serverless https://docs.amplify.aws/guides/api-rest/express-server/q/platform/js/ or Amplify GraphQL compared to using Express hosted server-side (REST or GraphQL) for mobile app backend?与使用 Express 托管服务器端( REST或 GraphQL)用于移动应用程序后端?

I guess it depends on how you would host your "Express hosted server-side"?我想这取决于您将如何托管“Express 托管服务器端”?

The big advantage of Amplify is that it's serverless, meaning it scales automaticaly. Amplify 的一大优势是它是无服务器的,这意味着它可以自动扩展。 If you were for example to host your Express on EC2, you will have to manage scaling yourself (+ have to manage your Node server, etc)例如,如果你在 EC2 上托管你的 Express,你将不得不自己管理扩展(+ 必须管理你的节点服务器等)

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 Electron Amplify AppSync“在服务器端环境中实时禁用” - Electron Amplify AppSync "Realtime disabled when in a server-side environment" 使用无服务器部署 express 时出现内部服务器错误 - internal server error with when deploying express with serverless 在 firebase 上部署 react 前端和 express/nodejs 后端 - Deploying react frontend & express/nodejs backend on firebase Python 无服务器 webapp 与 WSGI 服务器 - Python serverless webapp vs WSGI server Express 服务器在 EC2 上没有响应 - Express Server not responding on EC2 .htaccess 服务器端路由和节点环境重定向 - .htaccess server-side routing and node environment redirects AWS Lambda + Angular web 应用抛出“错误:找不到模块‘@vendia/serverless-express’” - AWS Lambda + Angular web app throwing "Error: Cannot find module '@vendia/serverless-express'" 在 GCP 中查找已部署的 Google 跟踪代码管理器服务器端版本 - Finding deployed Google Tag Manager server-side version in GCP 仅使用函数修改服务器端对象的元数据 - Modify metadata of object on server-side only using a function 使用服务器端 firestore 客户端时是否可以选择乐观锁定? - Is optimistic locking an option when using a server-side firestore client?
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM