If i have to correlate different Domains such as Movies/ Books/ Music then which database would be ideal for linking different domains? I tried Freebase but that does not correlate different domains.
Might sound like a naive comment. Have you considered the possibility of coding the data from different domains rather than using the direct song/movie etc?
Related
We have a website which provides services for people based in particular city.
We want to scale and provide it for more cities but we want to remain separated IT within the city realm: one webhost, cloud service , database etc for one location. It does not only enables us to scale individually (some cities are bigger than other several times) but most significantly it improves our code-base and db queries to not use city's predicates - despite the fact it is more expensive in general.
At the same time we do not want to use subdomain. User can switch city through dropdown and request should go to appropriate VM without url being changed so the routing should work seamlessly.
Based on Azure documentation we are still not sure what solution would meet our needs, Traffic Manager, Load balancer or custom redirects.
How you accomplish this is ultimately up to you, but from an Azure-specific perspective, the only multi-region built-in load-balancing service is Traffic Manager. This operates in one of three routing modes:
Primary/failover
Round-robin
Closest (based on latency, not physical distance)
For any other type of routing (such as letting the user choose location, per your question), you'd need to implement this on your own or via 3rd-party service (and how to accomplish that would be a matter of opinion/debate/discussion, which is off-topic for StackOverflow).
Since you're looking to have a separate DB, cloud-role and webhost per city, I do not see how you can get away from doing subdomains.
Do you not want subdomains because of SEO? If so, it'd be easier to find another way to solve SEO problem.
But whatever Traffic Manager or other DNS based routing solution you use, it'll be splitting users by where they come FROM and not where they're going TO.
The destination problem is solved thru separate sub-domains
Top websites such as facebook, dropbox, seem to use another domain to load their css, js. Example. fbcdn.net. Whats going on? Why don't they use their own current url?
This is often done for load balancing purposes. Companies can speed up their services by offloading static content to different servers allowing their dynamic content servers to function more efficiently.
I don't work at any of those companies, but I've used that strategy successfully in the past.
Normally, we restrict access to our website from certain countries at the edge of our network. We are about to deploy our application to Azure and need to block certain countries from accessing it. This is due to U.S. Embargo policies... What is the best way to block certain countries so we meet U.S. laws and regulations?
Thanks,
Mike
One idea is to build a simple proxy that attempts to filter on region. My teammate Ricardo Villalobos co-wrote an MSDN article explaining how someone might do that with node.js, in Azure, filtering against the MaxMind geolocation database. It's probably not an exact fit, as it deals with media stream filtering, but you should be able to use the basic technique and proxy described, as a starting point.
I'm developing a new website with membership. Do you think any of these has advantages or disadvantages? I thought today that a mobile version will be available and I was planning m.website.com for that but in "username.website.com" case, this won't work. On the other hand, I think website.com/username is ugly.
I need and also want to know your ideas about this.
Thanks.
From a management standpoint, username.website.com will surely be greater. You have to create a new DNS record for each user. In order to do that programatically, you are going to have to manage your DNS with a service that has a API. I am pretty sure registrars like GoDaddy do not have this. Amazon has something called Route 53 that might?
username.website.com will never work as domain names are propagated via DNS servers and through millions of network devices. Any change to the domain name takes time.
Usually, if you want to handle users you can do something like this: www.website.com/users/bob so mobile version will differ only by m. prefix.
It's a lot harder to make a script that sets up subdomains than it is to make a folder for a user.
If you have a mobile site, you could fix the m.username.domain.com by making it username.domain.com/m, if you really want the subdomain.
My half a cent.
I've been trying to figure out how to best organize the dozen or so websites I have on a shared hosting service.
Lately I've been thinking that it's safer/easier to have separate accounts for each site that I have, but then I've lost some of the ability to share files, applications and what not. It seems nice to have a partitioning of sites, but Im curious as to what more experienced people would say is a better approach for this...
Thanks!
You should always have separate accounts, it's better for system security.
A small guide on basic shared hosting security is here: http://webhostinggeeks.com/blog/2010/02/25/an-introduction-to-linux-web-hosting-%E2%80%93-linux-vs-windows-web-hosting/
The security of separation depends how the Web server is setup. Different configurations will severely weaken the security of the system, however it is still useful to separate sites for cleanliness and security.