Question about the best approach to move from Laminas MVC application

[tasselchof]

I’m planning to migrate a large Laminas MVC application to DotKernel API 6.0 and would appreciate guidance on the best approach.

The challenge is that the current app has many legacy modules using Module.php and traditional Controller classes. Given the size of the codebase, a full rewrite isn’t feasible upfront. I need to be able to run old modules (MVC-style) in parallel with the new ones (middleware-based with config providers) during the transition.

What’s the recommended way to bootstrap legacy modules alongside the new middleware setup? Can DotKernel API 6.0 support hybrid apps during migration?

Any advice is appreciated.

[arhimede]

This seem to be a consulting job :-)

In theory is easy: services, repositories, module should be the same
But it depends on your code and the complexity of it

[tasselchof]

@arhimede thanks! It’s more of a discussion - I imagine there are others out there thinking about how to approach this too. I think your input is valuable as others might also think how to approach this. We will figure this out for sure.

We’ve just started building new APIs using middleware, adding a layer that, for now, connects to our Laminas MVC setup by converting the ConfigProvider class.

The biggest challenge so far has been the database refactoring. We had to implement and carefully manage a second EntityManager instance for the “new” entities.

Our plan is to introduce an additional bootstrap point once the APIs are in a more stable state, and gradually migrate the frontend app to use the new endpoints. Since the Bearer keys remain the same, it shouldn’t be a big issue.

Does this approach make sense to you?