facebook、twitter、groupon、foursquare...刚成立时使用什么？
我想知道哪个 - 编程语言 - 平台 - 数据库类型 - 主机提供商/服务器类型和配置 - 一些大公司（Fb、twitter、groupon、foursquare...）在成立时使用的是什么？
例如：Core2Duo 4GB RAM、2TB HDD 上的 Linux、Apache、Mysql、Php (LAMP)； Google AppEngine 上的 Python...
这会让我知道为我的初创公司选择哪一个：D
I wonder which
- programming language
- platform
- db type
- host provider/ server type and configuration
-
that some big companies (Fb, twitter, groupon, foursquare...) used when they were started?
ex: Linux, Apache, Mysql, Php (LAMP) on Core2Duo 4GB ram, 2TB HDD; Python on Google AppEngine...
This would give me some idea on which one to choose for my startup :D
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
嗯，你可以用谷歌搜索这些信息，但每个公司都使用其他的东西。
对于 foursquare，它的 MongoDB (NoSQL) 以及 php，可能还有 MySQL，今天他们使用 Hadoop 和 Hive。
对于 twitter，您可以阅读此处（Rails、MySQL）
对于 FB，首先使用 LAMP，如今，其庞大的 PHP/MySQL、Cassandra、Hadoop 和 Hive 以及可能还有更多，他们对自己的工程非常开放（他们为自己所做的事情感到自豪）
但是，如果您要求此为您的初创企业选择这个问题是错误的。
您应该规划前端和后端之间的数据和交互，并决定哪种解决方案最适合您。
您还需要注意到，如今有许多云服务 - 从其中一个开始是最有意义的，您为您使用的内容付费（几乎不需要付费）并根据需要进行扩展（这将是昂贵，但如果你有很多用户，那应该不是问题..）
你不应该看看一家拥有 1000 万（当然不是 8 亿）用户的公司所做的事情，并尝试为 50 个用户做同样的事情 - 你永远不会达到这样的地步50 个用户将使用您正在尝试构建的内容。
我也会从我知道的东西开始，在我将有优势的地方（例如，如果您从未接触过 .Net，但您非常熟悉 php，则不要选择基于 C# 的后端解决方案 - 没有意义）
Well, you can google that information, but every company used something else.
For foursquare its MongoDB (NoSQL), with php, probably MySQL someplace there as well, and today they use Hadoop with Hive.
For twitter you can read here (Rails, MySQL)
For FB its LAMP to start with, and today its massive PHP/MySQL, Cassandra, Hadoop and Hive and probably many more, they are very open company about their engineering (they are proud at what they have done)
But if you are asking this to choose for your start-up the question is wrong.
You should plan you data and interactions between front-end and back-end, and decide which solution is best for you.
You need to also notice that today there are many cloud services - starting with one of them would make the most sense, you pay for what you use (close to nothing) and scale as required (that would be expensive, but if you get a lot of users that should not be a problem..)
You should not look at what a 10 million (and surly not a 800 million) user company does and try to do the same for 50 users - you will never get to a point where the 50 users will use what you are trying to build..
I would also start with something that I know, someplace where I will have an edge (for example, if you never touched .Net but you are very familiar with php, do not choose a C# based solution for your back-end - makes no sense)
我可以代表 foursquare：
当 Dennis 和 Naveen 构建第一个版本时，它是 PHP + MySQL。 Harry Heymann 加入后，他使用 Scala 重写了所有 PHP 代码/liftweb.net/" rel="nofollow">Lift Web 框架 并将数据库切换到 PostgreSQL。最终，PostgreSQL 不太适合应用程序的需求，因此引入了 MongoDB。数据迁移到 MongoDB，随着时间的推移，PostgreSQL 被逐步淘汰。我相信它不再是生产堆栈的一部分。所有 foursquare 都在 Amazon EC2 上运行。
I can speak for foursquare:
When Dennis and Naveen built the very first version, it was PHP + MySQL. After Harry Heymann joined, he rewrote all the PHP in Scala using the Lift web framework and switched the database over to PostgreSQL. Eventually, PostgreSQL wasn't a good fit for the requirements of the application, so MongoDB was introduced. Data was migrated to MongoDB, and PostgreSQL was phased out over time. I believe it is no longer part of the production stack. All of foursquare runs on Amazon EC2.