Welcome to ledger-live-desktop-app.org
|
Web Hosting - Redundancy and Failover
Among the more useful innovations in computing, actually invented decades ago, are the twin ideas of redundancy and failover. These fancy words name very common sense concepts. When one computer (or part) fails, switch to another. Doing that seamlessly and quickly versus slowly with disruption defines one difference between good hosting and bad.
Network redundancy is the most widely used example. The Internet is just that, an inter-connected set of networks. Between and within networks are paths that make possible page requests, file transfers and data movement from one spot (called a 'node') to the next. If you have two or more paths between a user's computer and the server, one becoming unavailable is not much of a problem. Closing one street is not so bad, if you can drive down another just as easily.
Of course, there's the catch: 'just as easily'. When one path fails, the total load (the amount of data requested and by how many within what time frame) doesn't change. Now the same number of 'cars' are using fewer 'roads'. That can lead to traffic jams.
A very different, but related, phenomenon occurs when there suddenly become more 'cars', as happens in a massively widespread virus attack, for example. Then, a large number of useless and destructive programs are running around flooding the network. Making the situation worse, at a certain point, parts of the networks may shut down to prevent further spread, producing more 'cars' on now-fewer 'roads'.
A related form of redundancy and failover can be carried out with servers, which are in essence the 'end-nodes' of a network path.
Servers can fail because of a hard drive failure, motherboard overheating, memory malfunction, operating system bug, web server software overload or any of a hundred other causes. Whatever the cause, when two or more servers are configured so that another can take up the slack from one that's failed, that is redundancy.
That is more difficult to achieve than network redundancy, but it is still very common. Not as common as it should be, since many times a failed server is just re-booted or replaced or repaired with another piece of hardware. But, more sophisticated web hosting companies will have such redundancy in place.
And that's one lesson for anyone considering which web hosting company may offer superior service over another (similarly priced) company. Look at which company can offer competent assistance when things fail, as they always do sooner or later.
One company may have a habit of simply re-booting. Others may have redundant disk arrays. Hardware containing multiple disk drives to which the server has access allows for one or more drives to fail without bringing the system down. The failed drive is replaced and no one but the administrator is even aware there was a problem.
Still other companies may have still more sophisticated systems in place. Failover servers that take up the load of a crashed computer, without the end-user seeing anything are possible. In fact, in better installations, they're the norm. When they're in place, the user has at most only to refresh his or her browser and, bingo, everything is fine.
The more a web site owner knows about redundancy and failover, the better he or she can understand why things go wrong, and what options are available when they do. That knowledge can lead to better choices for a better web site experience.
Web Hosting - Databases, What Are They and Do You Need One? 'Database' is one of the most commonly used terms that one encounters in web site design. Yet, what they really are and whether they're essential is often not clear to novices. A database is a collection of organized data, stored in files that have a specific structure. It's that organization and structure that allows for easy and rapid storage and retrieval. The need for a database generally only arises when you have a certain amount of information and that information needs to have some structure. If you have a half-dozen names and addresses to store, a database is usually overkill. If you have a blob of data with no relationships between any of the items in that blob, maintaining a database is usually more trouble than it's worth. Maintain a database? Yes, like other complex systems a database, to be effective, needs to be designed properly at the outset then kept 'tuned' for good performance. The alternative is to gradually allow the database to become more and more disorganized. That leads to difficulty in use, poor speed of retrieval and more frequent failures. With MySQL, Access or MS SQL Server, the three most common choices of database product for web sites today, setting up a database is relatively simple. Even those with limited technical skill can get one up and running just by following some simple instructions. But some thought should be given to how you want the information organized, and to maintaining the system during its lifetime. Suppose you have a set of names, addresses, email addresses, products purchased, date purchased and amount. If you have only a few dozen records it matters very little how these pieces are arranged and related. A database usually isn't even warranted in this scenario. Once you have several thousand or more records, it matters a lot. Speed, the ease of expanding the set of attributes (like adding, say, product category), and other issues come into play. Even those with little technical expertise, but a willingness to exert logical thought and invest some time, can build a very robust database. Think about how you would organize a set of data (called 'tables'). Should Name, Address, and Product be in the same table? Or should the personal information be stored in one table and any product information (product, price, ...) in another? Some experimentation may be needed to get it right, but the choices have an impact on how easy the tables are to maintain. It also affects the speed with which programs can fetch old data and store the new. Having a database also introduces new maintenance issues for the server administrator, since backups usually need to be done differently. Recovering a failed database is usually more complicated than simply re-copying files from yesterday. Ask your hosting company what tools and skills they have for dealing with any database system you consider. It's true that introducing a database creates more complexity and the need for additional thought and administrative effort. At a certain level, professional expertise will be needed. But clearly the advantages outweigh the costs in many cases. Companies large and small eventually use databases to store and organize data. At some point, you may be fortunate enough to be one of them. Get Noticed at your Job by Doing it with Flair Doing your job with “37 pieces of flair” may have entered the pop culture vernacular through the famous movie about life working an office, Office Space, but there may just be something to it. You might not need 37 pieces of flair, but doing your job with a little bit of flair and a lot of hard work is a great way to get noticed in the office and to move on to bigger and better things. How do you go about doing your job with flair? The first way to make sure you are doing your job with distinction doesn’t involve much flair at all – it simply involves doing your job and doing it well. Know exactly what your responsibilities are and attend to them every day. Don’t let any of the things that come under your job description fall by the wayside because you think they are unimportant. If you are unsure exactly what all of your responsibilities are, ask your boss for a meeting and discuss your job description with them. You will get noticed simply for your desire to make sure you are covering all of your bases and not letting any of your responsibilities fall by the wayside. Another way to do your job with flair is to add to the good morale in the office. Everyone has at least one person in the office that is like a black cloud hanging in the air. Gloom, doom and pessimism don’t really have a place in the office. Even if you feel like you are heading for a fall with the way a certain project is coming together or because someone on the team is not pulling their weight, look for solutions instead of standing around and complaining about it. When your attitude can help people stay on track with their work and not dread coming into the office every day, you are bound to get noticed. If you really want to add some flair to your work performance, learn how to manage your time and avoid procrastination. Time management is one of the biggest problems all employees face, and when you don’t manage your time efficiently, you are not being as productive as possible for your boss, which never wins you any fans among the management team. If you find yourself always rushing through your work at the last minute trying to meet your deadline, try keeping a journal of all of your activities at work for a few days. When you see how much time you spending doing things like talking with co-workers by the water cooler and surfing the net, you might see ways you can improve your work habits, so you can get things done well before the deadline is pressing down on you. Increasing your productivity by managing your time is a surefire way to earn some praise from the people over your head. Another way to add flair to your work performance is by being a team player. It can be tempting to thing that to have flair you have to go out on a limb and try to do everything yourself, but that is not the case. Employers don’t like to see an employee trying to hog credit for things that everyone has worked on together or trying to one up everyone else on the staff. When you work together with the team, you show your employer that your interests are with making the company a success and not trying to advance you own personal agenda. If your employer understands that you see the bigger picture of making the company succeed, you are sure to get noticed and rewarded. |