Why Legolas?
Enjoy the history of Legolas and why we created it.
The History
Most developers in Archmix have at least a decade of the profession and it seems like always we need to do the same boring thing when we start a new project: prepare development environment, find docker images available or even create our own, guarantee connectivity with those infrastructure components and then, start to code.
At the same time, we wanted to solve this problem we did not want to create another framework. So we really focused on getting databases, messaging brokers, and anything we need in terms of infrastructure components and delivering it in a modular solution, where you just put the module in the classpath and all the hard work was, done.
Right now, Legolas is helping developers to have an integrated developer environment effortless, giving them more time to be concerned about the solution they need to code.
How Legolas can help you?
Legolas helps you to create a reproducible development environment effortless.
Think Legolas like a built-in development environment that you can just choose which infrastructure service you need in your project and go.
Legolas is not a framework, it is a modular library. It means that you can combine Legolas with any java framework you are using.
Key Features
Lifecycle

Legolas has a predefined lifecycle compound by Starters, Bootstrappers and Migrations. They will be executed in this exact order as soon it is applied to Legolas Runtime Environment and produces a Legolas Running Environment.
Using Legolas in your project
Since Legolas is a modular project and you can use each module apart, consider importing the parent pom in your project as a managed dependency, and import what you need as a dependency. Each feature mentioned earlier describes in its documentation section which dependency you need to import.
Last updated
Was this helpful?
