The document discusses Firebase and its features for building realtime web and mobile applications. It explains that Firebase provides a database, authentication, security, and hosting capabilities. It also outlines how to set up Firebase in an Android app by including the library, setting the context, reading and writing data to the database, and enabling different authentication methods. Security rules and offline capabilities with Firebase are also briefly mentioned.
This document discusses AWS Step Functions and how it can be used to orchestrate serverless applications and functions. It provides examples of how Step Functions allows developers to sequence functions, select functions based on data, retry functions, implement try/catch/finally blocks, run functions in parallel, and coordinate long-running code. It also discusses how Step Functions is scalable, maintains state, handles errors/timeouts, is easy to build and operate, and provides auditable workflows. The document contains examples of JSON state machine definitions and demonstrates how Step Functions integrates with other AWS services.
Application Performance Management - Solving the Performance PuzzleLDragich
The document outlines a methodology for Application Performance Management (APM). It discusses various components of an APM strategy including top-down monitoring, bottom-up monitoring, reporting and analytics, and aligning with ITIL processes. Top-down monitoring focuses on real-time application monitoring using techniques like synthetic transactions. Bottom-up monitoring ties into infrastructure monitoring tools. Reporting and analytics is used to analyze performance data and establish baselines. APM supports various ITIL processes like incident management, problem management and service level management.
Email authentication using firebase auth + flutterKaty Slemon
Learn about building a demo application from scratch and implementing email authentication using Firebase auth + flutter with a ready github repository.
In this session we’ll take a high-level overview of AWS Lambda, a serverless compute platform that has changed the way that developers around the world build applications. We’ll explore how Lambda works under the hood, the capabilities it has, and how it is used. By the end of this talk you’ll know how to create Lambda based applications and deploy and manage them easily.
Speaker: Chris Munns - Principal Developer Advocate, AWS Serverless Applications, AWS
This document discusses key concepts related to cloud adoption and cloud rudiments. For cloud adoption, it states that cloud is suitable for low priority or short term projects that have low availability requirements and short life spans. For cloud rudiments, it outlines essential cloud capabilities like resource aggregation, application services, self-service portals, and dynamic resource management. It also discusses concepts like reservation of services, allocation engines, reporting and accounting, and metering of resources.
The document provides an overview of the Software Development Life Cycle (SDLC), including:
- The SDLC is a process consisting of planned activities to develop or alter software products. It aims to produce high-quality software that meets requirements.
- Common SDLC models include waterfall, iterative, spiral, V-model, big bang, agile, RAD, and prototyping. Each has distinct phases and approaches.
- The waterfall model is sequential with distinct phases like planning, design, implementation, testing, and deployment. It works well for small, stable projects but not for complex projects with changing requirements.
The document discusses Firebase and its features for building realtime web and mobile applications. It explains that Firebase provides a database, authentication, security, and hosting capabilities. It also outlines how to set up Firebase in an Android app by including the library, setting the context, reading and writing data to the database, and enabling different authentication methods. Security rules and offline capabilities with Firebase are also briefly mentioned.
This document discusses AWS Step Functions and how it can be used to orchestrate serverless applications and functions. It provides examples of how Step Functions allows developers to sequence functions, select functions based on data, retry functions, implement try/catch/finally blocks, run functions in parallel, and coordinate long-running code. It also discusses how Step Functions is scalable, maintains state, handles errors/timeouts, is easy to build and operate, and provides auditable workflows. The document contains examples of JSON state machine definitions and demonstrates how Step Functions integrates with other AWS services.
Application Performance Management - Solving the Performance PuzzleLDragich
The document outlines a methodology for Application Performance Management (APM). It discusses various components of an APM strategy including top-down monitoring, bottom-up monitoring, reporting and analytics, and aligning with ITIL processes. Top-down monitoring focuses on real-time application monitoring using techniques like synthetic transactions. Bottom-up monitoring ties into infrastructure monitoring tools. Reporting and analytics is used to analyze performance data and establish baselines. APM supports various ITIL processes like incident management, problem management and service level management.
Email authentication using firebase auth + flutterKaty Slemon
Learn about building a demo application from scratch and implementing email authentication using Firebase auth + flutter with a ready github repository.
In this session we’ll take a high-level overview of AWS Lambda, a serverless compute platform that has changed the way that developers around the world build applications. We’ll explore how Lambda works under the hood, the capabilities it has, and how it is used. By the end of this talk you’ll know how to create Lambda based applications and deploy and manage them easily.
Speaker: Chris Munns - Principal Developer Advocate, AWS Serverless Applications, AWS
This document discusses key concepts related to cloud adoption and cloud rudiments. For cloud adoption, it states that cloud is suitable for low priority or short term projects that have low availability requirements and short life spans. For cloud rudiments, it outlines essential cloud capabilities like resource aggregation, application services, self-service portals, and dynamic resource management. It also discusses concepts like reservation of services, allocation engines, reporting and accounting, and metering of resources.
The document provides an overview of the Software Development Life Cycle (SDLC), including:
- The SDLC is a process consisting of planned activities to develop or alter software products. It aims to produce high-quality software that meets requirements.
- Common SDLC models include waterfall, iterative, spiral, V-model, big bang, agile, RAD, and prototyping. Each has distinct phases and approaches.
- The waterfall model is sequential with distinct phases like planning, design, implementation, testing, and deployment. It works well for small, stable projects but not for complex projects with changing requirements.
VP of APM, Aruna Ravichandran of CA Technologies walks you through what Application Performance Management really is and discusses some of the major benefits of using the software.
Learn more about APM solutions from CA Technologies at http://www.ca.com/apm
AWS Cloud Computing Tutorial | Migrating on Premise VM to AWS Cloud | AWS Tra...Edureka!
** AWS Certification Training: https://www.edureka.co/cloudcomputing **
** Migration Training to AWS: https://www.edureka.co/migrating-to-aws **
This Edureka "AWS Cloud Computing Tutorial” will introduce you to the fundamentals of AWS and Cloud Computing and also explain various migration concepts. Following is the list of content covered in this tutorial:
1. What is Cloud?
2. Cloud Computing Basics
3. What Is AWS?
4. Migration
5. Migration Strategies
6. Demo
Check out our AWS Playlist: https://goo.gl/8qrfKU
AWS CLI Installation : https://goo.gl/gjniYx
AWS Migration Codes: https://goo.gl/veyZvW
This document discusses cross-platform mobile application development. It covers native, web, and hybrid approaches. Native apps are developed for specific platforms using languages like Java and Objective-C. Web apps use HTML5, CSS, and JavaScript and can be accessed via a browser. Hybrid apps combine web technologies with native features using frameworks like NativeScript, React Native, and Xamarin. These frameworks allow building native mobile apps with shared codebases across platforms.
This document provides an introduction to Firebase, a mobile and web application development platform. It discusses what Firebase is, its use cases, features like its realtime database and security rules. The document also covers Firebase's pricing, history, and alternatives. Firebase provides tools to create applications without server-side programming and allows for realtime syncing of data across clients. It advocates for structuring data in a flattened, scalable manner and provides security rules to control access.
AWS offers customers a range of different database options. These include Amazon DynamoDB, a fully-managed NoSQL database service that makes it simple and cost-effective to store and retrieve any amount of data as well as Amazon Relational Database Service (RDS), a service that makes it easy to set up, operate, and scale a relational database in the cloud with support for MySQL, Microsoft SQL Server, PostgreSQL, and Oracle Database. In this session you’ll get an overview of AWS database options and how they might help support your application and see how to get started.
Android Intents allow communication between app components and sharing of data. An Intent specifies an action and can contain data and extras. There are explicit intents, which target a specific component, and implicit intents, which specify an action that may be handled by multiple apps. Components declare intent filters in the manifest to receive implicit intents matching the filter's action, data, and category. When an implicit intent is received, the system resolves matching components by comparing the intent to intent filters.
Rapid Application Development (RAD) is an incremental software development process used to build systems within 60-90 days. It involves business, data, and process modeling, application generation, and testing. RAD is based on agile methods like Scrum and extreme programming and enables quick reviews, constant integration, and flexibility. However, it requires a modularized approach and skilled developers, and is not suitable for small projects or all applications due to higher costs.
This document discusses different approaches to requirements modeling including scenario-based modeling using use cases and activity diagrams, data modeling using entity-relationship diagrams, and class-based modeling using class-responsibility-collaborator diagrams. Requirements modeling depicts requirements using text and diagrams to help validate requirements from different perspectives and uncover errors, inconsistencies, and omissions. The models focus on what the system needs to do at a high level rather than implementation details.
AWS Elastic Beanstalk is a service that allows developers to quickly deploy and manage applications in the AWS cloud without worrying about the underlying infrastructure. It provides an easy way to launch applications developed in Java or other languages and have them automatically scaled across Amazon EC2 instances. Key features include automated provisioning and deployment, easy management of settings, built-in monitoring, and troubleshooting tools. Developers retain full control over their AWS resources while taking advantage of Elastic Beanstalk's management capabilities.
Customer case - Dynatrace Monitoring RedefinedMichel Duruel
One of the largest Airline in the world chose Dynatrace, here is the customer case.
Including:
Vision and Goal / Challenges / Requirements / Why Dynatrace is Unique / ROI and TCO / Rollout Status / Solution Screenshots
Dynatrace redefined monitoring with AI powered 3rd Generation APM, User Experience Monitoring & Continuous Improvement, Cloud-native, Full Stack, Auto Everything, End-to-End, Easiest to Implement, Use and Maintain
Learn how the Blue/Green Deployment methodology combined with AWS tools and services can help reduce the risks associated with software deployment. We will illustrate common patterns and highlight ways deployment risks are mitigated by each pattern. Topics will include how services like AWS CloudFormation, AWS Elastic Beanstalk, Amazon EC2 Container Service, Amazon Route53, Auto Scaling and Elastic Load Balancing can help automate deployment. We will also address how to effectively manage deployments in the context of data model and schema changes. Learn how you can adopt blue/green for your software release processes in a cost-effective and low-risk way.
This document is a tutorial for learning Apache Spark with Python. It covers topics like configuring Spark on different platforms, an introduction to Spark's core concepts and architecture, and programming with RDDs. It then demonstrates various machine learning techniques in Spark like regression, classification, clustering, and neural networks. It also discusses automating Spark pipelines and packaging PySpark code.
The document provides an overview of cloud computing, including its basic concepts, deployment models (public, private, hybrid, community clouds), technologies (virtualization, service-oriented architecture, grid computing, utility computing), architecture, infrastructure, planning process, and benefits and risks of different cloud models. It is intended as a tutorial for beginners to understand cloud computing concepts.
[DevSecOps Live] DevSecOps: Challenges and OpportunitiesMohammed A. Imran
In this Practical DevSecOps's DevSecOps Live online meetup, you’ll learn DevSecOps Challenges and Opportunities.
Join Mohan Yelnadu, head of application security at Prudential Insurance on his DevSecOps Journey.
He will cover DevSecOps challenges he has faced and how he converted them into opportunities.
He will cover the following as part of the session.
DevSecOps Challenges.
DevSecOps Opportunities.
Converting Challenges into Opportunities.
Quick wins and lessons learned.
… and more useful takeaways!
This document summarizes the Rails request lifecycle and describes various middlewares used in Rails. It begins by explaining what a request is and how it travels from the browser to the Rails application. It then discusses the roles of the web server and app server. The bulk of the document describes each middleware in the Rails stack, from Rack middlewares to ActionDispatch middlewares to ActiveRecord middlewares. It explains what each middleware does to filter requests and responses. Finally, it outlines how the request travels through the middleware stack to the routes, controller, and back out again to complete the response sent to the client.
Rack provides a minimal and modular interface for building web applications in Ruby. It handles HTTP requests and responses, acting as an interface between web servers and frameworks. Rails uses Rack middleware to handle requests, with Action Controller implemented as middleware. The routing table maps routes to controller actions. When a request comes in, it is passed through middleware before being routed and dispatched to the controller action to generate a response.
VP of APM, Aruna Ravichandran of CA Technologies walks you through what Application Performance Management really is and discusses some of the major benefits of using the software.
Learn more about APM solutions from CA Technologies at http://www.ca.com/apm
AWS Cloud Computing Tutorial | Migrating on Premise VM to AWS Cloud | AWS Tra...Edureka!
** AWS Certification Training: https://www.edureka.co/cloudcomputing **
** Migration Training to AWS: https://www.edureka.co/migrating-to-aws **
This Edureka "AWS Cloud Computing Tutorial” will introduce you to the fundamentals of AWS and Cloud Computing and also explain various migration concepts. Following is the list of content covered in this tutorial:
1. What is Cloud?
2. Cloud Computing Basics
3. What Is AWS?
4. Migration
5. Migration Strategies
6. Demo
Check out our AWS Playlist: https://goo.gl/8qrfKU
AWS CLI Installation : https://goo.gl/gjniYx
AWS Migration Codes: https://goo.gl/veyZvW
This document discusses cross-platform mobile application development. It covers native, web, and hybrid approaches. Native apps are developed for specific platforms using languages like Java and Objective-C. Web apps use HTML5, CSS, and JavaScript and can be accessed via a browser. Hybrid apps combine web technologies with native features using frameworks like NativeScript, React Native, and Xamarin. These frameworks allow building native mobile apps with shared codebases across platforms.
This document provides an introduction to Firebase, a mobile and web application development platform. It discusses what Firebase is, its use cases, features like its realtime database and security rules. The document also covers Firebase's pricing, history, and alternatives. Firebase provides tools to create applications without server-side programming and allows for realtime syncing of data across clients. It advocates for structuring data in a flattened, scalable manner and provides security rules to control access.
AWS offers customers a range of different database options. These include Amazon DynamoDB, a fully-managed NoSQL database service that makes it simple and cost-effective to store and retrieve any amount of data as well as Amazon Relational Database Service (RDS), a service that makes it easy to set up, operate, and scale a relational database in the cloud with support for MySQL, Microsoft SQL Server, PostgreSQL, and Oracle Database. In this session you’ll get an overview of AWS database options and how they might help support your application and see how to get started.
Android Intents allow communication between app components and sharing of data. An Intent specifies an action and can contain data and extras. There are explicit intents, which target a specific component, and implicit intents, which specify an action that may be handled by multiple apps. Components declare intent filters in the manifest to receive implicit intents matching the filter's action, data, and category. When an implicit intent is received, the system resolves matching components by comparing the intent to intent filters.
Rapid Application Development (RAD) is an incremental software development process used to build systems within 60-90 days. It involves business, data, and process modeling, application generation, and testing. RAD is based on agile methods like Scrum and extreme programming and enables quick reviews, constant integration, and flexibility. However, it requires a modularized approach and skilled developers, and is not suitable for small projects or all applications due to higher costs.
This document discusses different approaches to requirements modeling including scenario-based modeling using use cases and activity diagrams, data modeling using entity-relationship diagrams, and class-based modeling using class-responsibility-collaborator diagrams. Requirements modeling depicts requirements using text and diagrams to help validate requirements from different perspectives and uncover errors, inconsistencies, and omissions. The models focus on what the system needs to do at a high level rather than implementation details.
AWS Elastic Beanstalk is a service that allows developers to quickly deploy and manage applications in the AWS cloud without worrying about the underlying infrastructure. It provides an easy way to launch applications developed in Java or other languages and have them automatically scaled across Amazon EC2 instances. Key features include automated provisioning and deployment, easy management of settings, built-in monitoring, and troubleshooting tools. Developers retain full control over their AWS resources while taking advantage of Elastic Beanstalk's management capabilities.
Customer case - Dynatrace Monitoring RedefinedMichel Duruel
One of the largest Airline in the world chose Dynatrace, here is the customer case.
Including:
Vision and Goal / Challenges / Requirements / Why Dynatrace is Unique / ROI and TCO / Rollout Status / Solution Screenshots
Dynatrace redefined monitoring with AI powered 3rd Generation APM, User Experience Monitoring & Continuous Improvement, Cloud-native, Full Stack, Auto Everything, End-to-End, Easiest to Implement, Use and Maintain
Learn how the Blue/Green Deployment methodology combined with AWS tools and services can help reduce the risks associated with software deployment. We will illustrate common patterns and highlight ways deployment risks are mitigated by each pattern. Topics will include how services like AWS CloudFormation, AWS Elastic Beanstalk, Amazon EC2 Container Service, Amazon Route53, Auto Scaling and Elastic Load Balancing can help automate deployment. We will also address how to effectively manage deployments in the context of data model and schema changes. Learn how you can adopt blue/green for your software release processes in a cost-effective and low-risk way.
This document is a tutorial for learning Apache Spark with Python. It covers topics like configuring Spark on different platforms, an introduction to Spark's core concepts and architecture, and programming with RDDs. It then demonstrates various machine learning techniques in Spark like regression, classification, clustering, and neural networks. It also discusses automating Spark pipelines and packaging PySpark code.
The document provides an overview of cloud computing, including its basic concepts, deployment models (public, private, hybrid, community clouds), technologies (virtualization, service-oriented architecture, grid computing, utility computing), architecture, infrastructure, planning process, and benefits and risks of different cloud models. It is intended as a tutorial for beginners to understand cloud computing concepts.
[DevSecOps Live] DevSecOps: Challenges and OpportunitiesMohammed A. Imran
In this Practical DevSecOps's DevSecOps Live online meetup, you’ll learn DevSecOps Challenges and Opportunities.
Join Mohan Yelnadu, head of application security at Prudential Insurance on his DevSecOps Journey.
He will cover DevSecOps challenges he has faced and how he converted them into opportunities.
He will cover the following as part of the session.
DevSecOps Challenges.
DevSecOps Opportunities.
Converting Challenges into Opportunities.
Quick wins and lessons learned.
… and more useful takeaways!
This document summarizes the Rails request lifecycle and describes various middlewares used in Rails. It begins by explaining what a request is and how it travels from the browser to the Rails application. It then discusses the roles of the web server and app server. The bulk of the document describes each middleware in the Rails stack, from Rack middlewares to ActionDispatch middlewares to ActiveRecord middlewares. It explains what each middleware does to filter requests and responses. Finally, it outlines how the request travels through the middleware stack to the routes, controller, and back out again to complete the response sent to the client.
Rack provides a minimal and modular interface for building web applications in Ruby. It handles HTTP requests and responses, acting as an interface between web servers and frameworks. Rails uses Rack middleware to handle requests, with Action Controller implemented as middleware. The routing table maps routes to controller actions. When a request comes in, it is passed through middleware before being routed and dispatched to the controller action to generate a response.
Rails is a web application framework written in Ruby that makes programming web applications easier. The key principles of Rails are DRY (Don't Repeat Yourself), convention over configuration, and using RESTful architecture. Rails uses the MVC pattern with models representing data, views representing the user interface, and controllers handling requests and passing data between models and views. Creating a Rails application involves generating the app, setting up the database schema through migrations, and using validations and callbacks to control object state changes.
An Overview of the React Ecosystem
with Rami Sayar
OVERVIEW
React has been named the front-end library to learn in 2016 however few people talk about the React without mentioning Flux (or Redux or React Native or Relay). In this talk, we will explore the ecosystem of tools and libraries that surround React. We will look at the various Flux implementations (including a short explanation of Flux) like Redux, at some of the React routing libraries, at some of the reactive database or reactive API libraries and finally at everyday tools and techniques that make the React developer happy. By the end of this talk, you will have a greater grasp of the ecosystem and leave with new tools in your developer arsenal.
OBJECTIVE
Learn about the React Ecosystem
TARGET AUDIENCE
Front-End Developers with knowledge of JavaScript, React Beginners
ASSUMED AUDIENCE KNOWLEDGE
JavaScript, Front-End Dev, Beginner React
FIVE THINGS AUDIENCE MEMBERS WILL LEARN
What is Flux?
What is Redux
What is React Native
What is Relay (and other Reactive Databases/APIs)
Useful React Dev Tools
The document discusses setting up a Ruby on Rails web application. It explains how to install Ruby and Rails, configure the database, and generate models. The Rails directory structure is described, including the app, config, and db folders. Finally, it shows how to start the web server and create a basic Rails application.
Ruby on Rails is a full-stack web application framework written in Ruby. It allows developers to build database-backed web applications rapidly using conventions like MVC pattern and follows "convention over configuration" principle. Rails includes features like Active Record (ORM), validations, migrations, scaffolding, routing and helpers to help develop web applications quickly. Testing is an important part of Rails development using tools like RSpec, Factory Girl, Cucumber and Capybara.
Ruby on Rails is a full-stack web application framework written in Ruby. It uses the MVC pattern and convention over configuration principles. Rails makes it possible to develop database-backed web applications rapidly by minimizing configuration through conventions and providing scaffolding. Key Rails concepts include Active Record for ORM, migrations for schema changes, routing for URLs, controllers for application logic, views for presentation, and testing frameworks. Rails emphasizes productivity through conventions that reduce configuration overhead.
This document discusses Rack, a modular Ruby web server interface.
It describes problems with different web servers and frameworks, and how Rack provides an abstraction layer through a simple request-response interface. Rack middleware is explained, as well as how Rails integrates with Rack. Examples of Rack applications and middleware are provided.
Ruby on Rails is an open source web application framework that allows developers to create database-backed web applications quickly using conventions over configurations. Rails emphasizes less code and faster development through features like scaffolding that can generate basic CRUD functionality and views in minutes. Popular sites like Basecamp and 43 Things were built using Ruby on Rails by small teams in short periods of time due to Rails' conventions and built-in features for caching, validation, callbacks, and Ajax support.
This document provides an overview of Ruby on Rails, a web application framework written in Ruby. It discusses what Ruby and Rails are, the key strengths of Rails like productivity and convention over configuration. It then demonstrates how to build a basic Rails application, including generating models and controllers, scaffolding, and adding relationships between models. The document aims to introduce developers to Ruby on Rails and demonstrate its capabilities.
This document provides an overview and agenda for a presentation on TorqueBox, which allows running Ruby on Rails applications with enterprise capabilities by running them on the JBoss application server. The presentation covers how Rails applications can be deployed on TorqueBox to gain access to services like the web container, message bus, and databases. It also discusses how additional features like scheduled jobs, asynchronous task queues, and SOAP endpoints can be integrated by following Rails-like conventions.
This document introduces React on Rails, which allows using React, Redux, and React-Router within Ruby on Rails views. It discusses using Webpack and NPM to manage front-end assets, integrating React components with Rails, supporting features like hot reloading and server rendering, and sharing Redux stores between components. React on Rails provides helpers, configuration, and documentation to facilitate building JavaScript-rich UIs with Rails.
Ruby On Rails Seminar Basis Softexpo Feb2010arif44
This document provides an introduction and overview of Ruby on Rails (RoR), including its background, key features like MVC architecture and ActiveRecord ORM, and how it delivers business value through rapid application development. Rails simplifies and speeds up the web development process using conventions over configurations and Don't Repeat Yourself principles. It also includes examples of popular websites built with Rails and concludes with a discussion of actions, controllers and templates in the MVC framework.
This document provides an overview of prerequisites for developing a Ruby on Rails application. It discusses key concepts like MVC, REST, and installation steps. It then demonstrates creating a sample "greeting" application by generating a controller, updating routes, and adding an index action that renders text. The document emphasizes following MVC patterns by updating the controller to assign a variable for the view, and updating the view to display it. It also explains that ERB files allow embedding Ruby code for logic and display.
I prepared this presentation to introduce Ruby on Rails to
a group of students at Università di Catania.
It is not enough to get a good grasp of Rails, the
presentation in fact was supported by live coding, where
I started created a Phrasalbook (no more blog engine
please :) )
Ruby on Rails is an open source web application framework written in Ruby that is intended to be used with an Agile development methodology. It provides pre-built components and tools to help developers build web applications quickly without having to reinvent the wheel for basic functions like working with databases and handling web requests. Rails includes common components needed for application building like a database, web server, and object relational mapping library to simplify accessing databases and converting records to objects.
This document provides an overview of Ruby on Rails, including what it is, how to install it, how to create a sample Rails application, and recommended resources for learning more. Ruby on Rails is an open source web application framework written in Ruby. It uses a model-view-controller pattern and convention over configuration approach to provide a full stack framework for developing database-backed web applications rapidly.
Web Clients for Ruby and What they should be in the futureToru Kawamura
Toru Kawamura discusses the need for web clients in Ruby to be adaptable to change by being decoupled and easy to reuse through versatility. He outlines some of the issues with existing tightly coupled clients and gems dedicated to specific APIs. Kawamura proposes a "Web Client" concept modeled after Rack middleware and Faraday middleware, which can be combined and reused across clients and APIs. He demonstrates implementations of this concept through the faraday-hypermedia and faraday-link-extractor gems. The presentation argues that a decoupled, modular approach to web clients following standards can help address current issues around rigid coupling and lack of reusability.
How to Build a Big Data Application: Serverless Editionecobold
Come learn how to build, launch, and scale a Big Data application in a serverless context. This is going to be an information packed meetup around Big Data processing, Lambda functions, Lambda Step functions, and everything that ties them together.
Big Data is something we're very passionate about. As the cost of servers have come down and the cost of software has become free, using data to drive your business has become much more obtainable to a larger group of companies. The serverless methodology has recently come in the scene, and it's proving to be just as transformational as cloud has been to the Big Data analytics space. We will be sharing some of our learnings and experiences over the last two years of working with Big Data in a serverless context. We will cover one or two examples of eventful Big Data processing, and the impact it can have on your business in terms of speed of analytics and cost savings to the bottom line.
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?Speck&Tech
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
Infrastructure Challenges in Scaling RAG with Custom AI modelsZilliz
Building Retrieval-Augmented Generation (RAG) systems with open-source and custom AI models is a complex task. This talk explores the challenges in productionizing RAG systems, including retrieval performance, response synthesis, and evaluation. We’ll discuss how to leverage open-source models like text embeddings, language models, and custom fine-tuned models to enhance RAG performance. Additionally, we’ll cover how BentoML can help orchestrate and scale these AI components efficiently, ensuring seamless deployment and management of RAG systems in the cloud.
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
8. Request is a…
• It is set of instructions that tells a server what
kind of response we want.
• It is a part of HTTP (request/response) protocol.
• HTTP uses one of the verbs like GET, POST, PUT
& DELETE when you perform the request to the
server.
13. What is a Web Server?
• Web Server is strictly HTTP based, it just takes
HTTP requests and sends back HTTP responses
to the clients(browsers).
• It is mostly designed to serve static files.
• It also has other functionality like request
pipeline, load balancing etc. App servers lack
these functionalities.
• E.g. Ngnix, Apache
15. What is an App Server?
• App Server actually runs your Rails app.
• App Server is mostly known for to serve dynamic
pages.
• E.g. Webrick, Passenger, Mongrel, Unicorn, Thin,
Puma & etc.
16. Request to Rails app
• Rails isn’t just one application, it has lots of
independent Rack applications (middlewares).
• When request comes to the Rails app, it goes
through the list of middleware series.
• Last part of that series, sends request to the
routes file.
17. Request to Rails app
• Based on request, Rails decides which controller
& action need to be executed from the routes file.
• After executing the controller’s action, Rails sends
back response to the the client.
• Web Server & App Server actually handle the job
of sending response back to the proper client.
19. What is a Middleware?
• Middleware is a Rack application.
• Middleware is basically a filter for request and
response.
20. Rails Middlewares
App
Server
Rails App
A B C D
Routes
Controller
Models
Views
Here A, B, C & D are middlewares
Each of these does processing on request & response
21. Why Rails uses Middlewares?
• Before rails 3, Rails was very tightly coupled.
• As Rails was growing, apps built on Rails had more
demanding requirements. For some apps, Rails gave
lots of additional stuffs by default, which was not
required like cookies/flash. For some other apps, to
implement new filter on the the request/response was
not possible.
• In Rails 3 and after, all these issues have got solved by
using a concept of Rack.
23. What is a Rack?
• Rack is not Rake.
• Rack is simple but powerful spec. Yes it is just
spec.
• It is not web framework or web server.
• Rack is created by Christian Neukirchen
24. Rack - Just an Interface
• It is an interface that sits between your web/app
server and your application. It wraps HTTP
requests and responses in the simplest way
possible, it unifies and distills the API for web
servers, web frameworks and software in
between (i.e. middleware) into a single method
call.
25. Rack Specification
• Specification: A Rack application is a Ruby object
(not a class) that responds to `call`. It takes
exactly one argument, the environment and
returns an Array of three values, The status, the
headers, and the body. That’s it.
26. Why do we need Rack?
• Rack promotes low coupling.
• If there was’t Rack, then each framework had to
add separate handler for Thin, Mongrel, Unicorn
and etc to run the app on these servers.
• In reality it’s not a job of framework. They should
not need to take care of it.
30. Using Middleware in a Rack app
• Using ‘use’ method of Rack, you can use
middleware component in Rack application.
• You can use multiple middleware components
which help to change request/response as you
need.
• You can add middlewares by using two methods.
By directly adding middleware in config.ru
and using Rack::Builder.
34. What is Rack::Builder?
• Rack::Builder implements a small DSL to
iteratively construct Rack applications.
• Rack::Builder is the thing that glues Rack
middlewares and application together and
converts them into single entity/rack application.
• Under the hood, ‘rackup’ command converts
your config.ru script to an instance of
Rack::Builder.
37. Rails on Rack
• Rails application is the primary Rack
application object.
• It has ‘call’ method similar to rack’s ‘call’
method in its source code (i.e. in
Rails::Application).
38. Rails’ Rack::Builder
• Same like Rack::Builder, we have similar
concept in Rails, it is called as
ActionDispatch::MiddlewareStack.
• Better flexibility and more features to meet Rails’
requirement.
39. Rails’ Rack::Builder
• Rails::Application uses
ActionDispatch::MiddlewareStack to
combine various internal and external
middlewares to form a complete Rails Rack
application.
40. Inspecting Rails Middlewares
• Rails provides a task for inspecting the
middleware stack in use.
• $ bin/rake middleware
42. Using Middleware in Rails
• Rails provides a simple configuration interface
config.middleware for adding, removing and
modifying the middlewares in the middleware stack via
application.rb or the environment specific configuration
file environments/<environment>.rb.
• Using these methods config.middleware.use,
config.middleware.insert_before,
config.middleware.insert_after, you can add
new middleware to the middleware stack.
• It also provides ‘swap’ and ‘delete’ methods for
swapping and deleting a middleware.
43. Add this file under config/initializers directory
And under config/application.rb file, add this following line
config.middleware.use "SayHelloMiddlware"
44. Always Remember That…
• When request comes to your Rails app, it goes
through these middlewares. From top to bottom.
• At the bottom, request enters into the your Rails’
MVC area.
In simple way, when we hit any url in the browser for some file, that browser converts that url into the request message and sends to the server and that request message is your actual request :)
When you want to get some data from the server, you use GET method.
When we want to create new data on the server, we use POST method.
When we want to update data like username we use PUT method.
For destroying the data we use DELETE verb.
There are also other methods like, HEAD, PATCH, OPTIONS, CONNECT & ETC which HTTP protocol provides.
This is a basic and standard diagram of Rails Request Life Cycle.
You can see here, When browser initiates the requests it goes to Web Server, From the Web Server It goes through the App server, From App Server, request enters into the Rails app.
Now if you see in the Rails app, request goes through the series of middlewares, From there request goes to the routes file and Based on request, Rails decides which controller & action need to be executed from the routes file. Now in controller if there is any business logic, it goes to model and from there it will fetch data from database or store the data in the database.
If there any view like html, then request goes to view. After processing it, controller sends back the response to Browser.
In this diagram, I’m showing how app server and rails app communicate with each other.
Communications between App Server and Rails app happen using Rack. Rack is a gem and acts as an interface between them. We will see more on rack in next slides.
It recognises Ruby application request and then it forwards its request to app server.
Web Server forwards its request to the App Server, and App Server in turn forwards that request to the Rails app.
In development mode, App Server can play role of web server too. In production it does not scale too much so we need web server in between.
This is all about basics of Rails request life cycle.
Now lets see how rails handles the request under the hood.
You can think of middlewares isolate the different stages of processing on the request and response.
One of the best things of Rack, you customise request/response very easily, by chaining middleware components in between the app server and the rails app.
Before Rails 3, handling of session, parsing for parameters and etc were too difficult.
Rake is “Make for Ruby” and it is task runner for Ruby.
Argument environment is nothing but environmental variables hash like PATH_INFO, QURY_STRING, REMOTE_ADDR, REQUEST_URI and all that junk.
You can say this environment variable has all information of the request.
Using low coupling, you can replace any component with another one without having to reimplement code.
Here is a simple example of rack application.
This is another way to write rack application using rackup command which is given by Rack. The only thing you need is, to write your code in config.ru and run it using rackup config.ru.
In this code, I have defined rack application using MyRackApp and I have defined one middleware using MyMiddleware class.
When you want to apply middleware to your rack application you have use ‘use’ method of Rack.
When request comes, it comes from top to bottom. Means from the middleware to the actual rack application.
Always remember that, middleware’s initialize method always takes an argument i.e. app that app is nothing but your next middleware or next rack application.
Think of Rack::Builder object as stack in which your actual rack application is at bottom and all middlewares on top of it. The whole stack you can call it as rack application too.
Many of Action Dispatcher’s internal components are implemented as Rack middleware.
You can inspect middleware stack of your rails application by using
This list is quite big, So I’m not going to explain what each of these middleware does here. But there is one middleware, I think most of you have seen it, that is CheckPending.
Anyone knows what it does?
Lets write one middleware in the rails app.
I mostly prefer to write middleware in config/initializers folder.
In this middleware, mostly in call method, if request_path is ‘say_hello’, then this middleware will send this response back to the client.
So here, our rails app will get called.
If request_path ‘say_hello’ then our rails app gets called.
To add this middleware in rails’s middleware stack, we need to set middleware to config.middleware.use or….config.middleware.insert_after
But when we use this config.middleware.use then that middleware will get applied at the bottom of rails middleware series.