What are the pros and cons of cross provider hosting?

February 26th, 2015

I have a B2B business model where small businesses will come to my site, sign up, purchase free and premium products (mostly software widgets with recurring charges), very mild provisioning (adding a URL to a coupon or landing page for example) of those products, and then occasionally go away only to come back for more purchases and re-provisioning.

On the flip side of that, these provisioned products will be served up to the businesses customers via mobile apps, browser extensions, youtube videos, physical beacons and potentially even TV commercials. This will mean there is much higher potential for spikes to my hosted database from the businesses customer rather than the businesses themselves. Even analytics for all of this will be hosted elsewhere (like maybe google analytics but not sure).

Right now I have my web page hosted on GoDaddy so I don't have to worry about scaling but I also don't know how well that will work if I start to sign up thousands and maybe tens of thousands of businesses. I have also secured an AWS free tier EC2 and RDS processor instances and I think it is a safe bet that I should move my database over to the RDS which is a managed service specifically for database scalability. What I don't know is should I also move my page over to the EC2 on AWS or just leave it on GoDaddy and have everything access the database in the RDS remotely including my web page? Assuming GoDadday can handle the B2B traffic, it is probably far cheaper for me to continue to host the lower bandwidth, more static, non-real time (aka responses in under a second) traffic there and put the more dynamic, real time dependent database under a managed service like Amazons RDS.

Anyone have experience with cross provider hosting like this or adamantly against it for some reason? I know also I will need a better email host than I have with Godaddy for customer signup confirmations. At least with their basic email hosting plan. My email had a 16 hour delay recently and when I called to complain they didn't really care because I was on what is basically free email hosting with my web site.

Igor Chernyy

February 26th, 2015

If you believe that your provider for static website can handle the load there is nothing wrong with that setup up.

I would urge you to ensure that you access your database in a secure way (don't hardcode your access keys, make sure your db calls are protected from sql scripting attacks, etc). Also I would also recommend you setup extensive monitoring and alerting on your database to ensure that if it is compromised you can cut off the access ASAP.

Clynton Caines SharePoint Developer at Discover Technologies

February 26th, 2015

I've managed domains and websites for a very long time - and even for static pages, I would stay away from godaddy and other low-cost/free-ish hosters. The reason is that they lump your site in with many others - on limited servers... for every service. That means email (as you've discovered) and web. Whenever I have pure static pages that can live on those types of hosters I always apply a CDN from a separate provider to ensure the pages/images get served.

As for the aws instances, you could buy a lot for $2k/month - a lot! However, from what you're describing, I would expect to spend no more than $200/month to start. If you're going to stick with the approach (as opposed to using a higher level provider like parse.com), then it's a good idea to start with the smaller, free instances and test your site's responsiveness under increasing load. Once everything is in place, it's really easy to scale up. Especially if this is your first big aws implementation, you could waste a ton of $ over a few months while you implement, test and optimize everything. They offer a large number of useful blocks - many of which you wont need. btw, if you've already budgeted a hefty sum right of the gate, then you might be better off spending it on tech talent to architect your solution or on aws optimization/implementation training.

Yazan Al-Sheikhly CEO at Right Servers Inc., Co-Founder at BitSent Inc.

February 26th, 2015

You shouldn't be having 16 hour delays, the server you're on is most likely overloaded. As far as using multiple hosting providers, that's no problem as all just point your application to use the remote DV and set up the appropriate security and permissions (keys, usernames, etc.), a managed hosing provider would be able to help you out with that. Kind regards, Yazan

Lisa Retief Veteran software engineering leader and entrepreneur.

February 26th, 2015

EC2 to RDS is nothing like a cross-host setup. It is highly optimized, in the same region, data transfer is free etc. They are build to work together, by the best in the business.

If your static pages are not talking to your database or application (which, by definition, they are not) then putting the dynamic pages in one place and the static pages in another should be a manageable intermediate situation.

However, I can not imagine having the static pages hosted in the same place as the dynamic pages would add much to your cost, and you would benefit in terms of simplicity and forward growth.

I would need more detail on volumes and usage of the static vs dynamic to advise further.

Jake Carlson Software Development Manager at Oracle

February 26th, 2015

Yes, you will want to move your application to the same internal network environment as the database server if at all possible. Less latency, more secure, period. If the mobile app connects directly to the remote database (doesn't use an intermediary API) then yes it doesn't really matter for mobile. If it uses an API which in turn hits the database, then the API should absolutely be hosted at the same place for the same reasons listed above. 200ms may not sound like a lot but 1) that's best case scenario, and 2) that may actually be a significant % of full run time depending on the operation. If you do connect to a remote database, make damn sure the connection is secure if you're dealing with sensitive data (I recommend this even for local network database connections, but there is less of a risk there).

Finally, I wouldn't make too many assumptions about mobile connections. When on decent wifi local network latency will not be the bottleneck, but off of wifi the connection can be quite slow.

Zachary McClung Chief Customer Officer | Cloud Servers | Disaster Recovery | CDN | Dedicated Servers

February 26th, 2015

Kerry - I'm sorry if you felt I didn't understand the question or properly answer it, it wasn't my intention at all. The logic comes from, your website doesn't need to connect remotely. The mobile apps do. There is simply no way around it. Being in this industry for a decade now, when designing a solution it is always about removing latency and improving reliability. I don't see a lot of cross provider hosting as a strategy, it doesn't make a lot of sense. A typical provider can provide fail over service, geo diversification, global dns and sql clustering without an issue. It can be done more affordable then $2,000.00 per month. For e-mail reliability I'd use something like mandrill. I'd host the site with the database, I'd use global dns and I'd load balance everything. You'll be able to do it for a couple hundred bucks to start and you'll be unlimited growth without the hassle of managing a bunch of providers and specialties. Normally providers aren't willing to get on the phone with each other to troubleshoot an issue and then your stuck miles from shore without a paddle.

Igor Chernyy

February 26th, 2015

I agree with Zachary. If you are using your web page to simply relay information about your business and maybe gather leads then what you have is probably ok. However if you are doing more than bare minimum you really want a much greater level of control over your system.

I have dealt with GoDaddy in the past and - if your website will be slammed it might take them as much as an hour to scale you up to handle the traffic. More so you don't even get notified when that happens (at least when I worked with them they didn't have that option).

Faraz Ahmed Co-Founder & CTO - Mindstorm Studios

March 4th, 2015

@Karl Heroku (also owned by Salesforce) is by no means a small player in the PaaS market. It has been maturing for longer than Azure/Google and comfortably falls in a "Big Three" list in the context of a solid toolset, market adoption and developer mindshare.

There are plenty of other metrics to consider. Here is an interesting PaaS evaluation tool.

Kerry Davis

February 26th, 2015

I wish I had not mentioned GoDaddy now:) My bad.

Let me restate the question. Is it OK to have a static web site unmanaged on a different host ASSUMING (big assumption on my part and I accept that) the unmanaged web host can handle the load and we know that load will be considerably less than the access to the database.

One might say that running your web site out of an unmanaged AWS EC2 instance that accesses your MySQL database from an RDS instance is the exact same thing? Is it not?

Kerry Davis

February 26th, 2015

Well actually I just had the latency discussion with the AWS consultant at their pop in facility in SF just yesterday. He told me that latency on their network was like 150 ms max across the US with most of that simply in travel and regen time, and around the world is less predictable but fairly safely under 1 second. I figure the latency in rendering most of my larger content into a mobile device is gated more by the last mile mobile wireless connection (or even a slow wifi connection which is also wireless) in most cases and not the internet connection which is mostly wired around the planet. Load balancing apparently adds a couple of ms but once again that is likely in the noise compared to the last mile content delivery.

However, this is more the response I was looking for with regard to things I had not considered like geo diversification and sql clustering. I understand the need for both those things (I think) but how to keep them in synch is a bit of a mystery to me along with AWS customer billing.

And honestly, if you are saving 200 ms in link latency on content that loads in seconds over the last mile, when, if ever, do you distribute your page and data geographically. (not a question that can be answered with this little detail I suspect).

(The $2k month comes from the fact that there is an AWS managed service partner out there that bills 18% but not until your bill reaches $2K/month with Amazon...I have no idea what $2K buys you at this point)

Question stats