Rafael Ponte rponte

Conhecendo e setando parâmetros da JVM

Material de suporte rápido para conhecer e setar parâmetros de JVM mais comuns relacionados a propriedades da JVM, configuração de frameworks e libs, aplicação e tuning de memória heap e metaspace, além da definição do algoritimo de GC e algumas configurações para troubleshooting.

Introdução

Todos os comandos aqui são executados via linha de comando, mas podem ser definidos na sua IDE, variável de ambiente (JAVA_OPTS) ou no seu servidor de integração contínua (CI).

Rodando uma aplicação (jar):

Modern Unix: ferramentas de linha de comando uteis

https://github.com/ibraheemdev/modern-unix

Material de estudos sobre troubleshooting

Conteúdo sobre troubleshooting em geral

Gloogle Cloud: Rate-limiting strategies and techniques

Sever-side

Even in the cases where the rate limiting is implemented entirely on the server side, the client should be engineered to react appropriately.
Decisions about failing open or failing closed are mostly relevant on the server side, but knowledge of what retry techniques the clients use on a failed request might influence your decisions made about server behavior.
In HTTP services, the most common way that services signal that they are applying rate limiting is by returning a 429 status code in the HTTP response. A 429 response can provide additional details about why the limit is applied (for example, a freemium user has a lower quota, or the system is undergoing maintenance).
Build your system with robust error handling in case some part of your rate-limiting strategy fails, and understand what users of your service will receive in those situations. [...] U

http://derekwilson.net/blog/2018/08/23/mokito-kotlin

	import com.google.common.cache.Cache;
	import com.google.common.cache.CacheBuilder;
	import org.slf4j.Logger;
	import org.slf4j.LoggerFactory;
	import javax.annotation.PostConstruct;
	import java.util.Optional;
	import java.util.concurrent.TimeUnit;

	@Component
	public class CacheStore {

	import org.slf4j.Logger;
	import org.slf4j.LoggerFactory;
	import org.springframework.dao.DataAccessException;
	import org.springframework.http.ResponseEntity;
	import org.springframework.web.bind.annotation.ExceptionHandler;
	import org.springframework.web.bind.annotation.RestControllerAdvice;
	import org.springframework.web.context.request.WebRequest;
	import java.time.LocalDateTime;
	import java.util.Map;

	@Entity
	class Proposal(
	val name: String,
	//
	@Column(columnDefinition = "binary(16)") // this works but uses a MySQL's specific type
	val customerId: UUID
	) {

	@Id
	@GeneratedValue

	[wsl2]
	memory=4GB
	swap=16GB
	localhostFowarding=true