Backend for a content-driven web applications
Stay organized with collections
Save and categorize content based on your preferences.
The most important consideration for choosing a backend for a web app is how
much control you need in operating the backend, informed by how unusual your
needs are and how much traffic you expect. If you're doing something relatively
common, you're generally best served by using a popular language and framework
with a managed server.
If you expect to have to serve heavy traffic, opting for a managed service lets
you save engineering effort in managing your own infrastructure.
Consider the tradeoffs of common web app architectures, language and framework
choices, and setting up a reliable testing and build pipeline.
Key Considerations for web backends
Multiple factors impact your architecture choice for a content-driven web
application.
| Considerations |
| 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.
|
| 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.
|
| Testing |
Testing is a critical part of the development process and any on-going monitoring to ensure
the health of your application.
|
| 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.
|
| Deployment |
Implement an effective build pipeline for your backend to cover the entire build, test,
deploy, and promote the lifecycle of your application.
|
| Security |
Consider a security solution that best meets your application's requirements to ensure the
confidentiality and integrity of private customer data.
|
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-07-10 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-07-10 UTC."],[[["\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,["The 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\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. |"]]
