Ecosystem Integrations, Beyond Plugins

[mpareja-godaddy]

The project could provide grater adoption through building ecosystem integrations for various topics.

• IAM: Identity & Access Management

  • Okta, AWS, GCP, Azure, Ping, OneLogin

• ORM: Data warehouse

  • xSQL, mongo, graphQL/Apollo, etc.

• CICD: Continuous Integration Continuous Development

  • GitHub Actions, CircleCI, Jenkins, etc.

• Orchestration:

  • Ansible, Puppet, Chef, etc.

• APM:

  • elastic, AWS, GCP, Azure, zoho, etc.

  I especially like backstage.io for exposing these patterns, references, templated applications.
  The principal here is to standup a solution repository that enables new users to adopt the framework more rapidly and employ some best practices in a common interface that is integrated.

  Many of the verticals listed here offer 'free' access for theses type of functions to opensource projects, as a consumer it would be really cool to have "Sandboxes" to play in when considering the framework for adoption.

[evantahler]

Great ideas @mpareja-godaddy! I agree that it would be awesome to have plugins for many of these! Some of the integrations you list (IAM, ORM) make a lot of sense as they need to integrate directly into the application, but I'm curious how you envision CI/CD and Orchestration fitting in.

How do you think we should incentivize the community to work on these? The plugins that I've made (sequelize, sentry, next, etc) are in response to a specific use-case I had at the moment, so I was externally motivated.

[mpareja-godaddy]

Swag, badging/gamification, even branding, Community could end up being comercial suppliers, or independent entities. However yes incentivizing would be key to success, another method would be project sponsors, sponsors contributing awards to community 'Hack-a-Thon' where derived products become part or in whole one of the templated "Solutions" , internally we refer to the baked solutions catalogue as "Solutions Repository" (clever I know) but it promotes less experienced dev's to pull a baked solution, regardless of the individual use case the data we use from the solutions repository contributes directly where we allocate future engineering resources or in this case promote community response.

Turn Key Solution for AWS may be
| App Container or Lambda | Redis Container or elastiCache/memDB | AWS Auora/RDS/Dynamo ORM Integration | AWS IAM Middleware Integration | AWS APM | AWS CICD or GH:Actions |

This is something that could be hosted at AWS or as a solution catalogue entry in Backstage.io

Goal, target common implementation patterns in a captive experience so you can use the data to steer product improvements .

[evantahler]

I worry that this tool is made for engaging an audience, but I believe that we should currently focus on acquiring an audience - conference talks, blog posts, etc. We need the users first, and then we can encourage them to create new plugins and tools.