I suggest you ...

Composite UI, Business Components and Deployment

To implement composite UI right, you often say that you need to deploy close together all the Business Components needed to fufill that use case.
If you deploy the same BC multiple times (on multiple endpoints), all those instances will share the same database right ? How do you handle updates of persistence and services ? dont we lose autonomy ?

119 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Valerio BorioniValerio Borioni shared this idea  ·   ·  Admin →

    1 comment

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Valerio BorioniValerio Borioni commented  · 

        I want to clarify the statement "How do you handle updates of persistence and services ?".
        I don't mean keeping data up to date, you have talked many times about strategies for doing that (from running on the same instance if inside the same organization, up to integration through pub-sub). I'm referring more about software (and schema) updates.
        And then, the business component deployed in multiple instances will act as a read only cache? If not, am I basically sharding my domain model persistence ?

      Feedback and Knowledge Base