内容驱动型 Web 应用的后端
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
为 Web 应用选择后端时,最重要的考虑因素是您在运行后端时需要多少控制权限,判断依据是您的需求的异常情况以及预期的流量。如果您要执行相对常见的操作,通常最好将常用语言和框架与代管式服务器搭配使用。
如果您预期需要处理大量流量,选择代管式服务可以让您在管理您自己的基础架构时节省工程工作。
请考虑常见 Web 应用架构、语言和框架选择的权衡,并设置可靠的测试和构建流水线。
Web 后端的关键注意事项
您在选择内容驱动型 Web 应用时,需要考虑多种因素。
注意事项 |
团队的专长 |
您的开发团队独特的技能组合、人才和知识会影响最符合您的需求的框架和语言类型。您的团队应该了解所选语言的复杂性。
|
框架和语言 |
后端框架和语言选项提供了创建成功的 Web 应用的组件和结构。选择最支持您选择的语言和架构模式的框架。
|
测试 |
测试是开发流程和任何持续监控的关键环节,旨在确保应用的运行状况良好。 |
扩缩和性能 |
扩缩和渐进式性能至关重要;请务必考虑您的应用将来如何发展和开发。横向和纵向扩缩可能需要额外的资源,并影响后端的运行费用,包括内容驱动的 Web 应用后端所面临的独特挑战。如果要扩展现有 Web 应用,请考虑当前基础架构的潜在限制以及您在扩展过程中的需求。 |
Deployment |
为后端实现有效的构建流水线,以覆盖应用的整个构建、测试、部署和生命周期。 |
安全性 |
请考虑选择最符合您的应用要求的安全解决方案,以确保客户隐私数据的机密性和完整性。 |
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2024-07-10。
[null,null,["最后更新时间 (UTC):2024-07-10。"],[[["\u003cp\u003eWhen choosing a backend for your web app, prioritize the level of control you need based on the complexity and traffic expectations of your application.\u003c/p\u003e\n"],["\u003cp\u003eConsider using a managed service for high-traffic applications to reduce infrastructure management efforts and improve scalability.\u003c/p\u003e\n"],["\u003cp\u003eEvaluate tradeoffs between different web app architectures, languages, frameworks, and testing processes to optimize performance.\u003c/p\u003e\n"],["\u003cp\u003eTake into account your team's expertise, the need for testing and scaling, deployment strategies, and security requirements when choosing your web app's backend.\u003c/p\u003e\n"]]],["Choosing a backend for a web app depends on the level of control needed, the uniqueness of requirements, and expected traffic. For common needs, popular languages and frameworks with managed servers are recommended. Heavy traffic warrants managed services to reduce infrastructure management effort. Key considerations include the team's expertise, framework and language choices, thorough testing, scaling and performance needs, deployment pipeline setup, and security measures. Each factor should align with the application's current and future demands.\n"],null,["# Backend for a content-driven web applications\n\nThe most important consideration for choosing a backend for a web app is how\nmuch control you need in operating the backend, informed by how unusual your\nneeds are and how much traffic you expect. If you're doing something relatively\ncommon, you're generally best served by using a popular language and framework\nwith a managed server.\n\nIf you expect to have to serve heavy traffic, opting for a managed service lets\nyou save engineering effort in managing your own infrastructure.\n\nConsider the tradeoffs of common web app architectures, language and framework\nchoices, and setting up a reliable testing and build pipeline.\n\nKey Considerations for web backends\n-----------------------------------\n\nMultiple factors impact your architecture choice for a content-driven web\napplication.\n\n| Considerations ||\n|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Team's expertise | Your development team's unique skill set, talent, and knowledge influence the types of frameworks and languages that best meet your needs. Your team should know the intricacies of your chosen language. |\n| Frameworks and languages | Backend framework and language options provide the components and structure for creating successful web applications. Select a framework that best supports the language and architectural pattern of your choice. |\n| Testing | Testing is a critical part of the development process and any on-going monitoring to ensure the health of your application. |\n| Scaling and performance | Scaling and progressive performance are critical; be sure to consider how your application will grow and develop in the future. Scaling horizontally and vertically may require additional resources and impact the cost of running your backend, including unique challenges for content-driven web application backends. If expanding an existing web application, consider the potential constraints of the current infrastructure and your needs as you expand. |\n| Deployment | Implement an effective build pipeline for your backend to cover the entire build, test, deploy, and promote the lifecycle of your application. |\n| Security | Consider a security solution that best meets your application's requirements to ensure the confidentiality and integrity of private customer data. |"]]