Your email was sent successfully. Check your inbox.

An error occurred while sending the email. Please try again.

Proceed reservation?

Export
  • 1
    Language: German
    Pages: 1 online resource (342 pages)
    Edition: 1. Auflage.
    Uniform Title: Learning domain-driven design
    DDC: 005.1/2
    Keywords: Application software Development ; Domain-specific programming languages ; Model-driven software architecture
    Abstract: Softwareentwicklung ist heutzutage anspruchsvoller denn je: Als Entwicklerin oder Entwickler müssen Sie technologische Trends im Blick behalten, aber genauso die Business Domains hinter der Software verstehen. Dieser Praxisratgeber beschreibt zentrale Patterns, Prinzipien und Praktiken, mit denen Sie Geschäftsbereiche analysieren, die Business-Strategie verstehen und, was am wichtigsten ist, Ihr Softwaredesign besser an den Geschäftsanforderungen ausrichten können. DDD-Praktiker Vlad Khononov zeigt Ihnen, wie diese Praktiken zu einer robusten Implementierung der Geschäftslogik führen und Ihr Softwaredesign und Ihre Softwarearchitektur zukunftsfähig machen. Abschließend wird DDD in Verbindung mit Microservices-basierten, Event-getriebenen und Data-Mesh-Architekturen beleuchtet.
    Note: Includes bibliographical references and index
    Library Location Call Number Volume/Issue/Year Availability
    BibTip Others were also interested in ...
  • 2
    Online Resource
    Online Resource
    [Erscheinungsort nicht ermittelbar] : O'Reilly Media, Inc. | Boston, MA : Safari
    Language: English
    Pages: 1 online resource (1 video file, approximately 49 min.)
    Edition: 1st edition
    Keywords: Electronic videos ; local
    Abstract: It turns out that domain-driven design is not just for cargo shipping. Vladik Khononov (Naxex) explains how he and his team embraced domain-driven design (DDD) (with very limited resources and a very short time to market) at Plexop, a large-scale marketing system that spans over a dozen different business domains. Join in to learn how DDD allowed the team to manage business complexities, find out strategies for defining context boundaries, explore lessons learned the hard way, and discover where they had to adapt the DDD methodology to fit the company’s needs. This session was recorded at the 2019 O'Reilly Software Architecture Conference in New York.
    Note: Online resource; Title from title screen (viewed October 31, 2019)
    Library Location Call Number Volume/Issue/Year Availability
    BibTip Others were also interested in ...
  • 3
    ISBN: 9788328392632 , 8328392631
    Language: Polish
    Pages: 1 online resource (296 pages) , illustrations
    Edition: [First edition].
    Uniform Title: Learning domain-driven design
    DDC: 005.1/2
    Keywords: Application software Development ; Domain-specific programming languages ; Model-driven software architecture
    Abstract: Domain-driven design, czyli projektowanie dziedzinowe, w skrócie DDD, jest zbiorem praktyk tworzenia architektury oprogramowania z uwzględnieniem dziedziny biznesu i jej problemów. W ten sposób logika biznesowa staje się sercem aplikacji. Wielu architektów jednak nie radzi sobie ze złożonością tworzonego oprogramowania. Nauczenie się zasad i wzorców DDD, przyswojenie technik dekompozycji dużego systemu, modelowania i projektowania integracji komponentów jest sposobem na zbudowanie systemu w pełni zgodnego z potrzebami i celami biznesowymi. Ta książka zawiera opis podstawowych wzorców, zasad i praktyk przydatnych podczas analizy dziedzin biznesowych, ułatwiających zrozumienie ich strategii i dostosowanie architektury do potrzeb biznesu, aby umożliwić zbudowanie solidnej implementacji logiki biznesowej. Omówiono tu narzędzia i techniki podejmowania decyzji projektowych, a także istotniejsze wzorce projektowe. Dużo uwagi poświęcono kodowi i różnym sposobom implementacji logiki biznesowej systemu. Opisano również techniki i strategie stosowania DDD w rzeczywistych projektach. Ciekawym elementem jest zaprezentowanie związków projektowania dziedzinowego z innymi ważnymi metodologiami i wzorcami.
    Note: Includes bibliographical references
    Library Location Call Number Volume/Issue/Year Availability
    BibTip Others were also interested in ...
  • 4
    Online Resource
    Online Resource
    [Erscheinungsort nicht ermittelbar] : O'Reilly Media, Inc. | Boston, MA : Safari
    Language: English
    Pages: 1 online resource (96 pages)
    Edition: 1st edition
    Keywords: Electronic books ; local
    Abstract: The majority of software projects are delivered late or over budget, or they fail to meet the client’s requirements. Attack the problem head-on and build better software with domain-driven design (DDD)—a methodology that aligns software design with a business’s domain, needs, and strategy. In this report, Vladik Khononov introduces the key patterns and practices of domain-driven design and shows you how to apply them to improve the success rate of your projects. You’ll discover how to explore, analyze, and model your company’s business domain along with techniques for implementing that knowledge. Once you understand the fundamentals, you’ll be able to selectively apply DDD concepts to analyze and simplify your codebase, explore new requirements, and more. You’ll learn: Key domain-driven design concepts, including ubiquitous language and bounded contexts How to employ “event storming” to streamline the process of discovering domain knowledge and building a ubiquitous language Patterns and techniques for implementing business logic and architecting solutions that deliver business goals How to maintain and evolve both tactical and strategic designs over time
    Note: Online resource; Title from title page (viewed October 25, 2019)
    Library Location Call Number Volume/Issue/Year Availability
    BibTip Others were also interested in ...
  • 5
    Online Resource
    Online Resource
    [Erscheinungsort nicht ermittelbar] : O'Reilly Media, Inc. | Boston, MA : Safari
    Language: English
    Pages: 1 online resource (1 video file, approximately 49 min.)
    Edition: 1st edition
    Keywords: Electronic videos ; local
    Abstract: It turns out that domain-driven design is not just for cargo shipping. Vladik Khononov (Naxex) explains how he and his team embraced domain-driven design (DDD) (with very limited resources and a very short time to market) at Plexop, a large-scale marketing system that spans over a dozen different business domains. Join in to learn how DDD allowed the team to manage business complexities, find out strategies for defining context boundaries, explore lessons learned the hard way, and discover where they had to adapt the DDD methodology to fit the company’s needs. This session was recorded at the 2019 O'Reilly Software Architecture Conference in New York.
    Note: Online resource; Title from title screen (viewed July 31, 2020) , Mode of access: World Wide Web.
    Library Location Call Number Volume/Issue/Year Availability
    BibTip Others were also interested in ...
  • 6
    Online Resource
    Online Resource
    [Erscheinungsort nicht ermittelbar] : O'Reilly Media, Inc. | Boston, MA : Safari
    Language: English
    Pages: 1 online resource (180 pages)
    Edition: 1st edition
    Keywords: Electronic books ; local ; Electronic books
    Abstract: Today, more than ever, building software is hard. Not only we have to chase ever-changing technological trends, but we also have to grasp business domains that we are building the software for. The latter is often overseen, and it explains why so many projects are doomed to fail. After all, how can you build a solution if you don't understand the problem? Through this book, you will learn the Domain-Driven Design (DDD) methodology which provides a set of core patterns, principles, and practices for analyzing business domains, understanding business strategy, and, most importantly, aligning software design with its business needs. These include Ubiquitous Language, Bounded Contexts, Event Storming, and others. You will see how these practices not only lead to robust implementation of business logic, but also to future-proof software design and architecture. You will also learn the relationship between DDD and other methodologies to ensure that you are able to make architectural decisions that will meet the business needs. The final section puts all of this into practice using a real life story of implementing Domain-Driven Design in a startup company. Reading the book will allow you to use DDD for analyzing business domains, aligning software and business strategies, and making socio-technical design decisions. By the end of this book, you will be able to:-Build a shared understanding of a business domain-Analyze a company's business domain and competitive strategy-Decompose a system into bounded contexts-Coordinate the work of multiple teams working together-Gradually start implementing domain-driven design
    Note: Online resource; Title from title page (viewed October 25, 2021) , Mode of access: World Wide Web.
    Library Location Call Number Volume/Issue/Year Availability
    BibTip Others were also interested in ...
  • 7
    Online Resource
    Online Resource
    [Erscheinungsort nicht ermittelbar] : O'Reilly Media, Inc. | Boston, MA : Safari
    Language: English
    Pages: 1 online resource (1 video file, approximately 43 min.)
    Edition: 1st edition
    Keywords: Electronic videos ; local
    Abstract: “Ninety-five percent of the words are spent extolling the benefits of ‘modularity’ and that little, if anything, is said about how to achieve it”—Glenford J. Myers, 1978. The above quote is 40 years old. Today, four decades later, nothing has changed except terminology. Time to fix this. Vladik Khononov (Invesus Group) explains how to decompose a system into loosely coupled components: how to draw boundaries between services, how to decide whether some logic belongs to one service or another, and how domain-driven design can help us make those decisions. Finally, he takes a stab at answering the age-old question of what part of a microservice should be “micro” and how it can be measured. You’ll hear about neither Docker nor Kubernetes. Actually, nothing related to infrastructure. Instead, you’ll dive into the difference between microservices and bounded contexts, discover when each pattern should be used, and get takeaways from Vladik’s experience optimizing microservices-quotebased architectures at Naxex. This session was recorded at the 2019 O'Reilly Software Architecture Conference in San Jose.
    Note: Online resource; Title from title screen (viewed October 31, 2019)
    Library Location Call Number Volume/Issue/Year Availability
    BibTip Others were also interested in ...
Close ⊗
This website uses cookies and the analysis tool Matomo. More information can be found here...