<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ido Glikman on Medium]]></title>
        <description><![CDATA[Stories by Ido Glikman on Medium]]></description>
        <link>https://medium.com/@ido.glikman?source=rss-b8ce77e00994------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*oT_-njHaQC8Na1SMQJqMCg.jpeg</url>
            <title>Stories by Ido Glikman on Medium</title>
            <link>https://medium.com/@ido.glikman?source=rss-b8ce77e00994------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 09:55:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ido.glikman/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Our Journey in Angular: from Ngrx to Akita]]></title>
            <link>https://medium.com/datorama-engineering/our-journey-in-angular-from-ngrx-to-akita-9b70b3d7ea70?source=rss-b8ce77e00994------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b70b3d7ea70</guid>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[ngrx]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[redux]]></category>
            <dc:creator><![CDATA[Ido Glikman]]></dc:creator>
            <pubDate>Tue, 21 Aug 2018 11:44:08 GMT</pubDate>
            <atom:updated>2018-08-21T11:44:08.499Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k-uybBsKEbuivPf4ioVrVw.png" /></figure><h3>Introduction</h3><p>I’m Ido Glikman, front-end tech leader at Datorama. A few weeks ago I gave a lecture here in Israel in which I presented Akita and talked about why did we decide to develop a state manager of our own.</p><p>The lecture was in Hebrew, and I thought, why not write it up in English so that more people can be exposed to it and get insights from the things that we had experienced, so let’s begin.</p><h3>The Product Evolution</h3><p>When we just started developing our client-side, we wrote it in vanilla Javascript, without the use of components or a state manager. We quickly realized that we needed to upgrade the system and start using more advanced concepts and techniques.</p><p>We decided to go with Angular combined with ngrx which was the most recommended solution at the time, and likely the only one.<br>We started our journey with ngrx and very quickly discovered we were in for an adventure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/0*6O0xDFyqDzZsQ0wI" /><figcaption>THE JOURNEY TO NGRX WAS A BUMPY RIDE</figcaption></figure><h3>What we Experienced in ngrx</h3><h4>Steep learning curve</h4><p>I can testify for myself that as a developer first exposed to the world of redux, I had difficulties learning and connecting all the dots in order to create the smallest of features.</p><h4>Boilerplate</h4><p>A point I think that anyone who works or worked with ngrx experiences every day. To build even the smallest feature, you have to create so many things like reducers, effects, actions, actions creators, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SuqGOYUS9IkIOKxp20Kc1w.png" /><figcaption>LEARNING CURVE + BOILERPLATE</figcaption></figure><h4>Functional Programming Mindset</h4><p>ngrx similarly to redux tends to use functional programming, which I felt made it harder for programmers from other worlds like Java to join in the development and “feel at home”.</p><p>And this is how we felt at that period.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*L0oYNhvll3Fa7F_H" /></figure><p>All the above things led us to the conclusion that we need to develop a state manager that will be a comprehensive answer to all of our needs with a future thought on community needs. This is how Akita was born.</p><h3>Akita in <a href="https://datorama.com/">Datorama</a></h3><p>We will start by saying that behind Akita there is a company — Datorama. Datorama invests and pays us, the developers, to improve Akita and make it better for us and also for the community, and this is the way for us to give back to the community for all that it gives us.</p><p>Another thing is before we released it to the community, Akita was in internal use here for over six months, meaning that it passed all of the processes of tests, bugs, feature requests, etc.</p><p>The last thing is, our product is a big data product . We have vast amounts of data in the client, and Akita handles it amazingly.</p><h3>What is Akita</h3><p>Akita is a state management pattern built on top of RxJS. <strong>Akita encourages simplicity</strong>. It saves you the hassle of creating boilerplate code and offers powerful tools with a moderate learning curve, <strong>suitable for both experienced and inexperienced developers alike.</strong></p><p>Akita is based on object-oriented design principles instead of functional programming, so <strong>developers with OOP experience should feel right at home.</strong> Its opinionated structure provides your team with a fixed pattern that cannot be deviated from.</p><h3>Akita’s Architecture</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rOrBU265jPqcjUMzH0fz_g.png" /><figcaption>Architecture</figcaption></figure><p>The two main components of Akita are the store and the query. You can think of the store like a table that contains data in a database, and you can perform various actions on it like inserting, updating, etc.</p><p>In addition to the Store, there is the Query, which is our way to request data from the store. Queries can talk with other queries, perform a “join” between them to create a more complex query, etc.</p><p>The component reactively gets the data from the query. We believe that the component doesn’t need to know its data source, so we recommend not to inject the store inside components, but have store updates pass through service.</p><p>This is how we get to a one-way data flow with a precise architecture that you can’t deviate from.</p><h3>The <a href="https://netbasal.gitbook.io/akita/entity-store/entity-store">Store</a></h3><p>The basic store can contain any form of data that you would like, but in most cases, you would prefer working with an entity store. You can think of an entity store as a table in a database where each row represents an entity.</p><p>Akita entity stores give you all the tools you need to manage the store easily, for example inserting, updating and deleting entities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tW7IyoC2VsqTbBUQJ5jsfA.png" /></figure><p>So how do we create a store? Very easy — inheritance. Extend the super and get all that you need. For example, crud operations, active entity management, error management, showing “loading” while data loads and more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*buGIjinpVVxfXhH4mf7AVw.png" /></figure><h3>The <a href="https://netbasal.gitbook.io/akita/entity-store/entity-query">Query</a></h3><p>The Query is my favorite part of Akita, and it’s our way to get data from the store. Like the store, it has two types: query for basic stores, and query for entity stores.</p><p>You can classify the query methods into two types. A method that starts with select, for which you will get an observable for the requested data, and methods that start with get, in which you will get the requested data in a one-time, direct way.</p><p>It’s important to emphasize that the subscription won’t be triggered unless the value you asked is changed by reference.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mhp0KIV7SS7KAOTGEJtfeQ.png" /></figure><p>So how do we create a query? Like the store, inherit the super and get all that you need.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vhLMuLWh4DjBvo3S_OAkNg.png" /></figure><h3>Additional functionality</h3><h4>Plugins ecosystem</h4><ul><li><a href="https://netbasal.gitbook.io/akita/plugins/server-side-pagination">Server Side Pagination</a></li><li><a href="https://netbasal.gitbook.io/akita/plugins/state-history">State History</a></li><li><a href="https://netbasal.gitbook.io/akita/plugins/persist-form">Persist Forms</a></li><li><a href="https://netbasal.gitbook.io/akita/plugins/dirty-check">Dirty Check</a></li></ul><h4>Redux dev-tools</h4><p>Akita provides integration with the redux <a href="https://netbasal.gitbook.io/akita/enhancers/devtools">dev-tools</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Df9Yu63Rz8gUP13u4N_U-Q.gif" /></figure><h4>Angular Schematics</h4><p>Whether you want to add Akita to your application or you’re already using it, you can use <a href="https://netbasal.gitbook.io/akita/entity-store/angular-schematics">schematics</a> to streamline the generation of Akita features.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*dWd9sRGw4dutAwC5FmghIQ.gif" /></figure><h4>Store enhancers</h4><ul><li>Snapshot Manager — save the whole application state as a JSON</li><li>Persist State — automatic stores sync into the local storage</li></ul><h3>Akita in the Future</h3><ul><li>We’ll continue to add features and develop plugins.</li><li>It’s important to say; your bug is our bug. Akita is with us in production, and it’s crucial for us to solve any bug you find ASAP.</li><li>Right now Akita is oriented towards Angular, but it’s important to emphasize that there is no coupling between Angular and Akita, and we will try to see how it can integrate together with other frameworks like React or Vue.</li><li>There is already a significant amount of articles focusing on Akita, of course, we will continue to invest in the subject and create more like these.</li></ul><p>Here is an excellent <a href="https://netbasal.gitbook.io/akita/entity-store/blog-posts">content</a> that dives into code:</p><ul><li><a href="https://netbasal.com/introducing-akita-a-new-state-management-pattern-for-angular-applications-f2f0fab5a8">🚀 Introducing Akita: A New State Management Pattern for Angular Applications</a></li><li><a href="https://engineering.datorama.com/building-a-shopping-cart-in-angular-using-akita-c41f6a6f7255">👷 Building a Shopping Cart in Angular Using Akita</a></li><li><a href="https://netbasal.com/working-with-normalized-data-in-akita-e626d4c67ca4">Working with Normalized Data in Akita and Angular</a></li><li><a href="https://engineering.datorama.com/the-complete-guide-to-authentication-in-angular-with-akita-dc1b343f7e71">The Complete Guide to Authentication in Angular with Akita</a></li><li><a href="https://engineering.datorama.com/i-built-the-ngrx-demo-app-with-akita-heres-the-result-57f83fe92192">I Built the Ngrx Demo App with Akita. Here’s the Result.</a></li><li><a href="https://netbasal.com/infinite-scroll-in-angular-using-akita-c5edf51de4ed">Infinite Scroll in Angular Using Akita</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rwnz66mRvEnntcIkTOnmYA.png" /><figcaption>Cheers</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b70b3d7ea70" width="1" height="1" alt=""><hr><p><a href="https://medium.com/datorama-engineering/our-journey-in-angular-from-ngrx-to-akita-9b70b3d7ea70">Our Journey in Angular: from Ngrx to Akita</a> was originally published in <a href="https://medium.com/datorama-engineering">Datorama Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>