spring - SpringXD limitations? -


i'm evaluating springxd , wondering if there limitations current functionality provides. couldn't find documentation on , i'm sure answer falls under "it depends" category, thought ask anyways.

examples of mean are:

  • is there max limit on number of streams can created? (i'm guessing not these seem backed database answer may depend on streams doing)
  • is there max limit on number of named channels can created? (i'm guessing may depend on underlying mom used message passing)
  • is there max limit on number of nodes (xd-node or xd-admin) can running in system? (i'm guessing depends on zookeeper , on how many connections underlying mom allows)
  • etc.

so speaking, there limitations of potential use cases people should aware of before picking springxd?

thank you, aaron

edit answer @dturanski

the situation i'm thinking of having potentially large number of streams (technically unbounded). i'm talking minimum of maybe couple thousand in beginning potentially half million (or more) if goes well. many of these streams working on named channels technically unbounded. i'm not sure how springxd manages creation of underlying destinations see there problem having lots of topics/queues in message broker depending on underlying mom technology used . also, assume able scale number of xd nodes in system accommodate load (thus question on zookeeper limitations) , able deal other infrastructure concerns. these streams wouldn't performing heavy workload. question technological capabilities of systems used springxd.

so ignoring practical limitations of having resources, way out fo mind thinking capability of springxd?

in theory there no such limitations. there practical limitations suggest, distributed system, , entirely dependent on system resources , work load. if have specific use case in mind think might push these limits, provide context address these questions.


Comments

Popular posts from this blog

java - Custom OutputStreamAppender not run: LOGBACK: No context given for <MYAPPENDER> -

java - UML - How would you draw a try catch in a sequence diagram? -

c++ - No viable overloaded operator for references a map -