• 0 Posts
  • 10 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle
  • One of the large applications I was working on had the same issue, to solve it we ended up creating multiple smaller instances and started hosting a set of related API’s in each server.

    for example read operations like list posts, comments etc could be in one server. write operations can be clusered in one server.

    Later, whichever server is getting overloaded can be split up again. In our case 20% of API’s used around 3/4th of server resources, so we split those 20% API’s in 4 large servers and kept the remaining 80% API’s in 3 small servers.

    This worked for us because the DB’s were maintained in seperate servers.

    I wonder if a quasi micro-services approach will solve the issue here.

    Edit 1: If done properly this approach can be cost effective, in some cases it might cost 10 to 20 percentage more in server costs, however it will lead to a visible improvement in performance.





  • Will pass as they lose substantial number of followers and contribute to the growing fidiverse.

    However for them, it’s not a big deal as the get the following benefit

    1. All undesirable users leave for fidiverse or other reddit alternatives.
    2. The remaining users will be tame like the users of FB, Instagram. Which destroys Reddit as we know it, but the new Sanitised Reddit will be more appealing to investors in an IPO even with less users.

    Hopefully this is a turning point and leads to the development of The real Web 3.0, federated version of Web 1.0. (The Metaverse bullshit can no longer be called Web 3.0)