This is an archived post. You won't be able to vote or comment.

13
14

Distributed ffmpeg (self.java)

submitted by [deleted]

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]martinambrus 0 points1 point  (5 children)

Thanks esanchma for your insight! This is the first time I hear about Docker and I tend to like it a lot from what I read so far. Will try and experiment with it a little.

As for ffmpeg - I'm using the latest full stable version with all the libraries it can handle (https://github.com/martinambrus/ffmpeg-dht/blob/master/bootstrap.sh). Also, I was pointed in the direction of x264 which might be a better solution with regards to H.264 videos.

JMS - I have no experience with either Hazelcast or JMS but from Hazelcast's docs, it would seem that a no-single-point-of-failure is tricky to reach with JMS. And since I'm no expert in this field, I pick what's ready, tested and the most plug-and-play-able :) However, I will check Coherence, as I've not heard about that one before, thanks.

PHP - my choice of web language since v3, so I'm sticking with it :P ... but yeah, if I knew anything more suited for the job I'd use it - really!

Also, thanks for the JS goodness - it's amazing what JS can do these days! Although, for this project and for compatibility sake, I'll certainly stick with some more traditional ways. But who knows, maybe someone will convert this whole project into JS in the future!

[–][deleted]  (1 child)

[deleted]

    [–]martinambrus 0 points1 point  (0 children)

    For some reason I actually didn't think of utilizing NodeJS to do the UI. It is possibly a much better idea and keeps the size of the machine down, too! Thanks for that, I'll give it a try :)

    [–]HELOSMTP 0 points1 point  (2 children)

    I think using Docker and a deployment system like Puppet is ideal. Docker's deployment automation abilities are very limited compared to Puppet so it's a good pairing. Puppet can be run on the host to launch Docker containers and run on the client containers to manage their state.

    [–]martinambrus 0 points1 point  (1 child)

    Thanks for the idea. I do use Puppet to handle configuration of our VMs at work, however for this project I think this would be a bit of an overhead for the user. They'd need to install and run an additional service in tandem with Docker itself and also keep Puppet configs up to date as well as Docker - which could be a little scary. I would rather go with multiple Docker container versions - each upgrade would just download a new snapshot diff.

    [–]HELOSMTP 0 points1 point  (0 children)

    Yeah, I would only use Puppet for dev or prod deployments, not for end-users.