🇪🇨 𝑱𝒂𝒄𝒐𝒃𝒐

7.5K posts

🇪🇨 𝑱𝒂𝒄𝒐𝒃𝒐 banner
🇪🇨 𝑱𝒂𝒄𝒐𝒃𝒐

🇪🇨 𝑱𝒂𝒄𝒐𝒃𝒐

@jcobjoss777

📚 Software Developer | Backend Engineer | Javalover #Java ☕ | #microservicios #Spring 🌱 | Apasionado por la ciberseguridad 🤖 | human drummer 🥁| Anime

Detras de un proxy เข้าร่วม Kasım 2015
533 กำลังติดตาม191 ผู้ติดตาม
🇪🇨 𝑱𝒂𝒄𝒐𝒃𝒐 รีทวีตแล้ว
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
0
2
24
738
🇪🇨 𝑱𝒂𝒄𝒐𝒃𝒐 รีทวีตแล้ว
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
411
16.9K
🇪🇨 𝑱𝒂𝒄𝒐𝒃𝒐 รีทวีตแล้ว
Yoshik K
Yoshik K@AskYoshik·
understand the working parts of docker before moving to k8s
Yoshik K tweet media
English
1
28
184
12.2K
🇪🇨 𝑱𝒂𝒄𝒐𝒃𝒐 รีทวีตแล้ว
Uday👨‍💻
Uday👨‍💻@uday_devops·
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.8K
🇪🇨 𝑱𝒂𝒄𝒐𝒃𝒐
Lo único que se me a dado elegir bien, es el lenguaje de programación del resto, puras malas elecciones incluyendo las del amor xd
Español
0
0
0
11
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
691
33.5K