11 Dec

Horizontal and Vertical Scaling

Scalability is the capability of a system to expand from either existing configurations to handle increasing amount of load or by adding an extra hardware. There are mainly two types of scalabilities, horizontal and vertical. Horizontal scaling, is adding more servers to your application to spread the load. The simplest case of horizontal scaling may be to move your database onto a separate machine from your web server. Where as Vertical scaling is to add more RAM, more processors, more bandwidth, or more storage to your machine.

Horizontal scaling can only be applied to applications built in layers that can run on separate machines. Horizontal scaling applies really well to on-demand cloud server architectures, such as Amazon’s EC2 hosting platform. Horizontal scaling can also facilitate redundancy – having each layer running on multiple servers means that if any single machine fails, your application keeps running. While Vertical scaling can be a quick and easy way to get your application’s level of service back up to standard. On the negative side, vertical scaling will only get you so far. Upgrading a single server beyond a certain level can become very expensive, and often involves downtime and comes with an upper limit.

So what scaling strategy best suit your needs? It all comes down to the application it must be implemented on. There are many applications that can only scale vertically. They can only be run on a single server. You have a clear strategy choice with these applications! But, a well written application should scale horizontally very easily. An application that is designed to scale horizontally can also be scaled vertically. So your still left with an open choice. You can either weigh up the cost of vertically scaling with an extra bit of RAM vs horizontally adding a new server in your cluster.

Share this
08 Nov

TLD Domain: coming your way soon

Before we get started, for those that aren’t clear with the term, what is a TLD?
It’s one of the domains at the highest level in the hierarchical Domain Name System of the Internet. Top-Level domain names are installed in the root zone of the name space, and for all domains in the lower levels, it is the last part of the domain name. For example, in the domain name www.webairy.com, the top level domain would be COM.

The Silicon Valley giant paid ‘$25m for acquisition rights’ to the .app domain. The purchase overcomes the $5m that Amazon paid for the rights to .buy last year. In fact, it’s the most any company has ever paid for a domain this far– and so it’s a pretty safe to say that Google’s got some sort of game plan. It will also likely toss the rest of the internet into the dust. Let’s think about it: over the past decade, the tech giant has become virtually synonymous with the web. You don’t “search for it”, you Google it.

Consequently, the well-being of millions of small business depend almost entirely upon the stability of Google’s search algorithms. So after its forking of over $25m on a previously unknown TLD, it only makes sense for Google to push emerging .app websites to the top of results pages. After all, Google might have quite a sum of cash, but whoever authorized that purchase is going to have to prove some sort of return on investment.

So, where does that leave us? Sitting on a precipice, it seems. As of now, unique TLD’s haven’t taken off because of one or two major roadblocks. If anybody on earth can find a way to circumnavigate those roadblocks and monetize the system, it’s going to be Google. All we can do now is wait and see what happens. But either way, it looks like we’re about to start seeing a whole lot of new TLD’s floating about on the web frankly very soon.

Share this

© 2014 Alaska Hosting. All rights reserved.

Powered by themekiller.com anime4online.com animextoon.com apk4phone.com tengag.com moviekillers.com