Applying API LED arquitecture in DOMO

A lot has been talked about microservices type arquitecture, and the API led arquitecture introduced by mulesoft. After reading and studying a lot about it, and looking at the challenges we're facing in Domo, I have the feeling we could and should apply the same arquitecture within domo to organize Datasets.

The api led arquitecture for application integrations talks about creating different layers of abstraction between the different services, which allows for a lot more reuse, more flexibility and an agile methodology (pictures attached).

We had a problem last week integrating time and attendance information and sales information and we decided to create a simple diagram of different datasets one feeding the next, creating different abstraction layers, and creating a lot more modularity and reuse. After implementing it, we started thinking that this approach would benefit all of us going forward, and help organize the sheer number of datasets we have which are getting more difficult to manage.

 

Whats your view on this ?

 

image

 

image

Ricardo Granada 

[email protected]

**If the post solves your problem, mark it by clicking on "Accept as Solution"
**You can say "Thank you" by clicking the thumbs up in the post that helped you.

Comments

  • I will probably move this later to the Domo Developer board. Great summary!

     

    @ericpete @btm @Gavatar @product_John

     

    Who is on point for the Domo Developer conversations?

     

    Thanks!

  • Would love to hear your thoughts on this. And also, if you can, any other techniques you have to better organize and manage the increasing number of dataflows and datasets, and if you can, share with us what are the plans on the roadmap for this.

This discussion has been closed.