News for hackers. Stuff that matters.

ftreml

partially agree. In another repo, the same vulnerability was only fixed after years ...

https://github.com/watson-developer-cloud/assistant-simple/c...

We are using JavaScript for our SaaS-Backend

For our SaaS-product Botium Box - a full functional and non-functional testing infrastructure for chatbot - we decided to go for Node.js in the backend. ... The one single argument why we decided for Node.js was that in our small developer team (4 people) everyone is a full-stack-developer, and it will ultimately safe time to develop client and server in the same programming language.

( Read More... | 1 comment | 5 points | on HN )
Re:Ask HN: Showing the HN ranking history of an article? on Thursday January 21, 2021 @03:23PM (#25863727)
awesome, many thanks!
Re:We Are Saving Costs by Dumping AWS Cloud on Thursday January 21, 2021 @02:54PM (#25863362)
We built a software (Botium Box - https://botium.ai) mainly for On-Premise use, and we delivered as Kubernetes, Openshift, Docker. We added a hosted plan later and thought it would be a good idea to just use managed Kubernetes for this offer as it didn't require much coding changes.

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.

Re:We Are Saving Costs by Dumping AWS Cloud on Thursday January 21, 2021 @01:49PM (#25862471)
sure, that's a good point. and scaling a one-node-cluster to a multi-node-cluster is also nearly no effort on AWS. but for the topics where we can predict the computing power for the next months, we migrated everything to baremetal.
Re:We Are Saving Costs by Dumping AWS Cloud on Thursday January 21, 2021 @01:47PM (#25862439)
fully agree - that's how we started - getting some servers up and running is quick and easy, but as soon as you can foresee what computer power you will need in the next months and years, baremetal is surely the better choice. If you can deal with the technical stuff, of course.
Re:We Are Saving Costs by Dumping AWS Cloud on Thursday January 21, 2021 @01:44PM (#25862386)
> The only people who are optimizing for three-figure costs every month are either:

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

Re:We Are Saving Costs by Dumping AWS Cloud on Thursday January 21, 2021 @12:22PM (#25861401)
thanks for this valuable input

We Are Saving Costs by Dumping AWS Cloud

Amazon is using the same trick with AWS pricing as cellphone providers: they rely on bad math capabilities of their clients. The costs for one single item, in the case of AWS this is one hour of computing, is incredibly low, parts of a cent - but most people out there are not able to do simple maths like multiplication (by 720, the number of hours in a month) or summation (with the costs of the...

( Read More... | 23 comments | 20 points | on HN )
Re:Clubhouse Sucks and That's the Reason on Thursday January 21, 2021 @10:30AM (#25859866)
nobody asks how to make money if you already have a hell lot of money and a growth rate like clubhouse. there is plenty of venture money available, more that can be spent.

Clubhouse Sucks and That's the Reason

Clubhouse is a one-trick pony: by following the scarcity principle on multiple levels (iPhone-only, invite-only, audio-only, ...) it creates the feeling of superiority for the ones who are in the position to join the exclusive circle. That's it.

( Read More... | 2 comments | 10 points | on HN )
After several months of beta test we now published Botium Speech Processing version 1.0.0. It was proven to work in several client-specific speech processing tasks, mainly related to automated testing of voice interfaces.
Re:A two-person startup already uses twenty-eight other tools on Saturday February 29, 2020 @02:41AM (#22449493)
gsuite, hubspot, github, jira, bitbucket, confluence, codeship, vs code, slack, discord

partially our product botium is open source, thats why we have github and bitbucket.

same here
Re:Machine Learning and Node.js, is this a match? [video] on Saturday February 01, 2020 @06:12AM (#22209928)
Personally, when using node.js i am a little bit envious on python, for pandas, sklearn, keras.
Re:Show HN: Voice Synthesis and Editing Platform on Saturday February 01, 2020 @06:03AM (#22209897)
hi, from your point of view, how does this compare to amazon polly snd google cloud speech ?

Show HN: Community Updates for Open-Source Speech-to-Text and Text-to-Speech

Following up to the latest discussions on Hackernews together with this awesome community we pushed several updates to Github. Botium Speech Processing is now using way better pre-trained modesl from the Zamia Speech project and has an option to watch a file system folder for running text-to-speech and speech-to-text recipies.https://github.com/codeforequity-at/botium-speech-processing

( Read More... | 1 comment | 3 points | on HN )
Recently we had to evaluate if chatbot we built for an Austrian telecommunication provider would perform better on other NLP engines than the one we had in use (a cloud-based one). We took the training data and calculated common performance metrics, confusion matrices and accuracy scores for a bunch of the blockbuster providers (IBM Watson, Google Dialogflow, Amazon Lex, Microsoft LUIS, Rasa and some more).

We published the scripts in a Github repository and a blog article with instructions: https://medium.com/@floriantreml/tutorial-benchmark-your-cha...

Older »