Elias Nogueira ๐Ÿ‡ง๐Ÿ‡ท๐Ÿ‡ณ๐Ÿ‡ฑ

@eliasnogueira.com

Java Champion | Senior Principal Software Engineer | Speaker | Writer | Oracle ACE | Java Magazine NL | OSS

Testing distributed systems is not about more tests โ€” itโ€™s about better signals. I gave this talk at InfoQ Dev Summit Boston sharing practical strategies for realistic, fast, and reliable testing in complex architectures. ๐ŸŽฅ Watch the talk or read its transcript.

Test Smarter, Not Harder: Achieving Confidence in Complex Distributed Systems

Elias Nogueira shares a strategic approach to modern microservice testing, detailing solutions for three core challenges. He discusses parallel execution for multiple databases using Testcontainers,โ€ฆ

infoq.com

๐Ÿ› ๏ธ ๐“๐ž๐ฌ๐ญ๐ข๐ง๐  #๐ƒ๐ข๐ฌ๐ญ๐ซ๐ข๐›๐ฎ๐ญ๐ž๐๐’๐ฒ๐ฌ๐ญ๐ž๐ฆ๐ฌ ๐๐จ๐ž๐ฌ๐ง'๐ญ ๐ก๐š๐ฏ๐ž ๐ญ๐จ ๐›๐ž ๐Ÿ๐ซ๐š๐ ๐ข๐ฅ๐ž! @eliasnogueira.com explains how to build ๐ฌ๐ญ๐š๐›๐ฅ๐ž, ๐Ÿ๐š๐ฌ๐ญ & ๐ฌ๐œ๐š๐ฅ๐š๐›๐ฅ๐ž ๐ญ๐ž๐ฌ๐ญ๐ฌ using techniques like ๐ฌ๐ž๐ซ๐ฏ๐ข๐œ๐ž ๐ฏ๐ข๐ซ๐ญ๐ฎ๐š๐ฅ๐ข๐ณ๐š๐ญ๐ข๐จ๐ง & ๐š๐ฌ๐ฒ๐ง๐œ-๐š๐ฐ๐š๐ซ๐ž ๐ญ๐ž๐ฌ๐ญ ๐Ÿ๐ซ๐š๐ฆ๐ž๐ฐ๐จ๐ซ๐ค๐ฌ. ๐ŸŽฅ Watch the #InfoQ video: bit.ly/4mQRzp8 #SoftwareTesting #SoftwareEngineering

Bild

๐Ÿ‡ง๐Ÿ‡ท Gravei um episรณdio do Tech Leadership Rocks com o Eduardo Matos ๐ŸŽ™๏ธ Conversamos sobre como testar microsserviรงos, um dos maiores desafios para garantir qualidade e confianรงa em sistemas modernos. Obrigado, Eduardo, pela oportunidade de compartilhar essa discussรฃo! ๐Ÿ”—

Como testar microsserviรงos com Elias Nogueira โ€ข Tech Leadership Rocks

Como testar microsserviรงos com Elias Nogueira

escolaforja.com.br

No, because if I have a library that is feature complete, this would force me to create a release per year, because people will think the library is outdated. One of my customers uses that to force his customers to update to the newest version.

I like CalVer whenever versions become a point of discussion; it's hard to argue to continue to use 2019.08 today, whereas 1.5 hides that nuance of using outdated technology. Breaking changes with SemVer are a solved problem when you use the right technology! ;)