Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate Universal Resolver to Spring Boot #259

Closed
peacekeeper opened this issue Dec 8, 2021 · 3 comments · Fixed by #271
Closed

Migrate Universal Resolver to Spring Boot #259

peacekeeper opened this issue Dec 8, 2021 · 3 comments · Fixed by #271
Assignees

Comments

@peacekeeper
Copy link
Member

Hi all, we are planning to work on migrating the Universal Resolver to the Spring Boot framework, in order to better support logging, metrics, configuration, and other features that could be useful for more professional/enterprise deployments in the future.

This should be fully backwards compatible, i.e. no changes necessary to the external API or driver implementation.

Please let us know if you have any feedback or concerns.

@solidnerd
Copy link

How does it affect the architecture and which components are targeted here? Let us make a more detailed plan on what will be migrated. So for example I think the main target is here the web component is targeted as migration but for example, drivers aren't needed to do this. Are also repositories structures changes included ?

But I'm looking forward to this :)

@peacekeeper
Copy link
Member Author

Yes, this is about the web component, not about individual drivers. I don't think repository structures will change.

We'll see about the details once we start working on it, happy to discuss also in DIF Slack!

@solidnerd
Copy link

@BernhardFuchs @peacekeeper @cihanss I think this breaking change we should bump the version to 2.x or make at least a new version 0.5.x since the packaging has changed completely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants