Skip to main content

· 5 min read

One of the best things about JAMSTACK is that it is possible to provide searching the entire site with the search processing done entirely on the client. This is a big deal as there is no need for expensive servers to drive the search and more importantly it provides milliseconds latency for the users so they love to stay on the website for longer and explore.

Text search is an important part of data analysis and being able to do it entirely on the client is possible by projects like lunr. SQL Frames has integrated text search (thank you lunr). Use cases with examples are discussed below.

· 3 min read

Most data analysis workflows involve a) exploring data with ad-hoc reports b) identifying key metrics and trends c) creating dashboards consolidating important metrics and repeating the process.

Dashboards offer rich interactivity that single reports cannot and benefit the end users of the dashboards. But don't ad-hoc reports created during the data exploration stage also need dashboards for the same level of interaction? The problem with most analytics tools is that building dashboard is a ceremonial action that involves creating a new dashboard entity, giving it a name, determining the layout and then adding reports one by one and reordering with drag-n-drop all making it a lengthy process. Is there some way to make it extremely easy to create dashboards for ad-hoc reports as well with out all that extra baggage? The answer is yes, and I call it ad-hoc dashboards that are perfect in a low-code environment.

· 6 min read

These days most enterprise applications are delivered on the cloud as SAAS applications. There are also many low-code application development platforms that make it easy to create custom workflows and user experiences. However, even the big players in this space such as Salesforce, seldom provide powerful analytics. That is, we are not talking about simple reports but more advanced reports that actually can provide deeper insights. Wondering why? I will explain it with a few examples.

· 5 min read

It is common to pre-aggregate data to improve the performance of generating the reports. While pre-aggregation is in general a good technique, grouping of data by various dimensions and their permutations and time dimension and its various buckets including sliding windows can lead to explosion of pre-aggregated data. Hence the requirements should be carefully evaluated and in some cases it may be better solved using a technique called double aggregation, where data is pre-aggregated to the lowest level first and is then aggregated further as needed on-demand.

· 4 min read

Technologies like React have pushed the boundaries of web applications from each interaction is a separate page to the entire app being in a single page tremendously improving the user experience. These technologies also support server-side rendering making it possible to render the entire markup on the server. This helped to create next generation static site generators that leverage this wonderful Javascript technology and provide highly interactive web sites that are pre-rendered and generated making the entire site static to serve the content which can then become dynamic if needed on the client-side using JavaScript.

This resulted in a design paradigm called JAMSTACK for making websites and docs.