๐Ÿ‡ช๐Ÿ‡จ ๐‘ฑ๐’‚๐’„๐’๐’ƒ๐’

7.5K posts

๐Ÿ‡ช๐Ÿ‡จ ๐‘ฑ๐’‚๐’„๐’๐’ƒ๐’ banner
๐Ÿ‡ช๐Ÿ‡จ ๐‘ฑ๐’‚๐’„๐’๐’ƒ๐’

๐Ÿ‡ช๐Ÿ‡จ ๐‘ฑ๐’‚๐’„๐’๐’ƒ๐’

@jcobjoss777

๐Ÿ“š Software Developer | Backend Engineer | Javalover #Java โ˜• | #microservicios #Spring ๐ŸŒฑ | Apasionado por la ciberseguridad ๐Ÿค– | human drummer ๐Ÿฅ| Anime

Detras de un proxy Beigetreten Kasฤฑm 2015
533 Folgt191 Follower
๐Ÿ‡ช๐Ÿ‡จ ๐‘ฑ๐’‚๐’„๐’๐’ƒ๐’ retweetet
BellSoft
BellSoft@bellsoftwareยท
One JEP worth revisiting: JEP 485 in JDK 24. It introduced gather(...) to streams, a new intermediate operation for transformations that do not fit neatly into map, filter, or flatMap. Tiny example ๐Ÿ‘‡
BellSoft tweet media
English
1
4
28
881
๐Ÿ‡ช๐Ÿ‡จ ๐‘ฑ๐’‚๐’„๐’๐’ƒ๐’ retweetet
Vivek Galatage
Vivek Galatage@vivekgalatageยท
CPU Architecture Explained by BitLemon (beginner-friendly) youtu.be/GtVDTp826DE
YouTube video
YouTube
Vivek Galatage tweet media
English
0
50
416
17.9K
๐Ÿ‡ช๐Ÿ‡จ ๐‘ฑ๐’‚๐’„๐’๐’ƒ๐’ retweetet
Yoshik K
Yoshik K@AskYoshikยท
understand the working parts of docker before moving to k8s
Yoshik K tweet media
English
1
28
185
12.7K
๐Ÿ‡ช๐Ÿ‡จ ๐‘ฑ๐’‚๐’„๐’๐’ƒ๐’ retweetet
Uday๐Ÿ‘จโ€๐Ÿ’ป
How to reduce Docker image size from 846 MB to 2.5 MB (a 99.7% reduction)๐Ÿ“š The Problem (Before): -> Single-stage Dockerfile -> Heavy base image (e.g., full Ubuntu/Debian or bloated builder like golang with all dev tools) -> Build dependencies, caches, temporary files, and unnecessary OS packages all shipped to production -> Result: 846 MB bloated image -> slow pulls, high storage costs, larger attack surface. The Solution (After) โ€“ Key Techniques Applied Step-by-Step: 1. Switch to a Lightweight Builder Base: -> Started with golang: alpine (or equivalent slim builder) instead of the full image. This alone dropped it significantly (e.g., from 846 MB to ~300 MB). 2. Multi-Stage Builds (The Game Changer): -> Stage 1 (Builder): Use a full builder image with all tools, compile the app, and produce a small binary/artifact. -> Stage 2 (Runtime): Start fresh with a tiny base like Alpine (~5 MB) or even scratch/distroless (near-zero OS). -> Only COPY the final compiled binary (and minimal runtime deps) from the builder stage. Everything else (compilers, caches, dev packages) stays behind in the builder stage and never reaches production. 3. Additional Optimizations: -> Combine RUN commands and clean up in the same layer (rm -rf /var/cache/apk/* etc.). -> Use .dockerignore to exclude tests, docs, git, node_modules, etc. from build context. -> For Go: Build with CGO_ENABLED=0 GOOS=linux for a static binary. -> Final runtime base: Minimal Alpine + only the binary -> 2.5 MB. Result: 846 MB -> 2.5 MB. Faster deploys, cheaper storage, better security.
Uday๐Ÿ‘จโ€๐Ÿ’ป tweet media
English
7
26
203
6.9K
El Programador Senior
El Programador Senior@5eniorDeveloperยท
Iniciando el dรญa con un buen cafรฉ!
El Programador Senior tweet media
Espaรฑol
6
6
133
7.2K
Alejandra Vera
Alejandra Vera@vegaalaia14ยท
Salgansรฉ de tw, quiero estar sola
Espaรฑol
7
1
24
876
Nataly Parks
Nataly Parks@Nataly_Parksยท
Cielito precioso ๐Ÿงก
Nataly Parks tweet media
Portuguรชs
4
4
131
1.6K
Nataly Parks
Nataly Parks@Nataly_Parksยท
Cuando uno no tiene nada bueno que decir, mejor se queda calladito.
Espaรฑol
1
4
41
1.6K
Sin.
Sin.@sindykiuยท
Ya lleguรฉ al lado del internet dรณnde calculan cuantas metidas de rifle le aguantas a Geto jajsajajssjaaj.
Espaรฑol
17
21
692
33.5K