Is your company in the process of migrating(or considering it) from isolated applications architecture to the open API? If the answer is yes, then choosing the GraphQL instead or REST might be the right choice for you. The benefits of GraphQL over REST are numerous, and we will not repeat them here, you may find many resources online (for example, Top Five Reasons to use GraphQL).
GraphQL suits Maximo naturally
The basic building blocks of Maximo are its business objects (Mbos), business objects fields, and the relationships between them. If you have even the slightest idea about the GraphQL, you can easily spot the similarities: Mbos - object types, Mbo fields - object fields, and the relationship - nested object types.
Why GraphQL server for Maximo?
The GrapqhQL Server for Maximo requires no programming at all. You simply define the schema in the GraphQL schema definition language (SDL), and the server automatically creates the resolvers. The server covers the complete Maximo functionality: you can use the GraphQL mutations to change the data, route the workflow, or execute any action available in Maximo (for example: change the status, change the balance of item inventory, create RFQ from PR...)
Want to try it out? Check out the documentation, or the next blog post - Installing GraphQL server for Maximo