Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Meteor hits 1.0

meteor.com

Post reply on HN
Print view View original

91–100 of 250 posts

Re: Meteor hits 1.0

#91

Post by theckel »

bsilvereagle wrote: post #87
theckel wrote: post #65

Earlier quoted context omitted.

We've built a huge meteor app that has scaled to 1000s of concurrent users and still growing -- there have been some sticky points along the way, but overall, we're extremely pleased. Meteor is an amazing engineering feat.

Do you have any posts on how you scaled Meteor?

We will be sharing more soon. We've been developing with Meteor since the winter of 2012 and two main scaling issues have crept up: (1) the web tier was a bottleneck prior to 0.7.0's implementation of oplog tailing; and (2) post oplog tailing, mongo actually became our bottleneck with the write locks. We were able to get to about 3300 concurrent users (in our very data-intensive application) against a single beefy mongo primary before the database started choking, and at that point, we could set our readPreference to the secondary in order to further scale horizontally.

Re: Meteor hits 1.0

#92

Post by gooseus »

dasmithii wrote: post #61
lclarkmichalek wrote: post #56

Earlier quoted context omitted.

So, to put it glibly, the only people who will use Meteor for large-scale projects are those who have no choice?

No, not at all. It's the other way around, really. Those who don't use Meteor for their projects may not be able to without trashing existing codebases.

What I'm hearing is that Meteor doesn't play well with others and that you should make the decision to go with Meteor carefully since changing your mind later will require a ground-up refactor.

This is pretty much my experience as someone who started working on a project where the lead dev had decided to use Meteor and then quit leaving a wonky prototype with "reactive data", poor performance and missing functionality.

Now, some would say "it's not Meteors fault the UI wasn't made well!" and then I'd reply "sure, but if Meteor didn't encourage (and it seems, require) tight coupling of the data access and presentation layers, then maybe we wouldn't have spent the last 3 weeks rebuilding the entire app from the ground up just to add some missing functionality and fix UI bugs".

Honestly, I really can't figure out the lack criticism I see of Meteor around here. All these comments to congratulate on an arbitrary step in version number? I see other articles of accomplishment with a fraction of the positive encouragement and many times the criticisms. Is there a silent majority, or did I spend the last few months being underwhelmed by Meteor because I'm missing something?

Meteor embodies, for me, a tool that makes things 'easy', rather than one that makes things 'simple'.

http://www.infoq.com/presentations/Simple-Made-Easy

Anyways, that's just one developers experience and opinion, take if for whatever you feel it's worth.

Re: Meteor hits 1.0

#93

Post by nojvek »

Congrats Meteor! but I really find it loading a bazillion javascript files a bit of an overkill. Also debugging is a pain in the butt.

Re: Meteor hits 1.0

#94

Post by imslavko »

thathonkey wrote: post #76
imslavko wrote: post #49

Earlier quoted context omitted.

[I work at Meteor and contributed to the MongoDB realtime driver] Scaling low-latency data synchronization is a challenge for scalability for sure! We are gradually building better and better drivers with persistence to MongoDB. The scalability can vary greatly depending on your application's data schema, usage patterns and amount of writes. If you watch the mentioned talk carefully, the speaker describes a collabora…

The "running from a single box" at the end seems like it could be the most important part of the equation. Would you agree? Or rather, would that be the recommended place to start optimizing if your app runs into scaling problems?

Here is a very fine blog posts series on scaling Meteor horizontally, please consider looking at it: https://meteorhacks.com/pro-meteor/

Re: Meteor hits 1.0

#95

Post by mononcqc »

brentjanderson wrote: post #82
dasmithii wrote: post #60

At this point, what percentage of web development can't/shouldn't be done with Meteor? It seems like everything else is obsolete in comparison. The only non-Meteor cases I can think of involve especially large scale.

Even at "especially large scale" there are things that can be done to support unique scale cases, including swapping out database drivers and other components that don't work as well as you might need. Although this may be corrected in 1.0, single page applications in Javascript like this (whether in Angular or other tools) tend to underperform in SEO (Or not perform at all). Meteor has a sort of hack that handles SE…

If you can swap out the drivers to solve the problem, chances are this is not "especially large scale."

Re: Meteor hits 1.0

#96

Post by killertypo »

Congratulations on 1.0 but these kinds of buzzwordy lines

    Accomplish in 10 lines what would otherwise take 1000,
    thanks to a reactive programming model that extends all 
    the way from the database to the user's screen.
Really bother me.

Show me where you eliminated 1000 lines of code and how it was beneficial. Each line of code, to me, is placed with purpose and intent.

Are you eliminating thousands of lines of boilerplate? Or are you making best guess assumptions that fit the common need, and we still end up with those 1000 lines for something truly custom?

Re: Meteor hits 1.0

#98

Post by joshowens »

bduerst wrote: post #90
sferoze wrote: post #44

Earlier quoted context omitted.

Meteor just hit 1.0 and is not the type of framework you can just start including in your stack. You really have to build a meteor app from the ground up, so it is hard for established tech companies to get into Meteor when they already have spent years coding on another stack. As new startups who use Meteor grow you will see those large-scale projects come about.

So is it a PaaS like Google App Engine? Is it just an MVC like angular or ember?

It is not a PaaS, it is a framework that goes a bit further than previous frameworks. Angular and ember really just work for front-end code.

Meteor spans both the front-end and back-end to offer a seamless API experience when building your application.

Re: Meteor hits 1.0

#99

Post by sarciszewski »

rdtsc wrote: post #52
aroman wrote: post #40

Earlier quoted context omitted.

It uses a database, specifically MongoDB. But as I understand it, Meteor manages this for you itself, and abstracts the orchestration of those things into the Meteor platform itself. It's just a higher level of abstraction, not a new technology. And certainly not flat files.

MongoDB? I think to be accepted and taken more seriously they'd have to at least have an option for something else.

I say PostgreSQL. Not only can it do everything MongoDB can do (and faster* too), it's time-tested technology.

* http://blogs.enterprisedb.com/2014/09/24/postgres-outperform...

Post reply on HN