Patterns Backlog Review ‐ November 2024

Patterns Project Backlog

Pending Issues

Pending Issues	Existing Category	New category	Overlapping with existing	Suggestions	Future Action	Action	State
Design Category for coding patterns	No	maybe	Yes	Coding practices are compiler specific	Maybe find the best practices of languages to see if they can be correlated with SCI	Close
Using Complied Languages rather than Interpreted Languages	No	maybe	Yes	Coding practices are compiler specific	Maybe find the best practices of languages to see if they can be correlated with SCI	Close
Automatically scaledown K8s clusters	Cloud	No	Yes	NA	NA	Close
Azure well architected Framework patterns	Yes	Yes	No	Intresting and can be put in different categories	NA	Take up
Specify Pattern Reading Persona(s)	No	No	No	No	Can consider the idea of persona based patterns while restructuring	Take up if restructuring patterns is picked up
Collaboration with W3C web patterns	Yes	Yes	NA	NA	Uplift-Check possibility	Take
Add uglify pattern	Web	No	No	Interesting pattern idea, could be integrated with a guide on how to do that --> And do we have real evidence that it will bring improvement?	NA	Take after restructuring
Green Software Design Resource	No	Yes	No	NA	NA	Take when restructuring
Patterns Use Case Microsoft & DOW	No	No	No	We should discuss, how we want to handel Use Cases and how we want to present them	Discuss this in a meeting	Take after restructuring? (or should we look into use cases before restructuring
Multi-level caching in Web	Web/Cloud	No	No	Have a look, when creating a concept on new structure of patterns	NA	Take when restructuring
Adopter: Mastercard	No	No	No	We have to look into, how others took our patterns and what did they do, to make them better for themself	NA	Take when restructuring
Graduation of Patterns v1	No	No	No	We should definitely look into that, maybe even before restructuring it.	Graduate the project so that we have v1 approved	Take before restructuring
Example architectures	No	No	No	Look into that when creating concept of structure for patterns	NA	Take when restructuring
Integrate Energy Efficient Machine Learning patterns from academia into AI section	AI	No	No	Intresting pattern idea might need to look into possible association with SCI	NA	Take when restructuring
For Data Compression use ZTSD instead of gzip	NA (maybe cloud but not really)	No	Yes	Can be absorbed into the existing pattern for compressing data	NA	Take while restructuring
"Right-sizing" Kubernetes Instances	In cloud	No	Yes	Can be absorbed into the existing pattern	Do we need a section for k8s patterns, it not really all Cloud	Close
Add additional description field	NA	NA	NA	Shown as ongoing, looks like done	Look to see if all task related to this is done

Grouping Chart

graph TD;
    A[Patterns]
    A-->B[Compiler Specific]
    A-->C[Cloud]
    A-->D[Web]
    A-->E[AI]
    A-->F[Uncategorized]
    
    B-->G[Design Category for coding patterns]
    B-->H[Using Complied Languages rather than Interpreted Languages]
    
    C-->I[Automatically scaledown K8s clusters]
    C-->J[Azure well architected Framework patterns]
    C-->K[Multi-level caching in Web]
    C-->L[For Data Compression use ZTSD instead of gzip]
    C-->M["Right-sizing" Kubernetes Instances]

    D-->N[Add uglify pattern]
    D-->O[Collaboration with W3C web patterns]
    
    E-->P[Integrate Energy Efficient Machine Learning patterns from academia into AI section]
    
    F-->Q[Green Software Design Resource]
    F-->R[Patterns Use Case Microsoft & DOW]
    F-->S[Specify Pattern Reading Persona(s)]
    F-->T[Adopter: Mastercard]
    F-->U[Graduation of Patterns v1]
    F-->V[Example architectures]
    F-->W[Add additional description field]

Loading