Skip to content

Instantly share code, notes, and snippets.

@axymthr
axymthr / index.js
Created January 8, 2022 10:06
csv reader node
{
"name": "csvreader-node",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1"
},
"keywords": [],
"author": "",
"""
Conversion functions for the NATO Phonetic Alphabet.
"""
# To save a lot of typing the code words are presented here
# as a dict, but feel free to change this if you'd like.
ALPHANUM_TO_NATO = {
"A": "ALFA",
"B": "BRAVO",
"C": "CHARLIE",
@axymthr
axymthr / jaeger-tracing-spring.md
Last active July 26, 2021 10:37
Distributed tracing with Spring Cloud

Spring Cloud supports OpenZipkin out of the box through Spring Cloud Sleuth https://docs.spring.io/spring-cloud-sleuth/docs/current/reference/html/project-features.html#features-zipkin

Jaeger is based on OpenTracing.

Spring Cloud Sleuth claims to support OpenTracing https://docs.spring.io/spring-cloud-sleuth/docs/current/reference/html/integrations.html#sleuth-opentracing-integration

OpenCensus and OpenTracing are merged into OpenTelemetry, but will recieve support for some time.

OpenCensus has a plain JDBC integration https://opencensus.io/integrations/sql/java_sql/

@axymthr
axymthr / micronaut-vs-springboot.md
Created May 21, 2021 08:22
Comparison points for Micronaut vs Spring Boot

Comparison between Micronaut and Spring Boot

Comparison Micronaut Spring Boot Remarks
Organization Object Computing (Grails) Spring ecosystem
Ease if use Command line tools and IDE support
Memory usage Claims lower memory consumption in general Slightly more memory usage - heap and non-heap
@axymthr
axymthr / hot-rod-helm-values.yaml
Last active April 10, 2021 16:59
Jaeger Hot R.O.D k8s deployment extracted from Helm chart since there is nothing in official docs + Traefik
# to be used with Jaeger non-operator Helm chart, enable ingress if needed
hotrod:
enabled: true
ingress:
enabled: false
@axymthr
axymthr / api-version.md
Last active March 16, 2021 19:17
API versioining notes

Look at current API defn guidelines

“You should not be versioning your API at all.”

Do we have a well-defined API lifecycle?