Sally Kleinfeldt and Aaron VanDerlip describe ore.bigfile, a minimalist solution to the problem of uploading, downloading, and versioning very large files in Plone.
The document discusses various tools for debugging, profiling, and monitoring symfony applications including loggers, timers, XHProf for profiling, Tsung for benchmarking, and Graphite for live metrics. It provides examples of using these tools and outlines a roadmap for improving metric recording through a C PHP extension.
This document provides an overview of CentOS Linux 6.0, including what CentOS is, its relationship to Red Hat Enterprise Linux, how to download CentOS, and basic system configuration after installation such as setting the hostname and IP address. It also briefly discusses differences between Linux and Windows and using virtualization with Linux.
How OpenNTF Open Source Solutions Can Save You Time, Money And Your HairBruce Elgort
The document describes a presentation given by Bruce Elgort on how OpenNTF open source solutions can save time and money. The presentation covers what OpenNTF is, why use open source software, an overview of the OpenNTF site and applications like OpenLog, and how to get started on your own open source project. OpenLog is highlighted as a tool that can help log and track errors in applications to assist with compliance audits and troubleshooting.
This document provides an introduction and overview to building server-side APIs with Node.js and the Express framework. It begins with an agenda that covers the basics of Node.js, concepts like HTTP and the module system, and then introduces Express as a web framework for Node.js. Several code examples are provided to demonstrate basic Express routing and handling HTTP requests.
This document provides an overview of 0MQ, an open-source library for message-oriented middleware. It discusses 0MQ's message-oriented communication capabilities, disconnected sockets, asynchronous and high-performance messaging, common messaging patterns like request/reply and publish/subscribe, and language bindings. The document also demonstrates basic usage of 0MQ sockets in Node.js and provides additional resources for learning more about 0MQ.
The document discusses how to write a scalable Symfony application in the cloud. It covers upgrading points like database connections, file uploads, session storage, local development, and deploying. Database connections should use a master-slave configuration. File uploads can use Amazon S3 for storage. Sessions can be stored in a database. Local development differs from production. Deploying can use SVN update or checkout with symlinking. Automation helps deployment.
This document discusses using Puppet and Splunk to audit change management policies and ensure compliance. It outlines how Puppet manages system configurations but the logs provide no link between configuration changes and commits. The document proposes enhancing Puppet reports to tag events with the Git commit, allowing Splunk to search for the commit that caused a specific event. This would help determine if systems were compliant by tying configuration changes to commits and answering questions about what happened and why.
Sally Kleinfeldt and Aaron VanDerlip describe ore.bigfile, a minimalist solution to the problem of uploading, downloading, and versioning very large files in Plone.
The document discusses various tools for debugging, profiling, and monitoring symfony applications including loggers, timers, XHProf for profiling, Tsung for benchmarking, and Graphite for live metrics. It provides examples of using these tools and outlines a roadmap for improving metric recording through a C PHP extension.
This document provides an overview of CentOS Linux 6.0, including what CentOS is, its relationship to Red Hat Enterprise Linux, how to download CentOS, and basic system configuration after installation such as setting the hostname and IP address. It also briefly discusses differences between Linux and Windows and using virtualization with Linux.
How OpenNTF Open Source Solutions Can Save You Time, Money And Your HairBruce Elgort
The document describes a presentation given by Bruce Elgort on how OpenNTF open source solutions can save time and money. The presentation covers what OpenNTF is, why use open source software, an overview of the OpenNTF site and applications like OpenLog, and how to get started on your own open source project. OpenLog is highlighted as a tool that can help log and track errors in applications to assist with compliance audits and troubleshooting.
This document provides an introduction and overview to building server-side APIs with Node.js and the Express framework. It begins with an agenda that covers the basics of Node.js, concepts like HTTP and the module system, and then introduces Express as a web framework for Node.js. Several code examples are provided to demonstrate basic Express routing and handling HTTP requests.
This document provides an overview of 0MQ, an open-source library for message-oriented middleware. It discusses 0MQ's message-oriented communication capabilities, disconnected sockets, asynchronous and high-performance messaging, common messaging patterns like request/reply and publish/subscribe, and language bindings. The document also demonstrates basic usage of 0MQ sockets in Node.js and provides additional resources for learning more about 0MQ.
The document discusses how to write a scalable Symfony application in the cloud. It covers upgrading points like database connections, file uploads, session storage, local development, and deploying. Database connections should use a master-slave configuration. File uploads can use Amazon S3 for storage. Sessions can be stored in a database. Local development differs from production. Deploying can use SVN update or checkout with symlinking. Automation helps deployment.
This document discusses using Puppet and Splunk to audit change management policies and ensure compliance. It outlines how Puppet manages system configurations but the logs provide no link between configuration changes and commits. The document proposes enhancing Puppet reports to tag events with the Git commit, allowing Splunk to search for the commit that caused a specific event. This would help determine if systems were compliant by tying configuration changes to commits and answering questions about what happened and why.
The document summarizes Andreas Jung's presentation on using MongoDB as the database for BRAINREPUBLIC. Some key points include:
- Andreas evaluated different "no-SQL" database options for BRAINREPUBLIC including key-value stores, MongoDB, and CouchDB.
- MongoDB was chosen because it offered the best performance compared to CouchDB, and its rich query API was preferable to map-reduce alone.
- The proposed architecture for BRAINREPUBLIC involved using MongoDB for the database, RabbitMQ for messaging, and SOLR for search, behind a load balancing layer.
This document discusses Comet and web sockets. Comet refers to techniques for long-lived HTTP connections to allow real-time data transmission from server to browser. Common Comet methods include long-polling, forever frames, and callback polling. Web sockets provide bi-directional communication over a single TCP connection and are being standardized by the W3C, addressing limitations of Comet techniques. The document provides examples of implementing Comet using Dojo and discusses related topics like Comet servers, protocols, and clients.
This document discusses using Node.js and Redis to build a real-time web application. Ruby code is used to model users who can follow each other. When a user updates their status, Redis publishes the update to followers' timelines. Node.js code subscribes to Redis channels and sends updates to connected clients in real-time via websockets. This allows building a Twitter-like application where the web interface updates without reloading as users publish new statuses.
HTTP2 in action - Piet Van Dongen - Codemotion Amsterdam 2017Codemotion
We've all heard about HTTP/2, but what's in it for us? Is it really that much better? How can we start using it? During this talk, we will explore HTTP/2's new features while creating our own web server, demonstrating new features like server push, multiplexing and header compression. At then end, we can proof how HTTP/2 benefits not only the end user, but developers and operations as well!.
A Network Architecture for the Web of Thingsbenaam
The document proposes a network architecture for integrating physical devices and objects into the web. It involves using gateways to ensure device URLs are available, reachable, stable, and discoverable. Gateways queue requests when devices are asleep, cache responses, and update locations when devices move. The architecture addresses issues like energy efficiency, network constraints, mobility, and discovery. A preliminary version was implemented on Sun SPOT devices to demonstrate integrated physical and web resources.
Node.js is an asynchronous event-driven JavaScript runtime that aims to build scalable network applications. It uses an event loop model that keeps the process running and prevents blocking behavior, allowing non-blocking I/O operations. This makes Node well-suited for real-time applications that require two-way connections like chat, streaming, and web sockets. The document outlines Node's core components and capabilities like modules, child processes, HTTP and TCP servers, and its future potential like web workers and streams.
Source Code Management and Version Control Systems are tools for helping you track your file based assets (typically source code). Traditional SCM systems are centralised (CVS, Subversion, Visual Source Safe), Distributed version control systems systems provide new capabilities, work-flows, are becoming mature and are gaining mind share in the open source community.
Git is one of those Distributed Version Control Systems. It was invented by the creator of Linux (Linus Torvalds) for protecting the Linux kernel source code and coordinating the activity of hundreds of developers. This talk discusses what Distributed Version Control is, the history of Git, basic version control features and some very uncommon and amazing capabilities of git. Time permitting it will include live demonstration of the tools.
Covers the concepts on how to build a web service (Rest API), data formats (JSON vs XML), HTTP, troubleshooting your API, tools and how to bring it all together in PHP.
The document discusses various standards and protocols for distributed social networking, including WebFinger for user discovery, Portable Contacts for accessing user profiles, ActivityStreams for sharing status updates, PubSubHubbub for subscribing to feeds, Salmon for commenting, and OExchange for sharing content across networks. The presentation provides examples and demonstrations of how these standards work together to enable interoperability between decentralized social applications and services.
SeaBeyond 2011 ProcessOne - Eric Cestari: XMPP over WebSocketProcessOne
This document discusses using XMPP over the WebSocket protocol. It provides an overview of WebSocket, including its benefits over older protocols like Comet. It describes the WebSocket API and standardization process. It then outlines how XMPP can be implemented as a sub-protocol over WebSocket, including support in ejabberd and StropheJS. Finally, it introduces a new product called GitLive that visualizes GitHub activity in real-time over WebSocket.
Opening up the Social Web - Standards that are bridging the Islands Bastian Hofmann
Social networks are not closed off to the rest of the web anymore. Various standards like ActivityStreams, PubSubHubbub, WebFinger, OpenSocial, Salmon, OEmbed, XAuth or OExchange are emerging to open them up to other websites. I will introduce these protocols, show how they work together, how you can benefit from them and give an outlook on how they will change the world of social networks.
PHP in a Mobile Ecosystem (Zendcon 2010)Ivo Jansch
A look at PHP's role in mobile web and app development. Delivered at Zendcon 2010 on November 3, 2010.
If you like the content or want to give feedback or if you need help with any of the concepts mentioned here, contact me at egeniq.com.
Sally Kleinfeldt and Aaron VanDerlip describe ore.bigfile, a minimalist solution to the problem of uploading, downloading, and versioning very large files in Plone.
Networks have layers according to different models like the OSI model and TCP/IP model. The document discusses each layer including physical, data link, network, transport, session, presentation, and application layers. It provides examples of common protocols that operate at each layer like Ethernet at the data link layer, IP at the network layer, and HTTP at the application layer. The document demonstrates using Wireshark to capture network packets at different layers like ARP, DNS, ping, and HTTP requests to analyze the network traffic and observe how protocols work.
AppSec PNW: Android and iOS Application Security with MobSFAjin Abraham
Mobile Security Framework - MobSF is a free and open source automated mobile application security testing environment designed to help security engineers, researchers, developers, and penetration testers to identify security vulnerabilities, malicious behaviours and privacy concerns in mobile applications using static and dynamic analysis. It supports all the popular mobile application binaries and source code formats built for Android and iOS devices. In addition to automated security assessment, it also offers an interactive testing environment to build and execute scenario based test/fuzz cases against the application.
This talk covers:
Using MobSF for static analysis of mobile applications.
Interactive dynamic security assessment of Android and iOS applications.
Solving Mobile app CTF challenges.
Reverse engineering and runtime analysis of Mobile malware.
How to shift left and integrate MobSF/mobsfscan SAST and DAST in your build pipeline.
Dandelion Hashtable: beyond billion requests per second on a commodity serverAntonios Katsarakis
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
Essentials of Automations: Exploring Attributes & Automation ParametersSafe Software
Building automations in FME Flow can save time, money, and help businesses scale by eliminating data silos and providing data to stakeholders in real-time. One essential component to orchestrating complex automations is the use of attributes & automation parameters (both formerly known as “keys”). In fact, it’s unlikely you’ll ever build an Automation without using these components, but what exactly are they?
Attributes & automation parameters enable the automation author to pass data values from one automation component to the next. During this webinar, our FME Flow Specialists will cover leveraging the three types of these output attributes & parameters in FME Flow: Event, Custom, and Automation. As a bonus, they’ll also be making use of the Split-Merge Block functionality.
You’ll leave this webinar with a better understanding of how to maximize the potential of automations by making use of attributes & automation parameters, with the ultimate goal of setting your enterprise integration workflows up on autopilot.
"Scaling RAG Applications to serve millions of users", Kevin GoedeckeFwdays
How we managed to grow and scale a RAG application from zero to thousands of users in 7 months. Lessons from technical challenges around managing high load for LLMs, RAGs and Vector databases.
"$10 thousand per minute of downtime: architecture, queues, streaming and fin...Fwdays
Direct losses from downtime in 1 minute = $5-$10 thousand dollars. Reputation is priceless.
As part of the talk, we will consider the architectural strategies necessary for the development of highly loaded fintech solutions. We will focus on using queues and streaming to efficiently work and manage large amounts of data in real-time and to minimize latency.
We will focus special attention on the architectural patterns used in the design of the fintech system, microservices and event-driven architecture, which ensure scalability, fault tolerance, and consistency of the entire system.
QA or the Highway - Component Testing: Bridging the gap between frontend appl...zjhamm304
These are the slides for the presentation, "Component Testing: Bridging the gap between frontend applications" that was presented at QA or the Highway 2024 in Columbus, OH by Zachary Hamm.
The document summarizes Andreas Jung's presentation on using MongoDB as the database for BRAINREPUBLIC. Some key points include:
- Andreas evaluated different "no-SQL" database options for BRAINREPUBLIC including key-value stores, MongoDB, and CouchDB.
- MongoDB was chosen because it offered the best performance compared to CouchDB, and its rich query API was preferable to map-reduce alone.
- The proposed architecture for BRAINREPUBLIC involved using MongoDB for the database, RabbitMQ for messaging, and SOLR for search, behind a load balancing layer.
This document discusses Comet and web sockets. Comet refers to techniques for long-lived HTTP connections to allow real-time data transmission from server to browser. Common Comet methods include long-polling, forever frames, and callback polling. Web sockets provide bi-directional communication over a single TCP connection and are being standardized by the W3C, addressing limitations of Comet techniques. The document provides examples of implementing Comet using Dojo and discusses related topics like Comet servers, protocols, and clients.
This document discusses using Node.js and Redis to build a real-time web application. Ruby code is used to model users who can follow each other. When a user updates their status, Redis publishes the update to followers' timelines. Node.js code subscribes to Redis channels and sends updates to connected clients in real-time via websockets. This allows building a Twitter-like application where the web interface updates without reloading as users publish new statuses.
HTTP2 in action - Piet Van Dongen - Codemotion Amsterdam 2017Codemotion
We've all heard about HTTP/2, but what's in it for us? Is it really that much better? How can we start using it? During this talk, we will explore HTTP/2's new features while creating our own web server, demonstrating new features like server push, multiplexing and header compression. At then end, we can proof how HTTP/2 benefits not only the end user, but developers and operations as well!.
A Network Architecture for the Web of Thingsbenaam
The document proposes a network architecture for integrating physical devices and objects into the web. It involves using gateways to ensure device URLs are available, reachable, stable, and discoverable. Gateways queue requests when devices are asleep, cache responses, and update locations when devices move. The architecture addresses issues like energy efficiency, network constraints, mobility, and discovery. A preliminary version was implemented on Sun SPOT devices to demonstrate integrated physical and web resources.
Node.js is an asynchronous event-driven JavaScript runtime that aims to build scalable network applications. It uses an event loop model that keeps the process running and prevents blocking behavior, allowing non-blocking I/O operations. This makes Node well-suited for real-time applications that require two-way connections like chat, streaming, and web sockets. The document outlines Node's core components and capabilities like modules, child processes, HTTP and TCP servers, and its future potential like web workers and streams.
Source Code Management and Version Control Systems are tools for helping you track your file based assets (typically source code). Traditional SCM systems are centralised (CVS, Subversion, Visual Source Safe), Distributed version control systems systems provide new capabilities, work-flows, are becoming mature and are gaining mind share in the open source community.
Git is one of those Distributed Version Control Systems. It was invented by the creator of Linux (Linus Torvalds) for protecting the Linux kernel source code and coordinating the activity of hundreds of developers. This talk discusses what Distributed Version Control is, the history of Git, basic version control features and some very uncommon and amazing capabilities of git. Time permitting it will include live demonstration of the tools.
Covers the concepts on how to build a web service (Rest API), data formats (JSON vs XML), HTTP, troubleshooting your API, tools and how to bring it all together in PHP.
The document discusses various standards and protocols for distributed social networking, including WebFinger for user discovery, Portable Contacts for accessing user profiles, ActivityStreams for sharing status updates, PubSubHubbub for subscribing to feeds, Salmon for commenting, and OExchange for sharing content across networks. The presentation provides examples and demonstrations of how these standards work together to enable interoperability between decentralized social applications and services.
SeaBeyond 2011 ProcessOne - Eric Cestari: XMPP over WebSocketProcessOne
This document discusses using XMPP over the WebSocket protocol. It provides an overview of WebSocket, including its benefits over older protocols like Comet. It describes the WebSocket API and standardization process. It then outlines how XMPP can be implemented as a sub-protocol over WebSocket, including support in ejabberd and StropheJS. Finally, it introduces a new product called GitLive that visualizes GitHub activity in real-time over WebSocket.
Opening up the Social Web - Standards that are bridging the Islands Bastian Hofmann
Social networks are not closed off to the rest of the web anymore. Various standards like ActivityStreams, PubSubHubbub, WebFinger, OpenSocial, Salmon, OEmbed, XAuth or OExchange are emerging to open them up to other websites. I will introduce these protocols, show how they work together, how you can benefit from them and give an outlook on how they will change the world of social networks.
PHP in a Mobile Ecosystem (Zendcon 2010)Ivo Jansch
A look at PHP's role in mobile web and app development. Delivered at Zendcon 2010 on November 3, 2010.
If you like the content or want to give feedback or if you need help with any of the concepts mentioned here, contact me at egeniq.com.
Sally Kleinfeldt and Aaron VanDerlip describe ore.bigfile, a minimalist solution to the problem of uploading, downloading, and versioning very large files in Plone.
Networks have layers according to different models like the OSI model and TCP/IP model. The document discusses each layer including physical, data link, network, transport, session, presentation, and application layers. It provides examples of common protocols that operate at each layer like Ethernet at the data link layer, IP at the network layer, and HTTP at the application layer. The document demonstrates using Wireshark to capture network packets at different layers like ARP, DNS, ping, and HTTP requests to analyze the network traffic and observe how protocols work.
AppSec PNW: Android and iOS Application Security with MobSFAjin Abraham
Mobile Security Framework - MobSF is a free and open source automated mobile application security testing environment designed to help security engineers, researchers, developers, and penetration testers to identify security vulnerabilities, malicious behaviours and privacy concerns in mobile applications using static and dynamic analysis. It supports all the popular mobile application binaries and source code formats built for Android and iOS devices. In addition to automated security assessment, it also offers an interactive testing environment to build and execute scenario based test/fuzz cases against the application.
This talk covers:
Using MobSF for static analysis of mobile applications.
Interactive dynamic security assessment of Android and iOS applications.
Solving Mobile app CTF challenges.
Reverse engineering and runtime analysis of Mobile malware.
How to shift left and integrate MobSF/mobsfscan SAST and DAST in your build pipeline.
Dandelion Hashtable: beyond billion requests per second on a commodity serverAntonios Katsarakis
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
Essentials of Automations: Exploring Attributes & Automation ParametersSafe Software
Building automations in FME Flow can save time, money, and help businesses scale by eliminating data silos and providing data to stakeholders in real-time. One essential component to orchestrating complex automations is the use of attributes & automation parameters (both formerly known as “keys”). In fact, it’s unlikely you’ll ever build an Automation without using these components, but what exactly are they?
Attributes & automation parameters enable the automation author to pass data values from one automation component to the next. During this webinar, our FME Flow Specialists will cover leveraging the three types of these output attributes & parameters in FME Flow: Event, Custom, and Automation. As a bonus, they’ll also be making use of the Split-Merge Block functionality.
You’ll leave this webinar with a better understanding of how to maximize the potential of automations by making use of attributes & automation parameters, with the ultimate goal of setting your enterprise integration workflows up on autopilot.
"Scaling RAG Applications to serve millions of users", Kevin GoedeckeFwdays
How we managed to grow and scale a RAG application from zero to thousands of users in 7 months. Lessons from technical challenges around managing high load for LLMs, RAGs and Vector databases.
"$10 thousand per minute of downtime: architecture, queues, streaming and fin...Fwdays
Direct losses from downtime in 1 minute = $5-$10 thousand dollars. Reputation is priceless.
As part of the talk, we will consider the architectural strategies necessary for the development of highly loaded fintech solutions. We will focus on using queues and streaming to efficiently work and manage large amounts of data in real-time and to minimize latency.
We will focus special attention on the architectural patterns used in the design of the fintech system, microservices and event-driven architecture, which ensure scalability, fault tolerance, and consistency of the entire system.
QA or the Highway - Component Testing: Bridging the gap between frontend appl...zjhamm304
These are the slides for the presentation, "Component Testing: Bridging the gap between frontend applications" that was presented at QA or the Highway 2024 in Columbus, OH by Zachary Hamm.
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
QR Secure: A Hybrid Approach Using Machine Learning and Security Validation F...AlexanderRichford
QR Secure: A Hybrid Approach Using Machine Learning and Security Validation Functions to Prevent Interaction with Malicious QR Codes.
Aim of the Study: The goal of this research was to develop a robust hybrid approach for identifying malicious and insecure URLs derived from QR codes, ensuring safe interactions.
This is achieved through:
Machine Learning Model: Predicts the likelihood of a URL being malicious.
Security Validation Functions: Ensures the derived URL has a valid certificate and proper URL format.
This innovative blend of technology aims to enhance cybersecurity measures and protect users from potential threats hidden within QR codes 🖥 🔒
This study was my first introduction to using ML which has shown me the immense potential of ML in creating more secure digital environments!
In our second session, we shall learn all about the main features and fundamentals of UiPath Studio that enable us to use the building blocks for any automation project.
📕 Detailed agenda:
Variables and Datatypes
Workflow Layouts
Arguments
Control Flows and Loops
Conditional Statements
💻 Extra training through UiPath Academy:
Variables, Constants, and Arguments in Studio
Control Flow in Studio
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Keywords: AI, Containeres, Kubernetes, Cloud Native
Event Link: https://meine.doag.org/events/cloudland/2024/agenda/#agendaId.4211
"Choosing proper type of scaling", Olena SyrotaFwdays
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
What is an RPA CoE? Session 2 – CoE RolesDianaGray10
In this session, we will review the players involved in the CoE and how each role impacts opportunities.
Topics covered:
• What roles are essential?
• What place in the automation journey does each role play?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
Northern Engraving | Modern Metal Trim, Nameplates and Appliance PanelsNorthern Engraving
What began over 115 years ago as a supplier of precision gauges to the automotive industry has evolved into being an industry leader in the manufacture of product branding, automotive cockpit trim and decorative appliance trim. Value-added services include in-house Design, Engineering, Program Management, Test Lab and Tool Shops.
Must Know Postgres Extension for DBA and Developer during MigrationMydbops
Mydbops Opensource Database Meetup 16
Topic: Must-Know PostgreSQL Extensions for Developers and DBAs During Migration
Speaker: Deepak Mahto, Founder of DataCloudGaze Consulting
Date & Time: 8th June | 10 AM - 1 PM IST
Venue: Bangalore International Centre, Bangalore
Abstract: Discover how PostgreSQL extensions can be your secret weapon! This talk explores how key extensions enhance database capabilities and streamline the migration process for users moving from other relational databases like Oracle.
Key Takeaways:
* Learn about crucial extensions like oracle_fdw, pgtt, and pg_audit that ease migration complexities.
* Gain valuable strategies for implementing these extensions in PostgreSQL to achieve license freedom.
* Discover how these key extensions can empower both developers and DBAs during the migration process.
* Don't miss this chance to gain practical knowledge from an industry expert and stay updated on the latest open-source database trends.
Mydbops Managed Services specializes in taking the pain out of database management while optimizing performance. Since 2015, we have been providing top-notch support and assistance for the top three open-source databases: MySQL, MongoDB, and PostgreSQL.
Our team offers a wide range of services, including assistance, support, consulting, 24/7 operations, and expertise in all relevant technologies. We help organizations improve their database's performance, scalability, efficiency, and availability.
Contact us: info@mydbops.com
Visit: https://www.mydbops.com/
Follow us on LinkedIn: https://in.linkedin.com/company/mydbops
For more details and updates, please follow up the below links.
Meetup Page : https://www.meetup.com/mydbops-databa...
Twitter: https://twitter.com/mydbopsofficial
Blogs: https://www.mydbops.com/blog/
Facebook(Meta): https://www.facebook.com/mydbops/
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...Jason Yip
The typical problem in product engineering is not bad strategy, so much as “no strategy”. This leads to confusion, lack of motivation, and incoherent action. The next time you look for a strategy and find an empty space, instead of waiting for it to be filled, I will show you how to fill it in yourself. If you’re wrong, it forces a correction. If you’re right, it helps create focus. I’ll share how I’ve approached this in the past, both what works and lessons for what didn’t work so well.
This talk will cover ScyllaDB Architecture from the cluster-level view and zoom in on data distribution and internal node architecture. In the process, we will learn the secret sauce used to get ScyllaDB's high availability and superior performance. We will also touch on the upcoming changes to ScyllaDB architecture, moving to strongly consistent metadata and tablets.
1. “Because as rapid as the arrival of
networked pull media was,
the second act - networked push
media - is coming even faster. ”
WIRED Magazine
March 1997
Thursday, March 11, 2010
2. Push
A 2010 case study with
the NGINX HTTP Push Module,
Ruby on Rails, and friends
Luke Melia
Thursday, March 11, 2010
3. Who’s this guy?
★ VP, Engineering at weplay.com
★ Agilist
★ nyc.rb’er since ~2006
★ Ruby in Practice contributor
★ Interested in startup tech leadership
★ Beach volleyball player
★ Dad
Thursday, March 11, 2010
4. What’s this talk?
★ The goal and the problem
★ A quick survey of solutions
★ About the NGINX HTTP Push Module
★ How to use it with Ruby, by example
★ Gotchyas
★Q &A
Thursday, March 11, 2010
5. The Goal
★ Immediate encouragement
of positive on-site actions
★ “Points!”
Thursday, March 11, 2010
7. Constraints
★ Don’t want to figure out points earned
while processing the request (offload it to a
background work queue)
★ Do want to inform about points earned
through another user’s actions
★ Don’t want to wait for a second page load
Thursday, March 11, 2010
8. Pure push
doesn’t exist
on the open web
Thursday, March 11, 2010
10. ★ Don’t close the connection after
sending down the page
★ multipart/x-mixed-replace
★ Supported in non-Microsoft
browsers only
Streaming
Thursday, March 11, 2010
11. XMPP
★ Designed for presence and messaging
★ Browsers don’t speak XMPP natively
★ BOSH
★ Hemlock: Flex + ejabberd, by NYC’s
Mint Digital
Thursday, March 11, 2010
12. ★ Push data over a long held Ajax
request using browser-native
technologies
★ Bayeaux protocol
★ Long-polling Ajax
Comet
Thursday, March 11, 2010
13. WebSockets
★ HTML 5
★ Full-duplex single socket connection
between browser and server
★ ex: ws://websockets.org:8787
★ very limited browser support today
Thursday, March 11, 2010
14. XMPP WebSockets
Streaming Comet
Thursday, March 11, 2010
16. NGINX HTTP Push Module
★ Turns NGINX into a Comet server
★ “A useful tool with a boring name.”
★ By Leo P
★ http://pushmodule.slact.net/
★ Currently at 0.692β
Thursday, March 11, 2010
17. Basic HTTP Push
Relay Protocol
★ Subscriber locations
★ HTTP GET with channel ID
★ Publisher locations
★ HTTP POST with channel ID
★ POSTed data is passed through,
becoming the response to the
subscriber’s GET
Thursday, March 11, 2010
18. Diagramming the simple case
BACK-END
PROCESS
2. HTTP POST
Publisher endpoint
3. POST BODY
NGINX
IS ROUTED BY
CHANNEL ID
Subscriber endpoint
4. RESPONSE IS
1. HTTP GET DATA FROM
POST BODY
End User
Thursday, March 11, 2010
22. Diagram with storage
BACK-END
PROCESS
1. HTTP POST
4. MESSAGE Publisher endpoint
2. POST BODY
IS RETRIEVED
IS QUEUED
FROM QUEUE NGINX
Queue
BY CHANNEL ID
BY CHANNEL ID
Subscriber endpoint
5. RESPONSE IS
3. HTTP GET DATA FROM
QUEUE
End User
Thursday, March 11, 2010
24. Client-side Gotchas
★ Javascript blocking
★ Put it in an iframe
★ Per domain connection limit
★ use subdomain, with JSONP
Thursday, March 11, 2010
25. Server-side Gotchas
★ “Too many open connections”
★ Reduce worker_connections to less
than ulimit -n
★ Increase worker_processes to give
you enough total connection to
serve your users
★ Ours: worker_processes 24
worker_connections 960
Thursday, March 11, 2010
26. Testing
★ Fake Publisher for in-memory
cucumber scenarios
★ Run selenium scenarios through
NGINX to incorporate actual
push module behavior
Thursday, March 11, 2010
27. NGINX Configuration
Management
★Template it
★Version
it
★Automate it
Thursday, March 11, 2010
28. The Future
★ Multiplexing: subscribe
to more than one
channel
★ Use Redis as a
message store
★ Convention-based
approach for raising
javascript events
Thursday, March 11, 2010