A Blog about Savory
Savory is your second brain. You save interesting articles for reading later or bookmark a useful website for later reference. You add tags to everything you save in Savory to curate your collection and make them easier to find in future.
In this post, I will share some tips and tricks for using tags in Savory. I also talk about a few related features that are coming soon.
In the last blog post, I mentioned how I use Savory as a personal knowledge-base and as a queue for my reading list, podcast playlist and watchlist. In this blog post, I cover the major tools in my productivity stack and go into some detail about how exactly Savory fits in my workflow.
My big three tools of choice are Gmail, Google Keep and Savory. Let’s dive in.
It’s been a weird year for everyone. Despite the challenges we all faced getting through this rough year, I hope the arrival of new year gives you hope. The worst is behind us.
It was a special year for Savory. This is the year I took the plunge and actually launched Savory in May 2020. I had been using Savory as my primary bookmark manager for about an year before I made things official. Launching Savory became my so-called pandemic project and I am glad I did it.
Savory is a web app to organize and manage your long reading list, bookmarks and references. Since launch in May 2020, Savory has used MongoDB Realm for its backend, which was nothing more than a lightweight wrapper over the underlying MongoDB Atlas cluster, with some custom authorization rules sprinkled on top.
The original backend design, or the lack thereof, was good enough when we were just getting started. But as the number of bookmarks grew, performance issues started showing up. Page load time shot up to double-digit seconds for me (6000+ bookmarks). This is partly because I am in India and the database is hosted on the other side of the world in Oregon, US. But one of the major self-inflicted problems with the design was that we were loading and returning all the bookmarks for a user from the database at page load. Yes, all 6000 of them in my case. Every time.
