If you run a blog or a website, chances are that you want to make it easier for people to bookmark you website. Here is a nice little page with list of APIs to help you generate those links for your website.
Large distributed systems run into a problem which smaller systems donâ€™t usually have to worry about. â€œ Brewers CAP Theorem â€ [ Ref 1 ] [ Ref 2 ] [ Ref 3 ] defines this problem in a very simple way. It states, that though its desirable to have Consistency, High-Availability and Partition-tolerance in every system, unfortunately no system can achieve all three at the same time . C onsistent : A fully Consistent system is one where the system can guarantee that once you store a state (lets say â€œx=yâ€) in the system, it will report the same state in every subsequent operation until the state is explicitly changed by something outside the system. [ Example 1 ] A single MySQL database instance is automatically fully consistent since there is only one node keeping the state. [ Example 2 ] If two MySQL servers are involved, and if the system is designed in such a way that all keys starting â€œaâ€ to â€œmâ€ is kept on server 1, and keys â€œnâ€ to â€œzâ€ are kept on server
Introduction Loadbalancing may mean many different things to different people but its all about distributing load. For me its an architecture of how some network services can be scaled by adding multiple servers performing the same tasks. If you had a popular website with static content, and if your server couldn't keep up with the request, all you had to do was setup multiple web servers and use round-robin DNS entries to divide the load into multiple servers. For dynamic web applications like search engines this plays a significant role because the number of users per node can support is much lower. Over time, as applications grew more complex and as web companies found customers outside US they found out the hardware that the only way to optimize network performance was by going local. Loadbalancing POP (points of presence) around the world provide a snappy user experience which has been important and drawing more customers. While, static content on web servers can easily be rep
Most people prefer to disagree with the masses on whether they like sunny side up or scrambled eggs. And the form of getting patches is no different. If you ask an IT administrator (which is the person applying patches in most corporate organizations) they will tell you horror stories of how patches can go wrong and would be happy to give you examples of why every patch needs to be individually tested before deploying. But my dad, for example, doesn't care about patches, and while he won't go out of the way to install a patch, he may be ok with patches being pushed to him automatically. This debate reminds me of another interesting debate in the Web-Operations world about " continuous deployment ". In that case the debate was whether applications should be deployed in scheduled releases (for example every quarter) or whether it should be released as things gets developed and pushed. If you think about this a little more it would be very clear that the developers