Reputation
Top tag
Next privilege 125 Rep.
Vote down
Badges
5
Newest
 Student
Impact
~82 people reached

  • 0 posts edited
  • 0 helpful flags
  • 9 votes cast
Nov
10
comment API and a shared API client
there are, and yes, it's an overhead. This is not the point of the question. The point is to have consistent objects before and after transfer.
Nov
10
comment API and a shared API client
the whole point of HTTP is to have each of the services on a separate node, that's the real point of microservices, really, to have them separated as much as possible. When you keep everything on one node and in one project, it's still a monolithic application with the only thing being really separated is the class tree.
Nov
10
comment API and a shared API client
Thanks for sharing, I do something similar like the services you have mentioned but I have called them an APIClient in my question. The point of the question is how can you share real objects with all their behaviour if they're transmitted by HTTP - I know about serialize() & unserialize(), but they don't do the job well in this case as they may have different implementations in one point in time if you don't deploy ALL projects at the same time.
Nov
10
awarded  Student
Nov
10
awarded  Editor
Nov
10
revised API and a shared API client
diagram added
Nov
10
asked API and a shared API client
May
6
awarded  Teacher
Sep
24
awarded  Autobiographer
Dec
27
answered Why is naming a table's Primary Key column “Id” considered bad practice?
Sep
27
awarded  Supporter