Lambros Petrou lambrospetrou

## DOCKERFILE
FROM golang:1.21.0-bullseye as builder

COPY . /workdir
WORKDIR /workdir

ENV CGO_CPPFLAGS="-D_FORTIFY_SOURCE=2 -fstack-protector-all"
ENV GOFLAGS="-buildmode=pie"

RUN go build -ldflags "-s -w" -trimpath ./cmd/app

## akka-and-kotlin-coroutines.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              12 stars
            
          
                joost-de-vries
                / akka-and-kotlin-coroutines.md
            
            
              Last active
              February 27, 2024 07:00
            
              
                Akka and kotlin coroutines
              
          
    Akka and Kotlin coroutines: ♡

I've experimented with Kotlin and coroutines in programming Akka. And I must say, I really like the combination so far.

But before I go into it some brief preliminaries for those who don't know Akka and actors.
Actors and Akka

Actors are a programming model that fits cloud native architectures particularly well. Being highly available and scaling horizontally. All while embracing the realities of multiple servers collaborating, server instances coming and going and the network having hickups.
On the JVM Akka is the prominent actor framework. It's been around for a while now and as a result it's highly reliable, well thought out and offers a wide programming eco system. My own interest in Akka is because of its suitability for software systems that can only be built with business events as a key construct and thinking model.
And then of course materialized views, CQRS and near real-time data streams play a big role in constructing those systems.

  
## build.sh
#!/usr/bin/env bash

cd $(dirname $0)

docker run --rm -it -v "$(pwd)":/home/rust/src -v cargo-git:/home/rust/.cargo/git -v cargo-registry:/home/rust/.cargo/registry -v "$(pwd)/target/":/home/rust/src/target ekidd/rust-musl-builder:nightly-2021-01-01 sudo chown -R rust:rust /home/rust/.cargo/git /home/rust/.cargo/registry /home/rust/src/target

docker run --rm -it -v "$(pwd)":/home/rust/src -v cargo-git:/home/rust/.cargo/git -v cargo-registry:/home/rust/.cargo/registry -v "$(pwd)/target/":/home/rust/src/target ekidd/rust-musl-builder:nightly-2021-01-01 cargo build --release

## foo.service
[Unit]
Description = Foo HTTP server
Requires    = foo.socket
After       = multi-user.target

[Service]
User             = www-data
Group            = www-data
WorkingDirectory = /var/foo
ExecStart        = /var/foo/bin/foo-server

## microweb.cljs
(set! *warn-on-infer* true)

(def ^js wifi (js/require "Wifi"))
(def ^js http (js/require "http"))

(def n (atom 0))

(defn build-response []
  (str
   "<html>"

## index.md

      
              1 file
            
          
              35 forks
            
          
              46 comments
            
          
              271 stars
            
          
                bvaughn
                / index.md
            
            
              Last active
              April 19, 2024 04:34
            
              
                How to use profiling in production mode for react-dom 
              
          
    React recently introduced an experimental profiler API. This page gives instructions on how to use this API in a production release of your app.
Table of Contents

Profiling in production

Create React App
Webpack 4


Profiling in production

React DOM automatically supports profiling in development mode for v16.5+, but since profiling adds some small additional overhead it is opt-in for production mode. This gist explains how to opt-in.

  
## cljs-serverless.md

      
              1 file
            
          
              3 forks
            
          
              2 comments
            
          
              7 stars
            
          
                lilactown
                / cljs-serverless.md
            
            
              Last active
              January 27, 2020 05:06
            
              
                CLJS in AWS Lambda Quick Start
              
          
    CLJS in AWS Lambda Quick Start

Setup

First, a few dependencies:

Leiningen: https://leiningen.org/
Node.js & NPM: https://nodejs.org/
Serverless: https://serverless.com/
An active AWS account: https://aws.amazon.com/


## test.clj
(ns dynamic.test
  (:require [clojure.test :refer :all]))

;; This example shows how tests can be generated dynamically, by
;; creating new vars with the correct metadata.

(defn add-test
  "Add a test to the given namespace. The body of the test is given as
  the thunk test-fn. Useful for adding dynamically generated deftests."
  [name ns test-fn & [metadata]]

## System Design.md

      
              1 file
            
          
              2603 forks
            
          
              58 comments
            
          
              9386 stars
            
          
                vasanthk
                / System Design.md
            
            
              Last active
              April 26, 2024 13:40
            
              
                System Design Cheatsheet
              
          
    System Design Cheatsheet


Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps


Clarify and agree on the scope of the system


User cases (description of sequences of events that, taken together, lead to a system doing something useful)

Who is going to use it?
How are they going to use it?


## slim-redux.js
function mapValues(obj, fn) {
  return Object.keys(obj).reduce((result, key) => {
    result[key] = fn(obj[key], key);
    return result;
  }, {});
}

function pick(obj, fn) {
  return Object.keys(obj).reduce((result, key) => {
    if (fn(obj[key])) {
	FROM golang:1.21.0-bullseye as builder

	COPY . /workdir
	WORKDIR /workdir

	ENV CGO_CPPFLAGS="-D_FORTIFY_SOURCE=2 -fstack-protector-all"
	ENV GOFLAGS="-buildmode=pie"

	RUN go build -ldflags "-s -w" -trimpath ./cmd/app
	#!/usr/bin/env bash

	cd $(dirname $0)

	docker run --rm -it -v "$(pwd)":/home/rust/src -v cargo-git:/home/rust/.cargo/git -v cargo-registry:/home/rust/.cargo/registry -v "$(pwd)/target/":/home/rust/src/target ekidd/rust-musl-builder:nightly-2021-01-01 sudo chown -R rust:rust /home/rust/.cargo/git /home/rust/.cargo/registry /home/rust/src/target

	docker run --rm -it -v "$(pwd)":/home/rust/src -v cargo-git:/home/rust/.cargo/git -v cargo-registry:/home/rust/.cargo/registry -v "$(pwd)/target/":/home/rust/src/target ekidd/rust-musl-builder:nightly-2021-01-01 cargo build --release
	[Unit]
	Description = Foo HTTP server
	Requires = foo.socket
	After = multi-user.target

	[Service]
	User = www-data
	Group = www-data
	WorkingDirectory = /var/foo
	ExecStart = /var/foo/bin/foo-server
	(set! warn-on-infer true)

	(def ^js wifi (js/require "Wifi"))
	(def ^js http (js/require "http"))

	(def n (atom 0))

	(defn build-response []
	(str
	"<html>"
	(ns dynamic.test
	(:require [clojure.test :refer :all]))

	;; This example shows how tests can be generated dynamically, by
	;; creating new vars with the correct metadata.

	(defn add-test
	"Add a test to the given namespace. The body of the test is given as
	the thunk test-fn. Useful for adding dynamically generated deftests."
	[name ns test-fn & [metadata]]
	function mapValues(obj, fn) {
	return Object.keys(obj).reduce((result, key) => {
	result[key] = fn(obj[key], key);
	return result;
	}, {});
	}

	function pick(obj, fn) {
	return Object.keys(obj).reduce((result, key) => {
	if (fn(obj[key])) {