Pluto 2024 Roadmap

[jianzs]

Annual Goal: Increase Pluto's Visibility

1. Individual Developer Outreach: Bring Pluto to individual developers' attention and make it a preferred option for cloud development.
2. Acquiring Customers through Key Accounts: Enable large clients to integrate with their platforms, using Pluto to offer their platform capabilities to developers.

Goals for the First Half of the Year

Purpose:

1. Make Pluto an option for individual developers for cloud development.
2. Enable large clients to start integrating their platforms with Pluto. 

Vision:

• Enhance Business Development Experience (Usability):
  • Friendly error prompts, including programming constraints and execution errors.
  • Developers can use familiar frameworks (Express, Koa, etc.) to harness Pluto's capabilities.
  • Developers can perform general computations (Word Count) in addition to web backend development with Pluto.
  • Accessible tutorials and case documentation for reference.
• Simplify the Extension Development Process (Simplicity):
  • Users extend the cloud platform or modify resource types by updating four files: Client implementation class, Client base class, Infra implementation class, Infra base class.
  • Users can adapt platforms not supporting IaC by implementing third-party Adapters. 

Goals:

• Product Feedback
  • Stars: 200+
  • Suggestions and Requirements: 10+
  • NPM Downloads: 3k+
• Error Prompt Optimization
  • Build a comprehensive framework for error prompts.
  • Standardize error messages.
• Support Framework Adaptation
  • Framework SDK Development: Express
  • Deep analysis of SDK capabilities.
  • Multi-file analysis capability.
• Support General Computation Scenarios
  • Transition to main closure execution mode.
  • Passage of compile-time generated values Transfer the values generated by compile-time to runtime. #102.
• Documentation Construction
  • Develop a documentation website.
  • Tutorials and a Playground.
  • Enrich case studies: 4+.
• Simplify SDK Development
  • Adjust the timing of FaaS resource instance creation Move the timing of FaaS object creation to the Infra API #103.
  • Change the timing of specific implementation class selection Move the selection of specific implementation classes to the static method within the base classes #106.
  • Auxiliary tools for Pluto NPM package release.
• Build a working mechanism for non-IaC engine Adapters, supporting platforms like Simulation, HUSE, etc. 

Challenges:

1. Implementation of static analysis.
2. The adapter without IaC engine working mechanism design.

Goals for the Second Half of the Year

Purpose:

1. Make Pluto a preferred option for individual developers for cloud development.
2. Increase Pluto's visibility. 

Vision:

• Enhance Business Development Experience (User-friendly):
  • Developers can debug code without using the cloud platform's console.
  • Developers can globally configure expected infrastructure through plugins, such as cost control, VPC settings, etc.
  • Developers can view resource consumption and cost statistics through the server. 

Goals:

• Product Visibility:
  • Stars 500+
  • Suggestions and Requirements 30+
  • Contributors 10+
  • NPM Downloads 10k+
• Enrich Pluto's Case Studies: 10+
• Produce a Killer Application
  • Software delivery tools.
• App Store (Challenge)
• Design plugin mechanism and complete PoC verification.
• Build server-side system framework.