https://github.com/watson-developer-cloud/assistant-simple/c...
256 karma · joined December 28, 2019
https://github.com/watson-developer-cloud/assistant-simple/c...
https://floriantreml.medium.com/security-threats-and-securit...
We have to support multiple clouds (Azure and AWS), but with Rancher, it is really easy in usage - setting up new clusters, deploying new services, restarting, logging etc. But now that we built up container technology know-how we are transitioning every service where we don't need the scaling capabilities of Kubernetes to plain old docker-compose on baremetal.
Thanks for the interesting article, didn't know about Nomad and will try it for sure.
In our case, we are doing the same for around 50 clients, so it sums up :-)
> Who would do this and why? Why would you have a load balancer in front of a single server?
afaik, for publishing something to the outside world from EKS, that's the only way - even for single node clusters
partially our product botium is open source, thats why we have github and bitbucket.
We published the scripts in a Github repository and a blog article with instructions: https://medium.com/@floriantreml/tutorial-benchmark-your-cha...
the english is from the tedlium recipe with WER of 7%.
room for improvement, but for our original purpose it was sufficient.
We gave it a pluggable architecture to work with all relevant Conversational AI and NLP/NLU providers out there, made it DevOps- and TestOps-friendly with a CLI and bindings to most loved test runners out there (Mocha, Jest, Jasmine, ...), and still the whole stack is Open Source on Github - thanks to our awesome community and cooperations with ISVs.
Curious to hear your thoughts on the topic - clearly, testing a Conversational AI holds some special challenges for you in regards of test coverage and test levels (API vs E2E).
We gave it a pluggable architecture to work with all relevant Conversational AI and NLP/NLU providers out there, made it DevOps- and TestOps-friendly with a CLI and bindings to most loved test runners out there (Mocha, Jest, Jasmine, ...), and still the whole stack is Open Source on Github - thanks to our awesome community and cooperations with ISVs.
Curious to hear your thoughts on the topic - clearly, testing a Conversational AI holds some special challenges for you in regards of test coverage and test levels (API vs E2E).
Do you have any experience with online decoding in wav2letter ? Is there something like a Websocket API available somewhere ?
high quality with google cloud speech and amazon polly.
It basically describes the thing you mentioned - matching freely available audio books with the source text and using some tools to preprocess the data suitable for ASR training (alignment, splitting).
Of course it is not a competitor to Google in any sense.