[progress Communities] [progress Openedge Abl] Forum Post: Re: Oe Reference Arccitecture...

  • Thread starter Thread starter Mike Fechner
  • Start date Start date
Status
Not open for further replies.
M

Mike Fechner

Guest
The same RESTful API's can be implemented with pure OpenEdge capabilities with ease. We have implemented true Restful API's for our Business Entities based on annotations. No need for node.js here. Sent from Nine Von: "marian.edu" Gesendet: 11.08.2017 8:50 nachm. An: TU.OE.Development@community.progress.com Betreff: RE: [Technical Users - OE Development] OE Reference Arccitecture and ORM considerations... Update from Progress Community marian.edu I think OERA it’s more about layers and how one should build/use application’s blocks, very often this is referred to in relation with a framework that implements generic functionality of some of those blocks - data access, business logic, service interface, generic services (authentication, authorisation, logging, session/context management, etc) but it doesn’t automatically imply any framework. The ORM on the other hand tries to provide a simple solution for data access, specifically my mapping “objects” to underlying data storage and provide basic CRUD functionality some also supporting navigation based on table relations (foreign key). Outside of Progress world this is how an ORM might look like - http://sports.akera.io:8080/explorer/ , you can see the “objects” being exposed, each with generic CRUD methods and some with convenient methods to access related (parent/child) data based on defined relationships. To get customer information using the primary key a simple GET request like this can be used - http://sports.akera.io:8080/api/Customers/1 (last path parameter is the customer number), to get invoices for the same customer this simple request will do: http://sports.akera.io:8080/api/Customers/1/invoices . Well, you might recognise the famous sports database so it’s still a Progress “app” behind that we’ve build for demo purposes - the actual web app using the services exposed by Loopback (the ORM part of Strongloop) looks like this - http://sports.akera.io:8080/ . More complex business logic processing can be added to specific methods, using our node.js API we can easily call 4GL code by passing parameters around. Marian Edu Acorn IT www.acorn-it.com www.akera.io +40 740 036 212 View online You received this notification because you subscribed to the forum. To unsubscribe from only this thread, go here . Flag this post as spam/abuse.

Continue reading...
 
Status
Not open for further replies.
Back
Top