Avoid machine learning mistakes and boost model performance! Discover key ML patterns, anti-patterns, data strategies, and more.
Releasing software shouldn't be stressful or risky. Learn how to leverage progressive delivery techniques to ensure safer deployments.
CORE
CEO at RJ Technology
Ravno Pole, BG
Joined Dec 2013
Stats
| Reputation: | 632 |
| Pageviews: | 79.7K |
| Articles: | 3 |
| Comments: | 3 |
Comments
May 27, 2020 · Triphon Penakov
I've changed the native build to go through Docker.
You can find the detailed instructions here.
I should update accordingly and the article.
Please let me know if you face any other troubles :)
Dec 03, 2019 · Triphon Penakov
This was an internal microservice - protected by AWS Security Group Rules. No needs for security there.
Dec 01, 2019 · Triphon Penakov
Thank you! AFAIK - for the moment Quarkus is with the smallest resource consuming footprint - even for the JVM applications. If you include in addition the compilation to the native code with GraalVM in the equation - the comparation becomes pretty useless :) Currently (because ot the smallest footpring) when I start a brand new project - I am using Quarkus. So it was a logical step to migrate this legacy microservice to it. As for the Eureka client - it is just a REST API and you have to implement only two calls. You can use it as a library from here: https://github.com/tpenakov/otaibe-commons-quarkus . Also there is another implementation for Eureka client - you can find more details in the initial Quarkus task (https://github.com/quarkusio/quarkus/issues/2052)