web deployment - What To Consider Before Deploying A Meteor App? -


as heard there many things need considered before deploying meteor app, however, it's still quite vague. please give me opinions issue.

this wrong forum type of question, since it's highly opinionated , not in q&a format, i'll give of personal opinions.

where hosting app?

this has lot app (web-based app, android-only), how many users plan have, if public app or private, how have spend, , many other factors. options include:

  1. host - on vps (virtual private server, digital ocean , others), cloud offering (aws or similar), or bare-metal server have hosted somewhere (like in closet).
  2. pay dedicated hosting - several out there offer many different features, galaxy or modulus, etc.

if host yourself, have maintain hosting solution, i.e need support on own. may mean provisioning/installing os, installing , configuring server apps (mongodb, node.js, web servers, etc), , maintaining on time. benefits, however, potentially cheaper hosting costs (although debated) , custom setups/architectures. if creating app should remain private (i.e. not public app) may want consider option can host internal company , not make public-facing. there tools out there can ease process of setting server, instance mup/mupx.

for dedicated meteor hosting, benefit else installation, configuration, , maintenance of core apps, , have push button move code in. these options can more pricey covering costs of supporting environment, come benefit a) don't have install stuff yourself, b) don't have expert @ "plumbing", c) don't have hire staff of people support infrastructure, d) these hosting services know how optimize things better performance app.

do deploy manually or use tool?

this depends highly on answer #1, hosting decision may come it's own set of tools used deploy (ex. galaxy), or may need shop around best tool you. manual deploys, i'd suggest looking @ mup/mupx, can automate deployment of app, configuring web server, db server, , setting docker images. or, if want have more control, maybe take @ grunt or gulp, more build-scripting solutions (similar ant/maven/gradle java).

do expect fast growth, or slow trickle?

again, has lot plan host. lots of cloud services make easy grow/shrink cluster of servers based on load, takes lot of configuration past installing os. vps , bare-metal solutions hardest expand. dedicated hosting depend on provider.

you need serious need think how might handle fast-growth situation, if don't think app take off. internet riddled apps failed because didn't think successful were. takes 1 mention on reddit, y combinator, or product hunt app sudden , unexpected rush of traffic takes down server(s). if know growth controlled in way, if have private app pre-set number of users, might not need worry it.

do need monitor app?

the answer "yes", extent? need provide 24x7 uptime? outage cost lots of money, make loose biggest client, etc? can users live without service little while if goes down, or loose face , customers? depending on how serious need be, should consider sort of monitoring of infrastructure , app. again, there lots of options here, , decision might swayed quite bit answer first question.

i sure there other questions, these biggest come with.


Comments

Popular posts from this blog

Spring Boot + JPA + Hibernate: Unable to locate persister -

go - Golang: panic: runtime error: invalid memory address or nil pointer dereference using bufio.Scanner -

c - double free or corruption (fasttop) -