I’m starting to think about the final deployment of WAMP applications built with Crossbar + Autobahn|Python. I’ve also read the info I could find on WAMPlets.
In my case, the application will consist of ~10 components. During development, some of them are guests (simulators for various hardware devices), but in production I think it will be 100% native containers.
- In the votegame example README.md, it says “A WAMPlet can be thought of a reusable application component that can be deployed dynamically as needed.”. In what way are WAMPlets dynamically deployable? Must I not specify them statically in the Crossbar configuration? Also, the config.json presented in that example doesn’t seem to be valid if looking at the .
- What will running components as native containers currently give me, as opposed to running them as guests or even standalone scripts? Crossbar will start them for me, that’s a plus. Anything else? (Considering the management API is not finalized yet AFAIK). To me, I kind of like being able to start/stop individual components without having to bring down the entire node, which is why I’m asking.
- Just so I’m clear: If I am to go the WAMPlet route, then I would deploy my application as a regular Python distribution, and specify one autobahn.twisted.wamplet entry point for each component of my application? What benefit will deploying as WAMPlets give me? I guess the benefit right now is that I can install my application package using setuptools like as usual, instead of pointing the Crossbar configuration at some scripts that are just lying around?
I’d love to hear from people who are also starting to think about deployment, or who already have a good system set up.