Common ddd pitfalls

•

3 likes•1,562 views

While DDD is becoming more and more popular, there are quite a few potential misinterpretations and malpractices floating around. These issues are time-consuming, and they induce a lot of frustrations and needless yak-shaving experiences. These pitfalls are plenty, ranging from higher level things (for example a lack of focus on the strategic part) to technical things (for example misinterpretations of the repository pattern), and even the surrounding area (for example errors made when"selling DDD" to your team members). By sharing this experience I hope to reduce the huge amount of time and effort people spend on "doing DDD wrong".

TacticalInfrastructure
Strategic
Sellingit

TacticalInfrastructure
Strategic
Sellingit
General

Strategic Bounded contexts A lot Little
POV  
Amount  
Up- / Downstream A lot Little
Contracts  
Dependencies  
Some things that work *
* n = 1

Tactical
Repositories, exposing state
https://www.facebook.com/Jeroom.Inc

Tactical
In repos, “Tell, don’t ask”
… but don’t overdo it

Infrastructure
Frameworks & Libraries: too generic

Infrastructure
Generic frameworks & Libraries => hacks

Infrastructure
Eventual consistency: do you need it?

Infrastructure
Anything: do you need it?
”Il semble que la perfection soit atteinte
non quand il n'y a plus rien à ajouter,
mais quand il n'y a plus rien à retrancher.”
Antoine de Saint-Exupéry

Selling it
Selling DDD to your peers & bosses

Selling it
This is a different presentation

Selling it
… but I’ll show you the recap

Strategic
• Don’t ignore bounded contexts
• Understand Conway’s Law
• Think first, act later
• Have domain experts
Craft BCs and make them explicit

Tactical
• Only in core domains
• Find all ways to model them
• Repositories = domain only
• Repositories = Tell, don’t ask

Infrastructure
• Don’t build a BDUF
• Frameworks <> libraries
• Avoid hacks
• Aim for simplicity, not ease of building

Selling it
• Don’t force feed
• Lead by example
• One step at a time

Domain-Driven Design (DDD) and Functional Programming (FP) have a lot of good things in common: DDD has borrowed many ideas from the FP community, and both share a common inspiration on established formalisms like maths. For the software developer, the result is a style of code that mixes the best of DDD, OO and FP. Even in non functional languages like Java or C#, this combined set of practices helps craft simple and powerful code that reads well and that is very easy to test. In this talk we will have a closer look at some of these ideas, in the context of domain models inspired from real-world projects. From basic FP hygiene like immutability and closure of operations to more mathematical inspirations from abstract algebra like monoids, we will show how all that translates into beautiful code. WARNING: This may influence your coding style… This talk was presented on the first day of I T.A.K.E. 2013 at Bucharest http://itakeunconf.com/

Getting better

Tom Janssens

What is "Domain Driven Design" and what can you expect from it?

Tom Janssens

This talk will give you pointers on what DDD is and what it is not, so you can figure out whether it might be useful for you. Next it will provide you some guidance so you can avoid the mistakes most people make when they get started with DDD. These mistakes range from strategic modelling misconceptions to tactical pattern misinterpretations, and things like enforcing DDD on your team members. By the end of this talk you should know whether DDD might be interesting for you, and what to watch out for in case you do get started.

Leveraging more then DDD Lite in the startup project

Thomas Jaskula

Functional programming in C#

Thomas Jaskula

Selling ddd

Tom Janssens

Not every part of a software system will be well-designed. How do you know where to put the time and effort to refine the design, or refactor existing code? Learn how strategic Domain-Driven Design (DDD) patterns can show you how to know which parts of your system matter most to your business and how to focus your team’s design efforts most effectively. Context mapping and Core Domain are key concepts in DDD, providing valuable techniques and insights into where to focus your design attention, yet most developers have never heard of them. This presentation will introduce the tools of strategic DDD and show you how they can shine a light on your design challenges.

Como DDD e Strategic Design estão nos ajudando a modernizar um Legado

Luiz Costa

O objetivo desta palestra é mostrar como é possível evoluir e reescrever partes de uma aplicação legada com mais 5 anos em produção utilizando técnicas de uma parte Domain Driven Design conhecida como Strategic Design. É uma aplicação web escrita em Python e Django que suporta a operação de um grupo focado em medicina do trabalho, com clínicas espalhadas pelo país. Nesta palestra vamos mostrar uma abordagem que pode ajudar times que precisam lidar com aplicações legadas grandes e complexas no caminho da modernização.

From legacy to DDD

Andrzej Krzywda

This talk was delivered at the PHPers meetup in Wroclaw, 10 August 2015. I presented a set of techniques which help you transition from a legacy codebase to DDD. I focused more on the strategic DDD patterns like bounded contexts. The main idea in such refactorings is to: 1. List all your (potential) bounded contexts 2. Decide which ones are deserving the DDD tactical patterns 3. Decide which ones can stay as CRUD 4. Communicate between the BCs via events

Domain driven design in a nutshellToni Esteves

Simplifying your design with higher-order functionsSamir Talwar

Domain Driven Design Quickly

Mariam Hakobyan

Introduction to-ddd

John Ferguson Smart Limited

Parallel Complex Event ProcessingKarol Grzegorczyk

Developing functional domain models with event sourcing (sbtb, sbtb2015)

Chris Richardson

Event sourcing persists each entity as a sequence of state changing event. An entity’s current state is derived by replaying the events. Event sourcing is a great way to implement event-driven micro services. When one service updates an entity, the new events are consumed by other services, which then update their own state. In this talk we describe how to implement business logic using a domain model that is based on event sourcing. You will learn how to write functional, immutable domain models in Scala. We will compare and contrast a hybrid OO/FP design with a purely functional approach. You will learn how Domain Driven Design concepts such as bounded contexts and aggregates fit in with event-driven microservices.

A year with event sourcing and CQRS

Steve Pember

As businesses grow, so does the complexity of their software. New features, new models, and new background processes all continue to be added. . .and developers struggle to make sense of it all. Yet the end user demands a swift and functional experience when interacting with your application. It is paramount to be open to alternative patterns that help tame complex, high-demand services. Two such patterns are command-query responsibility segregation (CQRS) and event sourcing (ES). Command-query responsibility segregation is an architectural pattern for user-facing applications that extends from the now standard Model-View-Controller (MVC) pattern and is an alternative to the CRUD pattern. At its core, CQRS is about changing how we think of and work with our data by introducing two types of models: all user actions become commands, and a read-only query model powers our views. Commands and queries are logistically separated, providing additional decoupling of our application. CQRS also calls for changes in how we store and structure our data. Enter event sourcing. Instead of persisting the current state of our domain objects or entities, we record historical events about our data. The key advantage is that we can examine our application data at any point in time, rather than just the current state. This pattern changes how we persist and process our data but is surprisingly efficient. While each of the two patterns can be used exclusively, they complement each other beautifully and facilitate the construction of decoupled, scalable applications or individual services. Stephen Pember explores the fundamentals of each pattern and offers several examples and demonstration code to show how one might actually go about implementing CQRS and ES. Steve discusses task-based UIs and domain-driven design as he outlines some of the advantages—and challenges—that ThirdChannel has seen when developing systems using CQRS and ES over the past year.

Harnessing Domain Driven Design

Capgemini

Gayathri Thiyagarajan Lead Software Engineer - Capgemini Andrew Harmel-Law Principal Software Engineer - Capgemini Eric Evans’ Domain Driven Design (DDD) is a core text for all developers, and it's experiencing a renaissance due to the rise of microservices. But are most of us really applying DDD when we're "doing" distributed systems development? Gayathri and Andrew are going to argue that we're not, but we should be – we need to recalibrate. We'll begin by laying out what DDD means to us based on experiences we've had building microservices with distributed teams over the last two years. We'll touch lightly on the well-understood elements such as "ubiquitous language", "intention revealing interfaces" and "hands on architects", before clarifying and explaining the much misapplied concept of "bounded contexts". Finally we'll draw up in front of the largely ignored ones, such as the many patterns for inter-team communication which derive from "context maps". As we move away from the well-understood to the disregarded, we'll illustrate why these later ones are by far the most important to successful microservice-based projects. We'll explain why they matter, and the bene ts you'll see from applying them. You will leave ready to apply the full power of DDD, and you'll have more fun as you do it.

A Practical Guide to Domain Driven Design: Presentation Slides

thinkddd

Domain Driven Design 101

Richard Dingwall

Domain Driven Design (DDD) is a topic that's been gaining a lot of popularity in both the Java and .NET camps recently. Entities, value types, repositories, bounded contexts and anti-corruption layers -- find out what all the buzz is about, and how establishing a domain model can help you combat complexity in your code. Richard Dingwall is a .NET developer and blogger with a passion for architecture and maintainable code. He is currently working at Provoke Solutions as lead developer on a six-month project introducing test-driven development (TDD) and domain-driven design (DDD) to a large ASP.NET ERP system. An hour-long talk given at Wellington .NET user group, Sept 23 2009.

The Good the Bad and the Ugly of Dealing with Smelly Code (ITAKE Unconference)

Radu Marinescu

We all have a burning desire to write clean code. Every morning we wake up, look in the mirror, and promise ourselves that today we will follow the principles and best practices learned from Uncle Bob and his disciples. But we live in a cruel environment, surrounded by millions of smelly lines of code, reflections of a stinky design… and these constantly challenge our pure-hearted desire for writing clean code. In such an environment, the stubbornness to practice daily the writing of clean code is vital. But is it enough? Can we avoid getting lost in a sea of smelly code and design? In this talk I will try to persuade you that, in dealing with large-scale systems, craftsmanship must be supported by proper techniques and tools that can help us to quickly understand, assess and improve the sea of smelly design that surrounds us. I will present a pragmatic approach on how design anti-patterns (e.g. God Class, Feature Envy, Refused Bequest, Shotgun Surgery) can be automatically detected using a set of metrics-based detection rules, by analyzing the history of the system, and by using intriguing software visualizations. The presentation will also include a live demo of tools that can automate the entire approach to a high-extent. These tools are so robust that they can deal with systems of several million lines of code; but they are also friendly enough to provide you with customized hints that help you deal with each and every case of an “unclean” code.

Lean innovation

Philip Wheat

How to Implement Domain Driven Design in Real Life SDLC

Abdul Karim

Expo 2013 Lisa Hammer & David Newman; Effective Presentations

lhagan

Presenting correct and truthful information may get you by, but if you want to stand out, an effective presentation is the key to making a lasting impression. Not only can it help your career, but you represent your team in a way that shines the most favorable light on them! In this brief session, you will learn the basic principles of preparing and delivering an effective presentation, how slides can make of break the presentation, and perhaps even learn a little about the great presenter inside of you!

Production roles - top trumps

hasnmedia

Viewers also liked

DDD Basics: Bounded Contexts, Modelling - Kortrijk Edition

Mathias Verraes

DDD Modeling Workshop

Dennis Traub

Strategic Appplication Development with Domain-Driven Design (DDD)Dennis Traub

Domain-driven design - tactical patterns

Tom Janssens

Strategic design using ddd

Paul Rayner

Como DDD e Strategic Design estão nos ajudando a modernizar um Legado

Luiz Costa

From legacy to DDD

Andrzej Krzywda

Domain driven design in a nutshellToni Esteves

Simplifying your design with higher-order functionsSamir Talwar

Domain Driven Design Quickly

Mariam Hakobyan

Introduction to-ddd

John Ferguson Smart Limited

Parallel Complex Event ProcessingKarol Grzegorczyk

Developing functional domain models with event sourcing (sbtb, sbtb2015)

Chris Richardson

A year with event sourcing and CQRS

Steve Pember

Harnessing Domain Driven Design

Capgemini

A Practical Guide to Domain Driven Design: Presentation Slides

thinkddd

Domain Driven Design 101

Richard Dingwall

The Good the Bad and the Ugly of Dealing with Smelly Code (ITAKE Unconference)

Radu Marinescu

Viewers also liked (18)

DDD Basics: Bounded Contexts, Modelling - Kortrijk Edition

DDD Modeling Workshop

Strategic Appplication Development with Domain-Driven Design (DDD)

Domain-driven design - tactical patterns

Strategic design using ddd

Como DDD e Strategic Design estão nos ajudando a modernizar um Legado

From legacy to DDD

Domain driven design in a nutshell

Simplifying your design with higher-order functions

Domain Driven Design Quickly

Introduction to-ddd

Parallel Complex Event Processing

Developing functional domain models with event sourcing (sbtb, sbtb2015)

A year with event sourcing and CQRS

Harnessing Domain Driven Design

A Practical Guide to Domain Driven Design: Presentation Slides

Domain Driven Design 101

The Good the Bad and the Ugly of Dealing with Smelly Code (ITAKE Unconference)

Similar to Common ddd pitfalls

Lean innovation

Philip Wheat

How to Implement Domain Driven Design in Real Life SDLC

Abdul Karim

Expo 2013 Lisa Hammer & David Newman; Effective Presentations

lhagan

Production roles - top trumps

hasnmedia

Devconf 2011 - PHP - How Yii framework is developed

Alexander Makarov

DevDay 2013 - Building Startups and Minimum Viable Products

Ben Hall

Resilient Functional Service Design

Uwe Friedrichsen

This slide deck addresses the importance of proper functional design for creating resilient distributed systems (not only, but also microservice-based systems). It starts by explaining the pitfall that many developers fall into when getting started with resilience: Quite often the effects of the fundamentals, i.e., creating bulkheads and choosing the communication paradigm, on system robustness at runtime are heavily underrated. Instead, the pure technical measures like circuit breakers, backpressure, etc. are often overestimated. Unfortunately, all technical measures will not help to create a robust system if the functional design leads to highly coupled services where the availability of one service functionally totally depends on the availability of another service. The same is true if you need to call many services that all need to be available to answer a client request. To make it worse, most of the wide-spread design approaches like functional decomposition, DRY (don't repeat yourself), design for re-use or layered architecture exactly lead to those problems, i.e., they are not suitable for designing distributed systems. This slide deck does not offer any silver bullets to solve the problem (and actually I believe there is no silver bullet), but at least a few guiding principles. Additionally, it shows how the choice of the communication paradigm influences the bulkhead design and this way creates more options to create a good service design that also supports resiliency on a functional level. As always this slide deck is without the voice track, i.e., most of the information is missing. But I hope that the slides on their own also provide some helpful hints. Remark: As the "dismiss reusability" slide tends to get quite some attention, one more remark about that slide: On the voice track I usually add "If you find something that is worth being made reusable, i.e., that it satisfies the commercial constraints of Fred Brooks 'Rule of 9' (see https://blog.codecentric.de/en/2015/10/the-broken-promise-of-re-use/ for details), do not put it in a service. Instead create a library and put the functionality in there. And make sure that changes to the library do not mean that all users have to upgrade at the same time, but that any library user can update whenever it fits the user's schedule. Otherwise, you would have introduced tight coupling through the back door again."

What I have learned by dealing with a dungeon master

Raúl Araya Tauler

Domain storytelling-one size fit all process

Michael Chen

The Lost Tales of Platform Design (February 2017)

Julien SIMON

Pitch the way VCs think

khoslaventures

Getting Started with Architecture Decision Records

Michael Keeling

Documenting architecture design decisions is commonly considered a good practice and yet many teams don't take the time to write down the decisions they make. In our experience this happens for a few reasons: documentation is rejected as being too heavyweight, documentation has little influence since it is typically out of sight and out of mind, and many developers don’t know what to document. Architecture Decision Records (ADRs) address many of these problems by capturing design decisions in a simple, lightweight templates that is stored close to repositories used by stakeholders -- often in the same repository as code affected by the ADR. In this hands-on workshop you will learn how to write effective ADRs and how to overcome road bumps teams often experience when first getting started with ADRs. By the end of this session you will have the skills you need to champion ADRs and help your team start (or improve) your design decision log.

Getting Bought by Google: Or another technology heavyweight - MaRS Best Pract...

MaRS Discovery District

What do technology majors or other desirable purchasers really seek? What do they value that would not be obvious unless you had been through such a deal? How can past success be replicated? Does IP really matter? And most importantly, how does one build a strong valuation? Using practical case studies, this presentation focuses on aspects of acquisitions that may be new to many entrepreneurs. http://www.marsdd.com/events/details/bought-google-technology-heavyweight/

Conversation patters for ubiquitous language

Michał Bartyzel

50.000 orange stickies later

Alberto Brandolini

Jeff Katz on Prototyping

Jeff Katz

Allan Kelly - Do it right, then do the right thing

DevConFu

Several generations of managers have been taught to "Do the right thing, then do it right." It has a logic all of its own doesn't it? What's the use of being highly effective is you are highly effective at the wrong thing? But what if the obsession with doing the right thing is itself harmful? What if you don't know the right thing to do until you have do something? What if you need to do something in order to know what is right and what is wrong? Rather than analyse before doing anything, it may well be cheaper and faster with modern tools to do something, and then analyse what happens before deciding what to do next. But only if you can iterate: do something, learn and go around again. In this session Allan Kelly will present an alternative, possibly heretical, view of the world and argue that doing things right is essential if you are to do the right thing.

Elaine Wherry, Meebo: What Web Application Design Can Learn from the Harpsichord

BayCHI

Baroque harpsichordists excelled at taking simple melodies and creating elaborate, beautiful pieces of music. But in their desire to push the boundaries of experimentation, these keyboard virtuosi eventually ornamented the music beyond the limits of good taste, making the composer's original melody unrecognizable. Listen to enough Baroque music, and you'll ultimately decide, "This is ridiculous. I never want to hear another harpsichord!" Something similar happens in Web design. With new technology comes a natural desire to experiment, challenging fundamental design rules to push the limits of web applications. As designers explore just how far they can go, there inevitably comes a breaking point, where you think, "This is ridiculous. I never want to see another rounded corner!" In both cases, the lesson learned is that just because you can, doesn't mean you should. Web application interaction design brings a wealth of creative freedom and makes it increasingly important to identify the functional rationale for UI choices rather than gut reactions like "this is the way users are accustomed to it" or "this just looks better." Elaine will discuss how to approach web application design when, instead of one dominant voice, there's a multitude of web product and design philosophies. Elaine Wherry is co-founder and VP of Products at Meebo. Originally a classically-trained violinist, Elaine graduated from Stanford University with a degree in Symbolic Systems with a concentration in Human-Computer Interaction. After graduating, she became the manager of Usability and Design at Synaptics. She co-founded Meebo.com in 2005 with two good friends, Seth Sternberg and Sandy Jen. Initially, she wrote Meebo's JavaScript framework and went on to build and oversee Meebo's web, user experience, and product management teams. Today, Meebo has approximately 40 million unique users in the United States and nearly 100 million unique users worldwide, according to Quantcast.

Goto Chicago; Journeys To Cloud Native Architecture: Sun, Sea And Emergencies...

OpenCredo

Many businesses want to embrace modern business practices by delivering projects quickly and scaling faster. For this, adopting a Cloud Native mindset and architecture makes sense but is not a simple magic carpet ride. In this talk, Nicki Watt from OpenCredo will share the realities of making that journey for a number of clients. Far from being a smooth journey to the promised land, you will learn about the numerous detours, bumps and challenges encountered along the way. Microservices, Kubernetes, Success, but also Bandages and Crutches; This talk is for you if you want to gain some pragmatic insight into what is entailed with such endeavors.

How To (Not) Open Source - Javazone, Oslo 2014

gdusbabek

Releasing an open source project while maintaining a shipping product is hard! Different behaviors, attitudes and actions can help or hinder your cause; and they are not always obvious. The Blueflood distributed metrics engine was released as open source software by Rackspace in August 2012. In the succeeding months the team had to strike a manageable balance between the challenges of growing a community, being good open source stewards, and maintaining a shipping product for Rackspace. Find out what worked, what did not work, and the lessons that can be applied as you endeavor to take your project out into the open. In this presentation you will learn about strategies for releasing open source products, pitfalls to avoid, and the potential benefits of moving more of your development out in the open. We have also made a few realizations about the community growing up around metrics. It is still young, and there are problems that come with that youth. I'll talk about some things we can do to make a better software ecosystem.

Similar to Common ddd pitfalls (20)

Lean innovation

How to Implement Domain Driven Design in Real Life SDLC

Expo 2013 Lisa Hammer & David Newman; Effective Presentations

Production roles - top trumps

Devconf 2011 - PHP - How Yii framework is developed

DevDay 2013 - Building Startups and Minimum Viable Products

Resilient Functional Service Design

What I have learned by dealing with a dungeon master

Domain storytelling-one size fit all process

The Lost Tales of Platform Design (February 2017)

Pitch the way VCs think

Getting Started with Architecture Decision Records

Getting Bought by Google: Or another technology heavyweight - MaRS Best Pract...

Conversation patters for ubiquitous language

50.000 orange stickies later

Jeff Katz on Prototyping

Allan Kelly - Do it right, then do the right thing

Elaine Wherry, Meebo: What Web Application Design Can Learn from the Harpsichord

Goto Chicago; Journeys To Cloud Native Architecture: Sun, Sea And Emergencies...

How To (Not) Open Source - Javazone, Oslo 2014

Recently uploaded

Encryption in Microsoft 365 - ExpertsLive Netherlands 2024

Albert Hoitingh

Generating a custom Ruby SDK for your web service or Rails API using Smithy

g2nightmarescribd

Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.

FIDO Alliance Osaka Seminar: Overview.pdf

FIDO Alliance

JMeter webinar - integration with InfluxDB and Grafana

RTTS

Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application. In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics. Length: 30 minutes Session Overview ------------------------------------------- During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana: - What out-of-the-box solutions are available for real-time monitoring JMeter tests? - What are the benefits of integrating InfluxDB and Grafana into the load testing stack? - Which features are provided by Grafana? - Demonstration of InfluxDB and Grafana using a practice web application To view the webinar recording, go to: https://www.rttsweb.com/jmeter-integration-webinar

Monitoring Java Application Security with JDK Tools and JFR Events

Ana-Maria Mihalceanu

Elevating Tactical DDD Patterns Through Object Calisthenics

Dorra BARTAGUIZ

After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!

To Graph or Not to Graph Knowledge Graph Architectures and LLMs

Paul Groth

Essentials of Automations: Optimizing FME Workflows with Parameters

Safe Software

Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place. Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects. Here’s what you’ll gain: - Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows. - Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy. - Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency. - Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity. We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic. Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.

From Daily Decisions to Bottom Line: Connecting Product Work to Revenue by VP...

Product School

FIDO Alliance Osaka Seminar: Passkeys at Amazon.pdf

FIDO Alliance

Knowledge engineering: from people to machines and back

Elena Simperl

Securing your Kubernetes cluster_ a step-by-step guide to success !

KatiaHIMEUR1

Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster. However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks. In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.

UiPath Test Automation using UiPath Test Suite series, part 3

DianaGray10

State of ICS and IoT Cyber Threat Landscape Report 2024 preview

Prayukth K V

The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development. The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers: State of global ICS asset and network exposure Sectoral targets and attacks as well as the cost of ransom Global APT activity, AI usage, actor and tactic profiles, and implications Rise in volumes of AI-powered cyberattacks Major cyber events in 2024 Malware and malicious payload trends Cyberattack types and targets Vulnerability exploit attempts on CVEs Attacks on counties – USA Expansion of bot farms – how, where, and why In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East Why are attacks on smart factories rising? Cyber risk predictions Axis of attacks – Europe Systemic attacks in the Middle East Download the full report from here: https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/

Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...

UiPathCommunity

💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™: See how to accelerate model training and optimize model performance with active learning Learn about the latest enhancements to out-of-the-box document processing – with little to no training required Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath. Speakers: 👨‍🏫 Andras Palfi, Senior Product Manager, UiPath 👩‍🏫 Lenka Dulovicova, Product Program Manager, UiPath

GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...

James Anderson

Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management. The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM). Speakers: Bob Boule Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle. Gopinath Rebala Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.

FIDO Alliance Osaka Seminar: Passkeys and the Road Ahead.pdf

FIDO Alliance

FIDO Alliance Osaka Seminar: The WebAuthn API and Discoverable Credentials.pdf

FIDO Alliance

The Art of the Pitch: WordPress Relationships and Sales

Laura Byrne

Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes? All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.

Unsubscribed: Combat Subscription Fatigue With a Membership Mentality by Head...

Product School

Recently uploaded (20)

Encryption in Microsoft 365 - ExpertsLive Netherlands 2024

Generating a custom Ruby SDK for your web service or Rails API using Smithy

FIDO Alliance Osaka Seminar: Overview.pdf

JMeter webinar - integration with InfluxDB and Grafana

Monitoring Java Application Security with JDK Tools and JFR Events

Elevating Tactical DDD Patterns Through Object Calisthenics

To Graph or Not to Graph Knowledge Graph Architectures and LLMs

Essentials of Automations: Optimizing FME Workflows with Parameters

From Daily Decisions to Bottom Line: Connecting Product Work to Revenue by VP...

FIDO Alliance Osaka Seminar: Passkeys at Amazon.pdf

Knowledge engineering: from people to machines and back

Securing your Kubernetes cluster_ a step-by-step guide to success !

UiPath Test Automation using UiPath Test Suite series, part 3

State of ICS and IoT Cyber Threat Landscape Report 2024 preview

Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...

GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...

FIDO Alliance Osaka Seminar: Passkeys and the Road Ahead.pdf

FIDO Alliance Osaka Seminar: The WebAuthn API and Discoverable Credentials.pdf

The Art of the Pitch: WordPress Relationships and Sales

Unsubscribed: Combat Subscription Fatigue With a Membership Mentality by Head...

Common ddd pitfalls

1. Common DDD pitfalls @ToJans - 2014

4. Strategic

5. Tactical Strategic

6. TacticalInfrastructure Strategic

7. TacticalInfrastructure Strategic Sellingit

8. TacticalInfrastructure Strategic Sellingit General

9. Strategic Bounded contexts

10. Strategic Bounded contexts

11. Strategic Ignoring bounded contexts

12. Strategic Ignoring bounded contexts

13. Strategic Conway’s law

14. Strategic Conway’s law

15. Strategic “Gedankenexperiment”

16. Strategic “Gedankenexperiment”

17. Strategic Lack of a domain expert

18. Strategic Lack of a domain expert

19. Strategic Bounded contexts A lot Little POV   Amount   Up- / Downstream A lot Little Contracts   Dependencies   Some things that work * * n = 1

20. Tactical

21. Tactical

22. Tactical DDD for non-core domains

23. Tactical DDD for non-core domains

24. Tactical Ignoring some aspects

25. Tactical Ignoring some aspects

26. Tactical Repositories, exposing state

27. Tactical Repositories, exposing state https://www.facebook.com/Jeroom.Inc

28. Tactical In repos, “Tell, don’t ask”

29. Tactical In repos, “Tell, don’t ask” … but don’t overdo it

30. Infrastructure

31. Infrastructure BDUF – what you built

32. Infrastructure BDUF – what you need

33. Infrastructure Frameworks <> Libraries

34. Infrastructure Frameworks <> Libraries

35. Infrastructure Frameworks & Libraries: too generic

36. Infrastructure Generic frameworks & Libraries => hacks

37. Infrastructure Eventual consistency: do you need it?

38. Infrastructure Eventual consistency: do you need it?

39. Infrastructure Anything: do you need it? ”Il semble que la perfection soit atteinte non quand il n'y a plus rien à ajouter, mais quand il n'y a plus rien à retrancher.” Antoine de Saint-Exupéry

40. Selling it Selling DDD to your peers & bosses

41. Selling it Tough

42. Selling it Really tough

43. Selling it This is a different presentation

44. Selling it … but I’ll show you the recap

45. And now it’s time for a

46. And now it’s time for a

47. Recap And now it’s time for a

48. Strategic • Don’t ignore bounded contexts • Understand Conway’s Law • Think first, act later • Have domain experts Craft BCs and make them explicit

49. Tactical • Only in core domains • Find all ways to model them • Repositories = domain only • Repositories = Tell, don’t ask

50. Infrastructure • Don’t build a BDUF • Frameworks <> libraries • Avoid hacks • Aim for simplicity, not ease of building

51. Selling it • Don’t force feed • Lead by example • One step at a time

52. General

53. General

54. General

55. General

56. General

57. General

58. General HAVE FUN!

59. And now it’s time for

60. Questions And now it’s time for