AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Share desktop jitsi meet12/11/2023 When I looked at the possible solution, I came up with 3 (open-source) possibilities: The candidates for the conferencing solution The low cost was part of the needs (as usual…).īut there is no specific need for call quality, specific devices or environments. Simple monitoring will be used to check health, usage and system resources used. Scalability? There will not be many meetings with a high number of persons and at the beginning there will be few parallel meetings. Time to market: The solution must be available ‘now’ without having to spend weeks or months on the development part.Ĭonvenient conferencing solution: No need to be lost by the features: Just the essentials: Video + chat + screen-sharing. So only hosting will have to be considered here. And while sovereign CPaaS platforms exist in Europe that meet these requirements, they are too expensive for a startup. Without going into details, a self-hosted solution was preferred over using an existing global cloud solution as a service. Several needs were expressed for this project:ĭata protection: This is due to the specific context of the project. This article focuses on the reasons why I used Jitsi and then my development experiences. The Jitsi Architecture scheme really helped me to understand the CPaaS possibilities. Note: webRTCH4cKS already shared an excellent article on Jitsi called The ultimate guide to Jitsi Meet and JaaS that describes completely the solution. I never had the opportunity to use it as a user nor as a developer. Why ? On one hand because it is the solution I chose for a project that requires a conference server and on the other hand because it was the opportunity for me to finally discover this product and more precisely its CPaaS side. In this first article dedicated to CPaaS solutions, I wanted to focus on Jitsi Meet.
0 Comments
Read More
Leave a Reply. |