1. 10

After a year of writing, my book Distributed Systems with Node.js was finally published today! The book is available here:

My intent with this book is to prove that Node.js is just as capable as traditional enterprise platforms (like Java or .NET) for building services that are observable, scalable, and resilient. It’s very hands-on and readers will write application code and integrate it with tooling from various layers of a modern service stack.

For example, readers will encapsulate two applications using Docker, run a private container registry to host images, deploy to Kubernetes, configure health checks, scale the instance count, and allow the apps to communicate with each other. Readers will send logs to Elasticsearch, build a dashboard with Kibana, send metrics to StatsD/Graphite, build another dashboard with Graphite, transmit request spans and visualize request hierarchies with Zipkin. They’ll even configure a CI pipeline, run unit tests, enforce code coverage, and deploy to a production server. And that isn’t even half of it!

I wrote this book as a Node.js developer who loves writing code that runs on the server but who doesn’t have much interest in frontend development. Node.js developers often get stereotyped into being frontend developers and I hope that this book can help bring an end to that.

Let me know if you have any questions!

  1. 2

    Interesting, I never heard of that stereotype of frontend devs.

    I’m a frontend dev who is becoming better at dev ops, simply because I need to figure out why my servers are crashing haha. Thanks for the coupon code, I’m gonna pick this up.

    1. 2

      I picked up the kindle edition and started running through it yesterday. I’m impressed! It’s not your typical node book. It’s a return to the kind and quality of book that O’Reilly /used/ to publish, and that I’d wish they’d return to. The brief introduction to micro queues and node states was enlightening. I’m really enjoying it so far

      1. 1

        As someone who is most comfortable with TypeScript, how TypeScript-compatible are the Node.js libraries being used? Or, is that not really a huge factor given the emphasis on deployment and observability?

        1. 1

          I’m not familiar with how TypeScript friendly the libraries are, sorry. I’m sure that half are pretty good and the other half are abysmal.