The main thing here is that you have a fast DB layer (preferably on SSDs) with high I/O and lots of IOPS. Depending on your needs and using this will vary. RC with Mongo and MM with Postgres both use about 500MB/RAM combined (front+back end) when idle. If you will host a lot of users you will probably have to deploy a load-balanced configuration (that I will not talk about). Of course, this will depend on the number of users that you intend to serve. Resource vise both platforms are lightweight. For both of them, I have articles linked at the beginning so you can see what needs to be done and how to get them running. So in short if you are looking at a solution that will give you options to migrate your DB to almost any opensource platform out there, MM is a clear winner here.įor my personal use, this does not matter even though I don't have any other app running with MongoDB.Īs I mentioned before running these two platforms doesn't take a lot to get them up and running. There are old GitHub tickets that are talking about his topic but RC DEV side is not looking to invest time into other DB platform support at this time. RC unfortunately is working only with Mongo and there is no reference that that will change in the near or distant future. Some organizations might have issues running or using one DB over the other, so having more options is always better. This fact alone can be a tipping point for someone to choose one chat platform over the other. RC uses MongoDB as it's backend and MM, on the other hand, can work with multiple backends such as Postgres, MySQL, SQLite, MSSQL, and Maria to name the few. So getting them up and running via Docker doesn't take that long at all.Įach of them is easy to set up and requires only two docker containers, the database one and the platform itself. Well, it wins for me just because of one single thing, but then again it doesn't matter if you win by a foot or a mile right? General overviewĪs I mentioned before the main reason I am looking into these two platforms is because they can be self-hosted. Permissions - mainly the options that both platforms offer in terms of working with user permissions (class/roles)Īnother TL DR - rocket.chat wins in the end :).Desktop, mobile, and web apps/access - how each platform works with their dedicated desktop and mobile app as well as browser support.Chat, audio/video conference, file share, and screen share features - focusing in general what apps can offer in terms of usability, and performance when using these features.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |