On Jul 9, 2013, at 1:42 PM, whatnow1204 <[email protected]> wrote:
>
> I'm interested into learning node.js. Before I dive into Node.js, I have no
> knowledge in back-end development in any areas (my knowledge in HTTP is very,
> very limited and basic), only know client side, such as HTML, CSS, and
> JavaScript. I want to expand my knowledge in other technologies, instead of
> just knowing interactivity and behavior on your web pages.
>
> What are the qualifications to know for server side technologies before I
> reach to node.js? Also, I notice people mentioning REST and RESTful API. Is
> REST important to know?
>
Hello whatnow/shurns (it would have been nicer to address you by a real name),
here are my 2 cents:
If you know JavaScript you are ready to start looking at Node. You could do a
lot in preparation, such as learning a bit about protocols especially HTTP, but
if you start on Node today, questions that lead to these areas will naturally
arise and you would do well to follow where they take you (to an extent!).
You will jump some hurdles with the async programming model which you are
already familiar with on the browser (and you may find some relief in Q, Async,
etc), with using npm to install and manage your packages/modules, the
interesting ins and outs of module caching when using require(), you will find
you need to save your data somewhere and take a hit off the MySQL vs Postgres
vs NoSQL vs NewSQL bong, and wonder if you really should use an ORM like
everyone says; you will need to serve pages and add an API, a REST API (these
days hospitals deliver babies with an API), and naturally that will lead you to
Express, which you will find awesome but tricky to figure out at times until
you discover Connect... and EventEmitters (beware, in the node forest, an event
sometimes makes a noise even if nobody is listening to it yet); you will wish
for the DOM on the server-side, find JSDOM and company, and wonder if you
really needed it after all; you will do WebSockets like all the cool kids and
you will learn that TCP/IP still matters; you may want more than just
interactivity and behaviour on the client side, explore server and client side
templates, flip a coin endlessly between Ember and Angular while you wait for
Meteor to mature; and if you are fortunate enough you will write your
server-side code on a *nix platform and learn about processes, IPCs, daemons…
...and above all, you will write a TODO app.
That’s not a lot of help, is it? So perhaps a direct answer will be a minimal
compensation: yes, REST is important to know and you should read up on it.
Good luck! Ask a lot of questions. And beware the embarrassment of riches when
it comes to modules and frameworks.
—ravi
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
