create-service

To scaffold a Firefly microservice automatically, provide a kebab-case service name and a tier. The tool then generates a multi-module Maven project layout with standardized groupId, basePackage, and module structure.

Generating a Firefly Framework microservice supports Core, Domain, Experience, Application, Data, and Library tiers. Each tier produces a consistent module layout with specific interfaces, models, or infrastructure modules.

Structuring a multi-module Maven project for domain-driven microservices requires generating a root pom and specific modules like interfaces, models, core, sdk, and web. This scaffolding tool automates that layout from a service name and tier.

Yes, the Firefly microservice scaffolding tool validates input parameters and prompts you when required information is missing. It needs a kebab-case name and a tier to derive the standardized package path and identifiers.

Yes, when scaffolding a domain tier microservice, the tool generates an infrastructure module named {name}-infra instead of the standard {name}-models module used in other architectural tiers.

Your generated Firefly microservice uses a kebab-case name because the scaffolding tool derives the basePackage and packagePath from it. This naming convention ensures standardized identifiers across the generated Maven modules.