How to start an architecture from a template in Yantra Studio
Open the template gallery, start from a pattern close to what you are designing, and edit it into your own architecture.
When this is useful
- The design resembles a well-understood pattern and re-deriving it is wasted effort.
- You are teaching or interviewing and want a correct worked example to talk over.
- You want a starting data model at the right level of abstraction rather than an empty canvas.
Before you start
- A diagram open. Nothing else — templates start from empty.
Step 1: Open the template gallery
The gallery is in the Page menu, alongside the shape packs.
Page ▸ Template galleryPage ▸ Shape packs
Step 2: Pick the right level
For data work, the quick-create templates start you at a chosen level of abstraction — a conceptual ER model, a logical model or a physical model — and the built-in models cover Star Schema, SaaS Multi-tenancy, an e-commerce model and Event Sourcing.
For system design, the simulation architecture templates cover 28 patterns: infrastructure shapes such as a 3-Tier Cloud Architecture and an ETL / Data Pipeline, and worked system designs including a URL Shortener, an API Rate Limiter and a Distributed Message Queue.
Star SchemaSaaS Multi-tenancyEvent Sourcing3-Tier Cloud ArchitectureETL / Data PipelineURL Shortener (TinyURL)API Rate LimiterDistributed Message Queue (Kafka)
Step 3: Cut it down before you add to it
Delete the components your design does not have before renaming the ones it does. A template adapted by addition tends to keep parts nobody chose, and those are the parts that mislead a reviewer.
What happens next
You have an ordinary diagram — the template is a starting content, not a live link, so editing it affects nothing else.
If your organisation maintains its own approved patterns, those are published separately through the administration screens and are the better starting point when they exist.
Example
A team designing a notification service started from Notification / Fan-out Service, deleted the SMS path they were not building, and had a reviewable design in under half an hour.
Tips
- Pick the template that matches the problem shape, not the technology names. Renaming a queue is trivial; restructuring a fan-out is not.
- The system-design templates are worth reading even when you do not use them — they are compact, correct examples of patterns people usually only describe.
Limitations
- A template is a copy. Improvements made to the built-in template later do not flow into diagrams already created from it.
- Organisation-specific pattern libraries depend on your organisation having published them.