小程序服務(wù)器域名5次

by Howard Lo

霍華德·羅

為什么您不應(yīng)該在100美元的服務(wù)器上用5天的時(shí)間構(gòu)建面向500,000個(gè)用戶的應(yīng)用程序 (Why you shouldn’t build an app aimed at 500,000 users in 5 days on a $100 server)

A few days ago, I read Erik Duindam’s “How I built an app with 500,000 users in 5 days on a $100 server” article. Basically, he spent an extra 2–3 hours (totaling 24) to make his app (GoSnap) scalable by using a CDN and some optimized databases. He gives another app (GoChat) a hard time for building an app that had technical issues at launch.

幾天前，我讀了Erik Duindam的“我如何在100美元的服務(wù)器上用5天的時(shí)間構(gòu)建500,000個(gè)用戶的應(yīng)用程序”一文。 基本上，他通過(guò)使用CDN和一些優(yōu)化的數(shù)據(jù)庫(kù)花費(fèi)了額外的2-3個(gè)小時(shí)(總共24個(gè)小時(shí))使其應(yīng)用程序(GoSnap)可擴(kuò)展。 他使另一個(gè)應(yīng)用程序(GoChat)難以構(gòu)建在發(fā)布時(shí)遇到技術(shù)問(wèn)題的應(yīng)用程序。

Those reading his article should take a few things into consideration:

那些閱讀他的文章的人應(yīng)該考慮以下幾點(diǎn)：

他是一位優(yōu)秀的開(kāi)發(fā)商。 (He is a good developer.)

Much better than me.

比我好多了。

I doubt I could push whatever he did out in 24 hours. He’s quick, and knows what he’s doing.

我懷疑我能在24小時(shí)內(nèi)將他所做的一切都推開(kāi)。 他很快，并且知道自己在做什么。

To him, 2–3 hours isn’t a big deal. You can shave that off your sleeping schedule and feel crappy for a day. But what if you’re not a strong developer? 24 hours turns into a week, and 2–3 hours can be nearly a full day.

對(duì)他來(lái)說(shuō)，2到3個(gè)小時(shí)沒(méi)什么大不了的。 您可以將其從睡眠時(shí)間安排中剔除，并一天變得cr腳。 但是，如果您不是一個(gè)強(qiáng)大的開(kāi)發(fā)人員，該怎么辦？ 24小時(shí)變成一周，而2–3小時(shí)可能幾乎是整天。

If you’re racing to push something out because you’re worried someone else might have the same idea (more common than you think), a full day can make or break you.

如果您因?yàn)閾?dān)心其他人可能有相同的想法(比您想像的更普遍)而競(jìng)相推出某些東西，那么整整一天都會(huì)使您成敗。

Gauge this for yourself, but I’d rather be first with a 90% solution than second with 100% solution.

自己衡量一下，但我寧愿以90％的解決方案排在第一位，而不是以100％的解決方案排在第二位。

％失敗>％成功 (%Failure > %Success)

Apps you build are far more likely to fail than they are to succeed.

您構(gòu)建的應(yīng)用失敗的可能性遠(yuǎn)大于成功的可能性。

Erik speaks from a winner’s point of view. Winners speak a lot louder than losers, whose stories about their failures probably aren’t as impactful (or exciting) as Erik’s is.

埃里克(Erik)從贏家的角度講。 勝利者的聲音要比失敗者的聲音大得多，失敗者的失敗故事可能不及埃里克的影響力(或令人振奮)。

If you do a quick search for Pokemon Go related apps, there are dozens of failed apps for every successful one.

如果您快速搜索與Pokemon Go相關(guān)的應(yīng)用程序，那么每一個(gè)成功的應(yīng)用程序都會(huì)有數(shù)十個(gè)失敗的應(yīng)用程序。

Barring massive partnerships (Google and Nintendo, in the case of Pokemon Go) the app store is essentially one giant numbers game. Yes, you can spend 10% more time to make your app scalable. But assuming your chance of failure is so high, in most cases that extra 10% of time is going to waste. If you spend 10% more time to make all your Minimum Viable Products (MVPs) scalable, but fail 9x, that’s one fewer MVP you could have built.

除非建立大規(guī)模的合作伙伴關(guān)系(例如Google和Nintendo，在《 Pokemon Go》中為Pokemon Go)，否則該應(yīng)用程序商店實(shí)質(zhì)上就是一個(gè)大型數(shù)字游戲。 是的，您可以花費(fèi)10％以上的時(shí)間來(lái)使您的應(yīng)用程序可擴(kuò)展。 但是，假設(shè)您失敗的可能性很高，那么在大多數(shù)情況下，將會(huì)浪費(fèi)10％的時(shí)間。 如果您將所有最低限度產(chǎn)品(MVP)的可擴(kuò)展時(shí)間花費(fèi)了10％以上，但失敗了9倍，那么您可以構(gòu)建的MVP就會(huì)減少一倍。

And are you really going to stop at 10%? Do you have so much self control and a birds eye view of what you’re doing?

而且您真的要停在10％的位置嗎？ 您是否擁有如此多的自我控制能力，并且對(duì)正在做的事情有鳥(niǎo)瞰圖？

For me, that 10% can become 20% really quick because “well, I put in a CDN on my app, why not put in caching, it’ll only take another 10%.”

對(duì)我來(lái)說(shuō)，這10％真的可以很快變成20％，因?yàn)椤昂冒?#xff0c;我在應(yīng)用程序中放入了CDN，為什么不進(jìn)行緩存，只需要再花10％。”

Go minimum or go all out. Drawing the line anywhere else isn’t optimal.

盡量減少或全力以赴。 在其他任何地方畫(huà)線都不是最佳選擇。

失敗還算不錯(cuò)。 (Failing isn’t so bad.)

Erik himself updated his article a few days after:

幾天后，埃里克本人更新了他的文章：

The Google Play page says [GoChat] “back 100%” with “over 2 million users”.Google Play頁(yè)面說(shuō)[GoChat]“支持100％”，擁有“超過(guò)200萬(wàn)用戶”。

GoChat launched an MVP, didn’t know they would get so much traction, and their crappy MVP code buckled under load. GoChat failed.

GoChat推出了MVP，但不知道他們會(huì)獲得如此大的吸引力，他們cr腳的MVP代碼在負(fù)載下也屈服了。 GoChat失敗。

Or did it?

還是呢？

Because even though GoChat went down, it’s still getting more users than Erik’s GoSnap, which is built to scale. They are different products, sure, but could the extra 10% of time Erik put into GoSnap been better used to hit the app market 2–3 hours sooner? Could Erik be sitting on more users with the 2–3 hours head start and a technical crash after?

因?yàn)榧词笹oChat出現(xiàn)故障，它仍然比Erik的可擴(kuò)展規(guī)模的GoSnap吸引更多的用戶。 當(dāng)然，它們是不同的產(chǎn)品，但是是否可以將Erik在GoSnap中投入的額外10％的時(shí)間更早地將其用于應(yīng)用市場(chǎng)2–3個(gè)小時(shí)？ Erik會(huì)在2到3個(gè)小時(shí)的啟動(dòng)時(shí)間之后又出現(xiàn)技術(shù)崩潰，從而吸引更多的用戶嗎？

Hard to say what the results could’ve been, but it’s interesting to think about.

很難說(shuō)出結(jié)果是什么，但是考慮一下很有趣。

Even though GoChat’s code failed them, they still bounced back. They optimized in the second step, and still captured over 2 million users. The failure of non-scalable MVPs doesn’t seem to have hurt them all that much in the end.

即使GoChat的代碼使它們失敗，它們?nèi)匀粫?huì)反彈。 他們?cè)诘诙竭M(jìn)行了優(yōu)化，至今仍吸引了超過(guò)200萬(wàn)用戶。 最終，不可擴(kuò)展的MVP的失敗似乎并沒(méi)有對(duì)他們?cè)斐商蟮膫Α?

Could GoChat have gotten more users by this point if they didn’t crash? Possibly. But they sure as hell didn’t miss the gravy train as Erik suggests, so what do you have to worry about?

如果他們沒(méi)有崩潰，那么GoChat能否在這一點(diǎn)上吸引更多用戶？ 可能吧 但是他們確信地獄不會(huì)像埃里克(Erik)所說(shuō)的那樣錯(cuò)過(guò)肉汁火車(chē)，那么您有什么需要擔(dān)心的呢？

It’s better to go ahead and launch than to miss the train entirely because you were too busy scaling.

最好不要完全錯(cuò)過(guò)火車(chē)，因?yàn)槟τ跀U(kuò)展了。

The thing about “scale” is that at the upper end there are so many users to go around, you can afford to run into problems initially and still capture a good market share post-fix.

關(guān)于“規(guī)?！钡氖虑槭?#xff0c;高端用戶太多了，您可以負(fù)擔(dān)得起最初的問(wèn)題，但在修復(fù)后仍然可以保持良好的市場(chǎng)份額。

At the lower end of “scale” there is nothing. You have nothing on your side but speed of execution. You have to get there fast. Just ask the dozens of other apps that aren’t being downloaded.

在“規(guī)?！钡牡投?#xff0c;什么都沒(méi)有。 除了執(zhí)行速度，您什么都沒(méi)有。 您必須快速到達(dá)那里。 只需詢問(wèn)其他數(shù)十個(gè)尚未下載的應(yīng)用即可。

Self promotion section!I made rabbut.com, a tool that lets you collect emails here on Medium (and other places). Oh look, here is one now:

自我推廣科！ 我制作了rabbut.com ，該工具可讓您在Medium(和其他地方)的此處收集電子郵件。 哦，看，現(xiàn)在是一個(gè)：

Looking for my older stories? I’ve got some. Here.Looking for older stories is a PITA on Medium. Click here for a shortcut.powered.by.rabbut.com

尋找我的老故事？ 我有一些 這里。 尋找較舊的故事是中級(jí)的PITA。 單擊此處獲取快捷方式。 powered.by.rabbut.com

Also, I’m giving away my free eBook on starting up a startup. Especially good for people who don’t know how to startup a startup:

另外，我還將贈(zèng)送免費(fèi)的電子書(shū)，以幫助您啟動(dòng)創(chuàng)業(yè)公司。 對(duì)于不知道如何啟動(dòng)創(chuàng)業(yè)公司的人尤其有用：

First 10 people to subscribe get my free eBook.How to startup your startup as a nobody.powered.by.rabbut.com

前10位訂閱者可獲得我的免費(fèi)電子書(shū)。 如何以無(wú)人啟動(dòng)您的啟動(dòng)。 powered.by.rabbut.com

Man, these rabbut things are like everywhere now. I wonder where you could get one…

伙計(jì)，這些拉布特的事現(xiàn)在到處都是。 我不知道你能在哪里買(mǎi)到……

翻譯自: https://www.freecodecamp.org/news/why-you-shouldnt-build-an-app-aimed-at-500-000-users-in-5-days-on-a-100-server-79c57304b445/

小程序服務(wù)器域名5次

總結(jié)

以上是生活随笔為你收集整理的小程序服务器域名5次_为什么您不应该在100美元的服务器上用5天的时间构建面向500,000个用户的应用程序...的全部?jī)?nèi)容，希望文章能夠幫你解決所遇到的問(wèn)題。

如果覺(jué)得生活随笔網(wǎng)站內(nèi)容還不錯(cuò)，歡迎將生活随笔推薦給好友。