home.social

#domainmodeling — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #domainmodeling, aggregated by home.social.

fetched live
  1. At Netflix, @bertails and his team have adopted #RDF to capture the meaning in their content in a consistent way and generate consistent representations of it for a variety of internal customers.

    The keys to their system are a Unified Data Architecture (UDA) and a #domainModeling language, Upper, that let them quickly and efficiently share complex #data projections in the formats that their internal engineering customers need.

    knowledgegraphinsights.com/ale

  2. At Netflix, @bertails and his team have adopted #RDF to capture the meaning in their content in a consistent way and generate consistent representations of it for a variety of internal customers.

    The keys to their system are a Unified Data Architecture (UDA) and a #domainModeling language, Upper, that let them quickly and efficiently share complex #data projections in the formats that their internal engineering customers need.

    knowledgegraphinsights.com/ale

  3. At Netflix, @bertails and his team have adopted #RDF to capture the meaning in their content in a consistent way and generate consistent representations of it for a variety of internal customers.

    The keys to their system are a Unified Data Architecture (UDA) and a #domainModeling language, Upper, that let them quickly and efficiently share complex #data projections in the formats that their internal engineering customers need.

    knowledgegraphinsights.com/ale

  4. At Netflix, @bertails and his team have adopted #RDF to capture the meaning in their content in a consistent way and generate consistent representations of it for a variety of internal customers.

    The keys to their system are a Unified Data Architecture (UDA) and a #domainModeling language, Upper, that let them quickly and efficiently share complex #data projections in the formats that their internal engineering customers need.

    knowledgegraphinsights.com/ale

  5. Typically I would recommend having two separate models* to address the different stages. Even if many of the fields exist in both models, each model will be simpler and there will be less risk of introducing more subtle bugs.

    3/n

    #domainDrivenDesign #ddd #ddDesign #softwareArchitecture #domainModeling

  6. Typically I would recommend having two separate models* to address the different stages. Even if many of the fields exist in both models, each model will be simpler and there will be less risk of introducing more subtle bugs.

    3/n

    #domainDrivenDesign #ddd #ddDesign #softwareArchitecture #domainModeling

  7. Typically I would recommend having two separate models* to address the different stages. Even if many of the fields exist in both models, each model will be simpler and there will be less risk of introducing more subtle bugs.

    3/n

  8. Typically I would recommend having two separate models* to address the different stages. Even if many of the fields exist in both models, each model will be simpler and there will be less risk of introducing more subtle bugs.

    3/n

    #domainDrivenDesign #ddd #ddDesign #softwareArchitecture #domainModeling

  9. Typically I would recommend having two separate models* to address the different stages. Even if many of the fields exist in both models, each model will be simpler and there will be less risk of introducing more subtle bugs.

    3/n

    #domainDrivenDesign #ddd #ddDesign #softwareArchitecture #domainModeling

  10. Should you have a separate domain model (and events in EDA) for "draft mode" and "validated mode" or reuse one model for both scenarios?

    This has been one of the interesting architectural themes I've been observing a team exploring at PayFit France over the last couple of weeks….

    1/n

    #domainDrivenDesign #ddd #ddDesign #softwareArchitecture #domainModeling

  11. Should you have a separate domain model (and events in EDA) for "draft mode" and "validated mode" or reuse one model for both scenarios?

    This has been one of the interesting architectural themes I've been observing a team exploring at PayFit France over the last couple of weeks….

    1/n

    #domainDrivenDesign #ddd #ddDesign #softwareArchitecture #domainModeling

  12. Should you have a separate domain model (and events in EDA) for "draft mode" and "validated mode" or reuse one model for both scenarios?

    This has been one of the interesting architectural themes I've been observing a team exploring at PayFit France over the last couple of weeks….

    1/n

  13. Should you have a separate domain model (and events in EDA) for "draft mode" and "validated mode" or reuse one model for both scenarios?

    This has been one of the interesting architectural themes I've been observing a team exploring at PayFit France over the last couple of weeks….

    1/n

    #domainDrivenDesign #ddd #ddDesign #softwareArchitecture #domainModeling

  14. Should you have a separate domain model (and events in EDA) for "draft mode" and "validated mode" or reuse one model for both scenarios?

    This has been one of the interesting architectural themes I've been observing a team exploring at PayFit France over the last couple of weeks….

    1/n

    #domainDrivenDesign #ddd #ddDesign #softwareArchitecture #domainModeling

  15. Has Agile made us anti-design?
    We should still design, and we can do it on the way to working code. Eric Normand explains.

    Recorded at Øredev 2023, where Eric discussed domain modeling and his concept of lenses for thinking about how you build your software.

    An excerpt from Kodsnack 570 - listen wherever you get your podcasts!
    #domainmodeling #lenses #ddd #softwaredevelopment #softwaredesign

  16. Has Agile made us anti-design?
    We should still design, and we can do it on the way to working code. Eric Normand explains.

    Recorded at Øredev 2023, where Eric discussed domain modeling and his concept of lenses for thinking about how you build your software.

    An excerpt from Kodsnack 570 - listen wherever you get your podcasts!
    #domainmodeling #lenses #ddd #softwaredevelopment #softwaredesign

  17. Has Agile made us anti-design?
    We should still design, and we can do it on the way to working code. Eric Normand explains.

    Recorded at Øredev 2023, where Eric discussed domain modeling and his concept of lenses for thinking about how you build your software.

    An excerpt from Kodsnack 570 - listen wherever you get your podcasts!
    #domainmodeling #lenses #ddd #softwaredevelopment #softwaredesign

  18. Has Agile made us anti-design?
    We should still design, and we can do it on the way to working code. Eric Normand explains.

    Recorded at Øredev 2023, where Eric discussed domain modeling and his concept of lenses for thinking about how you build your software.

    An excerpt from Kodsnack 570 - listen wherever you get your podcasts!
    #domainmodeling #lenses #ddd #softwaredevelopment #softwaredesign

  19. Has Agile made us anti-design?
    We should still design, and we can do it on the way to working code. Eric Normand explains.

    Recorded at Øredev 2023, where Eric discussed domain modeling and his concept of lenses for thinking about how you build your software.

    An excerpt from Kodsnack 570 - listen wherever you get your podcasts!
    #domainmodeling #lenses #ddd #softwaredevelopment #softwaredesign

  20. I have availability opening up at the end of October for client work. I'm open to discussing all opportunities, but my ideal projects include domain exploration and modeling.

    Email: [email protected]

    #DomainDrivenDesign #TechnicalProductManagement #ddd #php #phpc #EventStorming #ProductDevelopment #DomainModeling

  21. I have availability opening up at the end of October for client work. I'm open to discussing all opportunities, but my ideal projects include domain exploration and modeling.

    Email: [email protected]

    #DomainDrivenDesign #TechnicalProductManagement #ddd #php #phpc #EventStorming #ProductDevelopment #DomainModeling

  22. I have availability opening up at the end of October for client work. I'm open to discussing all opportunities, but my ideal projects include domain exploration and modeling.

    Email: [email protected]

    #DomainDrivenDesign #TechnicalProductManagement #ddd #php #phpc #EventStorming #ProductDevelopment #DomainModeling

  23. I have availability opening up at the end of October for client work. I'm open to discussing all opportunities, but my ideal projects include domain exploration and modeling.

    Email: [email protected]

    #DomainDrivenDesign #TechnicalProductManagement #ddd #php #phpc #EventStorming #ProductDevelopment #DomainModeling

  24. I have availability opening up at the end of October for client work. I'm open to discussing all opportunities, but my ideal projects include domain exploration and modeling.

    Email: [email protected]

    #DomainDrivenDesign #TechnicalProductManagement #ddd #php #phpc #EventStorming #ProductDevelopment #DomainModeling

  25. If you’re interested in attending or speaking at a domain-driven design conference in the US, then I recommend you check out Explore DDD.

    I’ve been to past events and really enjoyed them. It’s a very friendly, welcoming and enthusiastic crowd.

    The next one is in March 2024 in Denver.

    #domainDrivenDesign #softwareArchitecture #domainModeling #conference #softwareDevelopment #ddDesign

    linkedin.com/company/exploredd

  26. If you’re interested in attending or speaking at a domain-driven design conference in the US, then I recommend you check out Explore DDD.

    I’ve been to past events and really enjoyed them. It’s a very friendly, welcoming and enthusiastic crowd.

    The next one is in March 2024 in Denver.

    #domainDrivenDesign #softwareArchitecture #domainModeling #conference #softwareDevelopment #ddDesign

    linkedin.com/company/exploredd

  27. If you’re interested in attending or speaking at a domain-driven design conference in the US, then I recommend you check out Explore DDD.

    I’ve been to past events and really enjoyed them. It’s a very friendly, welcoming and enthusiastic crowd.

    The next one is in March 2024 in Denver.

    linkedin.com/company/exploredd

  28. If you’re interested in attending or speaking at a domain-driven design conference in the US, then I recommend you check out Explore DDD.

    I’ve been to past events and really enjoyed them. It’s a very friendly, welcoming and enthusiastic crowd.

    The next one is in March 2024 in Denver.

    #domainDrivenDesign #softwareArchitecture #domainModeling #conference #softwareDevelopment #ddDesign

    linkedin.com/company/exploredd

  29. If you’re interested in attending or speaking at a domain-driven design conference in the US, then I recommend you check out Explore DDD.

    I’ve been to past events and really enjoyed them. It’s a very friendly, welcoming and enthusiastic crowd.

    The next one is in March 2024 in Denver.

    #domainDrivenDesign #softwareArchitecture #domainModeling #conference #softwareDevelopment #ddDesign

    linkedin.com/company/exploredd

  30. We believe in being people-driven!

    People make complex things comprehensible. Take #DomainModeling, for example. We are very grateful to Scott Ambler, @rebeccawb, and Alberto Brandolini for their contributions to the field.

    Who would you add?

  31. We believe in being people-driven!

    People make complex things comprehensible. Take #DomainModeling, for example. We are very grateful to Scott Ambler, @rebeccawb, and Alberto Brandolini for their contributions to the field.

    Who would you add?

  32. I once was hired as consultant to guide a team who wanted move their monolith to #microservices. We got only halfway. And it was good!

    The route to microservices goes via #DomainModeling, #decoupling, and #encapsulation. Bounded contexts, decoupling and modules was enough to put the team back on track and moving again. We never built a single microservice.

    This week, Ted Neward wrote about this idea in a post that I now no longer have to write:

    blogs.newardassociates.com/blo

    #SoftwareArchitecture