Skip to content

[Spike] Evaluation of Application Foundation Toolkit and Architecture #2953

@lindnerby

Description

@lindnerby

Objective

To prepare for kicking off GAR and upcoming innovative PoCs, we should get familiar with Application Foundation’s (AppFND) internals and gain hands-on experience.

In this Spike, we aim to work through the Onboarding process and get started with the AppFND Toolkit. This hands-on workflow should be compared with the AppFND architecture and ideally be carried out by a pair of team members to exchange learnings and help resolve impediments.

Notes and prerequisites:

  • We already have an organization named pmkyma that has been onboarded, so parts of the onboarding process are already completed.
  • @lindnerby can add assignees to the organization and relevant team channels once this Spike is picked up.
  • Within the pmkyma organization, there are existing application repositories that can be used to walk through the onboarding guide, and new repositories may also be created. This organization should be treated as a playground to gain as much exposure to AppFND as possible.

While working through the toolkit hands-on, we will explore topics such as Container Hosting (deploying applications) and the specific SDKs in use.
We should document findings, identify blockers or hiccups encountered while following the guides, as well as developing initial ideas related to our Kyma offering.

The overall goal is to gain a better understanding of Application Foundation, its architecture and how Kyma is envolved, from a developer’s perspective.

As an outcome of this Spike, the assignees will prepare a presentation for the team to bring everyone up to speed and deepen understanding by explaining the concepts and learnings to others.

Acceptance Criteria

  • The AppFND toolkit and developer experience are understood by at least two team members
  • The mapping to AppFND architecture and Kyma usage is clear
  • All key learnings are distilled and presented to the team in a designated presentation

Timebox

8d

Constraints

Dependencies on permissions to other services (Cloud Identity, etc.) may cost some time.

Metadata

Metadata

Assignees

Labels

spikeSpike issue to research a new feature or clarify a complex problem.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions