With this kind of power, could a browser compile and run your code too? Ridiculous. Surely that couldn’t work…
Then again, why not? There’s no way I could ignore such a fascinating challenge. After four months of punching the keys and poring over documentation, I’ve finally created my answer: Go Wasm.
Go Wasm is a Go development environment with the essentials to write and run code entirely within the browser…
Starting at the end of last year, we put a plan in motion to revamp the CLI for the IBM Cloud Kubernetes Service. We focused on improving the user experience and overhauling the code. The key is to break compatibility, but surprise no one.
We had several problems with the CLI after a few years of adding new features. They ranged from user experience issues to technical debt buildup:
Web services running on the same network can be difficult to set up correctly, especially if you want all of them to work on an external network.
In this tutorial, I will guide you through setting up a Docker Swarm to route traffic to the appropriate containers, automatically.
There are three parts to get your cloud ready for web services: a load balancer to spread connections to available servers, an ingress router to direct traffic to containers, and DNS to point local traffic to the right IP addresses. Here’s a quick layout:
Scaling an application is hard, especially when you need to manage its important data yourself. One way to make this easier is by sharing the files across multiple servers — no matter where it runs, the data will always be available.
An important step in making highly available applications is setting up highly available data. With Docker, we will set up shared files with a volume plugin called Convoy.