nodejs-bigquery VS streamlit

If you've ever wondered what it's like to manage a BigQuery instance at Reddit scale, know that it's exactly like smaller systems just with much, much bigger numbers in the logs. Database management fundamentals are eerily similar regardless of scale or platform; BigQuery handles just about anything we throw at it, and we do indeed throw it the whole book. Our BigQuery platform is more than 100 petabytes of data that supports data science, machine learning, and analytics workloads that drive experiments, analytics, advertising, revenue, safety, and more. As Reddit grew, so did the workload velocity and complexity within BigQuery and thus the need for more elegant and fine-tuned workload management.

Now I know I've got some data I could use, I now need to find a platform that I can use to analyse the data coming from the Forem API. I did consider some other pieces of software, such as Google BigQuery (with looker studio) and ElasticSearch (with Kibana), I ultimately went with OpenSearch which is essentially a forked version of ElasticSearch maintained by AWS. The main reasons are that I could host it locally for free (unlike BigQuery). I do have some prior experience with both elastic (back when it was called ELK) and OpenSearch, but my work with OpenSearch was far more recent, so I decided to go with that.

First, in one of our recent projects, we helped our client to run the cloud-based infrastructure of their entirely automated, real-time SEO platform. The solution rested in the safe familiarity of Google’s popular cloud-based data centres (i.e. Google Cloud Platform), whilst also making use of BigQuery — a serverless, multi-cloud data warehouse.

Bigquery as our data warehouse

This post in github thinks it may be an error in bigquery's backend.

A data warehouse is a specialized database that's purpose built for gathering and analyzing data. Unlike general-purpose databases like MySQL or PostgreSQL, which are designed to meet the real-time performance and transactional needs of applications, a data warehouse is designed to collect and process the data produced by those applications, collectively and over time, to help you gain insight from it. Examples of data-warehouse products include Snowflake, Google BigQuery, Azure Synapse Analytics, and Amazon Redshift — all of which, incidentally, are easily managed with Pulumi.

Google BigQuery

Streamlit (https://streamlit.io/)

Does it need to be live (i.e when database or underlying spreadsheet updates does it need to be reflected in real time on the dashboard) or are you ok with static display.

Live updating data is a pain I've messed around using javascript to force refresh html iframes on a timer. But I was never really satisfied with this. I've heard you can do things with websockets but that is starting to get too complicated for me (I'm not a programmer).

For static stuff one of the data scientists in my org pointed me to Streamlit (https://streamlit.io/) it's a python package I found very easy to use. Can easily combine SQL with CSV imports and display them all on one dashboard. Can use forms toggle butotns etc to control the display.

Note that there are many tools that make this easier/simpler to prototype, including chainlit, streamlit, etc… The backend API we built is amenable to interacting with them as well.

2.-Go to https://streamlit.io, log in, and create a new app from your GitHub repository.

Developed using Langchain and Streamlit technologies for enhanced performance.

Hello,

Have you ever seen the https://streamlit.io/ ? I think this is what you are looking for.

While building dashboards in Streamlit, I found myself really missing Buefy's (Bulma) modern web components.

Specially due to the inability to add new values to Streamlit's multiselect [1], some missing controls like a polished image carousel [2] or a highly customizable data table.

Long story short, we put together streamfy (Streamlit + Buefy) as an MIT licensed project in GitHub to bring Buefy to Streamlit.

Demo: https://streamfy.streamlit.app

All the form components are implemented, missing half of other non-form UX components. There is plenty of room for PRs, testing, feedback, documentation, example, etc.

Please send issues and contributions to GitHub project [3] and general feedback to X / Twitter [4]

Thanks!

[1] https://github.com/streamlit/streamlit/issues/5348

Here's your savior, let's welcome Streamlit.

Looks cool. How do you see this differing from streamlit? https://streamlit.io/

Imagine you have an AI-powered personal alerting chat assistant that interacts using up-to-date data. Whether it's a big move in the stock market that affects your investments, any significant change on your shared SharePoint documents, or discounts on Amazon you were waiting for, the application is designed to keep you informed and alert you about any significant changes based on the criteria you set in advance using your natural language. In this post, we will learn how to build a full-stack event-driven weather alert chat application in Python using pretty cool tools: Streamlit, NATS, and OpenAI. The app can collect real-time weather information, understand your criteria for alerts using AI, and deliver these alerts to the user interface.