Explore >> Select a destination
|
You are here 
|
emasquil.github.io | ||
| | | | |
tongwing.woon.sg
|
|
| | | | | ||
| | | | |
brunoscheufler.com
|
|
| | | | | Over the years plenty of tools to simplify managing your vast infrastructure and deployments emerged. Whether it was Terraform that sought to create declarative representations of cloud resources, or later on Kubernetes with its custom resource definitions (CRDs) connected to the underlying cloud platform, there were many attempts to reduce the effort of deploying completely reproducible infrastructure that evolves with your product's lifecycle.... | |
| | | | |
boyter.org
|
|
| | | | | [AI summary] This blog post compares the performance of Java and Go when processing large files, highlighting the challenges Java faces with memory-mapped files and the efficiency of Go's concurrency model. The author tests various implementations, including a Java solution with threads and queues, and finds that Go's approach is faster, though Java can be optimized with batch processing and efficient queue implementations. The post concludes that for optimal large file processing, Go is more suitable, but Java can still be competitive with the right techniques. | |
| | | | |
sookocheff.com
|
|
| | | The Kubernetes sweet-spot is running stateless microservices that can scale horizontally. By keeping state out of your application, Kubernetes can seamlessly add, remove, or restart pods to keep your service healthy and scalable. Developing a stateless application is, without question, the easiest way to ensure that your app can scale with Kubernetes. However, there are some workloads that do not run effectively in a stateless way, and for that, Kubernetes offers a few tools for developing stateful applications: leader election, StatefulSets and session affinity. | ||
