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.
Last updated: 2024-03-25
Within the Fulfillment Infrastructure category we want to enable other fulfillment groups and contributors to ship with confidence, speed and efficiency, while ensuring that GitLab's fulfillment systems remain robust, performant and resilient.
As one of our key areas spans developer productivity we work on performance, scalability, and observability efforts with help from the Infrastructure department.
In order to enable other groups, contributors, and stakeholders, we are focusing on 2 key areas of the Fulfillment infrastructure:
| Key area | Principle | How | Performance Indicator |
|---|---|---|---|
| System reliability | Provide fulfillment infrastructure with best in class reliability and availability. | CustomersDot has a 99.95% target availability and must stay within allowed error budgets. |
General availability and Customer Journey Error Rate(s) |
| Developer productivity | Provide a great experience for every developer that contributes to fulfillment solutions. | Make code contribution easier by maintaining the underlying architecture, keeping it performant, observable and decrease complexity through abstractions at the platform level. | Mean time to recovery |
Roadmap:
For a full list of our upcoming and ongoing projects related to Fulfillment Infrastructure, check out our Roadmap.
Within the next 12 months we want to increase the level maturity of CustomersDot and continue improving our availability and observability through the following projects:
| What | Why | When |
|---|---|---|
| Decouple subscription update API into multiple end points | Reduce the determination complexity of the intended subscription update | Current focus |
| Iteratively migrate CustomersDot to a HA environment | Move CustomersDot services/components to high availability in order to improve reliability | Later (6-12 milestones) |
| Implement auto-rollback on error | Minimize disruption if an outage occurs after a deployment | Later (6-12 milestones) |
| Alerting of failed jobs for critical SaaS and SM metrics | Move away from noisy Sentry alerts to critical alerts for accurate SaaS and SM billing | Later (6-12 milestones) |
| Alerting over a threshold of payment failures | Encounter payment problems as they occur | Later (6-12 milestones) |
As we progress with our current key projects to build foundational strength and enable internal teams to be more efficient, we will identify new areas of opportunity. The future opportunities will have a continued focus on system reliability, developer productivity and fulfilment process efficiency.
For more details into future oportunities of other categories within the Fulfillment Platform group, please refer to the sections in the dedicated category pages: