MrDudeMan
Lifer
I'm contemplating moving my business's server to AWS (S3 + EC2 + RDS). The cost per year is less than buying and maintaining a server and the associated backup, IT, power, and upgrades. It's a win from that angle, but I'm equally concerned about speed and accessibility.
I have approximately 10 employees who use the server right now, but the load is always pretty light. I would LOVE to start writing tools that customers can use, which would all rely on an externally available database. For that reason, I'm considering moving my new project dashboard database to RDS and then allowing mobile apps and web based tools to access it concurrently with my employees. That got me thinking... why not move the whole server to the cloud?
I understand the reasons why this type of thing would be bad, but I'm having trouble convincing myself that the risk isn't worth it. I can get symmetric fiber at 20, 50, 100, 250, 500, and 1000 Mbps. Which one do you think would be most appropriate for my application? A typical file is between 0.25 and 10 MB (AutoCAD files, PDFs, docx/xlsx, etc.). I'm leaning toward 50 or 100 for cost reasons.
If I use S3 as a virtual drive, the functionality would be completely transparent to my employees. However, all of the IT issues with my in house server would be gone and presumably replaced by other IT issues that are simpler, right? (this is the main thing I want you to poke holes in).
I know if my internet connection goes down that I'm toast. I could fix that by purchasing a second internet connection, e.g. cable or dsl, for minimal connectivity requirements. I could also setup offline synchronization of some folders on each workstation's local disk. Note: I would use S3's Multi-AZ option, which duplicates the data in a geographically distant data center. The weak link is the internet connection to AWS as far as I can tell; everything else has either redundancy or an incredibly low risk of failure.
In a nutshell, I want to use AWS for my database and file server needs as well as rely on it to inherently backup and protect my data.
Do your worst.
Edit: I forgot to mention that I also have Office 365 Small Business Premium, which comes with Sharepoint Online that I believe can be used as a file server. I would still need to host my database somewhere else, but this is another option that would certainly cost less. The main drawback would be the lack of access to and from the database from the file server, which may or may not be a big deal. I don't know because I haven't finished developing the tool suite.
I have approximately 10 employees who use the server right now, but the load is always pretty light. I would LOVE to start writing tools that customers can use, which would all rely on an externally available database. For that reason, I'm considering moving my new project dashboard database to RDS and then allowing mobile apps and web based tools to access it concurrently with my employees. That got me thinking... why not move the whole server to the cloud?
I understand the reasons why this type of thing would be bad, but I'm having trouble convincing myself that the risk isn't worth it. I can get symmetric fiber at 20, 50, 100, 250, 500, and 1000 Mbps. Which one do you think would be most appropriate for my application? A typical file is between 0.25 and 10 MB (AutoCAD files, PDFs, docx/xlsx, etc.). I'm leaning toward 50 or 100 for cost reasons.
If I use S3 as a virtual drive, the functionality would be completely transparent to my employees. However, all of the IT issues with my in house server would be gone and presumably replaced by other IT issues that are simpler, right? (this is the main thing I want you to poke holes in).
I know if my internet connection goes down that I'm toast. I could fix that by purchasing a second internet connection, e.g. cable or dsl, for minimal connectivity requirements. I could also setup offline synchronization of some folders on each workstation's local disk. Note: I would use S3's Multi-AZ option, which duplicates the data in a geographically distant data center. The weak link is the internet connection to AWS as far as I can tell; everything else has either redundancy or an incredibly low risk of failure.
In a nutshell, I want to use AWS for my database and file server needs as well as rely on it to inherently backup and protect my data.
Do your worst.
Edit: I forgot to mention that I also have Office 365 Small Business Premium, which comes with Sharepoint Online that I believe can be used as a file server. I would still need to host my database somewhere else, but this is another option that would certainly cost less. The main drawback would be the lack of access to and from the database from the file server, which may or may not be a big deal. I don't know because I haven't finished developing the tool suite.
Last edited: