- Taschenbuch: 300 Seiten
- Verlag: Manning; Auflage: Pap/Psc (24. Oktober 2013)
- Sprache: Englisch
- ISBN-10: 1617290572
- ISBN-13: 978-1617290572
- Größe und/oder Gewicht: 18,7 x 2,2 x 23,5 cm
- Durchschnittliche Kundenbewertung: 4 Kundenrezensionen
- Amazon Bestseller-Rang: Nr. 30.940 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
Node.js in Action (Englisch) Taschenbuch – 24. Oktober 2013
Wird oft zusammen gekauft
Kunden, die diesen Artikel gekauft haben, kauften auch
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Über den Autor und weitere Mitwirkende
Mike Cantelon is a web programmer with 10 years of experience in bespoke and product-oriented web application development
T.J. Holowaychuk is a prolific open-source engineer who has backed Node since its infancy. He has also authored many robust Node.js modules, including the popular Express web framework, Cluster, Stylus, and Jade, among many others.
Nathan Rajlich is an active Node developer who has been working with Node since its early days. He has authored an impressive collection of Node modules including NodObjC and maintains a port of Node that runs on Apple's iOS.
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
But let's start from the begin:
- Node and Node libraries basics (incl. the npm Node module network)
- DB stuff (not restricted to relational databases but also discussing MongoDB, Mongoose and their concepts, e.g.)
- Express web framework with (the usual) concepts for security, templating, skeleton generation, auxiliary functionality, MVC pattern etc.
- testing (pointing to different frameworks)
- deployment / hosting aspects (whereas Node in itself provides already the / a web server)
- furthergoing aspects as provision of TCP/IP servers, cross browser communication via web sockets, CLI tool programming and OS APIs
- the Node ecosystem and community support.
The examples are formidable and educating.
Of some special interest for me were
Nevertheless, I do not understand completely, why - besides plenty of existing web programming stuff in most different flavours - this additional technique has been introduced.Lesen Sie weiter... ›
so be aware of that before you buy the book. either you fix the code by yourself or you wait for a second edition of this book.
but nevertheless it's a great book and helped me to get started with node and express.
node.js is a new environment and it's not that well documented yet for all its APIs and how things are mixed together from
jQuery over npm and nodeclipse, css, html, and I've probably forgotten another bunch of more or less arcane technologies.
One wonders how brittle the IT environments of the future shall be and who will be able to maintain the latest fads; fads being created at today's internet speed. it used to be called software engineering, but has evolved into software banging.
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
I found out this is the best book I've read so far on the topic.
It starts from the very beginning and guide you through the whole development process.
It doesn't delve deep into low level details but I think this is due to target audience for this book.
It explains you the basics and there are a lot of good examples to get you started.
Nodejs is very extensible and there are a lot of useful packages. The book tries to cover the most useful in the daily usage.
The only bit I didn't like a lot is the development of the first application, it comes to early in the book and doesn't really help in understanding the language.
The rest of the book is well done. I'd advice this book to all nodejs novice who want to get ready to use it quickly.
This book will guide you through the series of various use cases and walk you line-by-line through the code examples and patiently explain how Node works. Most of them get from very simple hello worlds to more complex problems (like full-blown app with photo uploading and pagination functionalities). On the other hand, some examples actually felt terrible - like the problem being solved was too artificial and uninteresting. In general I'd say that my feelings from the examples are a bit mixed.
Node.js has its own and unique ecosystem and you'll get through variety of very node friendly technologies. You'll see how to integrate Node.js with modern persistence solutions like MongoDB and Redis and more traditional SQL databases as well. You'll see how to use Node.js as your primary server-side framework and how to integrate it with popular web frameworks like Express or popular templating technologies like Mustache, Hogan.js, Jade etc. There is also chapter on 'Node ecosystem' and for some unknown reason it's the last chapter in the book. I suggest you read this chapter early to get the idea how does node.js taste out there in the wild.
One of the greatest advantages is that authors didn't forget about things like deployment, troubleshooting and clustering. There is a whole chapter on those things and it's definitely well wroth of reading!
Nothing's perfect though. Mistakes were made in this book as well. I have to say that most of the source code in the book is of rather poor quality. It's something I definitely wouldn't call 'representative'. And certainly not production ready, as most of the examples *COMPLETELY* omit tests. That's something I ain't forgivin'! You might wanna ask yourself why do I miss those tests so much? Well if you want to follow the examples in the book and you want to add function by function, you're probably going to make some typo and so the only reasonable thing to do is either *not to* write examples yourself (run those that are included), or write tests yourself.
Another sad thing (which is not exactly authors' fault) is that Node.js evolves so rapidly, that some chapters have become quite obsolete. For example, most of the things in chapters 6 and 7 are not even runnable with latest node.js distributions.
And yet another thing that I have mixed feelings about is that I think that those 400 pages could've been used a bit better. There is a whole chapter on a horrible thing called EJS that everybody hates. Also you'd probably expect from the super-hipster-modern Node.js book that REST would be first class citizen. Well, there is a chapter on REST, but most of the samples in other chapters are not RESTful in nature.
There are certainly some very good introductory chapters in this book, but I am afraid that poor code quality, lack of tests and plenty of obsolete information make this book less and less relevant with every new day.
(1) Scattered, unfocused, and disorganized.
(2) The code given in the examples in does not run. The code given by the authors on their website fails to run correctly.
Yes, I followed the directions in the book. The first example of a big application is given without any context so what happens when you make even a minor mistake in the code? It won't run, naturally. Will you know enough about the code to fix it? I'm a pretty good programmer and I couldn't. The only reason I have the example running is because I found someones fixed code on GitHub.
(3) There are very few practical things in this that make sense in the context of developing something that actually runs. If you can get something running this book will not give you the tools to extend the code or do anything useful.
(4) You really can't use this book as a reference. Where would you look stuff up?
Big disappointment. Pretty much useless.
The creator of express and one of the co-authors is no longer working with node. By the way, there are 4 authors in this book! It doesn’t have the flow or the same style. The book feels like a patchwork. The chapters are totally unrelated to each other. They jump from one topic to another. There are bits and pieces here and there, but overall they are confusing and mostly useless. Some parts contradict each other or duplicate what’s already been covered.
I also purchased practical node and happy with it so far, because all express examples work and versions are stated everywhere in the book.