Comprehensive Guide to Building a Backend Technology Stack for Startups
This article outlines a complete backend technology stack for startups, covering language choices, core components, processes, systemization, and detailed selections for project management, DNS, load balancing, CDN, RPC frameworks, service discovery, databases, messaging, logging, monitoring, configuration, deployment, and operational best practices.
The article defines the backend as everything running on servers—including frameworks, languages, databases, services, and operating systems—and structures it into four layers: language, components, processes, and systemization.
It then provides a step‑by‑step selection guide for each essential subsystem:
Project/Bug Management: Redmine, Phabricator, Jira, and Wukong CRM are discussed with their strengths and limitations.
DNS: Alibaba Wanwang and Tencent DNSPod are compared, with recommendations for domestic and overseas deployments.
Load Balancing (LB): Cloud provider LB services (Alibaba SLB, Tencent CLB, AWS ELB) and self‑hosted LVS + Nginx are described.
CDN: Major providers such as NetEase, Tencent, Alibaba, Amazon, and Akamai are evaluated, emphasizing multi‑CDN strategies for resilience.
RPC Frameworks: Cross‑language options (Thrift, gRPC, Hessian, Hprose) and service‑governance solutions (Dubbo, DubboX, Motan, rpcx) are compared.
Service Discovery: etcd, Consul, and ZooKeeper are presented as the primary registries.
Databases: Traditional relational databases (MySQL, MariaDB, PostgreSQL) and NewSQL solutions (CockroachDB, TiDB) are contrasted with NoSQL types (key‑value, columnar, document, graph).
Message Middleware: The role of messaging in async processing, system decoupling, and traffic shaping is explained, with a visual comparison of popular tools.
Logging System: The ELK stack (Elasticsearch, Logstash, Kibana, Filebeat) is recommended, including security hardening via Nginx.
Monitoring: Prometheus architecture, components, and integration with Grafana are detailed as a suitable solution for startups.
Configuration Management: zk/etcd‑based and automation‑driven approaches are outlined.
Release/Deployment: Artifact creation, deployment pipelines, and rollback strategies are described, mentioning tools like Jenkins, GitLab CI, Walle, and Piplin.
Jump Server & Machine Management: Jumpserver and Ansible (versus Puppet/Chef/SaltStack) are suggested for secure access and large‑scale host control.
Finally, the article stresses the importance of choosing appropriate languages, mature open‑source components, clear processes, and continuous evaluation of the stack as the organization grows.
IT Architects Alliance
Discussion and exchange on system, internet, large‑scale distributed, high‑availability, and high‑performance architectures, as well as big data, machine learning, AI, and architecture adjustments with internet technologies. Includes real‑world large‑scale architecture case studies. Open to architects who have ideas and enjoy sharing.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.