The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features or functionality remain at the sole discretion of GitLab Inc.
Fulfillment Platform maintains and evolves our underlying order-to-cash infrastructure, including integrations with Zuora to help accelerate our goals as a section.
Fulfillment Platform team supports all of the teams in Fulfillment by abstracting complex integration with Zuora, improving CustomersDot architecture to better align with order-to-cash systems, focusing on developer productivity, and working on support and maintenance of the CustomersDot infrastructure.
Fulfillment platform works on availability, reliability, performance, scalability, delivery, and observability efforts with help from the Infrastructure department.
We aim for CustomersDot to have the same service agreements as GitLab.com, with a 99.95% targeted availability.
We have recently migrated to GCP, added CustomersDot error budgets to Grafana, and SLI tracking.
Next, we want to get to a higher level maturity and continue improving our availability and observability:
| What | Why | When |
|---|---|---|
| Add a SLA (uptime/availability) dashboard | Add more visibility and tracking around CustomersDot SLA and availability | In-progress |
| Improve current CustomersDot runbooks | Eliminate dependency on Fulfillment when troubleshooting CustomersDot | 1-3 milestones |
| (HA) Migrate from postgreSQL to Cloud SQL | Less maintenance and better availability for the CustomersDot DB | 1-3 milestones |
| Improve redundancy between CustomersDot and Zuora | Adds a better caching layer to have no downtime due to frequent Zuora outages | 1-3 milestones |
| (HA) Iteratively migrate CustomersDot to a HA environment | Move CustomersDot services/components to HA in order to improve reliability | 3-12 milestones |
| Add logs to Kibana | We have GCP logs but Kibana is more complete and part of the maturity levels | 3-6 milestones |
| Implement auto-rollback on error | Minimize disruption if an outage occurs after a deployment | 3-6 milestones |
| (Business Metrics) Alerting of failed jobs for critical SaaS metrics | Move away from noisy Sentry alerts to critical alerts for accurate SaaS billing | 3-6 milestones |
| (Business Metrics) Alerting of failed jobs for critical SM metrics | Move away from noisy Sentry alerts to critical alerts for accurate SM billing | 3-6 milestones |
| (Business Metrics) Alerting over a threshold of payment failures | Encounter payment problems as they occur | 3-6 milestones |