Author

Topic: AWS Server requirement for Wallet for new ICO (Read 132 times)

newbie
Activity: 20
Merit: 0
There are solid plans on the way. But this is very initial phase of planning, so just putting everything on paper in advance.
Dedicated servers will be there and already that work is in progress for quotes, supports, etc. But for ICO webpage and user control panel can go on two (or more) separate servers for start. Eventually, it will be migrated to dedicated servers. It would give us some realistic facts, if we know, what resources are needed for servers.
When you say that there may be lot of requests on server(s), it looks like, it should have good network bandwidth. But from technical stats, need to figure out sufficient resources.
member
Activity: 126
Merit: 50
Ask me for Pools, Nodes and Explorers.
If you are doing an professional ICO, then you might want to skip AWS and for example invest on a dedicated server. If you are doing an ICO, you should have some budget to start with as it is unlikely that VPS's are that reliable if you get alot of requests on your servers.

I'd atleast try Godaddy, as they have always providen quality services to their customers.


Although last but not least, why are you making an ICO if you don't have a specialist plan about such things?
newbie
Activity: 20
Merit: 0
Hello,

(Mod: Please move it to appropriate forum, if this is not correct forum for this question)
I need some suggestions regarding server technical setup for Ethereum Wallet for new ICO. Obviously this is serious job of infrastructure and security engineer, but as a start, I am looking for some generic idea. Each user will have own login details to their control panel. They can always login to their control panel and see their invested Eth.
If it has to be planned on AWS Windows instance, what kind of instance can be picked (General Purpose vs Compute Optimized vs GPU Instances  vs Memory Optimized vs Storage Optimized) ?
I am feeling that network performance should be high, but how to determine the network performance ?
How redundancy will play here ?
How (large amount of) traffic will be handled, if many users will hit website ?

It would be great help, if somebody can suggest or have some discussion on this.

Thanks in advance
Jump to: