Pages:
Author

Topic: Is bitcoind reliable when depending on it for web services? - page 2. (Read 2148 times)

member
Activity: 111
Merit: 10
If not is there an alternative to be used that can keep up with an expanding web service?"

An alternative that can really take the heat of a web service is the BOP Enterprise Bitcoin Server.

You can run several instances of it and send requests to them through a load balancing message bus.
See the example repository https://github.com/bitsofproof/bop-explorer that shows a simple REST API forwarding to the bus.
The server code is in https://github.com/bitsofproof/supernode

Bits of Proof will launch its offer in two days in San Jose, dramatically reducing the pain of integrating with the Bitcoin protocol.

Interesting so, I can run the server myself or is this a service being sold so I'd have to pay per request for example? Secondly, is there much in the way of documentation for the REST API? I'm assuming you don't have any other examples or libraries that aren't Java?
hero member
Activity: 836
Merit: 1030
bits of proof
If not is there an alternative to be used that can keep up with an expanding web service?"

An alternative that can really take the heat of a web service is the BOP Enterprise Bitcoin Server.

You can run several instances of it and send requests to them through a load balancing message bus.
See the example repository https://github.com/bitsofproof/bop-explorer that shows a simple REST API forwarding to the bus.
The server code is in https://github.com/bitsofproof/supernode

Bits of Proof will launch its offer in two days in San Jose, dramatically reducing the pain of integrating with the Bitcoin protocol.
member
Activity: 111
Merit: 10
You don't mention what "service" you intend on providing, so it's hard to say.  Generally it's not advisable to use bitcoind directly as your sole accounting system because there is no synchronous replication of metadata and internal transactions (e.g. "move"s).

Ideally it's just to read data about transactions and get address balances but it needs each account to potentially be read once per hour.
staff
Activity: 4284
Merit: 8808
You don't mention what "service" you intend on providing, so it's hard to say.  Generally it's not advisable to use bitcoind directly as your sole accounting system because there is no synchronous replication of metadata and internal transactions (e.g. "move"s).
member
Activity: 111
Merit: 10
Hey all, I created a question here: http://bitcoin.stackexchange.com/questions/10878/is-bitcoind-reliable-when-depending-on-it-for-web-services

was wandering as there are a lot of technical minded people with bitcoin knowledge and knowledge of bitcoind and it's application in web services could answer it for me as I want to start work on a small project but my worry is scalability later on in running a service.

Here's the question:

"What I mean by the title is, say If I create a service with bitcoind being used to create and store large numbers of accounts and address, is it likely to take the strain? Can I setup multiple instances of bitcoind to access information about the network or would I need to one large instance of a bitcoin daemon to handle everything?

If not is there an alternative to be used that can keep up with an expanding web service?"

Please feel free to discuss here but if you have an experienced answer to give I'd hope you'd answer the question for me on stack exchange and so it's filed away easily for others to find.
Pages:
Jump to: