The talk presented by James Strachan (Red Hat) on the 6th of March 2013 at the London JBoss USer Group event.
Visit London JBUG on Meetup http://www.meetup.com/JBoss-User-Group/
- The document discusses optimizing Java performance on hardware by leveraging features like AES-NI, transparent huge pages, and compiler intrinsics.
- It provides examples showing performance improvements from using these features, such as faster encryption times when enabling AES-NI and fewer TLB misses with transparent huge pages.
- It also discusses Java VM options, garbage collection, and the HotSpot compiler related to hardware optimization.
Head toward Java 14 and Java 15 #LINE_DMYuji Kubota
Java 14 and 15 introduced several new features and changes including records, pattern matching, text blocks, and updates to the garbage collector. Some notable changes were the addition of records as a new data type, enabling pattern matching for instanceof, and deprecating biased locking and the CMS garbage collector. Tools were also improved with the packaging tool to create installers and event streaming to collect JVM events.
This document discusses new features and changes in Java 14 and previews for Java 15. For Java 14, it outlines 16 JEPs including helpful null pointer exceptions, NUMA-aware memory allocation, and removing legacy garbage collectors. It also covers new tools like JFR event streaming and the packaging tool. For Java 15, hidden classes, removing Nashorn, and low-latency garbage collectors like ZGC and Shenandoah are previewed. Overall it provides a concise yet informative summary of major changes and previews for Java 14 and 15.
Introduction httpClient on Java11 / Java11時代のHTTPアクセス再入門tamtam180
This document provides an overview and refreshers on HTTP access in Java 11. It discusses HttpUrlConnection, Apache HttpClient, and Java's new HttpClient. For HttpUrlConnection, it covers GET requests, modifying request methods and headers, sending request bodies, cookies, proxies, redirects, basic authentication, and debugging. For Apache HttpClient, it discusses GET requests, Accept headers, gzip encoding, query strings, connection pools, modifying request headers and POST requests. It also covers cookies, redirects, retries and proxies for Apache HttpClient.
A preview of likely features that will be included in Java 7 / JDK 7. Note that this presentation is from February 2009 and things are changing quickly.
The document discusses slowdowns, hangs, and thread dumps in troubleshooting Java applications. It explains that thread dumps provide a snapshot of thread states and what each thread is doing at a point in time. This can help identify issues like threads getting stuck or competing for resources. The document also demonstrates example output of a thread dump with threads in different states like waiting and provides tips for analyzing thread dumps to diagnose performance problems.
The Java EE 7 Platform: Productivity & HTML5 at JavaOne Latin America 2012Arun Gupta
The document discusses new features and improvements in Java EE 7 including higher productivity through less boilerplate code and richer functionality, support for HTML5 technologies like WebSockets and JSON, and simplified APIs for RESTful web services, Java Message Service, and JSON processing. Key areas of focus for Java EE 7 are improving developer productivity and adding support for HTML5.
Writing concurrent code that is also correct is unbelievably hard. Naturally, humanity has developed a number of approaches to handle concurrency in the code, starting from basic threads that follow the hardware way to do concurrency to higher level primitives like fibers and work-stealing solutions. But which approach is the best for you? In this session, we'll take a look at a simple concurrent problem and solve it using different ways to manage concurrency: threads, executors, actors, fibers, monadic code with completable futures. All these approaches are different from the simplicity, readability, configuration and management point of view. Some scenarios are better modelled with threads, while sometimes you're better off with actors. We'll discuss the benefits of each approach and figure out when it's worth pursuing in your project.
LyonJUG : Comment Jigsaw est prêt à tuer le classpathAlexis Hassler
Présentation au LyonJUG le 17 octobre 2015.
En 2009, la mort du classpath a été annoncée. Les classloaders à plat ou hiérarchiques devaient être remplacés par des systèmes modulaires et tous nos problèmes de dépendance devaient se résoudre d'eux-mêmes. C'est le projet Jigsaw qui devait accomplir cette tâche. Il sera finalement intégré au JDK 9 dont la sortie est prévue pour 2017.
Dans la première partie de cette présentation, on revient sur le fonctionnement des classloaders du JDK et on voit au travers quelques exemples les problèmes étranges qu'ils posent.
Dans la deuxième partie, on présente ce que Jigsaw va apporter et expliquera quels problèmes il va résoudre. On compare Jigsaw aux solutions qui existent déjà, comme OSGi et JBoss Modules.
Nashorn: JavaScript Running on Java VM (English)Logico
This document discusses Nashorn, Oracle's JavaScript engine for the Java Virtual Machine (JVM). Nashorn allows JavaScript code to run directly on the JVM. The presentation provides an overview of Nashorn and how it can be used for server-side JavaScript applications. It demonstrates how to invoke Nashorn from Java code and Java/JavaFX from JavaScript. It also covers Nashorn extensions for interacting with Java types and objects from JavaScript.
Nashorn : JavaScript Running on Java VM (Japanese)Logico
This document provides an overview of Nashorn, Oracle's JavaScript engine that runs on the Java Virtual Machine (JVM). Some key points:
- Nashorn replaces the previous Rhino JavaScript engine for better performance and security.
- It aims to be fully compatible with ECMAScript 5.1 and supports calling Java from JavaScript and vice versa.
- Features include a new command line tool called jjs and extensions that make JavaScript more suitable for server-side scripting on the JVM.
- Future areas of focus include better support for ECMAScript 6 features and integration with Java APIs and technologies.
The document provides instructions for setting up a Java and Flex application to connect to a MySQL database using Hibernate. It describes downloading required software, creating the database structure, writing the Java and Flex code, and configuring Hibernate and the Flex data services to enable bidirectional data binding between the front-end Flex UI and backend Java/database.
El desarrollo de aplicaciones en diversas plataformas y lenguajes en una empresa, es un caso de uso muy común que se presenta a lo largo del tiempo. Así mismo, la necesidad de poder integrar los datos de estas diversas aplicaciones, muchas veces incompatibles entre si, lleva a la necesidad de desarrollar aplicaciones que se encarguen del intercambio de estos datos para lograr un consolidado de información que aporte valor a la empresa.
Al momento de diseñar este tipo de aplicaciones, es común el observar patrones una y otra vez. Dichos patrones han sido recopilados y documentados por Gregor Hohpe y Bobby Woolf en su libro "Enterprise Integration Patterns", en el cual ofrecen una visión completa y muy bien explicada de estos patrones, así como de una nomenclatura que se ha vuelto estándar para representar estos patrones.
Apache Camel es la implementación de la gran mayoría de los patrones propuestos por Gregor y Bobby para la plataforma Java y de manera OpenSource bajo licencia Apache 2.0. Apache Camel es una alternativa a diversas herramientas comerciales para realizar aplicaciones empresariales de integración de aplicaciones.
En la conferencia se mostraran los patrones mas comunes, su notación, diseño e implementación usando Apache Camel, de igual manera se mostrara la infraestructura necesaria para ejecutar Apache Camel, los mecanismos de monitoreo de aplicaciones desarrolladas con Camel y como se puede integrar con productos de integración como Brokers de Mensajería (JMS), Enterprise Service Bus (ESB) y servidores de aplicaciones clásicos
AngularJS has become a very popular web development framework. Now that Telerik made Kendo UI open source, this framework is a possible alternative for many web developers. Learn about the differences and similarities.
Apache Camel - FUSE community day London 2010 presentationClaus Ibsen
My Apache Camel presentation from the FUSE community day event, London June 2010.
A video/audio/transcript of the presentation is in the works and will later be published at the fusesource (http://fusesource.com) website.
Using apache camel for microservices and integration then deploying and managing on Docker and Kubernetes. When we need to make changes to our app, we can use Fabric8 continuous delivery built on top of Kubernetes and OpenShift.
This document discusses integration in the age of DevOps. It describes how microservices help solve the problem of decoupling services and teams to move quickly at scale. Apache Camel is presented as a solution for integration that allows for reliable and distributed integration through mechanisms like messaging. Kubernetes and Docker are discussed as platforms that help develop and run microservices locally and at scale by providing automation, configuration, isolation and service discovery capabilities.
Este documento proporciona una visión general de las técnicas de transformación de datos en Camel, incluyendo el uso de EIPs como Message Translator y Content Enricher, formatos de datos como CSV y JSON, plantillas como Velocity, y el mecanismo de conversión de tipos de Camel. También describe cómo implementar la transformación mediante procesadores, beans y la operación <transform> en XML, con ejemplos de código.
The document discusses microservices and APIs. It covers how microservices optimize for speed by shedding dependencies and having dependencies on demand through services and APIs. It discusses consumer contracts for APIs and service versioning. It also discusses using an API gateway pattern for scalability, security, monitoring and more. It promotes API management for benefits like access control, analytics, and monetization of microservices.
This document provides an overview of integrating microservices with Apache Camel and JBoss Fuse. It introduces Apache Camel as a lightweight integration library that uses enterprise integration patterns and domain-specific languages to define integration "flows" and "routes". It describes how Camel supports features like dynamic routing, REST APIs, backpressure, load balancing, and circuit breakers that are useful for building microservices. The document also introduces JBoss Fuse as a development and runtime platform for microservices that provides tooling, frameworks, management capabilities and container support using technologies like Apache Camel, CXF, ActiveMQ and Karaf.
DevOps with ActiveMQ, Camel, Fabric8, and HawtIO Christian Posta
DevOps and Continuous Delivery slides with Fabric8 (http://fabric8.io), HawtIO (http://hawt.io), Camel, ActiveMQ, Docker Jenkins, etc.
10 yrs ago, SOA promised a lot of the same things Microservices promise use today. So where did we go wrong? What makes microservices different? In this talk, we discussed from an architectural view how we went sideways with SOA, why we must embrace things like Domain Driven Design and scaled-out architectures, and how microservices can be built with enterprises in mind. We also cover a step-by-step, in-depth tutorial that covers these concepts.
Christian Posta is a principal middleware specialist and architect who has worked with large microservices architectures. He discusses why companies are moving to microservices and cloud platforms like Kubernetes and OpenShift. He covers characteristics of microservices like small autonomous teams and decentralized decision making. Posta also discusses breaking applications into independent services, shedding dependencies between teams, and using contracts and APIs for communication between services.
Microservices architecture is a very powerful way to build scalable systems optimized for speed of change. To do this, we need to build independent, autonomous services which by definition tend to minimize dependencies on other systems. One of the tenants of microservices, and a way to minimize dependencies, is “a service should own its own database”. Unfortunately this is a lot easier said than done. Why? Because: your data.
We’ve been dealing with data in information systems for 5 decades so isn’t this a solved problem? Yes and no. A lot of the lessons learned are still very relevant. Traditionally, we application developers have accepted the practice of using relational databases and relying on all of their safety guarantees without question. But as we build services architectures that span more than one database (by design, as with microservices), things get harder. If data about a customer changes in one database, how do we reconcile that with other databases (especially where the data storage may be heterogenous?).
For developers focused on the traditional enterprise, not only do we have to try to build fast-changing systems that are surrounded by legacy systems, the domains (finance, insurance, retail, etc) are incredibly complicated. Just copying with Netflix does for microservices may or may not be useful. So how do we develop and reason about the boundaries in our system to reduce complexity in the domain?
In this talk, we’ll explore these problems and see how Domain Driven Design helps grapple with the domain complexity. We’ll see how DDD concepts like Entities and Aggregates help reason about boundaries based on use cases and how transactions are affected. Once we can identify our transactional boundaries we can more carefully adjust our needs from the CAP theorem to scale out and achieve truly autonomous systems with strictly ordered eventual consistency. We’ll see how technologies like Apache Kafka, Apache Camel and Debezium.io can help build the backbone for these types of systems. We’ll even explore the details of a working example that brings all of this together.
The document discusses Christian Posta's journey with microservices architectures. It begins by explaining why organizations are moving to microservices and defines microservices. It then covers related topics like cloud platforms, container technologies like Kubernetes and OpenShift, benefits and drawbacks of microservices, and tools for developing microservices like Docker, Kubernetes, OpenShift, and Camel.
The document discusses implementing enterprise integration patterns through Apache Camel. It provides an overview of enterprise integration patterns, describes what Apache Camel is and how it is based on these patterns, and gives examples of implementing the Message Filter pattern in XML, Java, Scala and Spring configurations. It also discusses using beans with Camel for message translation and binding beans to endpoints.
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.
Writing concurrent code that is also correct is unbelievably hard. Naturally, humanity has developed a number of approaches to handle concurrency in the code, starting from basic threads that follow the hardware way to do concurrency to higher level primitives like fibers and work-stealing solutions. But which approach is the best for you? In this session, we'll take a look at a simple concurrent problem and solve it using different ways to manage concurrency: threads, executors, actors, fibers, monadic code with completable futures. All these approaches are different from the simplicity, readability, configuration and management point of view. Some scenarios are better modelled with threads, while sometimes you're better off with actors. We'll discuss the benefits of each approach and figure out when it's worth pursuing in your project.
LyonJUG : Comment Jigsaw est prêt à tuer le classpathAlexis Hassler
Présentation au LyonJUG le 17 octobre 2015.
En 2009, la mort du classpath a été annoncée. Les classloaders à plat ou hiérarchiques devaient être remplacés par des systèmes modulaires et tous nos problèmes de dépendance devaient se résoudre d'eux-mêmes. C'est le projet Jigsaw qui devait accomplir cette tâche. Il sera finalement intégré au JDK 9 dont la sortie est prévue pour 2017.
Dans la première partie de cette présentation, on revient sur le fonctionnement des classloaders du JDK et on voit au travers quelques exemples les problèmes étranges qu'ils posent.
Dans la deuxième partie, on présente ce que Jigsaw va apporter et expliquera quels problèmes il va résoudre. On compare Jigsaw aux solutions qui existent déjà, comme OSGi et JBoss Modules.
Nashorn: JavaScript Running on Java VM (English)Logico
This document discusses Nashorn, Oracle's JavaScript engine for the Java Virtual Machine (JVM). Nashorn allows JavaScript code to run directly on the JVM. The presentation provides an overview of Nashorn and how it can be used for server-side JavaScript applications. It demonstrates how to invoke Nashorn from Java code and Java/JavaFX from JavaScript. It also covers Nashorn extensions for interacting with Java types and objects from JavaScript.
Nashorn : JavaScript Running on Java VM (Japanese)Logico
This document provides an overview of Nashorn, Oracle's JavaScript engine that runs on the Java Virtual Machine (JVM). Some key points:
- Nashorn replaces the previous Rhino JavaScript engine for better performance and security.
- It aims to be fully compatible with ECMAScript 5.1 and supports calling Java from JavaScript and vice versa.
- Features include a new command line tool called jjs and extensions that make JavaScript more suitable for server-side scripting on the JVM.
- Future areas of focus include better support for ECMAScript 6 features and integration with Java APIs and technologies.
The document provides instructions for setting up a Java and Flex application to connect to a MySQL database using Hibernate. It describes downloading required software, creating the database structure, writing the Java and Flex code, and configuring Hibernate and the Flex data services to enable bidirectional data binding between the front-end Flex UI and backend Java/database.
El desarrollo de aplicaciones en diversas plataformas y lenguajes en una empresa, es un caso de uso muy común que se presenta a lo largo del tiempo. Así mismo, la necesidad de poder integrar los datos de estas diversas aplicaciones, muchas veces incompatibles entre si, lleva a la necesidad de desarrollar aplicaciones que se encarguen del intercambio de estos datos para lograr un consolidado de información que aporte valor a la empresa.
Al momento de diseñar este tipo de aplicaciones, es común el observar patrones una y otra vez. Dichos patrones han sido recopilados y documentados por Gregor Hohpe y Bobby Woolf en su libro "Enterprise Integration Patterns", en el cual ofrecen una visión completa y muy bien explicada de estos patrones, así como de una nomenclatura que se ha vuelto estándar para representar estos patrones.
Apache Camel es la implementación de la gran mayoría de los patrones propuestos por Gregor y Bobby para la plataforma Java y de manera OpenSource bajo licencia Apache 2.0. Apache Camel es una alternativa a diversas herramientas comerciales para realizar aplicaciones empresariales de integración de aplicaciones.
En la conferencia se mostraran los patrones mas comunes, su notación, diseño e implementación usando Apache Camel, de igual manera se mostrara la infraestructura necesaria para ejecutar Apache Camel, los mecanismos de monitoreo de aplicaciones desarrolladas con Camel y como se puede integrar con productos de integración como Brokers de Mensajería (JMS), Enterprise Service Bus (ESB) y servidores de aplicaciones clásicos
AngularJS has become a very popular web development framework. Now that Telerik made Kendo UI open source, this framework is a possible alternative for many web developers. Learn about the differences and similarities.
Apache Camel - FUSE community day London 2010 presentationClaus Ibsen
My Apache Camel presentation from the FUSE community day event, London June 2010.
A video/audio/transcript of the presentation is in the works and will later be published at the fusesource (http://fusesource.com) website.
Using apache camel for microservices and integration then deploying and managing on Docker and Kubernetes. When we need to make changes to our app, we can use Fabric8 continuous delivery built on top of Kubernetes and OpenShift.
This document discusses integration in the age of DevOps. It describes how microservices help solve the problem of decoupling services and teams to move quickly at scale. Apache Camel is presented as a solution for integration that allows for reliable and distributed integration through mechanisms like messaging. Kubernetes and Docker are discussed as platforms that help develop and run microservices locally and at scale by providing automation, configuration, isolation and service discovery capabilities.
Este documento proporciona una visión general de las técnicas de transformación de datos en Camel, incluyendo el uso de EIPs como Message Translator y Content Enricher, formatos de datos como CSV y JSON, plantillas como Velocity, y el mecanismo de conversión de tipos de Camel. También describe cómo implementar la transformación mediante procesadores, beans y la operación <transform> en XML, con ejemplos de código.
The document discusses microservices and APIs. It covers how microservices optimize for speed by shedding dependencies and having dependencies on demand through services and APIs. It discusses consumer contracts for APIs and service versioning. It also discusses using an API gateway pattern for scalability, security, monitoring and more. It promotes API management for benefits like access control, analytics, and monetization of microservices.
This document provides an overview of integrating microservices with Apache Camel and JBoss Fuse. It introduces Apache Camel as a lightweight integration library that uses enterprise integration patterns and domain-specific languages to define integration "flows" and "routes". It describes how Camel supports features like dynamic routing, REST APIs, backpressure, load balancing, and circuit breakers that are useful for building microservices. The document also introduces JBoss Fuse as a development and runtime platform for microservices that provides tooling, frameworks, management capabilities and container support using technologies like Apache Camel, CXF, ActiveMQ and Karaf.
DevOps with ActiveMQ, Camel, Fabric8, and HawtIO Christian Posta
DevOps and Continuous Delivery slides with Fabric8 (http://fabric8.io), HawtIO (http://hawt.io), Camel, ActiveMQ, Docker Jenkins, etc.
10 yrs ago, SOA promised a lot of the same things Microservices promise use today. So where did we go wrong? What makes microservices different? In this talk, we discussed from an architectural view how we went sideways with SOA, why we must embrace things like Domain Driven Design and scaled-out architectures, and how microservices can be built with enterprises in mind. We also cover a step-by-step, in-depth tutorial that covers these concepts.
Christian Posta is a principal middleware specialist and architect who has worked with large microservices architectures. He discusses why companies are moving to microservices and cloud platforms like Kubernetes and OpenShift. He covers characteristics of microservices like small autonomous teams and decentralized decision making. Posta also discusses breaking applications into independent services, shedding dependencies between teams, and using contracts and APIs for communication between services.
Microservices architecture is a very powerful way to build scalable systems optimized for speed of change. To do this, we need to build independent, autonomous services which by definition tend to minimize dependencies on other systems. One of the tenants of microservices, and a way to minimize dependencies, is “a service should own its own database”. Unfortunately this is a lot easier said than done. Why? Because: your data.
We’ve been dealing with data in information systems for 5 decades so isn’t this a solved problem? Yes and no. A lot of the lessons learned are still very relevant. Traditionally, we application developers have accepted the practice of using relational databases and relying on all of their safety guarantees without question. But as we build services architectures that span more than one database (by design, as with microservices), things get harder. If data about a customer changes in one database, how do we reconcile that with other databases (especially where the data storage may be heterogenous?).
For developers focused on the traditional enterprise, not only do we have to try to build fast-changing systems that are surrounded by legacy systems, the domains (finance, insurance, retail, etc) are incredibly complicated. Just copying with Netflix does for microservices may or may not be useful. So how do we develop and reason about the boundaries in our system to reduce complexity in the domain?
In this talk, we’ll explore these problems and see how Domain Driven Design helps grapple with the domain complexity. We’ll see how DDD concepts like Entities and Aggregates help reason about boundaries based on use cases and how transactions are affected. Once we can identify our transactional boundaries we can more carefully adjust our needs from the CAP theorem to scale out and achieve truly autonomous systems with strictly ordered eventual consistency. We’ll see how technologies like Apache Kafka, Apache Camel and Debezium.io can help build the backbone for these types of systems. We’ll even explore the details of a working example that brings all of this together.
The document discusses Christian Posta's journey with microservices architectures. It begins by explaining why organizations are moving to microservices and defines microservices. It then covers related topics like cloud platforms, container technologies like Kubernetes and OpenShift, benefits and drawbacks of microservices, and tools for developing microservices like Docker, Kubernetes, OpenShift, and Camel.
The document discusses implementing enterprise integration patterns through Apache Camel. It provides an overview of enterprise integration patterns, describes what Apache Camel is and how it is based on these patterns, and gives examples of implementing the Message Filter pattern in XML, Java, Scala and Spring configurations. It also discusses using beans with Camel for message translation and binding beans to endpoints.
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.
This document provides an overview of Apache Camel, an open source integration framework. It discusses Camel's architecture, including routes, endpoints and components. It also describes Camel's domain specific language for defining routes. Finally, it provides a sample route that reads an XML file from FTP, transforms it using XSLT, and sends it to a JMS queue.
Keynote (Nandini Ramani) - The Role of Java in Heterogeneous Computing & How ...AMD Developer Central
Keynote presentation, The Role of Java in Heterogeneous Computing, and How You Can Help, by Nandini Ramani, VP, Java Platform, Oracle Corporation, at the AMD Developer Summit (APU13), Nov. 11-13, 2013.
This is the presentation given as a Webinar using Webex, on World IPv6 Launch, 6 June 2012.
http://www.ipv6matrix.org/
http://www.worldipv6launch.org/
With a strong focus on annotations, minimalist configuration, simple deployment, intelligent defaults and Java centric type-safety, Java EE is one of the most productive full-stack development platforms around today. This very code centric workshop is a quick tour of the Java EE platform as it stands today. If you haven't seen Java EE for a while and want to catch up, this session is definitely for you.
We will start with the basic principals of what Java EE is and what it is not, overview the platform at a high level and then dive into each key API like JSF, CDI, EJB 3, JPA, JAX-RS, WebSocket and JMS using examples and demos. This is your chance to look at Java EE 7 in the context of a realistic application named Cargo Tracker, available with an MIT license at http://cargotracker.java.net.
We will also briefly take a look at the emerging horizons of Java EE 8.
This talk provides a number of step-by-step examples that illustrate different ways in which Rails applications can interact effectively with third-party Java libraries. The presentation shows how developers can leverage JRuby to augment Rails applications with the mature, third-party libraries that are widely available in the Java world.
Static (ahead-of-time) compilation of code appeared in Oracle JDK 9. We have already discussed why this is necessary, and the scope of the current implementation. Now it makes sense to talk about the technical details. Anyone can easily suffer from some already known problems of current implementation. From the other hand it makes sense to test potential benefits and to try a tiny piece of bright future. But one must realize how to try it right. What information is generated by the AOT and how it is generated, how compiled AOT code interacts with Hotspot. What you can do with AOT code by external tools, and how to infiltrate into the compilation process. And of course, what grips to twist, and what will be the performance with AOT.
This document discusses integrating XGBoost machine learning with Spark and DataFrames. It provides examples of using XGBoost in Spark to train models on distributed data and make predictions on streaming data in parallel. It also discusses future work, such as using Rabbit for parallel learning, adding support to more platforms like Windows, and integrating with Spark ML pipelines.
ZK is a model-view-controller framework for building desktop-like web applications using ZUML, ZScript, and Java. It uses a servlet-based architecture where ZK Loader handles initial page loads and the AU Engine handles AJAX requests. The ZK library is included in the webapp and generates the necessary folder structure and files. Developers define the web application using ZUML and deploy it by copying the compiled files into Tomcat's webapps folder.
The Right Pill for JRuby Memory and Thread Issues: Eclipse Memory AnalyzerVladimir Pavlov
This document discusses memory and thread issues that can occur with JRuby applications and how Eclipse Memory Analyzer can help address them. It provides an overview of Ruby and JRuby, common problems like memory leaks and thread issues, and how the Memory Analyzer tool works. It then describes a JRuby extension plugin for Memory Analyzer that can produce readable Ruby stack traces from heap dumps to help debug issues. Further enhancements are discussed along with a call for feedback.
Project Avatar (Lyon JUG & Alpes JUG - March 2014)David Delabassee
The document discusses Project Avatar, which allows running server-side JavaScript applications on the Java Virtual Machine (JVM). Project Avatar uses Nashorn to run JavaScript on the JVM and provides an environment similar to Node.js. It allows leveraging Java libraries and frameworks from JavaScript code. Project Avatar also includes features like shared state, messaging, and an object-relational mapping framework to integrate JavaScript applications with the JVM and Java EE.
Java EE 7 et ensuite pourquoi pas JavaScript sur le serveur! David Delabassee
The document discusses Project Avatar, which allows server-side JavaScript applications to run on the Java Virtual Machine (JVM). It enables Node.js-style programming with advanced features like multi-threading and integration with Java EE. Project Avatar includes a runtime based on Nashorn and Node.js modules, and provides services for HTTP, WebSockets, messaging and data storage that leverage the JVM and Java EE.
The document discusses Oracle's GlassFish BOF presentation at JavaOne 2012. It summarizes Oracle's journey with GlassFish since the previous JavaOne, the roadmap ahead, and solicits community feedback. Key points include GlassFish shipping as the Java EE 7 reference implementation, increased community contributions, and the focus of GlassFish 4 being to make Java EE 7 usable for developers. It also outlines Project Avatar for supporting HTML5 connectivity and JavaScript services on the server.
Why you should be excited about ClojureScriptelliando dias
ClojureScript allows Clojure code to compile to JavaScript. Created by Rich Hickey and friends, it provides optimizations for performance while maintaining readability and abstraction. As a Lisp for JavaScript, ClojureScript controls complexity on the web and benefits from JavaScript's status as a compilation target for many languages.
"Petascale Genomics with Spark", Sean Owen,Director of Data Science at ClouderaDataconomy Media
"Petascale Genomics with Spark", Sean Owen, Director of Data Science at Cloudera
YouTube Link: https://www.youtube.com/watch?v=HY93FdK5i60
Watch more from Data Natives 2015 here: http://bit.ly/1OVkK2J
Visit the conference website to learn more: www.datanatives.io
Follow Data Natives:
https://www.facebook.com/DataNatives
https://twitter.com/DataNativesConf
Stay Connected to Data Natives by Email: Subscribe to our newsletter to get the news first about Data Natives 2016: http://bit.ly/1WMJAqS
About the Author:
Sean is Director of Data Science at Cloudera, based in London. Before Cloudera, he founded Myrrix Ltd, a company commercializing large-scale real-time recommender systems on Apache Hadoop. He has been a primary committer and VP for Apache Mahout, and co-author of Mahout in Action. Previously, Sean was a senior engineer at Google. He holds and MBA from the London Business School and a BA in Computer Science from Harvard.
This document summarizes JavaScript support on Google App Engine including frameworks like Rhino, Narwhal, Ringo, and JSGI/Jack that allow running JavaScript applications on App Engine. It also describes the AppengineJS stack which provides APIs for the App Engine datastore, memcache, and other services via CommonJS packages. Key features of AppengineJS include support for templating, HTML parsing, and the Nitro framework.
What's New and Newer in Apache httpd-24Jim Jagielski
Jim Jagielski presents an overview of new features and enhancements in Apache HTTP Server version 2.4, including configuration and runtime improvements, new modules and capabilities, cloud and proxy enhancements, performance increases, and support for HTTP/2. Key highlights include finer-grained configuration controls, new modules like mod_lua and mod_macro, improved proxy and load balancing functionality, better performance through optimizations and new MPMs like Event, and initial HTTP/2 support.
The document discusses how to deploy Rails applications using Capistrano. It covers setting up the Rails environment with Ruby, RubyGems, Rails, Mongrel, Subversion, and Capistrano. It then discusses configuring Capistrano, Apache virtual hosts, and Mongrel clusters. It provides details on the deploy.rb file configuration including database, mongrel cluster, and roles.
London JBUG April 2015 - Performance Tuning Apps with WildFly Application ServerJBUG London
This document discusses performance tuning for Wildfly8 applications. It outlines reasons for tuning like contractual obligations and user experience. It describes benchmarking methodology like defining test objectives and harnessing test tools. Common bottlenecks like the web tier, EJB tier, and JMS/JDBC connections are discussed. Wildfly tuning controls like thread pools, bean instance counts, and pool sizes are covered. Ideal request flow and queuing with timeouts are addressed. Specific thread pool types like unbounded, bounded, and blocking-bounded are explained. The presentation ends with questions.
Lightning talk by Navin Surtani (Consultant, C2B2 ) presented at the London JBoss User Group event on the 14th of January 2015.
For more information see Navin's blog post 'Clustering Websockets on WildFly' here: http://blog.c2b2.co.uk/2014/12/clustering-websockets-on-wildfly.html
Presentation delivered by Darran Lofthouse, Principal Software Engineer, Red Hat & Kabir Khan, Principal Software Engineer, Red Hat, during London JBoss User Group event on the 21st of May 2014.
Presentation by Peter Skopek (JBoss by Red Hat) delivered at the London JBoss User Group event on the 30th of April 2014.
Presentation
Introductory talk to PicketLink from Federation through to Identity Management.
What is PicketLink?
PicketLink is an umbrella project for security and identity management for Java Applications. PicketLink is an important project under the security offerings from JBoss.
A Picket Fence is a secure system of pickets joined together via some type of links. Basically, the Pickets by themselves do not offer any security. But when they are brought together by linking them, they provide the necessary security.
This project is that link for other security systems or systems to bring together or join, to finally provide the necessary secure system.
For more information visit http://picketlink.org/
Presentation by Tomaz Cerar (Red Hat), delivered at the London JBoss User Group event on the 12th of February 2014.
Watch the video here: http://www.youtube.com/watch?v=eu9K5NLUKBI
Join London JBUG: http://www.c2b2.co.uk/jbug
Presentation delivered by Mircea Markus (JBoss) at the London JBoss User Group Event on Wednesday, the 4th of December 2013.
In this talk, Mircea Markus (Infinispan Lead) covers the major features added in the 6.0 release to the Infinispan ecosystem:
- querying in client/server mode
- better integration with the persistent storage
- multi-master cross-site replication
- support for heterogeneous clusters
Participants will take home a better understanding of Infinispan capabilities and the use cases in which it can be put at work. Ideally the attendees should have a basic knowledge of the in-memory data grids.
Compensating Transactions: When ACID is too muchJBUG London
The talk was presented by Dr Paul Robinson (Red Hat) at the London JBoss User Group event on the 25th of September 2013.
Video available soon
ACID transactions are a useful tool for application developers and can provide very strong guarantees, even in the presence of failures. However, ACID transactions are not always appropriate for every situation.
ACID transactions are achieved by holding locks on resources and require the ability to rollback changes. In some situations, the blocking nature of the protocol can be too limiting to performance, especially if the transaction is distributed. Also, some actions can’t simply be rolled back; for example, sending an email.
A common strategy for applications that can’t use ACID, is to throw out transactions altogether. However, with this approach you are missing out on many of the benefits that transactions can provide. There are alternative transaction models that relax some of the ACID properties, while still retaining many of the strong guarantees essential for building robust enterprise applications. These should be considered before deciding not to use transactions at all.
In this talk, I’ll present one such alternative to ACID transactions: compensation-based transactions. I’ll provide an overview of ACID and it’s limitations and describe some use-cases where ACID is not appropriate. I’ll then present our new API for compensation-based transactions and demonstrate how it can be used to address these problems. Finally, I’ll present our future plans to improve and expand our support for compensation-based transactions.
London JBUG - Connecting Applications Everywhere with JBoss A-MQJBUG London
Presentation by Rob Davies (Red Hat) delivered at the London JBoss USer Group event on the 10th of July 2013.
See the video here: http://youtu.be/VrJyKLAXVTg
As part of the FuseSource acquisition, Red Hat now supports Apache ActiveMQ as the recently released Red Hat JBoss A-MQ product.
ActiveMQ is the most widely used message-oriented middleware that uses messaging to connect remote applications written in Java, C/C++, Python, Perl, Ruby, and many other languages. ActiveMQ is standards based and supports messaging protocols such as AMQP 1.0, WebSockets, Stomp, OpenWire, and MQTT.
In this session, Rob Davies will discuss the product’s features and functionality, and demonstrate connectivity from a microprocessor to web sockets using JBoss A-MQ.
Talk by Mauricio Salatino and Esteban Aliverti presented at the JBUG London Event on the 12th of December 2012.
To watch the video please visit http://www.youtube.com/watch?v=9M1eaH3v4qg
Arquillian - Integration Testing Made EasyJBUG London
Slides by Davide D'Alto presented at JBUG London event on the 24th of October 2012.
You can watch the presentation video here http://youtu.be/MuqAx9SuIOk
The document describes how Infinispan was used to improve the performance and scalability of two different systems - an existing production system (Part 1) and a new greenfield project (Part 2).
For the existing system, Infinispan replaced EhCache to distribute caching across multiple nodes and reduce heap usage. Benchmarking was used to validate the solution. Issues encountered with Hotrod were addressed by using embedded caching instead.
For the new project, distributed caching did not work due to high network traffic. Distributed execution was used instead, where tasks are run on nodes containing the data to minimize traffic. This reduced latency from 2 seconds to 200ms.
Hibernate OGM - JPA for Infinispan and NoSQLJBUG London
Hibernate OGM provides JPA support for NoSQL databases like Infinispan. It allows using the familiar JPA programming model while storing data in a flexible NoSQL database. Hibernate OGM acts as a JPA front-end that handles CRUD operations and basic queries, persisting objects to Infinispan. The goal is to encourage new data usage patterns with volume and types while using a familiar Java environment.
JBoss jBPM, the future is now for all your Business Processes by Eric SchabellJBUG London
This document discusses jBPM5 and its capabilities for business process management. It begins with an overview of business process management and workflow. It then discusses how jBPM5 has evolved from a workflow engine to a full BPMS with support for BPMN 2.0, rules, events, flexible processes, and domain-specific processes. It highlights features like the Eclipse plugin, web designer, and integration capabilities. The document promotes jBPM5 as providing a flexible solution for all process and workflow needs.
Presented by Matt Brasier on 15th of June 2011 at the JBUG is Back! June Event - JBoss 7
More info: http://www.meetup.com/JBoss-User-Group/events/19943531/
This is the keynote of the Into the Box conference, highlighting the release of the BoxLang JVM language, its key enhancements, and its vision for the future.
Spark is a powerhouse for large datasets, but when it comes to smaller data workloads, its overhead can sometimes slow things down. What if you could achieve high performance and efficiency without the need for Spark?
At S&P Global Commodity Insights, having a complete view of global energy and commodities markets enables customers to make data-driven decisions with confidence and create long-term, sustainable value. 🌍
Explore delta-rs + CDC and how these open-source innovations power lightweight, high-performance data applications beyond Spark! 🚀
DevOpsDays Atlanta 2025 - Building 10x Development Organizations.pptxJustin Reock
Building 10x Organizations with Modern Productivity Metrics
10x developers may be a myth, but 10x organizations are very real, as proven by the influential study performed in the 1980s, ‘The Coding War Games.’
Right now, here in early 2025, we seem to be experiencing YAPP (Yet Another Productivity Philosophy), and that philosophy is converging on developer experience. It seems that with every new method we invent for the delivery of products, whether physical or virtual, we reinvent productivity philosophies to go alongside them.
But which of these approaches actually work? DORA? SPACE? DevEx? What should we invest in and create urgency behind today, so that we don’t find ourselves having the same discussion again in a decade?
"Client Partnership — the Path to Exponential Growth for Companies Sized 50-5...Fwdays
Why the "more leads, more sales" approach is not a silver bullet for a company.
Common symptoms of an ineffective Client Partnership (CP).
Key reasons why CP fails.
Step-by-step roadmap for building this function (processes, roles, metrics).
Business outcomes of CP implementation based on examples of companies sized 50-500.
Role of Data Annotation Services in AI-Powered ManufacturingAndrew Leo
From predictive maintenance to robotic automation, AI is driving the future of manufacturing. But without high-quality annotated data, even the smartest models fall short.
Discover how data annotation services are powering accuracy, safety, and efficiency in AI-driven manufacturing systems.
Precision in data labeling = Precision on the production floor.
How Can I use the AI Hype in my Business Context?Daniel Lehner
𝙄𝙨 𝘼𝙄 𝙟𝙪𝙨𝙩 𝙝𝙮𝙥𝙚? 𝙊𝙧 𝙞𝙨 𝙞𝙩 𝙩𝙝𝙚 𝙜𝙖𝙢𝙚 𝙘𝙝𝙖𝙣𝙜𝙚𝙧 𝙮𝙤𝙪𝙧 𝙗𝙪𝙨𝙞𝙣𝙚𝙨𝙨 𝙣𝙚𝙚𝙙𝙨?
Everyone’s talking about AI but is anyone really using it to create real value?
Most companies want to leverage AI. Few know 𝗵𝗼𝘄.
✅ What exactly should you ask to find real AI opportunities?
✅ Which AI techniques actually fit your business?
✅ Is your data even ready for AI?
If you’re not sure, you’re not alone. This is a condensed version of the slides I presented at a Linkedin webinar for Tecnovy on 28.04.2025.
Rock, Paper, Scissors: An Apex Map Learning JourneyLynda Kane
Slide Deck from Presentations to WITDevs (April 2021) and Cleveland Developer Group (6/28/2023) on using Rock, Paper, Scissors to learn the Map construct in Salesforce Apex development.
UiPath Community Berlin: Orchestrator API, Swagger, and Test Manager APIUiPathCommunity
Join this UiPath Community Berlin meetup to explore the Orchestrator API, Swagger interface, and the Test Manager API. Learn how to leverage these tools to streamline automation, enhance testing, and integrate more efficiently with UiPath. Perfect for developers, testers, and automation enthusiasts!
📕 Agenda
Welcome & Introductions
Orchestrator API Overview
Exploring the Swagger Interface
Test Manager API Highlights
Streamlining Automation & Testing with APIs (Demo)
Q&A and Open Discussion
Perfect for developers, testers, and automation enthusiasts!
👉 Join our UiPath Community Berlin chapter: https://community.uipath.com/berlin/
This session streamed live on April 29, 2025, 18:00 CET.
Check out all our upcoming UiPath Community sessions at https://community.uipath.com/events/.
Dev Dives: Automate and orchestrate your processes with UiPath MaestroUiPathCommunity
This session is designed to equip developers with the skills needed to build mission-critical, end-to-end processes that seamlessly orchestrate agents, people, and robots.
📕 Here's what you can expect:
- Modeling: Build end-to-end processes using BPMN.
- Implementing: Integrate agentic tasks, RPA, APIs, and advanced decisioning into processes.
- Operating: Control process instances with rewind, replay, pause, and stop functions.
- Monitoring: Use dashboards and embedded analytics for real-time insights into process instances.
This webinar is a must-attend for developers looking to enhance their agentic automation skills and orchestrate robust, mission-critical processes.
👨🏫 Speaker:
Andrei Vintila, Principal Product Manager @UiPath
This session streamed live on April 29, 2025, 16:00 CET.
Check out all our upcoming Dev Dives sessions at https://community.uipath.com/dev-dives-automation-developer-2025/.
Buckeye Dreamin 2024: Assessing and Resolving Technical DebtLynda Kane
Slide Deck from Buckeye Dreamin' 2024 presentation Assessing and Resolving Technical Debt. Focused on identifying technical debt in Salesforce and working towards resolving it.
AI EngineHost Review: Revolutionary USA Datacenter-Based Hosting with NVIDIA ...SOFTTECHHUB
I started my online journey with several hosting services before stumbling upon Ai EngineHost. At first, the idea of paying one fee and getting lifetime access seemed too good to pass up. The platform is built on reliable US-based servers, ensuring your projects run at high speeds and remain safe. Let me take you step by step through its benefits and features as I explain why this hosting solution is a perfect fit for digital entrepreneurs.
Automation Hour 1/28/2022: Capture User Feedback from AnywhereLynda Kane
Slide Deck from Automation Hour 1/28/2022 presentation Capture User Feedback from Anywhere presenting setting up a Custom Object and Flow to collection User Feedback in Dynamic Pages and schedule a report to act on that feedback regularly.