[FOLIO-559] Consider to use common URL context per module Created: 12/Apr/17  Updated: 18/Jan/19

Status: Open
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: New Feature Priority: P3
Reporter: Hongwei Ji Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint:
Development Team: Core: Platform

 Description   

Currently, there is no common URL context per module. For example, mod-users supports URLs like /users, /groups, //tenant, /admin, and etc. Was there a consideration to use a common module context like /mod-users/users, /mod-users/groups, /mod-users//tenant, /mod-users/admin? Doing so will make path based routing possible. For example, in AWS if we deploy modules outside of OKAPI, we can leverage AWS load balancer to set up path (/mod-users) based routing so OKAPI can get all mod-users URLs through /server:port/mod-users.



 Comments   
Comment by Heikki Levanto [ 21/Apr/17 ]

This could be possible. But I can see some problems:

  • The APIs are to interfaces, not modules, so we should not have module names in the paths. One module may implement multiple interfaces, and the client using an interface should not know nor care which module is implementing it. But using interface names instead would be possible.
  • Okapi makes some calls to modules when enabling them for a tenant, most importantly the /_/tenant interface. That is an interface that most modules should implement, identically. So a path prefix would not help in routing.
Generated at Thu Feb 08 23:06:41 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.