AppsCode is a global leader in Enterprise-grade Kubernetes-native Data Platform with Automated Day 2 Operations founded on 2016. During the last IT Press Tour #61, Tamal Saha, Founder and CEO and former Google engineer, describes the different products.
Evolution of AppsCode follow the history of Kubernets:
Their products are focused in those specific areas, mostly related with database world:
- Manage full life-cycle of any databases
- Backup and fast recovery solution for workloads
- Manage Secrets & Users w/ Vault operator
- Ingress Controller w/ Gateway API Support
- Centrally Manage Clusters w/ Hub-Spoke Model
But why you need specific solutions? Aren’t they already covered by Kubernets? Not really… or at least not for statefull application (where database server fits):
AppsCode has a lot of cloud native products for Kubernetes including:
- KubeDB manages and simplifies provisioning, upgrading, scaling, volume expansion, monitor, backup, restore for various databases in Kubernetes on any public & private cloud.
- KubeStash a complete Kubernetes native disaster recovery solution for backup and restore your volumes and databases in Kubernetes on any public and private clouds.
- KubeVault is a Git-Ops ready, production-grade solution for deploying and configuring Hashicorp’s Vault on Kubernetes.
- Voyager is a secure L7 and L4 ingress controller for Kubernetes with Gateway API support. This can be used with any Kubernetes cloud providers including AWS, GCE, GKE, AZURE, ACS etc. This can also be used with baremetal Kubernetes clusters.
- Guard by AppsCode is a Kubernetes Webhook Authentication server. Using guard, you can log into your Kubernetes cluster using a Github or Google authentication token. Guard also sets authenticated user’s groups to their Github teams or Google groups. This allows cluster administrators to setup RBAC rules based on membership in Github teams or Google groups.
- Config Syncer (fka Kubed) by AppsCode syncs secrets and configmaps across Kubernetes clusters. From here you can learn all about Config Syncer’s architecture and how to deploy and use Config Syncer.
They try to solve the major pains for database management in a Kubernets environment:
And their solutions are very interesting making simple has DBaaS and drive all the configuration of a database with a desire state and a simple YAML file, like other resources in Kubernets:
And is not limited to the database creation, but cover the entire lifecycle.
The management interface is also web oriented and multi-tenant and has a lot of configuration options, including scaling settings (both scale-out and scale-in options are supported), backup and restore functions (including point-in-time).
It support a huge set of existing database products:
