When it comes to edge environments, Google Cloud’s role is clear: they treat the edge as the domain of their customers and partners. They do not send remote servers for pickup or preconfigure boxes to sync. Instead, they provide software and tools to configure and maintain all clusters as part of the Anthos suite, combined with Google Kubernetes Engine (GKE) and the open-source Kubernetes.
Learn more: https://cloudstrata.io/edge-computing-building-enterprise-edge-applications-with-google-cloud/
The evolution of technologies such as containerization, container orchestration, and cloud-native serverless services has given us the ability to develop distributed solutions based on microservices architectures that are both more scalable and more reliable.
https://cloudstrata.io/microservices-architecture-on-google-cloud/
This article describes how to integrate ROSA with AWS API Gateway HTTP APIs that are exposed to multiple end users. It thus becomes imperative to ensure that a shared backend service is able to distinguish between different client sources for the purpose of correct execution and auditing.
Technically this requires implementing a number of supporting technology patterns such as transparent proxying, wildcard certificates and split-horizon DNS to simplify end-to-end communications using a common custom domain name.
Read more: https://cloudstrata.io/using-rosa-with-aws-api-gateway-http-apis/
Now more than everService Mesh 2.1 introduces new resources for federating meshes across OCP clusters. This enables meshes located in different clusters to securely share and manage traffic between meshes while maintaining strong administrative boundaries in a multi-tenant environment.
Learn more: https://cloudstrata.io/introducing-openshift-service-mesh-2-1-federation-has-arrived/
Now more than ever, organizations are looking to accelerate their cloud adoption. They want easier development, faster innovation, and efficient scale, all while simultaneously reducing their technology risk. However, some of their workloads cannot move to the public cloud entirely or right away, due to factors such as industry or region-specific compliance and data sovereignty needs, low latency or local data-processing requirements, or because they need to run close to other services.
Based on Kubernetes 1.22 (and CRI-O 1.22), OpenShift 4.9 has a number of exciting new enhancements and new features for developers of cloud-native apps, for cloud-native DevOps practitioners, and for cluster and cloud administrators.
Learn more: https://cloudstrata.io/red-hat-openshift-4-9-is-now-generally-available/
@cloudstrata_io #cloudstrata
