About us UTN Córdoba
Spanish Version
More than 10 years ago we started the journey to migrate our systems to a scalable platform and that’s where Java entered in our plans.
We plan and develop a scalable, robust, secure infrastructure oriented to provide the ultimate experience for our users.
COVID-19 presents us new challenges in terms of agile and scalable development and it’s where Quarkus. helps us to carry it out.
Integration of Services
We integrate services of different types, where applications are combined.
- Legacy Systems - IIS, our Autogestion
- Administrative and Academic Systems
- Government Integration
- Virtual Education - Moodle
- Help and management - Gitlab
- Payment Management -NAS - File Systems
Why Quarkus
We currently have a monolithic Java EE architecture with Jboss clusters for our Academic Management Systems that integrates various services provided by our Faculty. However integration and provide services sometimes become a chimera that grows without control and that’s where microservices became a solution.
We have tried with the best microservices frameworks known on the market, such as Spring and Micronaut, but since we came from Jboss, Quarkus quickly opened the way for us to perform the decoupling in small modules that provides a specific service without sacrificing everything agreed and developed previously.
Times changes and we want to be cutting edge with technology like Quarkus.
The benefits of Quarkus
The creators themselves can say it through their blog and guides (see reference), but we are one of those who DO, test and if it works as we wish, we take advantage and squeeze the tools to get his maximum potential. Only by developing and implementing it, we can verify real benefits.
If you comes from Jboss, Wildfly or Jakarta infrastructures, the adaptations in terms of services are very similar and the same in the case of the first 2. This gives us well known and proven technologies that have been built with solid foundation like MicroProfile. So the learning curve of it is exponential.
The integration of dependencies, the deploy and hotreload of the applications makes Quarkus a unique experience for those of us who come from giant implementations of monolithic applications where deploying is a coherent bureaucracy but without practical sense.
Providing the development of native applications with GraalVM has its benefits and times of startup are incredible and unimaginable for an application written in Java.
Being reactive, the responses of the systems are kept at the level that current applications need.
With @QuarkusTest we can perform the Units and Integration Tests at the same time, simplifying the entire application testing process and the implementation of Profiles make the whole development process flow.
Looking at the future
Where are we …well the separation of each specific component into microservices, becoming Reactive, implementing Functions as a Service and Serverless, and thinking of a global deployment infrastructure for our entire National Technological Faculty.
More info at:
Centro de Cómputos UTNFRC
Adopting Quarkus - Spanish
Adopting Quarkus - English