Overview
Talisman Studio gives developers the Talisman designers. Each developer uses them in Studio Web or in Studio for VS Code, whichever they prefer, and the team can mix both. Both work on the same projects in your Git repository.
Side by side
| Studio Web | Studio for VS Code | |
|---|---|---|
| Where it runs | In the browser, served by the dev Talisman Server | In VS Code on the developer's machine |
| Install | Nothing on the developer's machine | The extension from the VS Code Marketplace, Git, Docker or a local Kubernetes |
| Git | Works on main in the dev Server |
Works on a branch, merged to main by pull request |
| Developer mode | In the dev environment | On the developer's own Docker or Kubernetes |
| Build | Server Build on the dev Server | Server Build on the dev Server, or CI/CD Build in your pipeline |
| Designers | Topology, Route, OpenAPI, AsyncAPI, JSON Schema | Topology, Route, OpenAPI, JSON Schema |
| Deployment option | Studio Web on Server | VS Code with Server Build, VS Code with CI/CD |
Studio Web
Studio Web is part of the dev Talisman Server. Developers sign in with a browser and start designing. See Studio Web.
Studio for VS Code
Studio for VS Code is the extension "Talisman Studio" (talisman-platform.talisman-studio). Developers keep their IDE, their Git tools and their pull request reviews. See Studio for VS Code.
How to pick
Your deployment option decides which Studio your developers use:
- Studio Web on Server: Studio Web. Choose it when developers should install nothing and work in one web interface.
- VS Code with Server Build: Studio for VS Code, with the dev Server building and deploying after each merge to
main. Choose it for branches and pull requests without a pipeline to maintain. - VS Code with CI/CD: Studio for VS Code, with your pipeline building and deploying. Choose it when your releases already go through CI/CD and GitOps.
The Subscription Overview describes what a subscription includes.