Using Node.js to Build Great Streaming Services - HTML5 Dev Conf
17 likes22,678 views
The document discusses using Node.js to build streaming services. It describes how Node.js allows for scalable server-side code using JavaScript and mentions libraries like JSONStream that can be used to parse JSON streams. The document also discusses different types of streaming like simplex, throughput, and duplex streaming and how to manage backpressure in streams.
1 of 51
Downloaded 177 times
![{"total_rows":129,"offset":0,"rows":[
{ "id":"change1_0.6995461115147918"
, "key":"change1_0.6995461115147918"
, "value":{"rev":"1-e240bae28c7bb3667f02760f6398d508"}
, "doc":{
"_id": "change1_0.6995461115147918"
, "_rev": "1-e240bae28c7bb3667f02760f6398d508","hello":1}
},
{ "id":"change2_0.6995461115147918"
, "key":"change2_0.6995461115147918"
, "value":{"rev":"1-13677d36b98c0c075145bb8975105153"}
, "doc":{
"_id":"change2_0.6995461115147918"
, "_rev":"1-13677d36b98c0c075145bb8975105153"
, "hello":2
}
},
]}
@sh1mmer](https://image.slidesharecdn.com/html5devconf2012-121017131811-phpapp02/85/Using-Node-js-to-Build-Great-Streaming-Services-HTML5-Dev-Conf-47-320.jpg)
![var stream = JSONStream.parse(['rows', true, 'doc']) //rows,
ANYTHING, doc
stream.on('data', function(data) {
console.log('received:', data);
});
stream.on('root', function(root, count) {
if (!count) {
console.log('no matches found:', root);
}
});
@sh1mmer](https://image.slidesharecdn.com/html5devconf2012-121017131811-phpapp02/85/Using-Node-js-to-Build-Great-Streaming-Services-HTML5-Dev-Conf-48-320.jpg)
Ad
Recommended
Node.js streaming csv downloads proxy
Node.js streaming csv downloads proxyIsmael Celis The document outlines the implementation of a streaming downloads proxy service using Node.js, focusing on generating CSV files from API responses related to orders. It details the mapping of JSON data to CSV format, the usage of JSON Web Tokens (JWT) for secure data access, and the setup of HTTP handlers for downloading order-related data. Various parameters, including sorting and filtering criteria, are defined to optimize API calls for CSV generation.
Nodejs Explained with Examples
Nodejs Explained with ExamplesGabriele Lana The document discusses Node.js and asynchronous I/O. It explains that Node.js is an asynchronous event-driven JavaScript runtime that uses a single-threaded model with non-blocking I/O to handle high volumes of simultaneous connections efficiently. It also discusses how Node.js handles asynchronous operations using an event loop and callback functions instead of blocking operations.
Node.js - Best practices
Node.js - Best practicesFelix Geisendörfer This document discusses best practices for handling errors and callbacks in Node.js applications. It covers techniques like error delegation, exception handling, error-first callbacks, avoiding nested callbacks, and using control flow libraries. It also discusses deployment strategies like using screen, restarting crashed processes, and innovating with platforms like Joyent, Nodejitsu and Heroku.
Node.js - A Quick Tour
Node.js - A Quick TourFelix Geisendörfer Node.js is an asynchronous event-driven JavaScript runtime that aims to provide an easy way to build scalable network programs. It uses an event loop model that keeps slow operations from blocking other operations by executing callbacks asynchronously. This allows Node.js programs to handle multiple connections concurrently without creating new threads. Common uses of Node.js include building web servers, real-time applications, crawlers, and process monitoring tools. The document provides examples of using modules like HTTP, TCP, DNS, and file system modules to demonstrate Node.js's asynchronous and non-blocking I/O model.
Ruby HTTP clients comparison
Ruby HTTP clients comparisonHiroshi Nakamura This document summarizes and compares Ruby HTTP client libraries. It discusses the sync and async APIs of 16 libraries including Net::HTTP, HTTPClient, and Faraday. It covers their compatibility, supported features like keep-alive connections, and performance based on benchmarks. The document recommends libraries based on priorities like speed, HTML handling, API clients, and SSL support. It encourages readers to check the detailed feature matrix and report any errors found.
Beyond Phoenix
Beyond PhoenixGabriele Lana This document discusses embracing HTTP and changing approaches to web application development. It suggests flipping dependencies so that applications are built around HTTP rather than frameworks. It also recommends taking a more stateful approach by going CQRS/ES rather than relying on CRUD and resources. The document questions common patterns and promotes thinking beyond frameworks to more fundamental concepts.
Integrating icinga2 and the HashiCorp suite
Integrating icinga2 and the HashiCorp suiteBram Vogelaar The document provides an overview of integrating Icinga2 with the HashiCorp suite, detailing configurations for Vagrant and Terraform to manage infrastructure and monitor services. It includes code snippets and configurations for setting up hosts, check commands, and notifications within Icinga2. Additionally, it covers the use of Consul for service discovery and its integration with Icinga, demonstrating the deployment and synchronization process.
Puppet and the HashiStack
Puppet and the HashiStackBram Vogelaar Puppet is an open source configuration management tool that can be used to automate the configuration and management of infrastructure and applications. It uses a client-server architecture and declarative language to define and enforce the desired state of systems. Other HashiCorp tools like Packer, Terraform, Vault and Nomad can integrate with Puppet for tasks like infrastructure provisioning, secrets management and workload orchestration. Bolt is a task orchestration tool from Puppet that can be used to automate operational tasks across infrastructure defined by tools like Terraform. Consul provides service discovery and configuration for the Puppet infrastructure.
Writing robust Node.js applications
Writing robust Node.js applicationsTom Croucher This document provides an introduction and overview of a Node.js tutorial presented by Tom Hughes-Croucher. The tutorial covers topics such as building scalable server-side code with JavaScript using Node.js, debugging Node.js applications, using frameworks like Express.js, and best practices for deploying Node.js applications in production environments. The tutorial includes exercises for hands-on learning and demonstrates tools and techniques like Socket.io, clustering, error handling and using Redis with Node.js applications.
Devinsampa nginx-scripting
Devinsampa nginx-scriptingTony Fabeen The document discusses extending Nginx functionalities with Lua. It provides an overview of Nginx architecture and how the lua-nginx-module allows running Lua scripts inside Nginx. This provides a powerful and performant programming environment while leveraging Nginx's event-driven architecture. Examples show how to access Nginx variables and APIs from Lua, issue subrequests, and handle requests non-blockingly using cosockets. Libraries like lua-resty-memcached reuse these extensions to build applications in a scalable manner.
Lua tech talk
Lua tech talkLocaweb The document discusses using Lua modules with Nginx. It provides an overview of Nginx and Lua, describing their key features and popular uses. It then covers how to integrate Lua into Nginx using the ngx_lua module, allowing Lua code to run at various phases of the Nginx request lifecycle. Specific techniques demonstrated include using Lua for shared memory caching, logging, issuing subrequests, and network communication via cosockets. Examples of practical applications like load balancing and analytics tagging are also presented.
Ubic
UbicVyacheslav Matyukhin The document describes UBIC, a toolkit for writing daemons, init scripts, and services in Perl. It provides common classes that handle tasks like starting, stopping, and monitoring services that simplify writing init scripts. Services can be organized hierarchically and non-root users can run services. The toolkit also provides HTTP status endpoints and watchdog functionality to restart services that fail. UBIC sees widespread use at Yandex across many packages, clusters, and hosts.
Node js presentation
Node js presentationmartincabrera Node.js is a server-side JavaScript environment that uses an asynchronous event-driven model for excellent performance handling many internet connections simultaneously. It is implemented on Google's V8 JavaScript engine and uses non-blocking I/O to avoid wasting CPU resources waiting for operations to complete. Example code demonstrates how Node.js can create an HTTP server or handle other network protocols without threads blocking like in traditional servers.
Introduction to Nodejs
Introduction to NodejsGabriele Lana The document provides an overview of Node.js and why it is useful for building scalable network programs. It discusses how Node.js uses asynchronous and non-blocking I/O to handle thousands of concurrent connections using a single thread. This allows Node.js applications to scale horizontally by adding more machines. It also covers how the asynchronous programming model requires a different "mind shift" compared to traditional synchronous approaches.
Bootstrapping multidc observability stack
Bootstrapping multidc observability stackBram Vogelaar The document outlines the configuration and architecture for a multi-data center observability stack incorporating tools like Prometheus, Loki, and Tempo for metrics, logs, and traces respectively. It addresses high availability (HA) strategies, including the use of Consul for service discovery and dynamic scraping across multiple data centers. The document also includes sample configurations, alerting setups, and references to additional resources for implementation.
Matthew Eernisse, NodeJs, .toster {webdev}
Matthew Eernisse, NodeJs, .toster {webdev}.toster Matthew Eernisse gave a presentation on NodeJS at the Toster Conference in 2011. He discussed what NodeJS is, how it uses asynchronous and event-driven JavaScript, and some examples of using NodeJS at Yammer for applications like a file upload service and real-time document editing. He also covered challenges like debugging asynchronous code, developing for NodeJS, and operations considerations like monitoring and logging.
A million connections and beyond - Node.js at scale
A million connections and beyond - Node.js at scaleTom Croucher This document discusses benchmarks and performance testing of Node.js. It notes that while Node.js can handle over 1 million connections, benchmarks are not that important as other factors like productivity. It explores how to meaningfully measure Node.js performance, compares Node.js to other frameworks like Erlang and Tornado, and argues that benchmarks should reflect real-world use cases rather than simplistic "hello world" tests. The document questions overreliance on benchmarks and emphasizes picking the right tool based on the task.
Securing Prometheus exporters using HashiCorp Vault
Securing Prometheus exporters using HashiCorp VaultBram Vogelaar The document details the process of securing Prometheus exporters using HashiCorp Vault, providing installation instructions for both Prometheus and Node Exporter. It covers secret management, configuring PKI, and automating certificate lifecycle management. The setup emphasizes security practices for scraping metrics with Vault-issued certificates and includes examples of configuration files and commands.
Testing your infrastructure with litmus
Testing your infrastructure with litmusBram Vogelaar The document discusses testing infrastructure using Litmus, a Ruby-based tool developed by Puppet that supports multi-node testing with Docker and Vagrant. It outlines various testing methods including unit tests, acceptance tests, and integration with other tools like RSpec, Beaker, and Inspec. Additionally, it provides examples of configuration and commands necessary for executing tests in a DevOps environment.
Bootstrapping multidc observability stack
Bootstrapping multidc observability stackBram Vogelaar The document outlines a multi-data center (multi-DC) observability stack using tools like Consul, Grafana, Loki, and Tempo, focusing on high availability (HA) configurations across various components. It includes details on service discovery, metrics scraping, and cluster configurations while addressing how to handle data redundancy and synchronization in a multi-DC setup. The author invites questions and provides contact information for further inquiries.
Nginx-lua
Nginx-luaДэв Тим Афс This document discusses using NGINX with embedded Lua scripting via OpenResty. Lua is a lightweight scripting language used in many applications and games. OpenResty bundles NGINX with LuaJIT and modules to allow full control over every stage of request processing with non-blocking Lua scripts. Examples show how to build a REST API for user scores with Redis using Lua scripts to handle data retrieval, modification and aggregation directly from NGINX.
Creating Reusable Puppet Profiles
Creating Reusable Puppet ProfilesBram Vogelaar The document discusses the creation of reusable Puppet profiles, emphasizing the use of component modules, profiles, and roles to manage and configure technology stacks effectively. It presents various design patterns, including granular roles and conditional logic, as well as providing examples of Puppet classes and defined types for web server and database setups. Additionally, it highlights best practices for documentation and validation of code within the Puppet ecosystem.
Rhebok, High Performance Rack Handler / Rubykaigi 2015
Rhebok, High Performance Rack Handler / Rubykaigi 2015Masahiro Nagano This document discusses Rhebok, a high performance Rack handler written in Ruby. Rhebok uses a prefork architecture for concurrency and achieves 1.5-2x better performance than Unicorn. It implements efficient network I/O using techniques like IO timeouts, TCP_NODELAY, and writev(). Rhebok also uses the ultra-fast PicoHTTPParser for HTTP request parsing. The document provides an overview of Rhebok, benchmarks showing its performance, and details on its internals and architecture.
Static Typing in Vault
Static Typing in VaultGlynnForrest Static typing in Vault refers to enforcing the structure and location of secrets stored in Vault. This can be achieved by using a script or tool to validate secrets against JSON schemas before they are written or accessed. The schemas define the required properties and structure for different secret types. Using a generic validation tool allows schemas to be centrally defined and ensures secrets match the expected format, reducing errors from incorrectly structured secrets.
Hopping in clouds: a tale of migration from one cloud provider to another
Hopping in clouds: a tale of migration from one cloud provider to anotherMichele Orselli The document details the migration of a platform from one cloud provider to another, focusing on enhancing system performance and reducing costs. Key components included upgrading software versions, optimizing resource usage, and implementing cloud services like AWS for improved infrastructure. The migration process lasted a year, resulting in a significant cost reduction and a more suited environment for the company's needs.
Observability with Consul Connect
Observability with Consul ConnectBram Vogelaar The document discusses the implementation of observability in a Consul Connect environment, detailing service definitions, connection setups, and metrics exposure using Envoy and Prometheus. It outlines how to create service meshes, manage service configurations, and collect metrics for monitoring applications. Additionally, it includes configurations for Grafana, Loki, and Tempo, providing a comprehensive overview of observability tools and their integration.
Nodejs - A quick tour (v6)
Nodejs - A quick tour (v6)Felix Geisendörfer This document provides an overview and introduction to Node.js. It discusses that Node.js is a platform for building scalable network applications using JavaScript and uses non-blocking I/O and event-driven architecture. It was created by Ryan Dahl in 2009 and uses Google's V8 JavaScript engine. Node.js allows building web servers, networking tools and real-time applications easily and efficiently by handling concurrent connections without threads. Some popular frameworks and modules built on Node.js are also mentioned such as Express.js, Socket.IO and over 1600 modules in the npm registry.
Nodejsexplained 101116115055-phpapp02
Nodejsexplained 101116115055-phpapp02Sunny Gupta The document discusses Node.js and asynchronous I/O. It explains that Node.js is an asynchronous event-driven JavaScript runtime that uses a single-threaded model with non-blocking I/O to handle high volumes of simultaneous connections efficiently. It also discusses how Node.js handles asynchronous operations using an event loop and callback functions instead of blocking operations.
About Node.js
About Node.jsArtemisa Yescas Engler Node.js is a JavaScript runtime built on Chrome's V8 engine that allows building scalable network applications using JavaScript on the server-side. It uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, suitable for data-intensive real-time applications that run across distributed devices. Common uses of Node.js include building web servers, file upload clients, ad servers, chat servers, and any real-time data applications. The document provides an introduction to Node.js concepts like callbacks, blocking vs non-blocking code, the event loop, streams, events, and modules.
More Related Content
What's hot (20)
Puppet and the HashiStack
Puppet and the HashiStackBram Vogelaar Puppet is an open source configuration management tool that can be used to automate the configuration and management of infrastructure and applications. It uses a client-server architecture and declarative language to define and enforce the desired state of systems. Other HashiCorp tools like Packer, Terraform, Vault and Nomad can integrate with Puppet for tasks like infrastructure provisioning, secrets management and workload orchestration. Bolt is a task orchestration tool from Puppet that can be used to automate operational tasks across infrastructure defined by tools like Terraform. Consul provides service discovery and configuration for the Puppet infrastructure.
Writing robust Node.js applications
Writing robust Node.js applicationsTom Croucher This document provides an introduction and overview of a Node.js tutorial presented by Tom Hughes-Croucher. The tutorial covers topics such as building scalable server-side code with JavaScript using Node.js, debugging Node.js applications, using frameworks like Express.js, and best practices for deploying Node.js applications in production environments. The tutorial includes exercises for hands-on learning and demonstrates tools and techniques like Socket.io, clustering, error handling and using Redis with Node.js applications.
Devinsampa nginx-scripting
Devinsampa nginx-scriptingTony Fabeen The document discusses extending Nginx functionalities with Lua. It provides an overview of Nginx architecture and how the lua-nginx-module allows running Lua scripts inside Nginx. This provides a powerful and performant programming environment while leveraging Nginx's event-driven architecture. Examples show how to access Nginx variables and APIs from Lua, issue subrequests, and handle requests non-blockingly using cosockets. Libraries like lua-resty-memcached reuse these extensions to build applications in a scalable manner.
Lua tech talk
Lua tech talkLocaweb The document discusses using Lua modules with Nginx. It provides an overview of Nginx and Lua, describing their key features and popular uses. It then covers how to integrate Lua into Nginx using the ngx_lua module, allowing Lua code to run at various phases of the Nginx request lifecycle. Specific techniques demonstrated include using Lua for shared memory caching, logging, issuing subrequests, and network communication via cosockets. Examples of practical applications like load balancing and analytics tagging are also presented.
Ubic
UbicVyacheslav Matyukhin The document describes UBIC, a toolkit for writing daemons, init scripts, and services in Perl. It provides common classes that handle tasks like starting, stopping, and monitoring services that simplify writing init scripts. Services can be organized hierarchically and non-root users can run services. The toolkit also provides HTTP status endpoints and watchdog functionality to restart services that fail. UBIC sees widespread use at Yandex across many packages, clusters, and hosts.
Node js presentation
Node js presentationmartincabrera Node.js is a server-side JavaScript environment that uses an asynchronous event-driven model for excellent performance handling many internet connections simultaneously. It is implemented on Google's V8 JavaScript engine and uses non-blocking I/O to avoid wasting CPU resources waiting for operations to complete. Example code demonstrates how Node.js can create an HTTP server or handle other network protocols without threads blocking like in traditional servers.
Introduction to Nodejs
Introduction to NodejsGabriele Lana The document provides an overview of Node.js and why it is useful for building scalable network programs. It discusses how Node.js uses asynchronous and non-blocking I/O to handle thousands of concurrent connections using a single thread. This allows Node.js applications to scale horizontally by adding more machines. It also covers how the asynchronous programming model requires a different "mind shift" compared to traditional synchronous approaches.
Bootstrapping multidc observability stack
Bootstrapping multidc observability stackBram Vogelaar The document outlines the configuration and architecture for a multi-data center observability stack incorporating tools like Prometheus, Loki, and Tempo for metrics, logs, and traces respectively. It addresses high availability (HA) strategies, including the use of Consul for service discovery and dynamic scraping across multiple data centers. The document also includes sample configurations, alerting setups, and references to additional resources for implementation.
Matthew Eernisse, NodeJs, .toster {webdev}
Matthew Eernisse, NodeJs, .toster {webdev}.toster Matthew Eernisse gave a presentation on NodeJS at the Toster Conference in 2011. He discussed what NodeJS is, how it uses asynchronous and event-driven JavaScript, and some examples of using NodeJS at Yammer for applications like a file upload service and real-time document editing. He also covered challenges like debugging asynchronous code, developing for NodeJS, and operations considerations like monitoring and logging.
A million connections and beyond - Node.js at scale
A million connections and beyond - Node.js at scaleTom Croucher This document discusses benchmarks and performance testing of Node.js. It notes that while Node.js can handle over 1 million connections, benchmarks are not that important as other factors like productivity. It explores how to meaningfully measure Node.js performance, compares Node.js to other frameworks like Erlang and Tornado, and argues that benchmarks should reflect real-world use cases rather than simplistic "hello world" tests. The document questions overreliance on benchmarks and emphasizes picking the right tool based on the task.
Securing Prometheus exporters using HashiCorp Vault
Securing Prometheus exporters using HashiCorp VaultBram Vogelaar The document details the process of securing Prometheus exporters using HashiCorp Vault, providing installation instructions for both Prometheus and Node Exporter. It covers secret management, configuring PKI, and automating certificate lifecycle management. The setup emphasizes security practices for scraping metrics with Vault-issued certificates and includes examples of configuration files and commands.
Testing your infrastructure with litmus
Testing your infrastructure with litmusBram Vogelaar The document discusses testing infrastructure using Litmus, a Ruby-based tool developed by Puppet that supports multi-node testing with Docker and Vagrant. It outlines various testing methods including unit tests, acceptance tests, and integration with other tools like RSpec, Beaker, and Inspec. Additionally, it provides examples of configuration and commands necessary for executing tests in a DevOps environment.
Bootstrapping multidc observability stack
Bootstrapping multidc observability stackBram Vogelaar The document outlines a multi-data center (multi-DC) observability stack using tools like Consul, Grafana, Loki, and Tempo, focusing on high availability (HA) configurations across various components. It includes details on service discovery, metrics scraping, and cluster configurations while addressing how to handle data redundancy and synchronization in a multi-DC setup. The author invites questions and provides contact information for further inquiries.
Nginx-lua
Nginx-luaДэв Тим Афс This document discusses using NGINX with embedded Lua scripting via OpenResty. Lua is a lightweight scripting language used in many applications and games. OpenResty bundles NGINX with LuaJIT and modules to allow full control over every stage of request processing with non-blocking Lua scripts. Examples show how to build a REST API for user scores with Redis using Lua scripts to handle data retrieval, modification and aggregation directly from NGINX.
Creating Reusable Puppet Profiles
Creating Reusable Puppet ProfilesBram Vogelaar The document discusses the creation of reusable Puppet profiles, emphasizing the use of component modules, profiles, and roles to manage and configure technology stacks effectively. It presents various design patterns, including granular roles and conditional logic, as well as providing examples of Puppet classes and defined types for web server and database setups. Additionally, it highlights best practices for documentation and validation of code within the Puppet ecosystem.
Rhebok, High Performance Rack Handler / Rubykaigi 2015
Rhebok, High Performance Rack Handler / Rubykaigi 2015Masahiro Nagano This document discusses Rhebok, a high performance Rack handler written in Ruby. Rhebok uses a prefork architecture for concurrency and achieves 1.5-2x better performance than Unicorn. It implements efficient network I/O using techniques like IO timeouts, TCP_NODELAY, and writev(). Rhebok also uses the ultra-fast PicoHTTPParser for HTTP request parsing. The document provides an overview of Rhebok, benchmarks showing its performance, and details on its internals and architecture.
Static Typing in Vault
Static Typing in VaultGlynnForrest Static typing in Vault refers to enforcing the structure and location of secrets stored in Vault. This can be achieved by using a script or tool to validate secrets against JSON schemas before they are written or accessed. The schemas define the required properties and structure for different secret types. Using a generic validation tool allows schemas to be centrally defined and ensures secrets match the expected format, reducing errors from incorrectly structured secrets.
Hopping in clouds: a tale of migration from one cloud provider to another
Hopping in clouds: a tale of migration from one cloud provider to anotherMichele Orselli The document details the migration of a platform from one cloud provider to another, focusing on enhancing system performance and reducing costs. Key components included upgrading software versions, optimizing resource usage, and implementing cloud services like AWS for improved infrastructure. The migration process lasted a year, resulting in a significant cost reduction and a more suited environment for the company's needs.
Observability with Consul Connect
Observability with Consul ConnectBram Vogelaar The document discusses the implementation of observability in a Consul Connect environment, detailing service definitions, connection setups, and metrics exposure using Envoy and Prometheus. It outlines how to create service meshes, manage service configurations, and collect metrics for monitoring applications. Additionally, it includes configurations for Grafana, Loki, and Tempo, providing a comprehensive overview of observability tools and their integration.
Nodejs - A quick tour (v6)
Nodejs - A quick tour (v6)Felix Geisendörfer This document provides an overview and introduction to Node.js. It discusses that Node.js is a platform for building scalable network applications using JavaScript and uses non-blocking I/O and event-driven architecture. It was created by Ryan Dahl in 2009 and uses Google's V8 JavaScript engine. Node.js allows building web servers, networking tools and real-time applications easily and efficiently by handling concurrent connections without threads. Some popular frameworks and modules built on Node.js are also mentioned such as Express.js, Socket.IO and over 1600 modules in the npm registry.
Similar to Using Node.js to Build Great Streaming Services - HTML5 Dev Conf (20)
Nodejsexplained 101116115055-phpapp02
Nodejsexplained 101116115055-phpapp02Sunny Gupta The document discusses Node.js and asynchronous I/O. It explains that Node.js is an asynchronous event-driven JavaScript runtime that uses a single-threaded model with non-blocking I/O to handle high volumes of simultaneous connections efficiently. It also discusses how Node.js handles asynchronous operations using an event loop and callback functions instead of blocking operations.
About Node.js
About Node.jsArtemisa Yescas Engler Node.js is a JavaScript runtime built on Chrome's V8 engine that allows building scalable network applications using JavaScript on the server-side. It uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, suitable for data-intensive real-time applications that run across distributed devices. Common uses of Node.js include building web servers, file upload clients, ad servers, chat servers, and any real-time data applications. The document provides an introduction to Node.js concepts like callbacks, blocking vs non-blocking code, the event loop, streams, events, and modules.
Node.js - As a networking tool
Node.js - As a networking toolFelix Geisendörfer Node.js is a JavaScript runtime built on Chrome's V8 JavaScript engine. It uses non-blocking I/O and event-driven architecture, making it suitable for real-time applications with many concurrent connections. Key features include a module system, asynchronous I/O bindings, common network protocols like HTTP and TCP/IP, and a streaming API. Addons allow extending Node.js with native code modules written in C/C++ for additional functionality.
Node js lecture
Node js lectureDarryl Sherman Node.js is a JavaScript runtime built on Chrome's V8 JavaScript engine. It introduces events and an event queue to handle asynchronous and non-blocking operations. Everything runs as a callback from the event loop. Node.js wraps OS operations in modules to make file, network, and other operations non-blocking and event-driven. It also introduces a module system where each module gets its own private scope. Common patterns in Node.js include using the listener/emitter pattern to handle events and building applications with streams of data.
Real Time Web with Node
Real Time Web with NodeTim Caswell The document discusses using Node.js for real-time web applications by allowing persistent connections and high concurrency. It introduces Connect, a Node.js framework that allows building reusable middleware blocks to handle tasks like logging, caching, compression etc. Examples of common middleware modules like method-override and response-time are provided. The challenges of writing scalable non-blocking servers and handling thousands of concurrent connections are addressed.
A language for the Internet: Why JavaScript and Node.js is right for Internet...
A language for the Internet: Why JavaScript and Node.js is right for Internet...Tom Croucher Node.js and JavaScript are well-suited for Internet applications because Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, capable of supporting many more concurrent connections than traditional server-side models like Apache. This event loop system allows Node.js to handle multiple requests simultaneously without blocking any specific request. It also minimizes memory usage so more requests can be served from fewer servers.
A language for the Internet: Why JavaScript and Node.js is right for Internet...
A language for the Internet: Why JavaScript and Node.js is right for Internet...Tom Croucher The document discusses why JavaScript, particularly with Node.js, is a suitable choice for building scalable internet applications by leveraging its event-driven, non-blocking I/O model. It highlights how Node.js can handle multiple concurrent connections efficiently, allowing for greater performance compared to traditional server-side languages. Coding examples illustrate how to set up a basic HTTP server with Node.js, emphasizing its simplicity and effectiveness for internet applications.
Introduction to Node.js
Introduction to Node.jsRichard Lee Richard Lee is an iOS, Ruby, and JavaScript developer and co-founder of Polydice, Inc. He gave an introduction to Node.js, an event-driven I/O framework for building scalable network applications. Node.js uses an event loop model and non-blocking I/O, making it fast and efficient for handling many concurrent connections. Common uses include building HTTP servers and implementing long polling or comet techniques. The community around Node.js is large and supportive, with many online resources and books available.
Real-Time with Flowdock
Real-Time with FlowdockFlowdock The document discusses the importance of real-time communication in a chat application and explores various transport channels such as websocket, server-sent events, and long-polling, each having its own trade-offs. It highlights the implementation of these transports in Flowdock and touches on issues like browser compatibility and error handling. The document concludes with performance benchmarks indicating that websockets are superior in terms of latency compared to other methods.
Functional Programming with Streams in node.js
Functional Programming with Streams in node.jsAdam Crabtree The document presents a discussion on functional programming with streams in Node.js, highlighting the benefits of using Node.js for building scalable network applications. It covers stream concepts, including readable and writable streams, as well as higher-order functions and their applications in processing data without buffering. The speaker also mentions ongoing work to port Node.js functionalities to the browser and invites collaboration with interested developers.
Building and Scaling Node.js Applications
Building and Scaling Node.js ApplicationsOhad Kravchick The document discusses building and scaling Node.js applications, outlining when to use Node.js and when not to, such as avoiding static file serving and simple CRUD apps. It covers essential setup requirements, includes code snippets for creating simple web servers using Express, and demonstrates the use of middleware and real-time communication with Socket.io. The document also touches on database integration, debugging techniques, concurrency models, and maximizing server capabilities using clustering and shared memory options.
Comet with node.js and V8
Comet with node.js and V8amix3k Node.js is a platform built on Google's V8 JavaScript engine that allows for non-blocking and event-driven web servers. It is well-suited for building real-time applications using techniques like Comet that require persistent connections to clients. The speaker demonstrates how to implement a basic chat application using WebSockets with node.js that maintains open connections to allow real-time messaging between users. Node.js's asynchronous and non-blocking model makes it a natural fit for Comet-style programming compared to traditional threaded server models.
Into to Node.js: Building Fast, Scaleable Network Applications
Into to Node.js: Building Fast, Scaleable Network ApplicationsFlatiron School Node.js is an event-driven, non-blocking server-side JavaScript runtime built on Chrome's V8 engine. It allows highly scalable network applications to be built by wrapping non-blocking libraries. Node.js uses an event loop that listens for events like connections, requests, data, and closures and queues callbacks for handling them asynchronously without blocking the main thread. This document provides an overview of Node.js and some of its core modules like Express for building web servers and Socket.io for real-time communication. It also includes examples of using Node.js and these modules to build a collaborative drawing application.
Server side JavaScript: going all the way
Server side JavaScript: going all the wayOleg Podsechin The document discusses the use of server-side JavaScript, particularly focusing on Node.js and its various frameworks and libraries such as RingoJS and Akshell. It contrasts synchronous and asynchronous programming styles, highlighting their applications and challenges, especially in areas like business logic and concurrency. The text also includes examples of practical implementations and benchmarks for various use cases in server-side JavaScript.
Node.js web-based Example :Run a local server in order to start using node.js...
Node.js web-based Example :Run a local server in order to start using node.js...Kongu Engineering College, Perundurai, Erode Run a local server in order to start using node.js in the browser and do server side tasks
Node Powered Mobile
Node Powered MobileTim Caswell The document discusses using a Node.js framework called Connect to build mobile web applications. Connect allows assembling reusable code blocks called middleware to handle common tasks like logging, parsing request bodies, caching, and serving static files. It also provides a simple interface using HTML, CSS, JavaScript, and network protocols like HTTP. Connect makes mobile app development light, networked, and in real-time by reusing pre-built middleware blocks and deploying to browsers for free with an open workflow.
Presentation.pptx
Presentation.pptxNaor Tedgi Node.js streams and asynchronous generators can help address issues around large data processing. Streams provide a way to handle data incrementally through pipes and avoid loading large amounts into memory at once. There are readable and writable stream types, with duplex and transform streams allowing bidirectional data flow and in-flight transformations. Custom streams can be created by extending the Readable or Writable class and implementing required methods. While streams help process data asynchronously, their documentation and APIs could be improved to be more intuitive and consistent.
Node.js File system & Streams
Node.js File system & StreamsEyal Vardi The document discusses Node.js streams and provides examples of how to create and use streams. It explains that streams are used for operations involving files, TCP sockets, child processes, and more. Examples are given for creating readable and writable streams, piping streams together, gzip compression with streams, and implementing the readable stream interface. Stream classes like Readable, Writable, Duplex and Transform are also briefly explained.
Nodejs - A quick tour (v4)
Nodejs - A quick tour (v4)Felix Geisendörfer - Node.js is a platform for building scalable network applications. It uses non-blocking I/O and event-driven architecture to handle many connections concurrently using a single-threaded event loop.
- Node.js uses Google's V8 JavaScript engine and provides a module system, I/O bindings, and common protocols to build network programs easily. Popular uses include real-time web applications, file uploading, and streaming.
- While Node.js is ready for many production uses, things like lost stack traces and limited ability to utilize multiple cores present challenges for some workloads. However, an active community provides support through mailing lists, IRC, and over 1,000 modules in its package manager.
Node.js - A practical introduction (v2)
Node.js - A practical introduction (v2)Felix Geisendörfer This document provides an introduction to Node.js including its history, uses, advantages, and community. It describes how Node.js uses non-blocking I/O and JavaScript to enable highly scalable applications. Examples show how Node.js can run HTTP servers and handle streaming data faster than traditional blocking architectures. The document recommends Node.js for real-time web applications and advises against using it for hard real-time systems or CPU-intensive tasks. It encourages participation in the growing Node.js community on mailing lists and IRC.
Node.js web-based Example :Run a local server in order to start using node.js...
Node.js web-based Example :Run a local server in order to start using node.js...Kongu Engineering College, Perundurai, Erode
Ad
More from Tom Croucher (20)
Using Node.js to improve the performance of Mobile apps and Mobile web
Using Node.js to improve the performance of Mobile apps and Mobile webTom Croucher The document is a presentation about using Node.js to improve mobile app and mobile web performance. It discusses how Node.js can help address issues like high latency on mobile networks by allowing for event-driven and asynchronous server-side code. It also covers how Node.js helps optimize resource usage on mobile devices.
Creating the Internet of Things with JavaScript - Fluent Conf
Creating the Internet of Things with JavaScript - Fluent ConfTom Croucher This document discusses how JavaScript is well-suited for creating applications for the Internet of Things. It notes that batteries and network bandwidth have improved over time based on various laws, but batteries have improved more slowly. It advocates for an event-driven programming model where devices only transmit interesting event data rather than a continuous stream of sensor data. This reduces power consumption and data transmission costs. JavaScript is highlighted as an easy way to create dynamic IoT applications that can be updated over the network. Example IoT development platforms that use JavaScript like BeagleBone and NinjaBlocks are also mentioned.
Using Node.js to make HTML5 work for everyone
Using Node.js to make HTML5 work for everyone Tom Croucher The document discusses using Node.js to build scalable server-side code with JavaScript in a way that works for all users regardless of device or browser capabilities. It covers topics like balancing goals of speed, maintainability and cost when building applications that need to work across computers, mobile phones and other devices with varying processing power and bandwidth. It provides examples of using JSON instead of HTML for lightweight data transfer and techniques like client-side MVC patterns and templates. It also emphasizes the importance of server-side fallbacks for HTML5 features not supported on all browsers to ensure a good experience for all users.
OSCON 2011 - Node.js Tutorial
OSCON 2011 - Node.js TutorialTom Croucher This document provides an overview and summary of a Node.js workshop presented by Tom Hughes-Croucher. The workshop covers:
1. Why use server-side JavaScript and how Node.js enables this through its event-driven and non-blocking architecture.
2. An introduction to Node.js, including how to install Node.js and build basic HTTP servers.
3. More advanced Node.js topics like modules, events, streams, debugging, and popular frameworks like Express.js.
4. Exercises are provided to help attendees get hands-on experience building Node.js applications.
Lessons from a coding veteran - Web Directions @Media
Lessons from a coding veteran - Web Directions @MediaTom Croucher This document provides lessons from a coding veteran organized into 3 rules. Rule 1 is to avoid complexity by having a clear goal, writing understandable code, picking conventions, and using abstraction wisely. Rule 2 is not to optimize too soon, and to rewrite code that is better understood, documenting any optimizations and using tools when possible. Rule 3 acknowledges that rules will be broken for deadlines, but that breaking rules requires cleanup and is not sustainable, advising to focus on Rules 1 and 2 for future success.
Multi-tiered Node Architectures - JSConf 2011
Multi-tiered Node Architectures - JSConf 2011Tom Croucher 1. The document discusses multi-tiered Node.js architectures to improve scalability and efficiency. It suggests moving non-client facing work like logging and processing to separate "farms" or clusters to avoid blocking the main event loop.
2. Another approach presented is to use front-end clusters or "shards" to distribute client requests across multiple Node processes to take advantage of parallel processing. This improves response times.
3. The key goals are to minimize client response times by keeping the main event loop available, while maximizing server resource efficiency by moving heavy processing tasks out of the main process.
Doing Horrible Things with DNS - Web Directions South
Doing Horrible Things with DNS - Web Directions SouthTom Croucher Doing horrible things to DNS involves using CNAME records to create multiple domain names that resolve to the same IP addresses. This allows making a single DNS query but receiving responses for multiple domains, enabling more parallel HTTP requests. The technique involves creating a chain of CNAME records that ultimately resolve to a single canonical name, gaining the ability to load resources from different apparent hostnames while only requiring one DNS lookup.
Doing Horrible Things to DNS in the Name of Science - SF Performance Meetup
Doing Horrible Things to DNS in the Name of Science - SF Performance MeetupTom Croucher The document discusses techniques for improving website performance through modifications to DNS. It describes how serial HTTP loading is slower than parallel loading due to round trip times for DNS lookups. It then evaluates options for implementing parallel DNS lookups, including using CNAME records to alias multiple hostnames to a single IP address, and placing additional IP addresses in the answer or additional sections of DNS responses to allow parallel lookups. While these techniques could improve performance, they may violate DNS standards or caching assumptions.
JavaScript is the new black - Why Node.js is going to rock your world - Web 2...
JavaScript is the new black - Why Node.js is going to rock your world - Web 2...Tom Croucher Node.js allows JavaScript to be used for server-side programming. It is a popular choice because JavaScript programmers can reuse code and libraries on both the client-side and server-side. Node.js is also fast and non-blocking which allows for high concurrency levels. The Node.js ecosystem includes many libraries like Express for building web servers and Mustache.js for templating that make building server-side JavaScript applications easy.
Sf perf
Sf perfTom Croucher The document discusses techniques for improving website performance through modifications to DNS. It describes how serial HTTP loading is slower than parallel loading due to round trip times for DNS lookups. It then evaluates options for implementing parallel DNS lookups, including using CNAME records to alias multiple hostnames to a single IP address, and placing additional IP addresses in the answer or additional sections of DNS responses to allow parallel hostname resolutions. While these techniques could improve performance, they may violate DNS standards or caching assumptions.
Node.js and How JavaScript is Changing Server Programming
Node.js and How JavaScript is Changing Server Programming Tom Croucher The document presents an overview of server-side JavaScript (SSJS) and introduces Node.js, emphasizing its efficiency through non-blocking and event-driven architecture. It highlights the advantages of using JavaScript for server programming, such as code reuse and progressive enhancement, and showcases basic Node.js server code examples. Additionally, it discusses the Node.js ecosystem and the importance of libraries like Mustache.js for rendering HTML.
Server Side JavaScript - You ain't seen nothing yet
Server Side JavaScript - You ain't seen nothing yetTom Croucher This document discusses using JavaScript on the server side with Node.js and the YUI framework. It begins by explaining why server-side JavaScript is useful and discusses JavaScript runtimes like V8, SpiderMonkey, and Rhino. It then covers Node.js, CommonJS frameworks, and how to use YUI modules on the server by enabling YUI's module loader. Examples are provided for accessing remote data, rendering HTML on the server, and implementing progressive enhancement.
JavaScript Everywhere! Creating a 100% JavaScript web stack
JavaScript Everywhere! Creating a 100% JavaScript web stackTom Croucher The document discusses the integration of YUI3 with Node.js, highlighting its server-side capabilities, non-blocking I/O, and modular structure. The presentation emphasizes the efficiency of using JavaScript libraries on the server alongside YUI’s features for managing remote data and DOM manipulation. Key resources and examples showcase the functionality of YUI3 in the Node.js environment, demonstrating its potential for creating dynamic applications.
Mobile Data: How to avoid the latency trap - SWDC 2010
Mobile Data: How to avoid the latency trap - SWDC 2010Tom Croucher The document discusses reducing latency when making requests to web services from mobile devices. It describes several techniques to avoid the "latency trap" including reducing the number of sequential requests, optimizing packet sizes, using Yahoo! Query Language (YQL) to bundle requests, and reducing the number of packets. YQL provides a way to consolidate data from multiple sources into one request, helping to minimize latency issues on mobile.
Let's run JavaScript Everywhere
Let's run JavaScript EverywhereTom Croucher This document discusses how server-side JavaScript is gaining popularity through frameworks like Node.js. It notes JavaScript can now be run on both the client-side through browsers and server-side through engines like V8, SpiderMonkey, and Rhino. Server-side JavaScript allows the same code to run on both client and server. The document also highlights how the YUI framework can be used with Node.js to build full-stack JavaScript applications that leverage YUI modules on both the front-end and back-end.
Pirate yql
Pirate yqlTom Croucher The document promotes using Yahoo Query Language (YQL) for "pirating" or accessing data from various sources, as demonstrated through pirate-themed jokes and references to plundering data from the "seven seas." It encourages visiting the YQL console and building something "arrrsome" with YQL, while providing links for more information.
YQL Tutorial
YQL TutorialTom Croucher The document contains code snippets and text related to Yahoo Query Language (YQL), including examples of using YQL to retrieve data from APIs and services like Flickr, weather, maps and more. It demonstrates how to structure YQL queries to search for images, get weather forecasts for locations, and retrieve geolocation data to plot markers on a map. The document also discusses using YQL with JavaScript and developing applications using YQL programmatically.
How to avoid the latency trap and lessons about software design
How to avoid the latency trap and lessons about software designTom Croucher The document discusses strategies for avoiding the latency trap when designing mobile applications and web services. It recommends reducing the number of requests made to servers by bundling requests and gzipping responses. It also suggests shaping data into packets in a way that minimizes the number of packets, such as ensuring static assets fit into discrete packet boundaries. The document then introduces Yahoo Query Language (YQL) as a way to unify access to web services and bundle requests from mobile devices without needing a dedicated backend. It provides an example of using YQL to search Flickr photos.
Ad
Recently uploaded (20)
The Future of Technology: 2025-2125 by Saikat Basu.pdf
The Future of Technology: 2025-2125 by Saikat Basu.pdfSaikat Basu A peek into the next 100 years of technology. From Generative AI to Global AI networks to Martian Colonisation to Interstellar exploration to Industrial Nanotechnology to Artificial Consciousness, this is a journey you don't want to miss. Which ones excite you the most? Which ones are you apprehensive about? Feel free to comment! Let the conversation begin!
Salesforce Summer '25 Release Frenchgathering.pptx.pdf
Salesforce Summer '25 Release Frenchgathering.pptx.pdfyosra Saidani Salesforce Summer '25 Release Frenchgathering.pptx.pdf
You are not excused! How to avoid security blind spots on the way to production
You are not excused! How to avoid security blind spots on the way to productionMichele Leroux Bustamante We live in an ever evolving landscape for cyber threats creating security risk for your production systems. Mitigating these risks requires participation throughout all stages from development through production delivery - and by every role including architects, developers QA and DevOps engineers, product owners and leadership. No one is excused! This session will cover examples of common mistakes or missed opportunities that can lead to vulnerabilities in production - and ways to do better throughout the development lifecycle.
OWASP Barcelona 2025 Threat Model Library
OWASP Barcelona 2025 Threat Model LibraryPetraVukmirovic Threat Model Library Launch at OWASP Barcelona 2025
https://owasp.org/www-project-threat-model-library/
" How to survive with 1 billion vectors and not sell a kidney: our low-cost c...
" How to survive with 1 billion vectors and not sell a kidney: our low-cost c...Fwdays Let's talk about our history. How we started the project with a small vector database of less than 2 million records. Later, we received a request for +100 million records, then another +100... And so gradually we reached almost 1 billion. Standard tools were quickly running out of steam - we were running into performance, index size, and very limited resources. After a long series of trials and errors, we built our own low-cost cluster, which today stably processes thousands of queries to more than 1B vectors.
Techniques for Automatic Device Identification and Network Assignment.pdf
Techniques for Automatic Device Identification and Network Assignment.pdfPriyanka Aash Techniques for Automatic Device Identification and Network Assignment
EIS-Webinar-Engineering-Retail-Infrastructure-06-16-2025.pdf
EIS-Webinar-Engineering-Retail-Infrastructure-06-16-2025.pdfEarley Information Science As AI reshapes expectations in retail and B2B commerce, organizations are recognizing a critical reality: meaningful AI outcomes depend on well-structured, adaptable infrastructure. In this session, Seth Earley is joined by Phil Ryan - AI strategist, search technologist, and founder of Glass Leopard Technologies - for a candid conversation on what it truly means to engineer systems for scale, agility, and intelligence.
Phil draws on more than two decades of experience leading search and AI initiatives for enterprise organizations. Together, he and Seth explore the challenges businesses face when legacy architectures limit personalization, agility, and real-time decisioning - and what needs to change to support agentic technologies and next-best-action capabilities.
Key themes from the webinar include:
Composability as a prerequisite for AI - Why modular, loosely coupled systems are essential for adapting to rapid innovation and evolving business needs
Search and relevance as foundational to AI - How techniques honed-in enterprise search have laid the groundwork for more responsive and intelligent customer experiences
From MDM and CDP to agentic systems - How data platforms are evolving to support richer customer context and dynamic orchestration
Engineering for business alignment - Why successful AI programs require architectural decisions grounded in measurable outcomes
The conversation is practical and forward-looking, connecting deep technical understanding with real-world business needs. Whether you’re modernizing your commerce stack or exploring how AI can enhance product discovery, personalization, or customer journeys, this session provides a clear-eyed view of the capabilities, constraints, and priorities that matter most.
OpenPOWER Foundation & Open-Source Core Innovations
OpenPOWER Foundation & Open-Source Core InnovationsIBM penPOWER offers a fully open, royalty-free CPU architecture for custom chip design.
It enables both lightweight FPGA cores (like Microwatt) and high-performance processors (like POWER10).
Developers have full access to source code, specs, and tools for end-to-end chip creation.
It supports AI, HPC, cloud, and embedded workloads with proven performance.
Backed by a global community, it fosters innovation, education, and collaboration.
The Future of Product Management in AI ERA.pdf
The Future of Product Management in AI ERA.pdfAlyona Owens Hi, I’m Aly Owens, I have a special pleasure to stand here as over a decade ago I graduated from CityU as an international student with an MBA program. I enjoyed the diversity of the school, ability to work and study, the network that came with being here, and of course the price tag for students here has always been more affordable than most around.
Since then I have worked for major corporations like T-Mobile and Microsoft and many more, and I have founded a startup. I've also been teaching product management to ensure my students save time and money to get to the same level as me faster avoiding popular mistakes. Today as I’ve transitioned to teaching and focusing on the startup, I hear everybody being concerned about Ai stealing their jobs… We’ll talk about it shortly.
But before that, I want to take you back to 1997. One of my favorite movies is “Fifth Element”. It wowed me with futuristic predictions when I was a kid and I’m impressed by the number of these predictions that have already come true. Self-driving cars, video calls and smart TV, personalized ads and identity scanning. Sci-fi movies and books gave us many ideas and some are being implemented as we speak. But we often get ahead of ourselves:
Flying cars,Colonized planets, Human-like AI: not yet, Time travel, Mind-machine neural interfaces for everyone: Only in experimental stages (e.g. Neuralink).
Cyberpunk dystopias: Some vibes (neon signs + inequality + surveillance), but not total dystopia (thankfully).
On the bright side, we predict that the working hours should drop as Ai becomes our helper and there shouldn’t be a need to work 8 hours/day. Nobody knows for sure but we can require that from legislation. Instead of waiting to see what the government and billionaires come up with, I say we should design our own future.
So, we as humans, when we don’t know something - fear takes over. The same thing happened during the industrial revolution. In the Industrial Era, machines didn’t steal jobs—they transformed them but people were scared about their jobs. The AI era is making similar changes except it feels like robots will take the center stage instead of a human. First off, even when it comes to the hottest space in the military - drones, Ai does a fraction of work. AI algorithms enable real-time decision-making, obstacle avoidance, and mission optimization making drones far more autonomous and capable than traditional remote-controlled aircraft. Key technologies include computer vision for object detection, GPS-enhanced navigation, and neural networks for learning and adaptation. But guess what? There are only 2 companies right now that utilize Ai in drones to make autonomous decisions - Skydio and DJI.
cnc-processing-centers-centateq-p-110-en.pdf
cnc-processing-centers-centateq-p-110-en.pdfAmirStern2 מרכז עיבודים תעשייתי בעל 3/4/5 צירים, עד 22 החלפות כלים עם כל אפשרויות העיבוד הדרושות. בעל שטח עבודה גדול ומחשב נוח וקל להפעלה בשפה העברית/רוסית/אנגלית/ספרדית/ערבית ועוד..
מסוגל לבצע פעולות עיבוד שונות המתאימות לענפים שונים: קידוח אנכי, אופקי, ניסור, וכרסום אנכי.
"How to survive Black Friday: preparing e-commerce for a peak season", Yurii ...
"How to survive Black Friday: preparing e-commerce for a peak season", Yurii ...Fwdays We will explore how e-commerce projects prepare for the busiest time of the year, which key aspects to focus on, and what to expect. We’ll share our experience in setting up auto-scaling, load balancing, and discuss the loads that Silpo handles, as well as the solutions that help us navigate this season without failures.
10 Key Challenges for AI within the EU Data Protection Framework.pdf
10 Key Challenges for AI within the EU Data Protection Framework.pdfPriyanka Aash 10 Key Challenges for AI within the EU Data Protection Framework
Oh, the Possibilities - Balancing Innovation and Risk with Generative AI.pdf
Oh, the Possibilities - Balancing Innovation and Risk with Generative AI.pdfPriyanka Aash Oh, the Possibilities - Balancing Innovation and Risk with Generative AI
WebdriverIO & JavaScript: The Perfect Duo for Web Automation
WebdriverIO & JavaScript: The Perfect Duo for Web Automationdigitaljignect In today’s dynamic digital landscape, ensuring the quality and dependability of web applications is essential. While Selenium has been a longstanding solution for automating browser tasks, the integration of WebdriverIO (WDIO) with Selenium and JavaScript marks a significant advancement in automation testing. WDIO enhances the testing process by offering a robust interface that improves test creation, execution, and management. This amalgamation capitalizes on the strengths of both tools, leveraging Selenium’s broad browser support and WDIO’s modern, efficient approach to test automation. As automation testing becomes increasingly vital for faster development cycles and superior software releases, WDIO emerges as a versatile framework, particularly potent when paired with JavaScript, making it a preferred choice for contemporary testing teams.
“MPU+: A Transformative Solution for Next-Gen AI at the Edge,” a Presentation...
“MPU+: A Transformative Solution for Next-Gen AI at the Edge,” a Presentation...Edge AI and Vision Alliance For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2025/06/mpu-a-transformative-solution-for-next-gen-ai-at-the-edge-a-presentation-from-fotonation/
Petronel Bigioi, CEO of FotoNation, presents the “MPU+: A Transformative Solution for Next-Gen AI at the Edge” tutorial at the May 2025 Embedded Vision Summit.
In this talk, Bigioi introduces MPU+, a novel programmable, customizable low-power platform for real-time, localized intelligence at the edge. The platform includes an AI-augmented image signal processor that enables leading image and video quality.
In addition, it integrates ultra-low-power object and motion detection capabilities to enable always-on computer vision. A programmable neural processor provides flexibility to efficiently implement new neural networks. And additional specialized engines facilitate image stabilization and audio enhancements.
From Manual to Auto Searching- FME in the Driver's Seat
From Manual to Auto Searching- FME in the Driver's SeatSafe Software Finding a specific car online can be a time-consuming task, especially when checking multiple dealer websites. A few years ago, I faced this exact problem while searching for a particular vehicle in New Zealand. The local classified platform, Trade Me (similar to eBay), wasn’t yielding any results, so I expanded my search to second-hand dealer sites—only to realise that periodically checking each one was going to be tedious. That’s when I noticed something interesting: many of these websites used the same platform to manage their inventories. Recognising this, I reverse-engineered the platform’s structure and built an FME workspace that automated the search process for me. By integrating API calls and setting up periodic checks, I received real-time email alerts when matching cars were listed. In this presentation, I’ll walk through how I used FME to save hours of manual searching by creating a custom car-finding automation system. While FME can’t buy a car for you—yet—it can certainly help you find the one you’re after!
"Database isolation: how we deal with hundreds of direct connections to the d...
"Database isolation: how we deal with hundreds of direct connections to the d...Fwdays What can go wrong if you allow each service to access the database directly? In a startup, this seems like a quick and easy solution, but as the system scales, problems appear that no one could have guessed.
In my talk, I'll share Solidgate's experience in transforming its architecture: from the chaos of direct connections to a service-based data access model. I will talk about the transition stages, bottlenecks, and how isolation affected infrastructure support. I will honestly show what worked and what didn't. In short, we will analyze the controversy of this talk.
Wenn alles versagt - IBM Tape schützt, was zählt! Und besonders mit dem neust...
Wenn alles versagt - IBM Tape schützt, was zählt! Und besonders mit dem neust...Josef Weingand IBM LTO10
Mastering AI Workflows with FME by Mark Döring
Mastering AI Workflows with FME by Mark DöringSafe Software Harness the full potential of AI with FME: From creating high-quality training data to optimizing models and utilizing results, FME supports every step of your AI workflow. Seamlessly integrate a wide range of models, including those for data enhancement, forecasting, image and object recognition, and large language models. Customize AI models to meet your exact needs with FME’s powerful tools for training, optimization, and seamless integration
You are not excused! How to avoid security blind spots on the way to production
You are not excused! How to avoid security blind spots on the way to productionMichele Leroux Bustamante
“MPU+: A Transformative Solution for Next-Gen AI at the Edge,” a Presentation...
“MPU+: A Transformative Solution for Next-Gen AI at the Edge,” a Presentation...Edge AI and Vision Alliance
Using Node.js to Build Great Streaming Services - HTML5 Dev Conf
- 1. Using Node.js to Build Great Streaming Services @sh1mmer
- 2. Tom Hughes-Croucher @sh1mmer
- 3. @sh1mmer
- 4. @sh1mmer
- 5. Scalable Server-Side Code with JavaScript Node Up and Running Tom Hughes-Croucher http://ofps.oreilly.com/titles/9781449398583/ http://shop.oreilly.com/product/0636920015956.do @sh1mmer
- 8. @sh1mmer
- 9. @sh1mmer
- 10. var http = require('http'); var server = http.createServer(); server.listen(8000); server.on('request', function(req,res) { var doodad = new Doodad(); res.writeHead(200,{'Content-Type':'text/doodad'}); res.end(doodad); }); @sh1mmer
- 12. Knobs Screens Antennas & buttons @sh1mmer
- 13. @sh1mmer
- 14. @sh1mmer
- 15. @sh1mmer
- 16. @sh1mmer
- 17. @sh1mmer
- 18. var http = require('http'), fs = require('fs'); var server = http.createServer(); server.listen(8000); server.on('request', function(req,res) { var screen = fs.readFileSync('/factory1/screen'); var dial = fs.readFileSync('/factory2/dial'); var doodad = new Doodad(screen, dial); res.writeHead(200,{'Content-Type':'text/doodad'}); res.end(doodad); }); @sh1mmer
- 19. Improving the factory with streaming @sh1mmer
- 20. @sh1mmer
- 21. @sh1mmer
- 22. @sh1mmer
- 23. var http = require('http'); var server = http.createServer(); server.listen(8000); server.on('request', function(req,res) { var parts = 0; http.get('factory1/screen/', function(res) { var screen = ""; res.on('data', function(d) { screen += d }); res.on('end', finish); parts++; }; http.get('factory2/dial', function(res) { var dial = "" res.on('data', function(d) { dial += d }); res.on('end', finish); parts++; } function finish() { if(parts == 2) { var doodad = new Doodad(screen, dial); res.writeHead(200,{'Content-Type':'text/doodad'}); res.end(doodad); } } }); @sh1mmer
- 25. Streams • Readable • Writable • 'data' event • write() • 'end' event • end() • pause() • resume() • 'drain' event • destroy() • destroy() • pipe() • destroySoon() @sh1mmer
- 26. var stream = require('stream'); var s = new stream.Stream(); //I am an EventEmitter s.readable = true; //now I implement read API s.emit('data', "my data"); s.emit('end'); //I'm done sending data @sh1mmer
- 27. var stream = require('stream'); var s = new stream.Stream(); //I am an EventEmitter s.writable = true; //now I implement write API s.data = ""; s.write = function(d) { s.data += d; }; s.end = function() { if(s.data) { console.log(s.data) } }; s.destroy = function() { s.writable = false; } @sh1mmer
- 28. The too many parts problem and why phone calls don't work @sh1mmer
- 29. @sh1mmer
- 30. nextTick Event Loop Fail nextTick Run stuff TCP Conn node.cc FS Read add-ons v8 TCP Conn Timeout libuv TCP Interval Conn libev iocp FS Timeout Read FS Read
- 31. stream.pause()
- 32. nextTick Event Loop Fail nextTick stream.pause() TCP Conn node.cc FS Read add-ons v8 TCP Conn Timeout libuv TCP Interval Conn libev iocp FS Timeout Read FS Read
- 33. Managing Backpressure • Manage Buffer sizes • Use pause() / resume() to control back pressure • Assume that 'data' event may happen after pause • Remember node buffer -> kernel buffer @sh1mmer
- 34. //manage Node's write Buffers if(socket.bufferSize > maxSafe) { writeStream.pause(); } //Manage RS read stream Buffers fs.createReadStream('./path/to/file', { flags: 'r', encoding: null, fd: null, mode: 0666, bufferSize: 64 * 1024 }); @sh1mmer
- 35. New API @sh1mmer
- 36. New Streams TBD • Writable streams • Same • Readable (https://github.com/isaacs/readable-stream) • configurable stream buffer waterline • 'readable' event • read(len) -> returns data • Pipe • Subscribers must implement readable stream • No more direct access with Pipe
- 37. @sh1mmer
- 39. Simplex @sh1mmer
- 40. var fs = require('fs'); var rs = fs.createReadStream('/my/file/path'); rs.on('data', function(d) { console.log(d); }); @sh1mmer
- 42. var fs = require('fs'); var rs = fs.createReadStream('/my/file/path'); rs.pipe(process.stdout); @sh1mmer
- 43. Duplex @sh1mmer
- 44. var bot1 = new chatterBot(); var bot2 = new chatterBot(); bot1.pipe(bot2).pipe(bot1); @sh1mmer
- 47. {"total_rows":129,"offset":0,"rows":[ { "id":"change1_0.6995461115147918" , "key":"change1_0.6995461115147918" , "value":{"rev":"1-e240bae28c7bb3667f02760f6398d508"} , "doc":{ "_id": "change1_0.6995461115147918" , "_rev": "1-e240bae28c7bb3667f02760f6398d508","hello":1} }, { "id":"change2_0.6995461115147918" , "key":"change2_0.6995461115147918" , "value":{"rev":"1-13677d36b98c0c075145bb8975105153"} , "doc":{ "_id":"change2_0.6995461115147918" , "_rev":"1-13677d36b98c0c075145bb8975105153" , "hello":2 } }, ]} @sh1mmer
- 48. var stream = JSONStream.parse(['rows', true, 'doc']) //rows, ANYTHING, doc stream.on('data', function(data) { console.log('received:', data); }); stream.on('root', function(root, count) { if (!count) { console.log('no matches found:', root); } }); @sh1mmer