Resin Outperforms NginX

Presented at Web Unleashed 2019 More info at www.fitc.ca/webu Luke DeWitt REDspace Overview JavaScript’s popularity has exploded over the last decade, taking it from a laughable scripting language to one that powers much of the web today. Because it’s so flexible and so easy to learn, it’s extremely popular with new developers looking to cut their teeth in programming. However, these strengths are also weaknesses, as it’s incredibly easy to write bad JavaScript without even knowing it. A lot of these newer developers jump from “Hello, World!”, to TodoMVC in order to find the library that makes their life easier. By doing this, they skip over some of the important details of not only how JavaScript works, but also how to optimize its performance to ensure the best user experience. The Chrome profiler is a very handy tool that not a lot of developers have experience with. In this talk, we’ll take a beginner’s look at the profiler tool and examine how to use it to best improve your web application, and identify bottlenecks in your code without having to rely only on console.log statements. Objective To help developers understand how to better make use of the JavaScript profiler. Target Audience Any JavaScript developers Assumed Audience Knowledge Basic JavaScript Level Beginner / intermediate Five Things Audience Members Will Learn Javascript inner-workings Profiling concepts Identifying bottlenecks Profiling node applications Tooling

WebSocket is a protocol that provides bidirectional communication over a single TCP connection. It uses an HTTP handshake to establish a connection and then transmits messages as frames that can contain text or binary data. The frames include a header with metadata like opcode and payload length. WebSocket aims to provide a standard for browser-based applications that require real-time data updates from a server.

Presented at FITC Toronto 2019 More info at www.fitc.ca/toronto Chris Zacharias imgix Overview The average website loads over 1.5MBs of content per page, making over 75 requests. Many popular websites are serving over 5MBs just to load their homepages. And these numbers represent measurements taken AFTER compression is applied. The full weight of many popular websites is pushing 20+ MBs these days. In an era where performance truly matters to the end user experience, web developers need techniques to help curtail this bloat in data down the wire. No matter how well you optimize, there is no better way to than to delete things you do not need. How does one determine what is essential to the user experience and what is not? One answer Chris posits is to develop a hyper-lightweight version of your website which will provide critical insights into your specific performance priorities. This is a process that he has leveraged on many projects, in particular at YouTube to reduce the size of the video watch page from 1.5MBs to 100KBs. In this talk, Chris will take real-world web pages and show techniques for dramatically reducing their page weight and for identifying areas to optimize, while outlining the key steps to doing this well. Objective Learn a process for building a hyper-lightweight version of your website for establishing reasonable performance budgets, grounded in reality, to work from. Target Audience Web developers Assumed Audience Knowledge HTML, CSS, Javascript, some server-side awareness. Level Intermediate Five Things Audience Members Will Learn How to analyze a web page for performance issues A holistic approach to deconstructing an existing website A clear process for building a hyper-lightweight version of your website Translating your findings into real performance priorities Establishing a realistic performance budget

This document discusses best practices for designing, scaling, and maintaining large-scale web applications. Some of the key points made include: having a consistent and flexible data model, loosely coupling components for easier testing and replacement, using caching strategies like page fragments and memcached, and emphasizing development practices like version control, testing, and monitoring performance. The document advocates for a modular architecture with components like load balancers, reverse proxies, caching layers, and asynchronous job queues.

This document provides an overview and introduction to Apache Camel, an open-source integration library. It discusses what integration is and why it is difficult. It then introduces Apache Camel as a lightweight integration library that uses enterprise integration patterns and components to provide routing, mediation, and transformation capabilities. The document provides examples of how to define integration logic in Camel using Java and XML domain-specific languages. It also discusses Camel's support for enterprise integration patterns, pre-built components, testing framework, and management capabilities.

This document provides an overview of Apache ActiveMQ, an open-source messaging server. It discusses ActiveMQ's features such as high performance, high availability, multiple protocols and transports. It also covers tools for benchmarking and performance tuning ActiveMQ brokers, including the ActiveMQ Performance Module, jms-benchmark, JMSTester, JMeter and OS monitoring tools. The document is intended to help understand how to approach performance tuning of ActiveMQ brokers.

The document discusses using Apache Camel and Apache Karaf to build distributed, asynchronous systems in a similar way to AKKA. It provides examples of building a dynamic routing system using Camel routing and JMS, as well as a modular ETL system for processing CSV files using a configurable, hot-deployable mutation framework. The examples demonstrate how to achieve scalability, modularity, and asynchronous behavior without deep knowledge of the underlying technologies through an event-driven architecture based on messaging.

Presentation by Peter Lubbers and Frank Salim presented at the San Francisco HTML5 User Group/GTUGSF Code Lab.

This document discusses how to integrate Grails applications with various enterprise systems and processes. It covers integrating Grails with build tools like Ant and Maven, managing dependencies, connecting to legacy databases, deploying applications, and integrating with Spring frameworks for messaging, web services, and other enterprise features. Grails can work with many external systems through plugins, custom ORM mappings, and by treating Grails as a Spring application. This allows Grails applications to fit into a variety of enterprise environments and development processes.

Apache Camel is a powerful open source integration framework that allows developers to focus on business logic by hiding complexity. It supports over 80 components and 19 data formats, and provides a domain-specific language for integration patterns in Java, XML, and Scala. Camel routes can be run in standalone applications or deployed to various containers.

We start with an introduction to what Apache Camel is, and how you can use Camel to make integration much easier. Allowing you to focus on your business logic, rather than low level messaging protocols, and transports. You will also hear what other features Camel provides out of the box, which can make integration much easier for you. We look into web console tooling that allows you to get insight into your running Apache Camel applications, which has among others visual route diagrams with tracing/debugging and profiling capabilities. In addition to the web tooling we will also show you other tools in the making.

The document summarizes TorqueBox, which allows Ruby applications to run on the JBoss Application Server. TorqueBox combines JRuby and JBoss AS to provide features like clustering, load balancing, high availability, messaging, background jobs, and long-running services to Ruby applications. It allows Ruby applications to leverage Java libraries and tools while retaining the simplicity and flexibility of Ruby.

TorqueBox allows developers to build and deploy Rack and JRuby applications on JBoss Application Server. It provides features such as background processing, scheduling, services and clustering out of the box. TorqueBox makes use of JRuby's Java integration to provide a fast Ruby runtime and access to Java libraries and tools. It aims to provide all the capabilities of a full application server while allowing developers to work in Ruby and avoid technologies like XML, Java code and WAR files. Setting up TorqueBox involves downloading the distribution, exporting some environment variables and using Rake tasks to deploy and manage applications.

This presentation describes Event Driven Architecture(EDA) support in Camel, and scalability features like SEDA and Akka support in Camel.It starts with an overview of Camel and introduces its simple syntax

This document provides an overview of HTML5 WebSocket technology. It discusses limitations of traditional HTTP and how WebSocket enables full-duplex communication by reducing overhead and latency compared to alternative techniques like polling. The WebSocket API and protocol are introduced, along with browser support and server library options. Key benefits of WebSocket include unlimited connections per server, very small overhead, and true real-time bidirectional communication across the web.