| |
| 🔗 From the web |
| |
|
| |
| Best practices for building an incident management plan and process |
| |
| |
| A thoughtful incident management plan can help you avoid future security incidents and cut down your incident response time drastically. |
|
| |
|
| |
|
| |
| Top 10 Microservices Design Patterns and Principles |
| |
| |
| A quick look into what is microservices architecture, its use cases and design patterns. |
|
| |
|
| |
|
| |
| How Snap made its old stack disappear ✅ |
| |
| |
Snap was built on Google App Engine (GAE), a serverless platform for developing and hosting web applications.
Snap started breaking out its back end into microservices that were backed by other services inside of Google Cloud. Shortly thereafter, it added AWS as its second cloud computing provider. |
|
| |
|
| |
|
| |
| How to make low code work long term |
| |
| |
| Low-code tools don’t always equal long-term solutions. Here's how businesses can make low-code tools work for the long haul. |
|
| |
|
| |
|
| |
| Dynamic Kubernetes Configuration for GKE |
| |
| |
Sometimes, you want to change or inspect resources on your GKE cluster from outside the cluster. For example you might have a simple Cloud Function or Cloud Run service, that schedules a Pod for you. The challenge can be in regards to setting up the configuration properly to connect to the Kubernetes Master API.
One approach could be to bake a K8S config file into the container or your function code, but this means that you have an environment specific container or function. That’s not really what we want, since it limits transferability of our deployable.
A better approach is to use the GKE API to discover the information we need from the cluster. |
|
| |
|
| |
|
