Here’s this week’s recap of the Node.js related content we posted in the last week or so, plus StrongLoop related articles we came across on the web.
Continuous Integration (CI) is an essential part to any modern development process. Gone are the days of monolithic releases with massive changes, today it’s all about releasing fast and often. Most teams have come to rely on some sort of automated CI system. In this article we are going to talk about some of the benefits of CI and how it fits into small, medium and large projects followed by a quick overview of three different hosted CI services and how they apply to projects of various sizes.
Node Streams are a powerful way to build modules and applications that deal with large streams of data. The Streams API has gone through a few revisions and has steadily been improving. Streams 1 introduced push-streams to allow developers to consume data efficiently. Streams 2 added pull-streams in addition to push-streams to allow advanced use-cases, however, the two styles could not be used together. Streams 3 solves this issue in an elegant manner and allows the same stream to be used in both push and pull mode. Streams3 is available in Node v0.11/v0.12 and io.js. Read on to dig into the details.
by Valeri Karpov
Recently, I’ve been looking into StrongLoop’s LoopBack framework. LoopBack generates Express REST APIs by asking you a few simple questions at the command line. LoopBack lets you swap out different storage layers. For each model you define, you can choose to store it in MongoDB, Oracle, MySQL, or Microsoft SQL Server (or even in memory). Say you decide to store your users in MongoDB but your user’s gift cards in MySQL (for transactions). Even if you started writing your code with gift cards stored in MongoDB, LoopBack’s database abstraction layer makes switching a one-liner. Furthermore, LoopBack has SDKs for generating REST API clients in AngularJS, Android, and iOS. In short, LoopBack is a powerful tool for generating REST APIs that you can extend to scaffold client-side code.s.
Over the last few months we’ve created quite a few sample apps to help you test out the various features of the Loopback framework without having to code up an example from scratch. For instance, sample apps that allow you to test out connectivity to databases plus the ability to quickly see in action features like model relations, application logic and access control.
Now, this is a story all about how my life got flipped – turned upside down – and I’d like to take a minute, just sit right there, I’ll tell you how I became the Developer Evangelist of a place called StrongLoop. Well, that didn’t turn out quite as well as I’d hoped, but you get the gist. I’m the newest employee at StrongLoop and will be stepping into the Developer Evangelist role! I’ll elaborate on what I’ll be working on later, but first, I wanted to give you some background as you’ll be hearing from me a lot.
In this presentation, Fred Schott from Box will give a presentation covering how to do things the Node Way. Including discussions on what this means to the community, coding and async. For more information visit: thenodeway.io/
In this talk, Randall Degges, Developer Evangelist at StormPath shares some of the best practices he learned while building Stormpath’s Express.js authentication libraries. Learn how to: safely log users into web applications, secure REST APIs, the low-level details that make this possible, and which Node libraries you should be using (and where).
In this talk, Shubhra Kar – StrongLoop Director of Products and Node.js trainer/evangelist, will dive into three essential areas you should be looking at to identify performance tuning opportunities in your Node apps. First, we’ll look at how and why to perform CPU and Heap profiling. Second, how to troubleshoot memory leaks and understand the difference between rapid and slow leaks. Finally, we’ll do a deep dive into how V8′s garbage collection works and the role it plays in optimizing Node apps.
Blogs in Portuguese
Em nossa última dica semanal sobre desempenho, nós discutimos em detalhes como o loop de evento do Node.js funciona como o orquestrador de requisições, eventos e callbacks. Também solucionamos um caso de loop bloqueante, o que poderia causar estragos no desempenho da aplicação. No post desta semana vamos mergulhar nos fundamentos do coletor de lixo (GC) da V8 e como ele mantém as “chaves para o reino” da otimização em aplicações Node. Também vamos ver algumas ferramentas para classificar problemas de GC e de gerenciamento de memória na V8.
Blogs in Spanish
Los streams de Node son una forma poderosa de construir módulos y aplicaciones que manejan grandes streams de data. La API de Streams ha pasado por varias revisiones y ha estado mejorando establemente. Los Streams 1 introducieron push-streams para permitir a los desarrolladores consumir data eficientemente. Los Streams 2 agregaron pull-streams en adición a push-streams para permitir casos de uso más avanzados, sin embargo, los dos estilos no pueden utilizarse juntos. Los Streams 3 resuelven este problema de una manera elegante y permite al mismo stream ser utilizado tanto en modo push cómo en modo pull. Los Streams 3 están disponibles en Node v0.11/v0.12 y io.js. Continua leyendo para entrar en los detalles.
- Ready to develop APIs in Node.js and get them connected to your data? Check out the Node.js LoopBack framework. We’ve made it easy to get started either locally or on your favorite cloud, with a simple npm install.