![]() As a vestige of an older, more open internet era, you don't have to pay to get a premium experience. In addition to that must-have, I required all the apps on this list to be:įree. They're all polished, easy to use, and put the content you want to read front and center. Thankfully, as it's a decades-old standard, there are a few great apps that have thoroughly cracked this problem. You don't want to have to deal with weird UI quirks or even really interact with your reader app-it's all about seamlessly mainlining as much high-quality content as possible. Good RSS services have a weirdly challenging job: they have to gather content from loads of different places and display it for you, all while getting out of the way as much as possible. It means I don't have to constantly check and see if Derek Sivers or Tynan has published a new post-it just pops up in my feeds. I follow a few dozen tech sites, but it's also really great for following blogs that only publish a few times a year. For more details on our process, read the full rundown of how we select apps to feature on the Zapier blog.Īs a tech writer, I rely on my RSS app to keep me up to date on what's going on. We're never paid for placement in our articles from any app or for links to any site-we value the trust readers put in us to offer authentic evaluations of the categories and apps we review. We spend dozens of hours researching and testing apps, using each app as it's intended to be used and evaluating it against the criteria we set for the category. Detailed monitoring was crucial in this, keeping track of disk, CPU and memory usage, slow database queries, handler details in MySQL, etc.All of our best apps roundups are written by humans who've spent much of their careers using, testing, and writing about software. With a loose methodology for locating problems, the analysis became very easy. The greatest challenge was finding the most efficient ways to locate hotspots and bottlenecks in the application.Profile your code, usually only needed on hard-to-find leaks.Helps keep crushing queries out of the system. Know your DB workload, Cacti really helps with this.They plan on moving to active-active model in the future. They have two sites in primary and secondary roles (active-passive) as their geographical redundancy plan.Create custom solution to download feeds to remote servers. Too much hardware, didn't like having half the hardware going to waste, and needed a really fast connection between data centers. Needed a disaster recovery/secondary site. Using a primary and slave there's a single point of failure because it's hard to promote a slave to a master. Scalability Problem 7: Master DB Failure.Move hottest tables/queries to own clusters. Went to horizontal partitioning: ad serving, flare serving, circulation. Added more stats tracking for ads, items, and circulation. Scalability Problem 6: Stats writes, again.Turned to batch processing, doing the rollups once a night. When stats get rolled up on demand popular feeds slowed down the whol system Scalability Problem 5: Lazy initialization.RAM on the machines, memcached, and in the database Everything slowed down, was using the database has cache, used MyISAM Scalability Problem 4: Total DB overload.Scalability Problem 3: Primary DB overload.Only stats for today are calculated in real-time. Used Doug Lea’s concurrency library to do updates in multiple threads. Every hit is recorded which slows everything down because of table level locks. Scalability Problem 2: Stats recording/mgmt.Using these tools you can look at uptime and performance to identify performance problems. Health Check all the way back to the database that is monitored by load balancers to route requests in to live machines on failure. Single-server failure, seen by 1/3 of all users Scalability Problem 1: Plain old reliability.Currently: 250 Mbps bandwidth usage, 310 million feed views per day, 100 Million hits per day ![]() ![]() April 2005: 5Mbps, 47,700 feeds, 6 app servers, 6 web servers (same machines) July 2004: 300Kbps, 5,600 feeds, 3 app servers, 3 web servers 2 DB servers, Round Robin DNS 11 million subscribers in 190 countries.FeedBurner is growing faster than MySpace and Digg with 385% traffic growth.Load balancing: NetScaler Application Switches.What the Web’s most popular sites are running on.FeedBurner - Scalable Web Applications using MySQL and Java.Services provided to publishers include traffic analysis and an optional advertising system. FeedBurner provides custom RSS feeds and management tools to bloggers, podcasters, and other web-based content publishers. ![]() FeedBurner is a news feed management provider launched in 2004. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |