I wish I were joking that I literally haven't received a delivery of four GET endpoints I wrote requirements for six months ago. The problem is that nobody seems to understand why this is an issue. We are constantly advertising to our customers that we are moving to API-based integrations and that the future of our product is being able effectively use our product without a user interface, and yet the management team is okay with four GET endpoints not being shipped in six months.
The next set of API endpoints we have in our backlog are write operations based on the Strangler Fig design pattern [1] using our existing stored procedures with a thin API wrapper around them. I can only imagine that if four GET endpoints have taken over six months to ship, that this is going to take an order of magnitude longer time, especially since our development team hasn't had to deal with things like concurrency and idempotency before.
The next set of API endpoints we have in our backlog are write operations based on the Strangler Fig design pattern [1] using our existing stored procedures with a thin API wrapper around them. I can only imagine that if four GET endpoints have taken over six months to ship, that this is going to take an order of magnitude longer time, especially since our development team hasn't had to deal with things like concurrency and idempotency before.
[1] https://learn.microsoft.com/en-us/azure/architecture/pattern...