y Factors

The [y] Factors are our guiding principles

At SAP Hybris, we believe developing scalable software for the cloud requires changes in old-fashioned organization and structure.

Self-sufficient teams

Open technology landscape

Release early, release often

Responsibility

APIs first

Predictable and easy-to-use UI

Small and simple services

Scalability of technology

Design for failure

Independent services

Understand your system

Self-sufficient teams

Teams own their product from design to delivery

Values

Development teams are trusted to work independently from the red tape of a big organization and therefore can develop a product quickly.

Effects for the team

Team members are happy because they are trusted and not frustrated by processes and decisions that are out of their control. In return, teams take more pride and responsibility for the quality of their product.

Benefit

You can take a concept to production with limited dependencies outside of your team.

Open technology landscape

Teams have the freedom to pick the right tool for the job

Values

Development teams choose the tools they want, because they know what tool works best for the job. When teams don’t want to choose, they can get input from the community or use the default tools.

Effects for the team

Development teams are more efficient when they can use tools they like and are familiar with, and they are more committed to the project when they are not forced to use certain tools.

Benefit

You have the freedom to pick the right tool for the job.

Release early, release often

Establish a deployment pipeline to deliver your product without the fear of breaking something

Values

The time to market is greatly reduced if you release early, get feedback, and then release again with the added improvements.

Effects for the team

Releasing early reduces the time between development and bug reports. High test coverage and automation are key factors to achieving this.

Benefit

Software only provides value when it's out in the market, so get it out there quick.

Responsibility

You own it, in every sense of the word

Values

Development teams are also trusted to interact with customers directly and act upon their feedback in a timely matter

Effects for the team

Valuable customer relationships are built, as is a win-win scenario with happy customers and a high-quality product.

Benefit

You build it, run it, release it, scale it, maintain it, support it, and improve it.

APIs first

Design APIs with your customer in mind

Values

Design the API based on an early agreement with your users, and build functionality into it later.

Effects for the team

Customers are happy because they are involved in the design of the product, and the maintenance costs are reduced with fewer revisions.

Benefit

Focus on developing rich APIs based on customer needs, and develop the functionality later.

Predictable and easy-to-use UI

Don't surprise your customers

Values

Development teams design UIs with straightforward and predictable interfaces using well-known technologies.

Effects for the team

There are no hidden surprises for the customer, because the APIs and UIs are consistent.

Benefit

Use predefined patterns and best practices to ensure a consistent API and UI.

Small and simple services

Keep it simple, yet the possibilities become endless

Values

Services are small and simple, which has a lot of advantages. They are easy to exchange, localize, and reuse. Although the services are kept small, they increase the complexity of the entire product landscape.

Effects for the team

For developers, refactoring services becomes a normal task, and this simplifies development and maintenance.

Benefit

The perfect service is small and does one thing.

Scalability of technology

Each component must scale cost-efficiently and without limits

Values

Services are small and simple, which has a lot of advantages. They are easy to exchange, localize, and reuse. Although the services are kept small, they increase the complexity of the entire product landscape.

Effects for the team

For developers, refactoring services becomes a normal task, and this simplifies development and maintenance.

Benefit

The perfect service is small and does one thing.

Scalability of technology

Each component must scale cost-efficiently and without limits

Values

Development teams design using multi-tenancy technology to ensure scalability.

Effects for the team

Scalability in the technology means lower overall costs for the customer.

Benefit

Linear horizontal scalability equals lower costs and fewer limits on maximum scalability.

Design for failure

Don’t design on hope

Values

Build resilient services that handle failure and recovery gracefully, instead of hoping they will never go offline.

Effects for the team

Developers get to design services in a different way and focus on testing failures.

Benefit

If the infrastructure or service can go down, it will go down. Design for failure and recovery.

Independent services

Don’t depend on others

Values

Ideally, design your service with no code dependencies on other teams.

Effects for the team

Developers have independent release cycles for faster delivery and can isolate failures to single components quickly.

Benefit

The perfect service has zero dependencies.

Independent services

Don’t depend on others

Values

Ideally, design your service with no code dependencies on other teams.

Effects for the team

Developers have independent release cycles for faster delivery and can isolate failures to single components quickly.

Benefit

The perfect service has zero dependencies.

Understand your system

Don’t guess. Know.

Values

Know your system inside and out so you can fix downtime, track logs, and predict scaling before it becomes an issue with customers.

Effects for the team

Customers want analytic data, insights into metrics, and a stable product they can trust.

Benefit

Know the state of your services and system. Make it visible and easy to observe.

  • Send feedback

    If you find any information that is unclear or incorrect, please let us know so that we can improve the Dev Portal content.

  • Get Help

    Use our private help channel. Receive updates over email and contact our specialists directly.

  • hybris Experts

    If you need more information about this topic, visit hybris Experts to post your own question and interact with our community and experts.