<aside> 🚧 This section is still work-in-progress! Building Wonder is a Highly complex tech challenge. Soon we are going to publish more interesting insights on our architecture 😇
</aside>
[React.JS](<https://wonderme.notion.site/8249dcc2c9f34545baf1d07f569bfcab>), TypeScript, WebGL, WebRTC[NodeJS](<https://wonderme.notion.site/cb3b0212d17145c9bee8bd4b0618209e>), JavaScript, [WebRTC](<https://wonderme.notion.site/6c72f235c59a4319be033e1b107e24f7>) SFUs, Mediasoup, Twilio, service-based architecturePostgreSQL, Redis[AWS](<https://wonderme.notion.site/25457d5e5ef04ee5b55f5c2ec2d025a1>), [Kubernetes](<https://wonderme.notion.site/25457d5e5ef04ee5b55f5c2ec2d025a1>), [CI/CD](<https://wonderme.notion.site/Methodologies-Best-Practice-b27843e07a404320804100d5c0151ab2>)Gitlab<aside> 💡 Learn more:
Methodologies & Best Practice ****Hardest tech challenges Product Roadmap Engineering culture Careers & Jobs @ Wonder
</aside>
Our user base is doubling almost every month and we are now at more than half a million monthly users.
Scaling the system is a huge architectural challenge.
We're transmitting live data (video, audio, text, images) between millions of users simultaneously who meet and walk on Wonder, including real-time video processing.
How much tolerance do you have for lag, connectivity-issues, downtime or poor audio quality? Probably zero. Wonder needs to be always up-and-running and milliseconds make a huge difference to the product experience.
We're pushing the boundaries on what you can do in your browser. We're building our own backend in WebRTC cluster and are working with some world-leading experts to satisfy the highest performance standards in relatively new technology.
Our Frontend is built with React.JS
While users move around Wonder, we're rendering the space in WebGL.
Continue exploring?
Engineering culture Product Roadmap Hardest tech challenges Careers & Jobs @ Wonder