Over the last year, all the new software components delivered by our software engineering teams have exposed HTTP standard REST APIs. This choice gave us a lot of benefits in terms of modularization and cooperation from an architectural point of view. But, we also had to learn new tools and practices in order to share documentation, design software solutions, and manage the evolution of our services.
We write private APIs (no need to deal with a public API portals or API economies). We also recently decided to adopt an open source solution based on Swagger tooling (I think there’s no need to introduce it or justify the choice in this post, there’s a lot of very well written stuff out there). https://goo.gl/hi4iFX #DataIntegration #ML
Share this:
- Click to share on Facebook (Opens in new window)
- Click to share on Twitter (Opens in new window)
- Click to email a link to a friend (Opens in new window)
- Click to share on LinkedIn (Opens in new window)
- Click to share on Tumblr (Opens in new window)
- Click to share on Pinterest (Opens in new window)
- Click to share on Reddit (Opens in new window)