1. There will be no limitations down the line. The limits will be gone.

2. Don't rely on embedded too much, there will be changes in upcoming releases 
(some drastic some not so).

3. Yes, but going forward that might change (wrt embedded). Do you mean 
nodes=servers? There is currently a practical limit depending on 
setup/use-case, going forward there won't be.

What is your concrete use-case? Can you answer what you actually want to do?

Michael

> Am 09.10.2015 um 18:40 schrieb Piyush Katariya <[email protected]>:
> 
> I wanted to adopt neo4j community edition for one of my new project. Its 
> datasize will grow exponentially after say couple of years. I could not able 
> to find an answer for couple of questions in terms of limitations and 
> scalability so asking them here.
> 
> As mentioned in the http://neo4j.com/docs/stable/capabilities-capacity.html 
> <http://neo4j.com/docs/stable/capabilities-capacity.html> max nodes is 
> limited to 2 ^ 35. are there any ways to mitigate this limitation with v2.2.5 
> ? or at least would it change in near future (in less than 2 years) to a 
> greater value ?
> 
> Is it safe to rely on or use neo4j embedded API or is it frequently changing 
> on every release . will there be drastic changes in API in near future.
> 
> In neo4j enterprise edition, is it possible to use neo4j as embedded and 
> master-slave clustering mode. If yes how much is the maximum nodes allowed ?
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Neo4j" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] 
> <mailto:[email protected]>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
You received this message because you are subscribed to the Google Groups 
"Neo4j" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to