{"id":6822,"date":"2017-01-14T21:10:57","date_gmt":"2017-01-14T21:10:57","guid":{"rendered":"https:\/\/itnigblog.live-website.com\/?p=6822"},"modified":"2020-06-11T13:12:56","modified_gmt":"2020-06-11T13:12:56","slug":"better-code-structure-working-with-pods","status":"publish","type":"post","link":"https:\/\/itnig.net\/blog\/better-code-structure-working-with-pods\/","title":{"rendered":"Better code structure: working with pods"},"content":{"rendered":"

Usually we organize our javascript apps either by what they are or by what they do. The first is like rails: separate directories like\u00a0components<\/code>,\u00a0containers<\/code>,\u00a0reducers<\/code>, etc. And the second more or less like feature\/DDD:\u00a0user<\/code>,\u00a0cart<\/code>, and so on. Tho both of these options are very mainstream and solid they contain some constraints.<\/p>\n

When you structure the code files tree\u00a0by what they are<\/strong>\u00a0you tend to keep every component of the same feature so distant that it\u2019s very\u00a0difficult to connect\u00a0<\/strong>the pieces. Therefore you dive into some troubles like the path hell; a lot of\u00a0require('..\/..\/..\/etc')<\/code>\u00a0in your code. And everything is extremely coupled to the directory structure.<\/p>\n

In the other hand, when you are driven\u00a0by what they do<\/strong>\u00a0everything is more isolated and maintainable. But there\u2019s\u00a0a lot of duplication<\/strong>.\u00a0<\/strong>And the\u00a0communication<\/strong>\u00a0between the features either is\u00a0based on a weak contract<\/strong>\u00a0or\u00a0depends upon some infrastructure<\/strong>. Both of these options are prone to raise some bugs.<\/p>\n

Pods it\u2019s an evolution of the last one.\u00a0You can think about pods like the microservices of the front applications<\/strong>. A pod is an isolated and completely independent microapp which can communicate 100% with other pods. Therefore, you get code base which is\u00a0composable, extendable, reusable<\/strong>and extremely\u00a0easy to test<\/strong>. Tho, the main benefit is that you completely erase the inter components side effects. Once a pod is failing you are totally sure that it\u2019s because itself has something wrong; not an external piece.<\/p>\n

A pod is an isolated and completely independent microapp which can communicate 100% with other pods<\/p><\/blockquote>\n

The\u00a0unique requirement<\/strong>\u00a0of the pods is to driven all the pods intercommunication through an\u00a0event bus<\/strong>. If you\u2019re already using any Flux pattern, lib or framework it\u2019s gonna be very easy to lead this communication to the dispatcher; which is actually a single point for the events.<\/p>\n

For a pod is not mandatory to have the logic, presentational and communication layers.\u00a0Can have all of just one of them<\/strong>. Imagine a router pod. It has the logic and communication layer but doesn\u2019t expose any view. Or the opposite, a form pod which only exposes a presentational layer and depends 100% on the arguments received (see React\u00a0props<\/code>).<\/p>\n

Because every pod acts like and independent application we place the\u00a0tests inside them<\/strong>. This means two things:\u00a0stop duplicating the files tree<\/strong>, and making\u00a0code coverage meaningful<\/strong>. When you have 100% coverage with a pod you know that it won\u2019t fail. No side effects.<\/p>\n

In a nutshell, by working with pods you get a\u00a0secure and very flexible structure<\/strong>. Very\u00a0easy to test<\/strong>\u00a0and\u00a0without side effects<\/strong>. It scales from 0 to millions without worrying about big refactors due to the fact that\u00a0every pod is<\/strong>\u00a0isolated but available to communicate<\/strong>\u00a0with all the other pods.<\/p>\n

In case you want to see some code here\u2019s a\u00a0Github repository<\/a>\u00a0with a simple pod architecture. Give it a look and check the benefits the pods can offer. If you have some doubts or proposals don\u2019t hesitate to open an issue or comment here. This is a living pattern. We\u2019re using the pods at\u00a0Ulabox<\/a>\u00a0and they\u2019re proving to be the solution to a lot of structural codebase problems. Tho, we\u2019re willing to listen about your thoughts and concerns.<\/p>\n

The journey is long, take some pods.<\/p>\n","protected":false},"excerpt":{"rendered":"

Usually we organize our javascript apps either by what they are or by what they do. The first is like rails: separate directories like\u00a0components,\u00a0containers,\u00a0reducers, etc. And the second more or less like feature\/DDD:\u00a0user,\u00a0cart, and so on. Tho both of these options are very mainstream and solid they contain some constraints. When you structure the code […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10],"tags":[],"class_list":["post-6822","post","type-post","status-publish","format-standard","hentry","category-technology"],"_links":{"self":[{"href":"https:\/\/itnig.net\/blog\/wp-json\/wp\/v2\/posts\/6822","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/itnig.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/itnig.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/itnig.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/itnig.net\/blog\/wp-json\/wp\/v2\/comments?post=6822"}],"version-history":[{"count":1,"href":"https:\/\/itnig.net\/blog\/wp-json\/wp\/v2\/posts\/6822\/revisions"}],"predecessor-version":[{"id":9626,"href":"https:\/\/itnig.net\/blog\/wp-json\/wp\/v2\/posts\/6822\/revisions\/9626"}],"wp:attachment":[{"href":"https:\/\/itnig.net\/blog\/wp-json\/wp\/v2\/media?parent=6822"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/itnig.net\/blog\/wp-json\/wp\/v2\/categories?post=6822"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/itnig.net\/blog\/wp-json\/wp\/v2\/tags?post=6822"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}