We are going to do some Integration work, that may include Azure functions, servicebus, micro services and other stuff.
We are creating some POCs for that and had a discussion about what approach to use. I have worked with multi repos and not so sure if Mono repo would be better. As most of the components that we will be creating will be interdependent.
sounds similar to our setup. my advice is be thoughtful how you are creating new micro services, be thoughtful with servicebus (as the SLA on the cheap tier is not great), and be thoughtful with azure functions! Can get out of hand - both in cost and productivity issues - quickly.
We have a guy on our team who loves the shiny new thing, but lots of times you can get it working in a much easier, more understandable way.
For azure functions, a separate repo may make sense. I would probably do that, but I also suggest not putting much logic at all in the azure functions. For example, this:
- When the function is executed, drop a document here
- ... write this db record
- ... execute some job somewhere ...
- ... call an API ...
Is a good use of azure functions. Keep it "functional!"
Bad uses are "systems" implemented in Azure functions. As soon as you feel like you need to use or even MIGHT need to use code in your main codebase, please, don't use azure functions! :)
WebRTC. Specifically Google's libWebRTC for Android/iOS mobile platforms [1]. All the major web browsers (including Safari 11+) support WebRTC. For the server, I am interested in trying Jangouts (Janus Hangouts) [2].
