Adv in Archaeological PracticeReposting from Kiva Journal:
Looking for funding for your Southwestern archaeological or historical research? AAHS offers research grants up to $1,400 and travel grants up to $700. Applications accepted between January 1st and February 15th!
https://aahs1916.org/grant/research-and-travel-grants/
Reposting from Kiva Journal:
Researchers analyze a dog burial from the Kipp site using morphology and isotope analyses. Discover the insights gained on how the dog’s diet may have reflected the dietary practices of the people at Kipp. #SWArch #Kipp #NewMexico #ArchaeologyDogs buff.ly/4fbRvMS
Researchers analyze a dog burial from the Kipp site using morphology and isotope analyses. Discover the insights gained on how the dog’s diet may have reflected the dietary practices of the people at Kipp. #SWArch #Kipp #NewMexico #ArchaeologyDogs buff.ly/4fbRvMS
Nick TuneSometimes it’s best not to overdo the "DDD" when shaping the boundaries in your software architecture.
Using techniques like EventStorming you might achieve a clear conceptual model with well defined subdomains that domain experts agree with.
But it’s also important to analyse data flows: What information does a subdomain need from other subdomains to apply rules and make decisions?
Recently I hit this scenario...
1/2
- are there any business rules or calculations that span all of this data?
- does all of this data need to always be consistent?
If you answer "no" to both, you should consider aggregating the data in the UI or a BFF.
But you may also need to do advanced searching across the combined data. This could push you towards a single subsystem although a separate search-oriented subsystem is a common option (especially as you need to search across more diverse data).
2/2
Should you design APIs based on what you (the owning team) think is the best way to expose your domain, or do you make compromises based on the needs of your API's consumers?
(API here refers to any element of the public contract of your service/subsystem/app/domain/context, such as HTTP endpoints or events.)
JP de Vooght#arc42 meets c4 for #swarch documentation https://bitsmuggler.github.io/arc42-c4-software-architecture-documentation-example/
I had a good day at the Global Software Architecture Summit in Barcelona.
The highlights for me were Sonya Natanzon talking about architectural decision making and @vladikk talking about coupling and complexity.
I've also enjoyed meeting so many new and familiar people. I'm sorry that I didn't have time to spend with everyone but I tried my best.
Looking forward to our next in-person DDD London meet-up on the 10th August.
A huge thank you to Schroders for hosting the event and making it possible.
On the night, we’ll have talks from Michael Plöd and Yevgen Nebesov 🇺🇦, along with plenty of chances to network and socialise.
Hope to see you there.
#domainDrivenDesign #softwareArchitecture #teamTopologies #dddesign #swarch #meetup #london
Modularity Maturity Index (MMI) enthüllt #swarch https://www.wps.de/wps/rechenzeit/softwarearchitektur-bewertung-mit-dem-modularity-maturity-index-mmi
I'm very happy to announce another in-person DDD London meetup, scheduled for the 4th September.
We are honoured to welcome Wolfgang Goebl, who will be talking about a very interesting topic, and one that is relevant to many organizations at the moment: how to connect Domain-Driven Design and Organization Design.
Hope to see you there for another great evening of learning and socializing.
