AgileWarsaw: Spikes

•Download as ODP, PDF•

3 likes•1,410 views

Mateusz Srebrny

How to deal with unknown technologies and research tasks in an Agile project. From AgileWarsaw, June 14, 2010

Technology

Redesign and scaling-out of the server-side infrastructure of the biggest polish instant messenger (over 2M peak concurrent users)

The document provides an overview of Agile and Scrum methodologies. It discusses the benefits of iterative development over traditional waterfall approaches. The key aspects of Scrum are described, including roles like the Product Owner, Development Team, and Scrum Master. Scrum practices like sprints, daily stand-ups, and retrospectives are outlined. Kanban is also introduced as a pull-based approach focused on continuous flow and limiting work-in-progress.

Design Spikes for the Dual-Track Agile Process

uxpin

From the designers laptop to the users

uxpin

The document discusses the goals and learnings from a design system mission to enable teams to create straightforward user experiences. It notes that the tension between product and design system goals is healthy. Key learnings include looking at existing products, synthesizing information to move forward, focusing on experiences rather than just components, and building the design system like a product. The document also outlines different models for how a design system can be built and aligned with product roadmaps.

Introduction to Design Thinking & Correlation to Scrum

Jeff ANGAMA

The document discusses how design thinking and agile frameworks like Scrum can be combined to deliver user-centered solutions. Some key points: - Design thinking focuses on empathy, defining problems from the user's perspective, ideating solutions, prototyping, and testing iteratively. - Scrum is an agile framework that uses sprints, daily stand-ups, backlogs and retrospectives for iterative delivery. - Design thinking can be incorporated into Scrum through techniques like backlog grooming to understand user needs, prototyping solutions, and testing with users after each sprint. - This approach ensures solutions are designed and delivered with a focus on the user experience through collaborative feedback loops.

Small team scrum and kanban

David Daniel

Scrum introduction

Martin Gasparovic

Scrum is an agile framework for managing software development projects that focuses on iterative delivery through short cycles called sprints. It utilizes roles like the product owner, development team, and scrum master. Key artifacts include the product backlog to track features and the sprint backlog to plan work for each iteration. Regular meetings like daily stand-ups, sprint reviews, and retrospectives promote transparency and process improvement. While long-term estimates are challenging, scrum values transparency and frequent delivery to build trust with stakeholders.

UX in a Dual Track Agile World

Andrea Neuhoff

What do you get when user experience drives the agile process? Dual-Track Agile, where the features of the product are discovered alongside the development of the product itself. This session will explain what dual-track agile is, the benefits of dual-track agile, the role of UX, and what to expect. It will focus on the discovery cycle, the role of validated hypotheses and assumptions and how UX uniquely contributes to this invaluable process.

UX Research in the Agile Cycle

uxpin

Slides Ari Tiktin recently used in his discussion w/ mentees of The Product Mentor. The Product Mentor is a program designed to pair Product Mentors and Mentees from around the World, across all industries, from start-up to enterprise, guided by the fundamental goals…Better Decisions. Better Products. Better Product People. Throughout the program, each mentor leads a conversation in an area of their expertise that is live streamed and available to both mentee and the broader product community.

How to Ace Your Scrum Master Interview

Pavel Dabrytski

At the start of my Agile career, it was tough to find an opening for the position of a Scrum Master in South Africa – Agile and Scrum was a new thing. When I was looking for a change in 2013, LinkedIn had three Scrum Master jobs and none for an Agile Coach. But when I search for Scrum Master jobs today, LinkedIn has a list of potential opportunities that spans over ten pages. At the same time, the job market is tougher today – the number of candidates on the market has increased significantly as well. The challenge for job seekers today is how to differentiate oneself from the rest of the crowd. For the past few years, I have been helping people find new opportunities, and companies find new candidates. Knowing the process from both sides, I would like to share the standard points you must have in your CV to land an interview. I will share the typical questions asked in a Scrum Master interview. And we will practice answering these questions in groups. Perhaps, this workshop is a small nudge that will help you land your next dream position. Join me to learn more!

Beginning SCRUM for Startups

Pradeep Sethi

Scrum is an iterative, incremental framework for project management that is often used in agile software development. It involves breaking projects into short cycles called sprints that typically last 1-4 weeks. The main roles in Scrum are the ScrumMaster, Product Owner, and Development Team. Key activities in each sprint include sprint planning meetings, daily standup meetings, development work, testing, and sprint retrospectives. At the end of each sprint, any potentially releasable work is demonstrated in a sprint review.

Agile Retrospective by Manohar Prasad

Manohar Prasad, PgMP®, PMP®, PMI-ACP®, CAL®, ACC®, CSP®

Scrum Basics

LuxoftAgilePractice

The document provides an overview of Scrum basics and components. It introduces Scrum as an Agile framework and discusses its core elements - events like sprints, planning and reviews; roles like product owner and scrum master; and artifacts like product backlog and sprint backlog. It also covers related concepts like capacity, velocity and how Scrum compares to Agile approaches. The document concludes by suggesting resources to learn more about Scrum and offers coaching for teams to understand how to apply Scrum.

What is Scrum?

Fredrik Fjällström

Mind the Product 2013: Sprint Zero

Harry Max

Prototyping and Scrum

Memi Beltrame

Design Systems Operations

uxpin

Sprint Zero in Scrum

Agile Vietnam

This document discusses Sprint Zero, which is the preparation period before real sprints begin for a new Scrum team. Sprint Zero is needed because the product owner and team need time to get acquainted, set up the development environment, establish processes like the definition of done, and clarify roles. The document provides a checklist of activities for Sprint Zero, including ensuring team training, setting up tools and infrastructure, defining the technical architecture and coding standards, and agreeing on the sprint agenda and planning process. It also lists signs of good and bad Scrum practices.

Close to agile

philywu

This document provides an overview of Agile and Scrum methodologies. It discusses why Agile approaches became popular, describing challenges with traditional waterfall methods. Key aspects of Scrum are outlined, including roles like Product Owner and Scrum Master, ceremonies like sprint planning and daily standups, and artifacts like product and sprint backlogs. Benefits of Scrum like adaptability, visibility and increased productivity are highlighted. The document aims to introduce readers to Scrum processes and terminology at a high level.

Balancing UX Consistency and Developer Productivity in a Design System

uxpin

Agile in Action - Agile Overview for Developers

Matt Cowell

Scrum Master Lessons from my 4 Year Old Son

Ryan Ripley

At a recent cookout, my 4 year old son, Dawson, ran for the back yard and easily joined a game of hide and seek. Watching this unfold, I realized that these kids are naturally agile. They got straight to playing (the value) and didn’t need a lot of ceremony to get there. They kids all did a quick hello, told Dawson what game they were playing, and invited him to join in (daily scrum). Then they played. He and his friends self-organize, self-manage, and solve problems on the fly. They naturally exhibit the agile values and scrum practices that many adults struggle with daily. For example, most parents have been bombarded with an unending stream of “Why’s?” from their child. Why does this work? Why did that happen? Why? Why? Why? While this line of questioning can be stressing, it is also invaluable to finding the root cause of an issue. Scrum teams use this approach – called The 5-Why’s – to get past technical issues and down to interpersonal issues that could be hindering the team. This session is a fun discussion about the behaviors I’ve noticed in my son and how they translate to important lessons that all scrum master need to learn to better serve their teams.

Breaking the mold: Lean Product Management and MVP in a Large Company

Ilia Kuznetsov (ilia.v.kuznetsov@gmail.com)

Welcome to Agile - Taipei Regent 2016/05/20

Adam Laskowski

This document provides an introduction to Scrum and Agile development. It explains why the traditional waterfall model is being changed, describing how Agile methods allow for shorter development cycles with quicker feedback. It then outlines the Scrum framework, including defining the roles of product owner, scrum master, and development team. The document uses a house building analogy to illustrate how Scrum sprints can adapt to changing requirements. It also shows how user stories are broken down into tasks for sprints and how features are estimated in story points. Finally, it briefly describes key Scrum ceremonies like sprint planning, daily standups, and sprint reviews.

Scrum In 15 Minutes

Srikanth Shreenivas

Scrum is an agile framework for managing product development that focuses on continuous delivery of working software in short cycles called sprints, typically two weeks or less. Scrum emphasizes self-organizing cross-functional teams and accountability, iterative development and progress transparency through regular inspection of working increments. Key Scrum practices include sprint planning, daily stand-up meetings, sprint reviews, and retrospectives. Scrum can scale to large, complex projects through techniques like Scrum of Scrums.

Scrum

Gennadiy Zlobin

Scrum is an agile framework that many large companies use for software development. It involves 3 roles - Product Owner, Development Team, and Scrum Master. The process involves sprint planning, daily stand-ups, and sprint reviews. Key artifacts include the product backlog, sprint backlog, and task board. The goal is rapid delivery of working software through short cycles of work called sprints, using an inspect and adapt approach.

Agile and Scrum Workshop

Rainer Stropek

This document provides an agenda and overview for an Agile and Scrum workshop. The workshop covers Agile development principles and how they differ from traditional waterfall approaches. It then discusses Scrum basics, including Scrum roles, events, and tools. The workshop aims to explain Agile and Scrum concepts, make the sessions interactive, and allow for an open discussion in the final session.

Postmortemanalysis 120520033844-phpapp02

Loriebel Manabat

The document discusses conducting a post-mortem analysis after a project to learn lessons. It provides context on the benefits of leveraging past project experiences. It then discusses the key aspects of performing a post-mortem analysis including collecting data, facilitating discussions, focusing on issues not people, being factual and brief. An example post-mortem meeting for the Microsoft Word 6 development project is then summarized, noting scheduling was unrealistic, milestones were too long, and proposed features' problems were not obvious until development started.

What's hot

Great Agile in a UX World

Anthony Viviano

Scaling Products With Design Systems

uxpin

Introducing Agile to Product Teams

Jeremy Horn

How to Ace Your Scrum Master Interview

Pavel Dabrytski

Beginning SCRUM for Startups

Pradeep Sethi

Agile Retrospective by Manohar Prasad

Manohar Prasad, PgMP®, PMP®, PMI-ACP®, CAL®, ACC®, CSP®

Scrum Basics

LuxoftAgilePractice

What is Scrum?

Fredrik Fjällström

Mind the Product 2013: Sprint Zero

Harry Max

Prototyping and Scrum

Memi Beltrame

Design Systems Operations

uxpin

Sprint Zero in Scrum

Agile Vietnam

Close to agile

philywu

Balancing UX Consistency and Developer Productivity in a Design System

uxpin

Agile in Action - Agile Overview for Developers

Matt Cowell

Scrum Master Lessons from my 4 Year Old Son

Ryan Ripley

Breaking the mold: Lean Product Management and MVP in a Large Company

Ilia Kuznetsov (ilia.v.kuznetsov@gmail.com)

Welcome to Agile - Taipei Regent 2016/05/20

Adam Laskowski

Scrum In 15 Minutes

Srikanth Shreenivas

Scrum

Gennadiy Zlobin

What's hot (20)

Great Agile in a UX World

Scaling Products With Design Systems

Introducing Agile to Product Teams

How to Ace Your Scrum Master Interview

Beginning SCRUM for Startups

Agile Retrospective by Manohar Prasad

Scrum Basics

What is Scrum?

Mind the Product 2013: Sprint Zero

Prototyping and Scrum

Design Systems Operations

Sprint Zero in Scrum

Close to agile

Balancing UX Consistency and Developer Productivity in a Design System

Agile in Action - Agile Overview for Developers

Scrum Master Lessons from my 4 Year Old Son

Breaking the mold: Lean Product Management and MVP in a Large Company

Welcome to Agile - Taipei Regent 2016/05/20

Scrum In 15 Minutes

Scrum

Similar to AgileWarsaw: Spikes

Agile and Scrum Workshop

Rainer Stropek

Postmortemanalysis 120520033844-phpapp02

Loriebel Manabat

Leading into the Future: Scanning

Terri Griffith

discussion_3_project.pdf

Kuan-Tsae Huang

This document provides information and guidance for students completing the CS231n course project. It discusses project expectations, how to pick a project idea, and deliverables. For project expectations, it notes the open-ended nature but focus on computer vision problems. Sources of inspiration for project ideas include conferences, papers, and previous student projects. Reading papers efficiently involves focusing on abstracts, methods, results rather than linear reading. Deliverables include a proposal, milestone report, final report, and poster presentation. The proposal and milestone report formats are also outlined.

The Technology Process (Updated)

Kay Smythe

Final cs1 m3 2.10.13

Paula Nottingham

This document provides guidance for students on their Module 3 professional inquiry project. It discusses defining a professional inquiry, reviewing the stages and steps of the inquiry process, and addressing where students currently are in their projects. The document offers advice on planning, analyzing findings from research and practitioner work, drafting the critical review, and developing the professional artifact. Key points covered include conducting a literature review, analyzing qualitative and quantitative data, and receiving formative feedback to guide work on the critical analysis and sample paragraphs.

software-dev-life.pptx

PhilipAdenekan1

The document provides an overview of software development methodologies and best practices used in corporate America. It discusses waterfall and agile methodologies, emphasizing agile's benefits like constant delivery of small features, transparency, and adaptability. It also covers topics like source control using Git, code quality practices like testing and code reviews, and considerations for applying agile principles in a research lab setting.

DesignProcess temp.ppt

SysteDesig

The document discusses the design process and provides examples of design processes that involve identifying problems, brainstorming solutions, developing and testing prototypes, and refining the design. It outlines a 12-step design process used by Project Lead the Way that involves defining problems, researching solutions, developing and testing prototypes, and communicating results. Several design processes from different technical fields and publications are also presented and compared.

Organisering av digitale prosjekt: Hva har IT-bransjen lært om store prosjekter?

Torgeir Dingsøyr

See to believe: capturing insights using contextual inquiry

Deirdre Costello

Presented by Deirdre Costello, Kate Lawrence and Melissa Pike to Boston UXPA members on September 18, 2014. EBSCO's User Research team recently completed an in-depth, ethnography-style study of physicians' research habits, including how they judge credibility, how they learn about the sources they use and what they do with the information they find. Two researchers and a product manager will talk about the methodology, the project and how the findings influenced a product roadmap. And answer your questions, of course!

Agile UX - Learning to Lead

Chris Farnum

Agile Development with Scrum.pptx

zuma14

The document provides an overview of agile development using Scrum. It discusses the foundations and principles of Scrum, including self-organizing cross-functional teams and delivering working software every sprint. The key roles of Product Owner, Scrum Master, and Scrum Team are defined. Sprints are short iterations usually 2-4 weeks where working software is delivered. Meetings like sprint planning, daily standups, reviews and retrospectives support the process.

Cs1 m3 22.5.12

Paula Nottingham

The document provides an overview of a campus session for a professional inquiry module. It discusses defining a professional inquiry, stages of the inquiry process like planning and analysis, and requirements for the module assessment including a critical review, professional artefact, and oral presentation. The session focused on understanding expectations, checking progress, discussing findings from research and literature, and getting feedback to move forward with analysis and writing up different parts of the assessment.

Tech Writing

guest2e5b7a

Technical writing involves taking complex information and making it easy for readers to understand. Technical writers create various documentation like user manuals, procedures, help guides, and training materials. The writing process includes defining the project goals, estimating time needed, researching the topic, designing the document, writing, editing, and delivering the final product. This ensures the writing is accurate, clear, consistent, and tailored to the intended audience.

Intro To Scrum

scottycn

Introduction into Scrum

msorin

Redistributable Intro To Scrum

Erwin Verweij

Scrum is an agile framework for managing product development that focuses on iterative delivery of working software in short cycles called sprints. It involves self-organizing cross-functional teams, prioritized backlogs to track requirements, and daily stand-up meetings. The goal is to rapidly and repeatedly deliver the highest business value in the shortest time through a flexible, holistic and collaborative approach.

Denver Startup Week 2018: Just Enough Research

Hillary Pitts

This document discusses approaches for conducting just enough product research with limited time and resources. It begins with establishing the importance of research for building inclusive, high-quality products. It then provides examples of quick qualitative and quantitative research methods like meeting with one customer per week and conducting moderated Kano sessions. The document also recommends facilitating internal feedback through sharing designs for comments. For synthesis, it suggests debriefing after sessions and using tools like empathy maps and rainbow sheets to identify themes. Finally, it proposes implementing passive user panel growth and tracking assumptions as a backlog for testing.

User centered design workshop

Patrick McNeil

User-centered design (UCD) is a design philosophy that focuses on the needs of users throughout the design process. The document discusses the key steps in UCD, which include defining the project and users, creating concepts, designing visual solutions, development, and deployment. It emphasizes early and continuous user research methods like interviews and usability testing to help ensure designs meet user needs.

To document or not to document? An exploratory study on developers' motivatio...

Hayim Makabee

This document summarizes a study on developers' motivation to document code. Through interviews and surveys, researchers identified hindering and motivating factors for code documentation. Hindering factors included documentation being tedious, difficult, time-consuming, and interrupting coding work. Motivating factors included documentation improving code comprehensibility, order, and quality. The researchers propose designing a solution to encourage documentation by emphasizing motivating factors and mitigating hindering ones. They plan to further validate findings through a quantitative questionnaire. The goal is to increase developers' internal motivation to document code.

Similar to AgileWarsaw: Spikes (20)

Agile and Scrum Workshop

Postmortemanalysis 120520033844-phpapp02

Leading into the Future: Scanning

discussion_3_project.pdf

The Technology Process (Updated)

Final cs1 m3 2.10.13

software-dev-life.pptx

DesignProcess temp.ppt

Organisering av digitale prosjekt: Hva har IT-bransjen lært om store prosjekter?

See to believe: capturing insights using contextual inquiry

Agile UX - Learning to Lead

Agile Development with Scrum.pptx

Cs1 m3 22.5.12

Tech Writing

Intro To Scrum

Introduction into Scrum

Redistributable Intro To Scrum

Denver Startup Week 2018: Just Enough Research

User centered design workshop

To document or not to document? An exploratory study on developers' motivatio...

Recently uploaded

Apps Break Data

Ivo Velitchkov

How information systems are built or acquired puts information, which is what they should be about, in a secondary place. Our language adapted accordingly, and we no longer talk about information systems but applications. Applications evolved in a way to break data into diverse fragments, tightly coupled with applications and expensive to integrate. The result is technical debt, which is re-paid by taking even bigger "loans", resulting in an ever-increasing technical debt. Software engineering and procurement practices work in sync with market forces to maintain this trend. This talk demonstrates how natural this situation is. The question is: can something be done to reverse the trend?

"Scaling RAG Applications to serve millions of users", Kevin Goedecke

Fwdays

Fueling AI with Great Data with Airbyte Webinar

Zilliz

Essentials of Automations: Exploring Attributes & Automation Parameters

Safe Software

Building automations in FME Flow can save time, money, and help businesses scale by eliminating data silos and providing data to stakeholders in real-time. One essential component to orchestrating complex automations is the use of attributes & automation parameters (both formerly known as “keys”). In fact, it’s unlikely you’ll ever build an Automation without using these components, but what exactly are they? Attributes & automation parameters enable the automation author to pass data values from one automation component to the next. During this webinar, our FME Flow Specialists will cover leveraging the three types of these output attributes & parameters in FME Flow: Event, Custom, and Automation. As a bonus, they’ll also be making use of the Split-Merge Block functionality. You’ll leave this webinar with a better understanding of how to maximize the potential of automations by making use of attributes & automation parameters, with the ultimate goal of setting your enterprise integration workflows up on autopilot.

Skybuffer SAM4U tool for SAP license adoption

Tatiana Kojar

Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool. SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.

Your One-Stop Shop for Python Success: Top 10 US Python Development Providers

akankshawande

inQuba Webinar Mastering Customer Journey Management with Dr Graham Hill

LizaNolte

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.

"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor Ivaniuk

Fwdays

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

Taking AI to the Next Level in Manufacturing.pdf

ssuserfac0301

Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as: 1. How quickly AI is being implemented in manufacturing. 2. Which barriers stand in the way of AI adoption. 3. How data quality and governance form the backbone of AI. 4. Organizational processes and structures that may inhibit effective AI adoption. 6. Ideas and approaches to help build your organization's AI strategy.

Monitoring and Managing Anomaly Detection on OpenShift.pdf

Tosin Akinosho

Monitoring and Managing Anomaly Detection on OpenShift Overview Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices. Key Topics Covered 1. Introduction to Anomaly Detection - Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems. 2. Understanding Edge (IoT) - Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source. 3. What is ArgoCD? - Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices. 4. Deployment Using ArgoCD for Edge Devices - Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD. 5. Introduction to Apache Kafka and S3 - Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions. 6. Viewing Kafka Messages in the Data Lake - Learn how to view and analyze Kafka messages stored in a data lake for better insights. 7. What is Prometheus? - Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices. 8. Monitoring Application Metrics with Prometheus - Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system. 9. What is Camel K? - Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes. 10. Configuring Camel K Integrations for Data Pipelines - Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow. 11. What is a Jupyter Notebook? - Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text. 12. Jupyter Notebooks with Code Examples - Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.

JavaLand 2024: Application Development Green Masterplan

Miro Wengner

Columbus Data & Analytics Wednesdays - June 2024

Jason Packer

Session 1 - Intro to Robotic Process Automation.pdf

UiPathCommunity

👉 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/

Dandelion Hashtable: beyond billion requests per second on a commodity server

Antonios 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).

Nordic Marketo Engage User Group_June 13_ 2024.pptx

MichaelKnudsen27

[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...

Jason Yip

The typical problem in product engineering is not bad strategy, so much as “no strategy”. This leads to confusion, lack of motivation, and incoherent action. The next time you look for a strategy and find an empty space, instead of waiting for it to be filled, I will show you how to fill it in yourself. If you’re wrong, it forces a correction. If you’re right, it helps create focus. I’ll share how I’ve approached this in the past, both what works and lessons for what didn’t work so well.

Northern Engraving | Modern Metal Trim, Nameplates and Appliance Panels

Northern Engraving

What is an RPA CoE? Session 1 – CoE Vision

DianaGray10

High performance Serverless Java on AWS- GoTo Amsterdam 2024

Vadym Kazulkin

Java is for many years one of the most popular programming languages, but it used to have hard times in the Serverless community. Java is known for its high cold start times and high memory footprint, comparing to other programming languages like Node.js and Python. In this talk I'll look at the general best practices and techniques we can use to decrease memory consumption, cold start times for Java Serverless development on AWS including GraalVM (Native Image) and AWS own offering SnapStart based on Firecracker microVM snapshot and restore and CRaC (Coordinated Restore at Checkpoint) runtime hooks. I'll also provide a lot of benchmarking on Lambda functions trying out various deployment package sizes, Lambda memory settings, Java compilation options and HTTP (a)synchronous clients and measure their impact on cold and warm start times.

Astute Business Solutions | Oracle Cloud Partner |

AstuteBusiness

Recently uploaded (20)

Apps Break Data

"Scaling RAG Applications to serve millions of users", Kevin Goedecke

Fueling AI with Great Data with Airbyte Webinar

Essentials of Automations: Exploring Attributes & Automation Parameters

Skybuffer SAM4U tool for SAP license adoption

Your One-Stop Shop for Python Success: Top 10 US Python Development Providers

inQuba Webinar Mastering Customer Journey Management with Dr Graham Hill

"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor Ivaniuk

Taking AI to the Next Level in Manufacturing.pdf

Monitoring and Managing Anomaly Detection on OpenShift.pdf

JavaLand 2024: Application Development Green Masterplan

Columbus Data & Analytics Wednesdays - June 2024

Session 1 - Intro to Robotic Process Automation.pdf

Dandelion Hashtable: beyond billion requests per second on a commodity server

Nordic Marketo Engage User Group_June 13_ 2024.pptx

[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...

Northern Engraving | Modern Metal Trim, Nameplates and Appliance Panels

What is an RPA CoE? Session 1 – CoE Vision

High performance Serverless Java on AWS- GoTo Amsterdam 2024

Astute Business Solutions | Oracle Cloud Partner |