Week 41, year 2019

  • Kalele Releases Developer Support Program - Carefree, AZ USA, October 7, 2019 Today Kalele released its developer support program for the VLINGO/PLATFORM. There is a sliding scale of options that address the specific needs of individual developers and teams. Vaughn Vernon, Founder and Chief Architect of the VLINGO/PLATFORM, expressed our vision: “We are deeply aware of and concerned for the need … Kalele Releases Developer Support Program Read More » The post Kalele Releases Developer Support Program appeared first on Kalele. [Kalele]
Permalink | From 07 October 2019 to 13 October 2019 | Last updated on: Fri, 16 Jul 2021 03:27:21 GMT

Week 39, year 2019

  • Modeling Temporal Occurrences - The inquiry arrived: “Are time lapsed events Domain Events?” The question is the result of wrestling with whether YearEnded and similar occurrences are actually useful. The inquirer’s assertion is that rather than capturing the fact that the year ended, just send a Command that requires some outcome as a result of the fact that the year ended. Of … Modeling Temporal Occurrences Read More » The post Modeling Temporal Occurrences appeared first on Kalele. [Kalele]
  • Advanced error handling techniques - This post describes some (more) advanced error handling techniques. I’ll probably do a series because this topic is large and there’s quite a few things that need to be cleared out, but we’ll see. [Enterprise Craftsmanship]
Permalink | From 23 September 2019 to 29 September 2019 | Last updated on: Fri, 16 Jul 2021 03:27:21 GMT

Week 34, year 2019

  • You are naming your tests wrong! - Giving your tests expressive names is important. Proper naming helps understand what the test verifies and how the underlying system behaves. In this post, we’ll take a look at a popular, yet inferior naming convention and see how it can be improved. [Enterprise Craftsmanship]
  • Eventsourcing: State from Events or Events as State? - Trying to get people to agree on a single unambiguous definition of a software concept is usually impossible. In the very least, I can point out that such ambiguity exists when it comes to eventsourcing. State from Events For a given stream of events, I can process them to derive some state. This is a very common practice, because it makes a lot of sense to do this. You’ll encounter this basic concept referenced with different names, such as stream processing, event processing, real-time analytics, complex event processing, streaming analytics, real-time streaming analytics, projections, all depending on the environment you’re in. That’s normal, communities evolve language to fit their needs, and we can’t expect the DDD crowd (mostly people developing backend for line of business applications) to synchronize language with, say, data scientists. [Mathias Verraes]
Permalink | From 19 August 2019 to 25 August 2019 | Last updated on: Mon, 7 Jun 2021 09:18:51 GMT

Week 32, year 2019

  • What You Need From Agile - There continues to be all kinds of messages about Agile. My assessment is that there is both a rejection of Agile and an effort to reestablish it more closely with its original guidance and aspirations. As a result, the message is close to this. Agile is dead. Long live Agile. The messages read to me … What You Need From Agile Read More » The post What You Need From Agile appeared first on Kalele. [Kalele]
  • DDD Weekly: Issue #62 - Sociotechnical Design Variables [blog] Nick Tune. Looking through the history of my talks and my posts you can see evolutions in my thinking. One of my current working models is that there are five main categories of criteria for designing boundaries: Business Value: design decisions aligned to the business strategy; Domain: design decisions aligning boundaries with the problem domain; Sociopolitical: design decisions driven by the needs of the people building the systems; Technical: design decisions affected by the technical requirements of a system (e. [DDD Weekly]
Permalink | From 05 August 2019 to 11 August 2019 | Last updated on: Fri, 16 Jul 2021 03:27:21 GMT

Week 27, year 2019

  • DDD Weekly: Issue #61 - Hands-On Domain-Driven Design with .NET Core [book] Alexey Zimarev. Solve complex business problems by understanding users better, finding the right problem to solve, and building lean event-driven systems to give your customers what they really want Should We Create a Shared Service? A Decision-making Checklist [blog] Nick Tune. Deciding when to create a shared service can be highly subjective and quite often highly controversial. But there are a series of heuristics, or questions we can ask ourselves, to improve our chances of making the right sociotechnical design decision. [DDD Weekly]
  • Patterns Are Not Defined by Their Implementation - I wrote about something that I called the Forgettable Payload pattern. The abstract reads “Store the sensitive payload of an event in a separate store to control access and removal. ” Please read the full pattern first. In short, it’s about being able to remove sensitive information from an eventstore, for example upon receiving a deletion request under the GDPR. Some readers have remarked that Forgettable Payloads is the same the Claim Check pattern. Enterprise Integration Patterns describes the problem that Claim Check solves as: “How can we reduce the data volume of a message sent across the system without sacrificing information content?” The solution of both patterns is pretty much identical: UserUploadedImage { userId:12, image: ". [Mathias Verraes]
Permalink | From 01 July 2019 to 07 July 2019 | Last updated on: Mon, 7 Jun 2021 09:18:52 GMT