Developing Microservices with Node.js

by David González

Key Features Real world example explained chapter after chapter with code examples. Useful concepts for other languages like Java or PHP Easy to follow by people with little to none experience in Node.js Node.js Version 0.12.2 and the latest compatible versions of Seneca and PM2 Book Description

Microservices architecture is a style of software architecture. As the name suggests, microservicess refers to small services. For a large implementation, this means breaking the system into really small, independent services. Alternative to monolithic architecture (where the entire system is considered as a single big, interwoven segment), microservices approach is getting more and more popular with large, complex applications that have a very long lifecycle, which require changes at regular intervals. Microservices approach allows this type of changes with ease as only a part of the system undergoes changes and change control is easy.

An example of such large system can be an online store—includes user interface, managing product catalog, processing orders, managing customer's account. In a microservices architecture each of these tasks will be divided and into smaller services. Also, these services will be further broken down into independent services—for user interface, there will be separate services for input, output, search bar management, and so on. Similarly, all other tasks can be divided in very small and simple services.

What you will learn Identify where the microservice oriented architectures can tackle the most common problems in the software used by the big organisations. Re-architecture an existing monolithic system into a microservices oriented software. Build robust and scalable microservices using Seneca and Node.js. Testing of the microservices in insolation in order to create a solid system. Deploy and manage microservices using PM2 Monitoring the health of a microservice (CPU, memory, I/O...) and how the degradation of the performance in one microservice could degrade the performance of full system. About the Author

David Gonzalez is a language-agnostic software engineer working in financial services for a number of years, trying to find solutions for the right level of abstraction and learning how to get the right balance between too concrete and too abstract.

He studied in Spain, but soon moved to the wider and more interesting market of Dublin, where he has been living since 2011. David is currently working as an independent consultant in the FinTech sector. The URL to his Linkedin account is https://ie.linkedin.com/in/david-gonz....

He loves experimenting with new technologies and paradigms in order to get the broader picture of the complex world of software development.

Table of Contents Microservices Architecture Microservices in Node.js – Seneca and PM2 Alternatives From the Monolith to Microservices Writing Your First Microservice in Node.js Security and Traceability Testing and Documenting Node.js Microservices Monitoring Microservices Deploying Microservices

Genres: Software, Programming, Computer Science

288 pages, Kindle Edition

Published April 26, 2016

Reviews

[David · Rating 3 out of 5]

While it's a valuable book for being the first one dedicated to Seneca.js, the book lacks depth in a few necessary areas and its Node.js-related code examples are sloppy. I submitted errata three times within the first hundred pages and after that I just gave up on making corrections. While most of the bugs in the code examples and step-by-step walkthroughs are recoverable if you have some experience with the technologies (ie, forgetting to tell you to start node-inspector before launching your node application with debug options, OR putting spaces after command line option hyphens), there are some flaws in the code that are due to the Seneca API changing a month or so before this book was published (ie, Seneca Entity was broken apart from the Seneca library and must be explicitly required and "seneca.used()" into your code). Another major knock on this book isn't a knock against the author but against the fact that "proofreaders" (as well as "technical reviewers") at Packt Publishing rarely seem to do their job, and this book was the worst I've ever seen for one of their books correcting consistent English grammar and vocabulary mistakes. You can certainly understand the book, but again it contributes to an overall feeling of sloppiness and lack of attention on the part of someone specifically listed in the book credits as a "proofreader".

The content the author chose was outstanding and it's an exciting subject. His sampling of Seneca, working in it's integration with express.js, using PM2 and docker to manage and deploy an application made this a very useful book. Working through the code examples is definitely worthwhile to learn the framework, though again, be warned, you have to spend some time pushing through it (because it seems unfortunately the technical reviewer never did). The latter chapters of the book are very clean and very informative on the devops side of things, and it was one of the more valuable sections of the book.

Overall it's a good resource, but the faults that keep me personally from giving this book higher marks are clearly the fault of the publisher and reviewers for failing to do their job.

[Abdul Qavi · Rating 4 out of 5]

A very good quick read to get introduction to different tools, implementing microservices, load balancing and more.

[Saleh Rahimzadeh · Rating 3 out of 5]

This is a essential book to learning Microservices for beginners, but not very sophisticated and comprehensive.

[Pawelek · Rating 4 out of 5]

Pod uwage wzieto wszystkie elementy tworzrnia nowoczesnego oprogramowania. Przedstawiono rozne frameworki z node.js. Po kolei ogarnieto tworzenie, testowanie, monitoring, bezpieczenstwo i na koniec deploy aplikacji z uzyciem najnowszych technologii. Wartosciowa ksiazka, ale raczej tylko dla zajaranych node.js.