JogoShugh

• Storing only "current state" completely loses all business value of "how things got this way over time" (time traveling lost)
• Think about showing how event-sourced projections do the same level of work that is traditionally done by complicated SQL queries and graph building from disparate data sources -- but when combined with read-models they do them ahead of query time so as to optimize the retrieval of such data when it's used.

Disadvantages

Learning curve

• Different thinking

JogoShugh

Calculating current state

When storing events to track the complete path of state transitions for an aggregate, it is always possible to also store a projection of the current state, but this is usually only necessary for aggregates that have large numbers of events. Since each SCA Transaction will not have a large number of events, that is probably overkill. Instead, a simple process of reading the list of past events and flowing them through a function that is capable of producing, or projecting, a model is rather straight forward. The most important part is to design this such that it only operates on the events, not on the original requests of "commands" since these often have side-effects like calling APIs, saving data, etc.

In Kotlin, this is easily achieved with a left fold over the set of events. For illustration purposes, consider the following simple illustration. You can run and edit the sample online here in the Kotlin Playground.

class Statef

JogoShugh

./MiniCapPortable/MiniCap.exe -save C:\\Users\\Josh\\cap.jpg -captureactivewin -exit
certutil -encode cap.jpg cap.txt
(lines=$(wc -l < cap.txt); tail -n +2 cap.txt | head -n $(($lines-2)) | tr -d '\n') | awk '{ print "data:image/jpg;charset=utf-8;base64,"$1 }' >data.url

JogoShugh

Request

JSON

{
  "AssetType": "Story",
  "Scope": "Scope:0",
  "Name": "First Story"
}

JogoShugh

Inspired by:

https://developer.atlassian.com/server/confluence/pagination-in-the-rest-api/ https://stackoverflow.com/questions/13872273/api-pagination-best-practices

The following command returns everything available, 47 results in this case:

Note: there's a default page size of 1000, which is why the next and prev have the same values in this case, though we might just strip the parameters out when everything is visible

JogoShugh

Execute AssignMemberWithRole Operation upon a Scope for list of Members by OID Token

Demonstrates how to use a single command to assign multiple Members to a Scope along with Scope-specific roles each Member will have for the target Scope.

Setup

For the context of this example, the following request will setup the instance with the needed starting conditions:

POST http://host/instance/api/asset

JogoShugh

The following input payload specifies an array with 9 commands. These nine commands expand to 13 concrete actions for the backend API processor to execute. However, 12 of these actions are erroneous! Only one of them will succeed against the database running on the instance.

[
  {
    "from": "Animal"
  },
  {
    "from": "Scope",
    "where": {

JogoShugh

    $(document).arrive('.story-card', function() {
        const story = $(this);

        const applyStatusAging = () => {
            const number = story.find('.number').text().trim();
            const title = story.find('.title');
            const query = `
from: PrimaryWorkitem
where:
 Number: ${number}

JogoShugh

Bulking up!

Summary

These are evolving notes demonstrating a new Bulk API for VersionOne Lifecycle to support Create, Update, and Execute Operation commands built upon the powerful and intuitive query.v1 syntax.

Where can I use this?

JogoShugh

$('.advisory').each((index, elm) => {
	const el = $(elm);
	const text = el.text().trim().replace(/\s+|\r|\n+/gmi, '');
	const matches = text.match(/\d+/gi);
	if (matches) {
		matches[0]+='d';
		if (matches.length>1) matches[1]+='c';
		const aging = `<span title='${text}'>${matches.join(', ')}</span>`;
		const story = el.parents('.story-card');
		el.parents('.aging').html(aging);