gui77aume | 2 years ago | on: Testcontainers
gui77aume's comments
gui77aume | 2 years ago | on: Testcontainers
gui77aume | 2 years ago | on: Companies embracing SMS for account logins should be blamed for SIM-swap attacks
gui77aume | 2 years ago | on: AWS us-east-1 down
gui77aume | 4 years ago | on: Optimizing Docker image size and why it matters
gui77aume | 4 years ago | on: Optimizing Docker image size and why it matters
gui77aume | 4 years ago | on: Container security best practices: Ultimate guide
Do you recommend to disable CPU limit? In the general case.
gui77aume | 4 years ago | on: Container security best practices: Ultimate guide
gui77aume | 4 years ago | on: My Logging Best Practices (2020)
- Always log errors
- Don't log errors twice (log or rethrow)
gui77aume | 4 years ago | on: Temporal: Getting started with JavaScript's new date time API
gui77aume | 4 years ago | on: Behind the design of the fresh new Firefox coming June 1
gui77aume | 5 years ago | on: I use `exa` instead of `ls` on Linux
gui77aume | 5 years ago | on: I use `exa` instead of `ls` on Linux
gui77aume | 5 years ago | on: Eclipse IDE 2021-03
- Eclipse type hierarchy view (and quick view) was nice
- Google-Java-Format plugin integration was better
- The default color scheme of Eclipse was better (not sure why but I can't use a dark theme with Java)
But Eclipse had too much strange behaviors where I had to restart it and IntelliJ has those warnings/suggestion about code quality and better auto-completion IMO.
gui77aume | 5 years ago | on: Modules, Monoliths, and Microservices
We have still some monoliths, like some EARs in some Jboss on-premise but the cloud+kubernetes+microservices trend seems the obvious way to go for everybody. Those monoliths are minimally maintained, new features go to microservices, and the end goal is to throw them out, it take years though.
It is very likely than microservices are way too small IMO, I've seen microservices just doing an IF, just doing an SQL select, or just adding some credentials in a HTTP header, stuff that could work in one service are sometimes splitted in tens of microservices.
Althought these microservices are Java/Spring Boot or Node/Express ones most of the times, despite the fact that you could potentially use the best tech for each microservice, managers want to maintain a limited tech stack where they can easily find cheap developers, basically Java and Javascript, some Python or Go maybe but not so much.
What strikes me the most is that it seems to work, till now at least, each developer have to maintain like between 3 and 10 microservices, but very simple ones.
Merging two microservices into one never happens.
Writing a new microservice is almost more frequent than evolving an existing one.
Is it a worldwide trend or am I living in a particularly excessive bubble?
gui77aume | 5 years ago | on: Ask HN: What low-code “dashboarding“ SaaS would you recommend in 2021?
gui77aume | 5 years ago | on: Show HN: Bunkerized-Nginx – Nginx Docker image secure by default
gui77aume | 5 years ago | on: Show HN: Bunkerized-Nginx – Nginx Docker image secure by default
gui77aume | 6 years ago | on: Guide to running Elasticsearch in production
gui77aume | 8 years ago | on: Would you use JSF for your next project?