Germán Goldenstein\r\nJanuary 21, 2019May 31, 2019\r\nReal Time Weekly, RTW\r\n0 Real Time Weekly #264: January 21, 2019 In this issue we’ve got a few articles and tutorials about WebRTC, SIP and Real-time development and a great article from BlogGeek.me about the role of WebAssembly in WebRTC! Do you have topics in mind that you wanna see more often? Do you want to share your tech blog posts and publish them here? Send your feedback and links! Happy Reading! @germangol Editor Serverless approach to build backend WebSocket Chat API Parag Poddar Jan 11 How to build a serverless backend WebSocket API in AWS API Gateway AWS. Socket Programming in Python: Client, Server, and Peer Examples PubNub Jan 11 How you can send data in real-time from device-to-device, client-to-server, and vice versa using socket programming in Python. What’s the Role of WebAssembly in WebRTC? Tsahi Levent-Levi, BlogGeek.me Jan 14 An overview of what is WebAssembly and how it impacts in WebRTC development. SIP Happens! And Kamailio Makes It Easy, Part I nerdvittles.com Jan 14 A tutorial of how to setup a a Debian-based Kamailio server on a cloud platform that is suitable for making thousands of free SIP phone calls. SMS In The Browser: An Adventure In WebSockets Nexmo Jan 15 How to build a “virtual” phone in the browser that can send and receive SMS via WebSockets in Node.js using Nexmo API. Upcoming Events Do you have a real-time related conference coming up? Tell us about it! Email firstname.lastname@example.org to be included in this listing. #ITEXPO Exhibitor Highlight January 29 – February 1, 2019 WebRTC Boston #6: Low-latency media & real time communications for the masses February 5, 2019 The Janus Conference for Janus Users. September 23 -25, 2019 If you know about any events worldwide please let us know emailing email@example.com. Real Time Weekly is a free service of WebRTC.ventures. If you have been forwarded this by a friend, then please sign up at RealTimeWeekly so you never miss an issue! Please send tips or suggestions to German Goldenstein, editor, firstname.lastname@example.org.