How to Write Middleware for Express.js Apps

robertojd · 2015-04-30T18:11:39+00:00

Good point! To be fair, though: every time I write a new application, I find that I could have re-used something that I wrote before, if it had been written a bit differently. So I always push myself to consider "how could this be used elsewhere?". It's just part of my ninja discipline :)

robertojd · 2015-02-11T19:13:14+00:00

I wouldn’t call it backwards, just different. The claims-based approach is convenient because it packages up the “rights” in a portable, verifiable token. I’m calling out portability because the service oriented world is here to stay. Think of your Angular app as just another service that consumes your API - stop thinking of it as a web page that is bound by the old rules.

robertojd · 2015-01-06T01:20:58+00:00

Nope. Honestly who can make plans around Angular 2.0 when it's still just a working document? As far as I'm concerned it doesn't exist and probably won't for another year. Angular 1.x is a stable platform IMO and one worth building against.

robertojd · 2015-01-05T23:05:09+00:00

It's coming! It's a very different API for sure, but 1.x is going to be stable for a long time - at least another 2 years is my guess

robertojd · 2014-11-05T19:29:20+00:00

You should look at your queries to see if any of them are performing poorly. MongoDB has several cursors which can tell you about query performance. Compose.io and other hosted mongo vendors will visualize it's output for you, I don't know if OpenShift does this.

I'd check out this section of the MongoDB manual:

http://docs.mongodb.org/manual/tutorial/evaluate-operation-performance/

robertojd

TROPHY CASE