The document discusses security considerations for web applications that use Oracle products. It covers topics like using virtual private databases and Oracle Label Security to restrict user access to different parts of application and database data based on their roles. The document also explains how these Oracle security features can be implemented to allow different users like teenagers, parents, and administrators to only see data that they are authorized to access.
CUbRIK Research at CIKM 2012: Efficient Jaccard-based Diversity Analysis of L...CUbRIK Project
Presentation at CIKM 2013 of the CUbRIK research paper: "Efficient Jaccard-based Diversity Analysis of Large
Document Collections" authored by Fan Deng, Stefan Siersdorfer and Sergej Zerr of L3S Research Center, partner of the CUbRIK Consortium.
The document provides instructions for an Agile in a Day workshop. Participants are instructed to sit with others who have different levels of Agile experience. They then initial questions they want to learn and discuss challenges to adopting Agile. The workshop covers Agile concepts through activities like visioning, user stories, mapping stories and estimating. Participants work through an iteration, including planning, a standup and retrospective. They conclude by reviewing what they learned.
The document discusses 7 ways to make an app learnable, usable, and enjoyable for users. It covers topics like integrating business goals, customer goals, prioritizing goals, recognizing good user experience, and adopting a customer-centric UX philosophy. The presentation aims to provide strategies for designing successful apps.
This document provides an overview of a presentation on advanced design patterns by Amir Barylko. It introduces Amir and lists his contact information and resources. It then outlines the topics that will be covered, including definitions of patterns and anti-patterns, examples of commonly used patterns like Chain of Responsibility and Proxy, and a discussion of which patterns the audience uses.
This document discusses the path of Trish Rempel and Brent Hamm's team at Friesens Corporation towards adopting agile practices. It outlines their current strengths and issues, as well as barriers to adopting agile. Their first steps included establishing improvement goals and training. The document contrasts traditional "waterfall" approaches like delivering late and solo work with agile practices like iterative delivery, examples-based specifications, team development, and limiting work-in-progress. It advises that agile is more about attitudes than processes and emphasizes improvement, learning, collaboration and having someone keep agile momentum.
The document discusses the potential shortcomings of relying solely on user stories in agile development. It introduces the concept of "active architecture" as a way to address these shortcomings by minimizing rework, ensuring consistency across iterations, and identifying potential gaps in the design. The document suggests active architecture can help complement user stories and planning poker sessions.
Este documento explica los conceptos básicos de CSS, incluyendo cómo escribir hojas de estilo y reglas CSS, y cómo vincular hojas de estilo a documentos HTML para describir su estructura y apariencia. También describe los componentes clave de una regla CSS como selectores, propiedades y valores.
CUbRIK Research at CIKM 2012: Efficient Jaccard-based Diversity Analysis of L...CUbRIK Project
Presentation at CIKM 2013 of the CUbRIK research paper: "Efficient Jaccard-based Diversity Analysis of Large
Document Collections" authored by Fan Deng, Stefan Siersdorfer and Sergej Zerr of L3S Research Center, partner of the CUbRIK Consortium.
The document provides instructions for an Agile in a Day workshop. Participants are instructed to sit with others who have different levels of Agile experience. They then initial questions they want to learn and discuss challenges to adopting Agile. The workshop covers Agile concepts through activities like visioning, user stories, mapping stories and estimating. Participants work through an iteration, including planning, a standup and retrospective. They conclude by reviewing what they learned.
The document discusses 7 ways to make an app learnable, usable, and enjoyable for users. It covers topics like integrating business goals, customer goals, prioritizing goals, recognizing good user experience, and adopting a customer-centric UX philosophy. The presentation aims to provide strategies for designing successful apps.
This document provides an overview of a presentation on advanced design patterns by Amir Barylko. It introduces Amir and lists his contact information and resources. It then outlines the topics that will be covered, including definitions of patterns and anti-patterns, examples of commonly used patterns like Chain of Responsibility and Proxy, and a discussion of which patterns the audience uses.
This document discusses the path of Trish Rempel and Brent Hamm's team at Friesens Corporation towards adopting agile practices. It outlines their current strengths and issues, as well as barriers to adopting agile. Their first steps included establishing improvement goals and training. The document contrasts traditional "waterfall" approaches like delivering late and solo work with agile practices like iterative delivery, examples-based specifications, team development, and limiting work-in-progress. It advises that agile is more about attitudes than processes and emphasizes improvement, learning, collaboration and having someone keep agile momentum.
The document discusses the potential shortcomings of relying solely on user stories in agile development. It introduces the concept of "active architecture" as a way to address these shortcomings by minimizing rework, ensuring consistency across iterations, and identifying potential gaps in the design. The document suggests active architecture can help complement user stories and planning poker sessions.
Este documento explica los conceptos básicos de CSS, incluyendo cómo escribir hojas de estilo y reglas CSS, y cómo vincular hojas de estilo a documentos HTML para describir su estructura y apariencia. También describe los componentes clave de una regla CSS como selectores, propiedades y valores.
The three sentence summary is:
The document provides information about a webinar on asset discovery, including introducing the expert panelists and noting that organizations manage 12+ inventory sources with 43% using spreadsheets to track IT assets. It discusses challenges in normalizing and reconciling asset data across sources, with organizations spending 10+ hours per week on reconciliation and having 30% of assets be "ghost assets". The webinar addresses how accurate asset data impacts security, why inventory data alone is insufficient, important asset insights needed, and future trends impacting asset discovery.
Asset data is everywhere: in your service desk, security systems, network and endpoint management systems, etc. Only when you fully understand what you have, can you manage and optimize for cost, security, and performance. Our panel will discuss how to properly manage all this data, the importance of asset discovery, and how to better collaborate across the business.
Volume refers to the large amount of data being generated every day from various sources like user activity logs, tweets, and game stats. Variety means the heterogeneous and complex nature of the data which includes structured, unstructured, textual, numeric and multimedia data. Velocity is the speed at which the data is being created and processed in real-time to power in-game experiences and drive business decisions. Veracity questions the accuracy and reliability of some data sources like self-reported user demographic information. Valence represents the connections and relationships between data points like social networks of players.
Virtual Data : Eliminating the data constraint in Application DevelopmentKyle Hailey
Virtual data provided by Delphix can eliminate data as a constraint in application development by enabling:
1) Fast provisioning of full-sized development databases in minutes from production data without moving large amounts of data. This allows development and testing to parallelize and find bugs earlier.
2) Self-service access to consistent, masked data for multiple use cases like development, security and cloud migration. Masking only needs to be done once before cloning databases.
3) Optimized data movement to the cloud through compression, encryption and replication of thin cloned data sets 1/3 the size of full production databases. This improves cloud migration and enables active-active disaster recovery across sites.
Using ~300 Billion DNS Queries to Analyse the TLD Name Collision ProblemAPNIC
This document summarizes a study analyzing over 300 billion DNS queries to understand the problem of name collisions with new generic top-level domains (gTLDs). The study found that:
1) Around 12% of root server DNS traffic consisted of queries with the RD bit set to 1, which is more than expected but does not appear to be causing major problems.
2) Traffic for most new gTLDs with the RD bit set was 4 orders of magnitude lower than for existing TLDs, suggesting name collisions may not be a large problem.
3) Some isolated examples of misconfigured devices and applications accounted for abnormal traffic levels for a few new gTLDs, but overall the analysis
Not every system has a database architect available to design it. But what happens when developers design database and don't take the proper care into designing a database? This session will take a real-world look into my experiences with some database design choices. In this interactive session, we'll take a deep look into these design choices including a detailed discussion on why they didn't work and what could have been done better. We may even take a peek into SQL Server internals. If you've ever needed to read or write to a database you'll learn some valuable lessons from this session.
Obtén visibilidad completa y encuentra problemas de seguridad ocultosElasticsearch
Aun las amenazas básicas pueden ser múltiples y complejas, y la visibilidad limitada de tus datos de seguridad simplemente no es suficiente. Ya sea que realices investigaciones o busques amenazas, necesitas todo el contexto relevante para la seguridad. Aprende las prácticas clave en la recopilación y normalización de datos y ve cómo puedes usar Elastic Security para clasificar, verificar y abordar problemas de forma rápida y precisa.
This document discusses user story mapping. It begins by explaining what user stories are not, such as tasks, big stories, use cases, and documents. It then explains what user stories are, focusing on them being independent, negotiable, valuable, estimable, small, and testable pieces of functionality described using a Who/What/Why format. The document demonstrates how to slice user stories by things like screen, button, field, workflow step, acceptance criteria, role, and value. It notes some tips for slicing stories, like keeping them as stories and slicing more when estimating. Finally, it provides an overview of how to create a user story map by gathering user tasks, grouping them into activities, adding more detailed stories,
This document discusses integrating user experience (UX) design into agile development processes. It describes common UX activities like user research, prototyping, and testing. It then provides examples of how companies have structured UX work within sprints, including frontloading UX work, biweekly design reviews, and participatory sketching sessions. The goal is to embed UX designers in teams to inform decisions early while still allowing flexibility.
The document summarizes key points from a book about improving the customer experience. It discusses how companies can better understand customer needs by asking customers questions, observing how they use products, and listening to their feedback. The document also provides a case study of how a company called Skinit used these techniques like iterative design reviews to improve their product and significantly increase conversion rates. It emphasizes the importance of involving customers early in the design process and being willing to change designs based on what customers say, not just assumptions or guesses by the company.
Sean and Mike will present on the history and lessons learned from developing the SDEC Mobile Conference application for Blackberry, Android, and Windows Phone 7. They will discuss developing for each platform and integrating the mobile apps with WCF services. Sean and Mike will demonstrate the Windows Phone 7 app and discuss what worked well, what they would change, and what they would not do again when developing for WP7.
This document provides an overview of a presentation titled "The ROR Trilogy Part I: A New Dev Hope" given by Amir Barylko. The presentation introduces Ruby and Ruby on Rails (ROR), covering topics such as dynamic languages, Ruby features, classes and objects, mixins, ROR conventions like MVC and scaffolding. It also lists resources for learning Ruby and ROR and concludes with a demo of a movie library application.
The document discusses how cloud service providers (CSPs) can help software developers by hosting their applications and services. It recommends partnering with a CSP to gain access to infrastructure, platforms, and services without having to build and maintain them. Developers should choose a CSP based on their technical capabilities, geographic coverage, security, scalability, and customer service/support. The case study profiles a payroll company that chose RackForce as their CSP due to its Canadian data centers, strong service level agreements, ease of use and support, security, and ability to scale on demand.
The document summarizes how the PSCAD Development Group transitioned to becoming an agile team. They identified problems with their previous approach and made changes such as improving communication within the rebuilt team, adopting iterative development cycles, introducing planning poker and automated testing, deploying software iteratively, and using paired programming and Kanban boards. The key steps taken included opening up to change, prioritizing adaptability, increasing collaboration, and continually experimenting with new agile methodologies.
The document discusses application portfolio management (APM) at the Manitoba government. It provides definitions and objectives of APM, including analyzing applications based on cost, value, quality and lifespan. It summarizes the APM work completed so far, including developing an inventory of 550 applications and analyzing trends in the portfolio. Analysis shows most applications are over 11 years old and the top 15 applications consume 50% of support resources. The overall aim is to optimize the application portfolio and guide investment decisions.
The document outlines an agenda for a session on monadic design patterns for the web. It discusses what to expect from the session, including fun, simplicity, engagement, and some challenge. It also discusses who the audience is and why monads are useful. The session will cover the monadic toolbox and provide simple and more complex examples of monadic patterns. It will discuss how monads can help manage complexity and provide abstraction.
This document provides an overview of applying Lean principles to transform services organizations. It discusses how Lean was applied to improve processes at Manitoba Immigration, focusing on registration, assessment, and employment solutions. The key aspects covered include reviewing Lean principles from both a production and customer viewpoint, taking a people-focused approach, and using tools like value stream mapping to eliminate waste and improve flow. Successful transformation requires executive commitment, employee engagement, and rigorous execution.
The document summarizes a presentation titled "Why User Experience matters for your App" given by David Alpert at a conference on October 17, 2011. The presentation discusses how customer expectations of software and digital experiences are rising due to influences from various parts of their lives and social media. It emphasizes that users are whole people, not just users, and stresses the importance of designing software with the user experience as the central focus from the outset.
The document introduces the Android operating system. It was created by Google and the Open Handset Alliance to provide an open-source alternative to Apple's iOS and compete in the growing smartphone market. Android uses the Linux kernel and a customized virtual machine called Dalvik to deliver the benefits of Java programming on mobile devices without the performance disadvantages of traditional Java VMs. The architecture is based around activities representing screens, views for building user interfaces, and intents for messaging and navigation between components.
1. The document provides an overview of Windows Azure offerings including Compute, Storage, SQL Azure, Virtual Network, AppFabric, and Marketplace.
2. It discusses the "7 Deadly Sins of Cloud Development" including under utilization of cloud resources, platform monogamy, poorly defined release cadence, always connected assumptions, synchronous application design, lack of load/failover testing, and lack of cloud reading.
3. The document includes demos of various Windows Azure features to illustrate how to avoid the sins.
Migrating an ASP.NET MVC application called Nerd Dinner to Windows Azure involves converting it to a web role, preparing the SQL database for SQL Azure, and configuring authentication. The presentation covers converting the project to a web role, deploying the SQL database to SQL Azure, and options for authentication including SQL Membership, Windows Azure Storage, and Claims-Based Authentication using Access Control Service.
This document discusses a software company's journey to adopting test-driven development (TDD) practices. It describes how the company initially launched its online scheduling system without TDD, which led to problems. A phone call made the company realize it needed to change its development approach to focus on quality. The company then transitioned to using TDD and other quality practices like continuous integration, code reviews, and acceptance testing. The document argues that TDD is not about the tests themselves but about quality, and lists benefits like growing the company and enjoying careers. It encourages readers to educate themselves on TDD, appoint a champion, and support their teams in getting started with these practices.
The three sentence summary is:
The document provides information about a webinar on asset discovery, including introducing the expert panelists and noting that organizations manage 12+ inventory sources with 43% using spreadsheets to track IT assets. It discusses challenges in normalizing and reconciling asset data across sources, with organizations spending 10+ hours per week on reconciliation and having 30% of assets be "ghost assets". The webinar addresses how accurate asset data impacts security, why inventory data alone is insufficient, important asset insights needed, and future trends impacting asset discovery.
Asset data is everywhere: in your service desk, security systems, network and endpoint management systems, etc. Only when you fully understand what you have, can you manage and optimize for cost, security, and performance. Our panel will discuss how to properly manage all this data, the importance of asset discovery, and how to better collaborate across the business.
Volume refers to the large amount of data being generated every day from various sources like user activity logs, tweets, and game stats. Variety means the heterogeneous and complex nature of the data which includes structured, unstructured, textual, numeric and multimedia data. Velocity is the speed at which the data is being created and processed in real-time to power in-game experiences and drive business decisions. Veracity questions the accuracy and reliability of some data sources like self-reported user demographic information. Valence represents the connections and relationships between data points like social networks of players.
Virtual Data : Eliminating the data constraint in Application DevelopmentKyle Hailey
Virtual data provided by Delphix can eliminate data as a constraint in application development by enabling:
1) Fast provisioning of full-sized development databases in minutes from production data without moving large amounts of data. This allows development and testing to parallelize and find bugs earlier.
2) Self-service access to consistent, masked data for multiple use cases like development, security and cloud migration. Masking only needs to be done once before cloning databases.
3) Optimized data movement to the cloud through compression, encryption and replication of thin cloned data sets 1/3 the size of full production databases. This improves cloud migration and enables active-active disaster recovery across sites.
Using ~300 Billion DNS Queries to Analyse the TLD Name Collision ProblemAPNIC
This document summarizes a study analyzing over 300 billion DNS queries to understand the problem of name collisions with new generic top-level domains (gTLDs). The study found that:
1) Around 12% of root server DNS traffic consisted of queries with the RD bit set to 1, which is more than expected but does not appear to be causing major problems.
2) Traffic for most new gTLDs with the RD bit set was 4 orders of magnitude lower than for existing TLDs, suggesting name collisions may not be a large problem.
3) Some isolated examples of misconfigured devices and applications accounted for abnormal traffic levels for a few new gTLDs, but overall the analysis
Not every system has a database architect available to design it. But what happens when developers design database and don't take the proper care into designing a database? This session will take a real-world look into my experiences with some database design choices. In this interactive session, we'll take a deep look into these design choices including a detailed discussion on why they didn't work and what could have been done better. We may even take a peek into SQL Server internals. If you've ever needed to read or write to a database you'll learn some valuable lessons from this session.
Obtén visibilidad completa y encuentra problemas de seguridad ocultosElasticsearch
Aun las amenazas básicas pueden ser múltiples y complejas, y la visibilidad limitada de tus datos de seguridad simplemente no es suficiente. Ya sea que realices investigaciones o busques amenazas, necesitas todo el contexto relevante para la seguridad. Aprende las prácticas clave en la recopilación y normalización de datos y ve cómo puedes usar Elastic Security para clasificar, verificar y abordar problemas de forma rápida y precisa.
This document discusses user story mapping. It begins by explaining what user stories are not, such as tasks, big stories, use cases, and documents. It then explains what user stories are, focusing on them being independent, negotiable, valuable, estimable, small, and testable pieces of functionality described using a Who/What/Why format. The document demonstrates how to slice user stories by things like screen, button, field, workflow step, acceptance criteria, role, and value. It notes some tips for slicing stories, like keeping them as stories and slicing more when estimating. Finally, it provides an overview of how to create a user story map by gathering user tasks, grouping them into activities, adding more detailed stories,
This document discusses integrating user experience (UX) design into agile development processes. It describes common UX activities like user research, prototyping, and testing. It then provides examples of how companies have structured UX work within sprints, including frontloading UX work, biweekly design reviews, and participatory sketching sessions. The goal is to embed UX designers in teams to inform decisions early while still allowing flexibility.
The document summarizes key points from a book about improving the customer experience. It discusses how companies can better understand customer needs by asking customers questions, observing how they use products, and listening to their feedback. The document also provides a case study of how a company called Skinit used these techniques like iterative design reviews to improve their product and significantly increase conversion rates. It emphasizes the importance of involving customers early in the design process and being willing to change designs based on what customers say, not just assumptions or guesses by the company.
Sean and Mike will present on the history and lessons learned from developing the SDEC Mobile Conference application for Blackberry, Android, and Windows Phone 7. They will discuss developing for each platform and integrating the mobile apps with WCF services. Sean and Mike will demonstrate the Windows Phone 7 app and discuss what worked well, what they would change, and what they would not do again when developing for WP7.
This document provides an overview of a presentation titled "The ROR Trilogy Part I: A New Dev Hope" given by Amir Barylko. The presentation introduces Ruby and Ruby on Rails (ROR), covering topics such as dynamic languages, Ruby features, classes and objects, mixins, ROR conventions like MVC and scaffolding. It also lists resources for learning Ruby and ROR and concludes with a demo of a movie library application.
The document discusses how cloud service providers (CSPs) can help software developers by hosting their applications and services. It recommends partnering with a CSP to gain access to infrastructure, platforms, and services without having to build and maintain them. Developers should choose a CSP based on their technical capabilities, geographic coverage, security, scalability, and customer service/support. The case study profiles a payroll company that chose RackForce as their CSP due to its Canadian data centers, strong service level agreements, ease of use and support, security, and ability to scale on demand.
The document summarizes how the PSCAD Development Group transitioned to becoming an agile team. They identified problems with their previous approach and made changes such as improving communication within the rebuilt team, adopting iterative development cycles, introducing planning poker and automated testing, deploying software iteratively, and using paired programming and Kanban boards. The key steps taken included opening up to change, prioritizing adaptability, increasing collaboration, and continually experimenting with new agile methodologies.
The document discusses application portfolio management (APM) at the Manitoba government. It provides definitions and objectives of APM, including analyzing applications based on cost, value, quality and lifespan. It summarizes the APM work completed so far, including developing an inventory of 550 applications and analyzing trends in the portfolio. Analysis shows most applications are over 11 years old and the top 15 applications consume 50% of support resources. The overall aim is to optimize the application portfolio and guide investment decisions.
The document outlines an agenda for a session on monadic design patterns for the web. It discusses what to expect from the session, including fun, simplicity, engagement, and some challenge. It also discusses who the audience is and why monads are useful. The session will cover the monadic toolbox and provide simple and more complex examples of monadic patterns. It will discuss how monads can help manage complexity and provide abstraction.
This document provides an overview of applying Lean principles to transform services organizations. It discusses how Lean was applied to improve processes at Manitoba Immigration, focusing on registration, assessment, and employment solutions. The key aspects covered include reviewing Lean principles from both a production and customer viewpoint, taking a people-focused approach, and using tools like value stream mapping to eliminate waste and improve flow. Successful transformation requires executive commitment, employee engagement, and rigorous execution.
The document summarizes a presentation titled "Why User Experience matters for your App" given by David Alpert at a conference on October 17, 2011. The presentation discusses how customer expectations of software and digital experiences are rising due to influences from various parts of their lives and social media. It emphasizes that users are whole people, not just users, and stresses the importance of designing software with the user experience as the central focus from the outset.
The document introduces the Android operating system. It was created by Google and the Open Handset Alliance to provide an open-source alternative to Apple's iOS and compete in the growing smartphone market. Android uses the Linux kernel and a customized virtual machine called Dalvik to deliver the benefits of Java programming on mobile devices without the performance disadvantages of traditional Java VMs. The architecture is based around activities representing screens, views for building user interfaces, and intents for messaging and navigation between components.
1. The document provides an overview of Windows Azure offerings including Compute, Storage, SQL Azure, Virtual Network, AppFabric, and Marketplace.
2. It discusses the "7 Deadly Sins of Cloud Development" including under utilization of cloud resources, platform monogamy, poorly defined release cadence, always connected assumptions, synchronous application design, lack of load/failover testing, and lack of cloud reading.
3. The document includes demos of various Windows Azure features to illustrate how to avoid the sins.
Migrating an ASP.NET MVC application called Nerd Dinner to Windows Azure involves converting it to a web role, preparing the SQL database for SQL Azure, and configuring authentication. The presentation covers converting the project to a web role, deploying the SQL database to SQL Azure, and options for authentication including SQL Membership, Windows Azure Storage, and Claims-Based Authentication using Access Control Service.
This document discusses a software company's journey to adopting test-driven development (TDD) practices. It describes how the company initially launched its online scheduling system without TDD, which led to problems. A phone call made the company realize it needed to change its development approach to focus on quality. The company then transitioned to using TDD and other quality practices like continuous integration, code reviews, and acceptance testing. The document argues that TDD is not about the tests themselves but about quality, and lists benefits like growing the company and enjoying careers. It encourages readers to educate themselves on TDD, appoint a champion, and support their teams in getting started with these practices.
Discover top-tier mobile app development services, offering innovative solutions for iOS and Android. Enhance your business with custom, user-friendly mobile applications.
Session 1 - Intro to Robotic Process Automation.pdfUiPathCommunity
👉 Check out our full 'Africa Series - Automation Student Developers (EN)' page to register for the full program:
https://bit.ly/Automation_Student_Kickstart
In this session, we shall introduce you to the world of automation, the UiPath Platform, and guide you on how to install and setup UiPath Studio on your Windows PC.
📕 Detailed agenda:
What is RPA? Benefits of RPA?
RPA Applications
The UiPath End-to-End Automation Platform
UiPath Studio CE Installation and Setup
💻 Extra training through UiPath Academy:
Introduction to Automation
UiPath Business Automation Platform
Explore automation development with UiPath Studio
👉 Register here for our upcoming Session 2 on June 20: Introduction to UiPath Studio Fundamentals: https://community.uipath.com/events/details/uipath-lagos-presents-session-2-introduction-to-uipath-studio-fundamentals/
"What does it really mean for your system to be available, or how to define w...Fwdays
We will talk about system monitoring from a few different angles. We will start by covering the basics, then discuss SLOs, how to define them, and why understanding the business well is crucial for success in this exercise.
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.
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
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).
The Microsoft 365 Migration Tutorial For Beginner.pptxoperationspcvita
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/
LF Energy Webinar: Carbon Data Specifications: Mechanisms to Improve Data Acc...DanBrown980551
This LF Energy webinar took place June 20, 2024. It featured:
-Alex Thornton, LF Energy
-Hallie Cramer, Google
-Daniel Roesler, UtilityAPI
-Henry Richardson, WattTime
In response to the urgency and scale required to effectively address climate change, open source solutions offer significant potential for driving innovation and progress. Currently, there is a growing demand for standardization and interoperability in energy data and modeling. Open source standards and specifications within the energy sector can also alleviate challenges associated with data fragmentation, transparency, and accessibility. At the same time, it is crucial to consider privacy and security concerns throughout the development of open source platforms.
This webinar will delve into the motivations behind establishing LF Energy’s Carbon Data Specification Consortium. It will provide an overview of the draft specifications and the ongoing progress made by the respective working groups.
Three primary specifications will be discussed:
-Discovery and client registration, emphasizing transparent processes and secure and private access
-Customer data, centering around customer tariffs, bills, energy usage, and full consumption disclosure
-Power systems data, focusing on grid data, inclusive of transmission and distribution networks, generation, intergrid power flows, and market settlement data
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor IvaniukFwdays
At this talk we will discuss DDoS protection tools and best practices, discuss network architectures and what AWS has to offer. Also, we will look into one of the largest DDoS attacks on Ukrainian infrastructure that happened in February 2022. We'll see, what techniques helped to keep the web resources available for Ukrainians and how AWS improved DDoS protection for all customers based on Ukraine experience
"$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.
ScyllaDB is making a major architecture shift. We’re moving from vNode replication to tablets – fragments of tables that are distributed independently, enabling dynamic data distribution and extreme elasticity. In this keynote, ScyllaDB co-founder and CTO Avi Kivity explains the reason for this shift, provides a look at the implementation and roadmap, and shares how this shift benefits ScyllaDB users.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
inQuba Webinar Mastering Customer Journey Management with Dr Graham HillLizaNolte
HERE IS YOUR WEBINAR CONTENT! 'Mastering Customer Journey Management with Dr. Graham Hill'. We hope you find the webinar recording both insightful and enjoyable.
In this webinar, we explored essential aspects of Customer Journey Management and personalization. Here’s a summary of the key insights and topics discussed:
Key Takeaways:
Understanding the Customer Journey: Dr. Hill emphasized the importance of mapping and understanding the complete customer journey to identify touchpoints and opportunities for improvement.
Personalization Strategies: We discussed how to leverage data and insights to create personalized experiences that resonate with customers.
Technology Integration: Insights were shared on how inQuba’s advanced technology can streamline customer interactions and drive operational efficiency.
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.
"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.
2. Syllabus
• It seems that organizations are taking security more and
more seriously these days. One motivator is avoiding
embarrassment which can collapse the organization in
a hurry. The architecture of a web based application
has a number of complexities when it comes to
implementing security properly. Jonathan will talk about
some of these complexities and identify a number of
considerations that can save you time and money. In
particular, he will explain how the Oracle suite of
products integrate and use that as a concrete example.
Architects, developers, and DBAs will learn from topics
such as virtual private databases, single sign on,
cookies, Hibernate interactions, and role-based security.
2
3. Setting the stage …
• Who is in the audience? Which one are you?
• Architect
• Database Administrator (DBA)
• Developer
• Java
• Other
• Other
• Goals:
• General Understanding
• Advice, related to Security in a web application
• Drill-in into to some unobvious specifics
• Questions?
3
4. What’s the big deal?
We have some challenges …
• Technology is more susceptible and more complicated
• unwanted system access
• localized damage
• global damage
• how do decision makers respond to pain? ~~ rational thinking
• Data (and Process) Ownership Trends
• Silos Sharing
• Terminology confusion ~~ talk about the same thing: Einstein quote
• Organizations Products AND Services
• Potential huge costs, time and $$$$
• Educate and then ask, are you sure?
4
5. Legal stuff …
• Legal questions can delay a project
• submit questions early as possible
• get feedback early as possible
• legal requirements are hard and fast – know them early to avoid
expensive rework
5
10. Step 3
• Reverse Proxy (Oracle’s WebCache)
• Guard at the door into the architecture
• In the middle of the DMZ sandwich
• Robust solutions include:
• Caching of static “public” content (picture files, Javascript)
• Load Balancing
• Decryption of HTTPS requests … more on that later
10
11. Step 4
• The Web Application Server is the brains with all the
business logic --- it knows what to with the HTTP GET
request
11
12. Step 5
• The server needs to first get a list of teenagers, and so,
get it from the server responsible for persisting
information
12
19. Audit Columns
• Every table in the database include the following
columns:
• A_CREATED_BY
• A_CREATED_TIMESTAMP
• A_MODIFIED_BY
• A_MODIFIED_TIMESTAMP
• Know the affects of the Sarbanes-Oxley act
• Create a companion history table for every table in the
database. It will be a complete history of “snapshots”.
These tables have the exact same columns plus a
timestamp column. (Data is almost free!)
19
20. Web Application Architecture
We now going to concentrate on the Database.
Will talk about:
• Virtual Private Databases
• Oracle Label Security
20
21. Database Tables
• TEENAGER
TEENAGER_ID TEENAGER_NAME
1 Raelene
2 Jenna
• EXPENSE
TEENAGER DETAILS AMOUNT DATE
_ID
1 Cell 45.00 Oct 1
1 Gum 1.35 Oct 6
2 Help Haiti 4.00 Oct 8
21
22. Raelene is allowed to see this …
• TEENAGER
TEENAGER_ID TEENAGER_NAME
1 Raelene
2 Jenna
• EXPENSE
TEENAGER DETAILS AMOUNT DATE
_ID
1 Cell 45.00 Oct 1
1 Gum 1.35 Oct 6
2 Help Haiti 4.00 Oct 8
22
23. Jenna is allowed to see this …
• TEENAGER
TEENAGER_ID TEENAGER_NAME
1 Raelene
2 Jenna
• EXPENSE
TEENAGER DETAILS AMOUNT DATE
_ID
1 Cell 45.00 Oct 1
1 Gum 1.35 Oct 6
2 Help Haiti 4.00 Oct 8
23
24. A VPD
• A Virtual Private Database (VPD) = restricts access on
horizontal slices
• Oracle Label Security is an implementation of a VPD
24
25. Who can view/edit what data?
• Label Security allows you to create a policy on the
TEENAGER_ID
TEENAGER
_ID = 1 100
(Raelene)
Raelene
Parents
TEENAGER (God-like access)
_ID = 2
(Jenna) 200
Jenna
25
26. Database Tables
with Label Security column added …
• TEENAGER
TEENAGER_ID TEENAGER_NAME
1 Raelene
2 Jenna
• EXPENSE
TEENAGER DETAILS AMOUNT DATE LS_
_ID TEENAGER
1 Cell 45.00 Oct 1 100
1 Gum 1.35 Oct 6 100
2 Help Haiti 4.00 Oct 8 200
26
27. Jenna will get a different answer
than Raelene and the Parents!
• TEENAGER
SELECT sum(amount)
FROM EXPENSE
TEENAGER_ID TEENAGER_NAME
1 Raelene
2 Jenna
• EXPENSE
TEENAGER DETAILS AMOUNT DATE LS_
_ID TEENAGER
1 Cell 45.00 Oct 1 100
1 Gum 1.35 Oct 6 100
2 Help Haiti 4.00 Oct 8 200
27
28. Jenna will get a different answer
than Raelene and the Parents!
• TEENAGER
SELECT sum(amount)
FROM EXPENSE
TEENAGER_ID TEENAGER_NAME
1 Raelene
WHERE LS_TEENAGER IN (100)
2 Jenna
• EXPENSE
TEENAGER DETAILS AMOUNT DATE LS_
_ID TEENAGER
1 Cell 45.00 Oct 1 100
1 Gum 1.35 Oct 6 100
2 Help Haiti 4.00 Oct 8 200
28
29. Parents type in …
• TEENAGER
SELECT sum(amount)
FROM EXPENSE
TEENAGER_ID TEENAGER_NAME
1 Raelene
2 Jenna
• EXPENSE
TEENAGER DETAILS AMOUNT DATE LS_
_ID TEENAGER
1 Cell 45.00 Oct 1 100
1 Gum 1.35 Oct 6 100
2 Help Haiti 4.00 Oct 8 200
29
30. … and this what happens under the
covers:
• TEENAGER
SELECT sum(amount)
FROM EXPENSE
TEENAGER_ID TEENAGER_NAME
1 Raelene
WHERE LS_TEENAGER IN (100, 200)
2 Jenna
• EXPENSE
TEENAGER DETAILS AMOUNT DATE LS_
_ID TEENAGER
1 Cell 45.00 Oct 1 100
1 Gum 1.35 Oct 6 100
2 Help Haiti 4.00 Oct 8 200
30
31. DBMS Triggers are used for INSERTs
and UPDATEs
• TEENAGER
INSERT (TEENAGER_ID, DETAILS, AMOUNT, DATE)
VALUES (2,
TEENAGER_ID “Book Fine”, 1, Oct 16)
TEENAGER_NAME
1 Raelene
Oracle Label Security auto-generated a DBMS Trigger on the EXPENSE
table. The trigger calculatesJenna
2 200 based on TEENAGER_ID
• EXPENSE
TEENAGER DETAILS AMOUNT DATE LS_
_ID TEENAGER
1 Cell 45.00 Oct 1 100
1 Gum 1.35 Oct 6 100
2 Help Haiti 4.00 Oct 8 200
2 Book Fine 1.00 Oct 16 Calculated
by DBMS
Trigger
31
32. Label Security can have up to 3 groupings
TEENAGER
_ID = 1 100
EXPENSE
Younger
_TYPE =
Siblings
8
8,000 TEENAGER
_ID = 2
200
Teenagers
770,000
Grandparents
32
35. LDAP
Oracle OAM & OID
• LDAP = Lightweight Directory Access Protocol
• Oracle Internet Directory is an implementation of
directory services, LDAPv3
• Oracle Access Manager (OAM) enforces policies and
works with OID
• Watch out for your firewalls settings -- timeouts
• Active Directory can “connect”
• DIP transfers name and passwords
35
36. Oracle LDAP Components
All the “green” servers support the LDAP responsibilities. Oracle Access Manager
(OAM) is the main interface into the outside world. However, the “purple” Oracle
Database has some direct connections with Oracle’s LDAP (OID), probably for
performance reasons. In theory, the dashed lines below were not really
necessary.
The two columns of “green” servers indicate that they can be clustered, and the
set of servers can be in different locations.
36
41. Simplified Web Application Architecture
• HTTP Server – Oracle’s MOD_OC4J
• Web Application Container – Oracle’s OC4J … and soon
WebLogic
41
42. Web Server interactions with LDAP
The “Happy Path” …
The Browser makes a HTTP Request, via interaction #1.
The HTTP Server looks at this request and asks the LDAP
Access services if this request is allowed to proceed. This
is done via interaction #2. If the answer is positive, it
passes on the request to the destination, via interaction #3.
42
43. Web Server interactions with LDAP
The “Happy Path” continued …
In this “Happy Path” scenario the user has already
authenticated (i.e. logged in).
Oracle can place authentication data in “HTTP Headers”
and/or in some “cookies”. It gives information about the
User ID, expiry time, etc. [Refer to interactions #1 & #3]
43
44. Web Server interactions with LDAP
The “Happy Path” continued …
The authorization rules are enforced in two different places:
• Interaction #2 – Can protect basic requests, such as, URL
requests that start with
www.TeenagerExpenses.mb.ca/expenses
• Interaction #4 – Using LDAP Queries, it can lookup more fine
grained permissions such as:
www.TeenagerExpenses.mb.ca/expenses/expense_details.jsp 44
46. Web Server interactions with LDAP
The “Happy Path” continued …
The authorization rules are enforced in two different places:
• Interaction #2 – Basic requests based on OAM polices
• Interaction #4 – Fine grained based on LDAP Queries / Role-
based Security
Decide which interaction is responsible for what, early in
the project!
46
47. Authorization and Role-based Security
User – Role – Feature
• Can be tricky. Can’t control the number of users. But
you can control the number of Roles and Features.
• Roles – Configure Roles and role names to match the
actual physical business processes – people need to
understand them. Be ready to refactor!
47
48. Authorization and Role-based Security
User – Role – Feature
• Can be tricky. Can’t control the number of users. But
you can control the number of Roles and Features.
• Roles – Configure Roles and role names to match the
actual physical business processes – people need to
understand them. Be ready to refactor!
48
49. Authorization and Role-based Security
• Features – Pick the number of features wisely, keep
them to a minimum and understandable.
Fine grained control Coarse grained control
Complicated Simple
• Ask questions! Find out what the real requirement is.
“Are you sure?” “Can this one feature represent both the
search and the detail page?” “How easy is it to test?”
49
50. Web Server interactions with LDAP
The “Unhappy Path” …
The “unhappy” path is one where the user has not logged
in yet. The Web Application Container can have two
applications:
• The OAM Single-Sign On (SSO) “helper” application, which
includes these pages: login, logout, and not authorized
• The business application, such as the “expenses” test
application 50
51. Web Server interactions with LDAP
Log out …
Your web applications will point to a logout page in the SSO
application. It can (or should) invalidate the web
applications under its protection.
51
55. Database Connections
• Perform adequate performance tests on this interactions
• Because we implemented a VPD at a low level, we want
to ensure that the end-user will be restricted from the
bottom up, and that means to connect as that user.
• Experience: Can take up to 5 seconds to “stamp” a user onto a
proxy connection. The solution is to make a connection pool for
each user
• Experience: The setup and use of Label Security is expensive
• Alternatives??
55
56. (If we have time …)
1. Creating a log of access – find out if one is needed
early in the project
2. Web Analytics – find out if test users are needed in
production, and what that means
3. Security on Web Services & Services (SOA) – again,
find out if this extra layer needs its own gatekeeper of
security
4. The need for Backend Reports with BI Publisher
5. Data Encryption in the Database
56