Discover and read the best of Twitter Threads about #Quarkus
Most recents (3)
#ApacheKafka has integrations with most of the languages used these days.
@alexsotob covers its integration with #Java and discusses how to provision, configure & secure an Apache Kafka cluster on a #Kubernetes cluster: bit.ly/3HN0Tqw
#InfoQ
Series Contents 👇
@alexsotob covers its integration with #Java and discusses how to provision, configure & secure an Apache Kafka cluster on a #Kubernetes cluster: bit.ly/3HN0Tqw
#InfoQ
Series Contents 👇
2/6 ➡️ Apache Kafka is a stream-processing platform for storing, consuming, and processing data streams in real-time. Learn how to produce and consume data using Kafka and Quarkus: bit.ly/3HGby6x
#ApacheKafka #Quarkus #Java
#ApacheKafka #Quarkus #Java
3/6 ➡️ The Kafka Streams project consumes real-time streams of events as they are produced, apply transformations, join streams, etc. Learn how to use Kafka Streams and Quarkus: bit.ly/3RGUbqy
#KafkaStreams #Quarkus #Java
#KafkaStreams #Quarkus #Java
Ter um blog técnico não é só escrever, exige preparação, escolha de temas, melhoria da técnica de escrita e divulgação. Eu comecei a escrever em 2017 e recomendo. Não parei, só mudei o foco nesse ano. Há coisas no forno que sairão ano que vem.
Mas antes disso tudo, comece! Escreva e avalie o que escreveu. Peça uma revisão de alguém ou mesmo uma avaliação do conteúdo. Qualquer coisa que você escrever terá uma finalidade, mesmo que seja o seu próprio aprendizado.
Não há aprendizado melhor que a escrita.
Meu único conselho é: valide o que você escreveu. Busque fontes e não apenas escreva código, mas escreva código que rodou e se possível coloque o repositório.
Meu único conselho é: valide o que você escreveu. Busque fontes e não apenas escreva código, mas escreva código que rodou e se possível coloque o repositório.
⏰ What time is it? Time for a #Mythbusters thread -- #Serverless edition!
Agreed, the term is sub-par. But hear me out, the architecture is not. Let's talk about a few common misconceptions about Serverless!
Agreed, the term is sub-par. But hear me out, the architecture is not. Let's talk about a few common misconceptions about Serverless!
1⃣ "Serverless means no servers"
There *are* servers involved, but it's not on you to run and operate them. Instead, the serverless provider is managing the platform, scaling things up (and down) as needed. Less things to take care of, billed per-use.
Myth: BUSTED!
There *are* servers involved, but it's not on you to run and operate them. Instead, the serverless provider is managing the platform, scaling things up (and down) as needed. Less things to take care of, billed per-use.
Myth: BUSTED!
2⃣ "Serverless is cheaper"
Pay-per-use makes low/medium-volume workloads really cheap. But pricing is complex: no. of requests, assigned RAM/CPU, API gateways, traffic etc. Depending on your workload (e.g. high, sustained), other options like VMs are better.
Myth: Kinda BUSTED!
Pay-per-use makes low/medium-volume workloads really cheap. But pricing is complex: no. of requests, assigned RAM/CPU, API gateways, traffic etc. Depending on your workload (e.g. high, sustained), other options like VMs are better.
Myth: Kinda BUSTED!
