DEV Community: TaqsBlaze

SQL Isn't the Problem. Scientific Data Is.

TaqsBlaze — Fri, 17 Jul 2026 06:26:20 +0000

We don't have a database problem.

We have a scientific data problem.

Every day, researchers, engineers, startups, and small teams work with data that doesn't naturally fit into traditional databases.

One moment you're storing measurements in SQL.

The next you're exporting them to NumPy for computation, HDF5 for storage, PostGIS for spatial analysis, and Python scripts to glue everything together.

Before long, your "data pipeline" is a collection of disconnected tools that each solve one piece of the puzzle.

The database becomes just another stop in the pipeline instead of the platform where the work happens.

That question stayed with me for a long time:

What if the database itself understood scientific data?

That simple idea became FlamingoDB.

Databases were built for business. Not science.

Traditional databases are exceptional at storing:

Customers
Orders
Products
Transactions

They've transformed how businesses build software.

But scientific and engineering workloads have different needs.

Think about working with:

Multidimensional arrays
Vectors
Matrices
High-precision numerical types
Geospatial objects
Time-series measurements
Satellite imagery
Sensor streams
Experimental datasets

Most of these end up being serialized into JSON, stored as blobs, or pushed into separate tools because the database doesn't understand what they are.

The result?

More complexity.
More data movement.
More opportunities for things to go wrong.

A Different Philosophy

FlamingoDB isn't trying to replace PostgreSQL, MySQL, DuckDB, or any of the incredible databases we already have.

Those projects are excellent.

Instead, FlamingoDB asks a different question:

What if scientific concepts were first class citizens instead of extensions?

Imagine defining a table like this:

CREATE TABLE satellites (
    id INT,
    position VECTOR3,
    velocity VECTOR3,
    spectrum ARRAY<FLOAT64>,
    footprint POLYGON
);

No blobs.

No custom serialization.

No plugins.

Just native scientific data types.

SQL Already Won

One design decision was non negotiable.

I didn't want scientists, developers, or data engineers to learn another proprietary query language.

FlamingoDB speaks SQL.

If you know SQL, you already know how to query FlamingoDB.

The goal isn't to replace SQL.

It's to make SQL feel natural for scientific computing.

That lowers the barrier to entry dramatically, especially for startups and small teams that don't have the time or resources to train people on yet another language.

Making Advanced Data Processing Accessible

One thing I've learned from building software is that innovation shouldn't only be available to organizations with massive engineering teams.

A startup analyzing IoT sensor data.
A university research lab.
A GIS consultancy.
An environmental monitoring project.
A solo developer experimenting with machine learning.

They all face the same challenge:

Building and maintaining complex data pipelines is expensive.

FlamingoDB aims to simplify that.

Instead of stitching together multiple storage engines, analytics tools, and custom scripts, the vision is to provide a single platform where data can be stored, queried, processed, and analyzed.

Less infrastructure.

Less glue code.

Native AI in the Data Pipeline

AI is rapidly becoming part of every data workflow.

Today, integrating AI often means exposing databases to external services, writing custom middleware, managing credentials, and building security around every interaction.

I believe AI should be a native part of the database ecosystem not an afterthought.

That's why the upcoming FlamingoDB v1.3.0 "Plumage" introduces built in Model Context Protocol (MCP) support.

With a single interface, developers can securely connect models like:

ChatGPT
Claude
Gemini
DeepSeek

But connectivity alone isn't enough.

FlamingoDB introduces fine grained security policies that can be assigned to both users and AI models, ensuring every model only accesses the data it's explicitly permitted to see.

The goal is simple:

Bring AI closer to the data while keeping security and governance at the core.

Why Go?

FlamingoDB is written in Go.

Not because it's fashionable.

Because it offers:

Excellent performance
Simple, maintainable code
Powerful concurrency
Fast compilation
Easy deployment as a single binary

Building a database is hard enough.

The implementation language should help reduce complexity, not add to it.

Building in Public

FlamingoDB is still early in its journey.

Every release teaches me something new about storage engines, query processing, scientific computing, and building reliable software.

That's exactly why I'm building it in the open.

The best ideas rarely come from working in isolation they come from conversations, code reviews, and people asking difficult questions.

If FlamingoDB succeeds, it won't just be because of the code.

It will be because a community helped shape it.

Looking Ahead

The vision for FlamingoDB isn't simply to become another SQL database.

It's to become a platform where structured data, scientific computing, geospatial analytics, and AI powered workflows come together in a way that's approachable, secure, and practical.

Whether you're a solo developer, a startup building the next data driven product, or a research team processing terabytes of scientific data, I want FlamingoDB to remove complexity not add to it.

We're only getting started, and that's the most exciting part.

If this vision resonates with you, I'd love to hear your thoughts, ideas, or even your skepticism. The best engineering projects are built through collaboration, and FlamingoDB is no exception.

Let's build a database that doesn't just store scientific data it understands it. 🦩

the github repo: GitHub

Help with Electron ICP and Vue3

TaqsBlaze — Fri, 11 Jul 2025 09:28:25 +0000

Hi everyone
I'm working on a electron application and I'm implementing software update check which is making use of ICP now this worked perfect before and all of a sudden stopped working, no error, no exception no thing just silently failing

here are snippets of the code

preload.js:

checkForUpdates: () => ipcRenderer.invoke('check-for-updates'),
  onUpdateStatus: (callback) => ipcRenderer.on('update-status:available', callback),
  onNoUpdate: (callback) => ipcRenderer.on('update-status:no-update', callback),
  onUpdateError: (callback) => ipcRenderer.on('update-status:error', callback),

main.js

ipcMain.handle('check-for-updates', async (event) => {
  try {

    const updateInfoUrl = 'url to update info';


    const updateInfoResponse = await fetch(updateInfoUrl);
    if (!updateInfoResponse.ok) {

      throw new Error(`Failed to fetch update info: ${updateInfoResponse.statusText}`);
    }
    const updateInfo = await updateInfoResponse.json();


    const currentAppVersion = app.getVersion();
    const latestVersion = updateInfo.version;
    const appName = `AppName${latestVersion}.exe`;
    const downloadUrl = `${updateInfo.downloadUrl}${appName}`;


    if (latestVersion > currentAppVersion) {
      try {
        let data = { version: latestVersion, downloadUrl: downloadUrl };
        console.log('Main Process: Sending update-status:available with data:', data);
        if (event.sender && !event.sender.isDestroyed()) { // Check if sender is still valid
          event.sender.send('update-status:available', data);
          console.log(`Main Process: Message 'update-status:available' sent successfully to sender ID ${event.sender.id}.`);
        } else {
          console.warn('Main Process: Could not send message. Renderer sender is destroyed or invalid.');
        }
        console.log(`Update version ${latestVersion} available. User will be prompted for manual download.`);
      } catch (error) {
        console.log(`Error sending update-status:available:: ${error.message}`);
      }
    } else {
      event.sender.send('update-status:no-update');
      console.log('No update available.');
    }
    return { success: true };
  } catch (error) {

    event.sender.send('update-status:error', error.message);
    return { success: false, error: error.message };
  }
});

app.js: (in mountent)

window.electronAPI.onUpdateStatus((data) => {
                    console.log('Update available:', data);
                    this.updateAvailableVersion = data.version;
                    this.updateDownloadLink = data.downloadUrl;
                    this.showUpdateModal = true; // Show the new update notification modal
                    this.updateStatusMessage = `New version ${data.version} is available!`;
                    this.updateErrorMessage = ''; // Clear any previous error messages
                });

(method triggering checking update)

async checkForSoftwareUpdates() {
            console.log('checking for updates....')
            this.updateStatusMessage = 'Checking for updates...';
            this.updateErrorMessage = '';
            this.showUpdateModal = false;
            this.updateAvailableVersion = null;
            this.updateDownloadLink = null;
            this.lastUpdateCheck = new Date().toLocaleString();

            if (window.electronAPI && window.electronAPI.checkForUpdates) {
                console.log("Cheking now...")
                await window.electronAPI.checkForUpdates();

            } else {
                console.warn('Electron API or checkForUpdates method not available. Cannot check for updates.');
                this.updateErrorMessage = 'Update check not available in this environment.';
            }
        },

If anyone can assist/point out what I'm doing wrong please
if the listener in mounted is triggered I should see a modal with new software update details and a download button which I currently do get but this was working fine previously

My 2024 Review: A Year of Growth and Innovation

TaqsBlaze — Sat, 28 Dec 2024 13:31:00 +0000

As the year draws to a close, I find myself reflecting on the milestones, challenges, and lessons that have defined 2024. It has been a year of relentless curiosity, technical exploration, and significant growth both personally and professionally. From diving deeper into cybersecurity to leading exciting development projects, here’s a look back at the journey.

Cybersecurity Adventures

Cybersecurity remained a cornerstone of my work in 2024. Whether it was through research, tool development, or contributing to discussions in the field, I continuously sought ways to make systems safer.

One of my proudest moments was conceptualizing and developing ReqWeb, my Web Application Firewall (WAF) project. This tool is designed to make web applications more secure by focusing on IP filtering, rate limiting, and intelligent request blocking. Seeing it evolve to the point where version 2.0 is almost ready has been incredibly rewarding.

Beyond ReqWeb, I deepened my understanding of penetration testing and network security, further solidifying my commitment to building a safer internet.

Building Cool Projects

This year also gave me opportunities to bring ambitious ideas to life. Some of the highlights include:

Flight Simulation System: I combined Python, Blender, and the Godot Engine to create a system that mimics basic flight physics with stunning weather effects and day-night cycles. This project not only challenged my technical skills but also reignited my passion for merging creativity with code.
Electricity Load Shedding Tracker: Living in a region where load shedding is common, I wanted to help people stay informed. This project combines Vue.js, Leaflet.js, and MongoDB to track and update load-shedding schedules, making it easier for users to plan their lives.
Cybersecurity Multiplayer Game: I started working on a web-based multiplayer game where players protect and upgrade their digital networks while competing to outsmart others. It’s an educational and fun way to engage with cybersecurity concepts.

Pushing Boundaries in Development

As a self-taught developer, every year is an opportunity to learn something new, and 2024 was no different. I honed my skills in Python, JavaScript, and Vue.js, while also exploring new frameworks and tools like Flask, TailwindCSS, and Express.js.

Notable achievements included:

Successfully transitioning ReqWeb to use Vue.js for its web interface.
Building the backend for a trucking marketplace, combining Python and Flask with Vue.js to create a seamless user experience.
Developing a session utility and refining ORM integrations for better database efficiency.

Looking Ahead to 2025

As exciting as 2024 has been, the journey is far from over. For 2025, I’m looking forward to:

Scaling ReqWeb to support distributed systems and deploying its version 2.0.
Expanding my work on the flight simulation system, incorporating more realistic physics and AI for pilot training.
Continuing to write and share my journey on LinkedIn, inspiring others to explore the world of technology and cybersecurity.

Final Thoughts

2024 was a year of resilience, learning, and creativity. It reminded me that progress often comes from stepping out of your comfort zone and embracing challenges. As I move into the new year, I’m grateful for the opportunities I’ve had and excited for what’s to come.

Thank you to everyone who’s been part of this journey—whether through collaboration, feedback, or simply following my updates. Here’s to an even more impactful 2025!

The Journey of ReqWeb: What’s Coming in Version 2.0

TaqsBlaze — Sat, 28 Dec 2024 13:07:16 +0000

When I started developing ReqWeb, my goal was simple: create a robust, lightweight Web Application Firewall (WAF) that anyone could use to protect their web applications. Over time, it has grown into a reliable solution, tackling challenges like IP filtering, rate limiting, rule based blocking, and logging with real time alerting. Now, the next big leap is here ReqWeb 2.0 is on the horizon, and it’s packed with exciting features to take security to the next level and w whole new dashboard and visuals enabling developers to visualize their applicans security and performance.

Reflecting on the Journey So Far
ReqWeb’s foundation was built on Express.js, chosen for its simplicity and scalability. Early on, the focus was on modularity, ensuring each component could function independently while still playing a role in the bigger picture. Features like seamless integration with external blackhole lists and real time alerting for suspicious activity have made ReqWeb a versatile tool for developers.

But the journey doesn’t stop there. The feedback, challenges, and lessons learned from the current version have inspired a new wave of innovation.

What’s Coming in ReqWeb 2.0?
Version 2.0 is not just an update it’s a transformation. Here’s a sneak peek at what’s in store:

Advanced Anomaly Detection
ReqWeb 2.0 will leverage machine learning to identify unusual patterns in incoming requests. This means smarter detection of zero day threats and evolving attack vectors, offering a proactive layer of security.
Enhanced Logging and Analytics
The new version will introduce a centralized logging system with detailed analytics. Users will gain insights into traffic patterns, blocked requests, and potential vulnerabilities through a clean, interactive dashboard.
Distributed Deployment Support
For businesses running multiple servers or microservices, ReqWeb 2.0 will support distributed deployments. This ensures consistent security policies across all instances while maintaining high performance.
Customizable Rules Engine
Version 2.0 will feature a revamped rules engine, allowing users to create highly specific rules for blocking or allowing traffic. Whether it’s based on geolocation, request headers, or custom parameters, you’ll have complete control.
Developer Friendly API
A new API will make it easier for developers to integrate ReqWeb into their workflows. Automate updates, retrieve logs, or manage configurations programmatically perfect for CI/CD pipelines.
Improved IP Reputation Management
Building on the external blackhole list integration, ReqWeb 2.0 will introduce dynamic IP reputation scoring. Threat levels will adjust in real-time based on behavior, reducing false positives while staying vigilant.

The Vision Moving Forward
ReqWeb 2.0 isn’t just about adding features it’s about creating a more intelligent, adaptive, and user friendly WAF. My vision is to empower developers and businesses with tools that make securing their applications intuitive and effective, regardless of their scale.

Final Thoughts
ReqWeb has come a long way, and version 2.0 is set to be the most significant milestone yet. By combining cutting edge technology with user feedback, I’m confident it will redefine what a modern WAF can do.

Stay tuned for the release of ReqWeb 2.0, and as always, your ideas and suggestions are welcome. Together, let’s build a safer web!

you can find the project on github here you can also install version 1.2.1 via npm/bun:

npm install reqweb@latest

My Dev Experience Season 1 Ep 2

TaqsBlaze — Mon, 25 Jul 2022 06:28:47 +0000

Continuing with my series....

2015 some guy reached out, he needed a website for some construction company
We agreed on the terms and I started working on the website
took me 3 days to build a demo as he had requested a demo site
and after that he requested me to work on the main website
gave me access to their hosting and cpanel then I started building the site, it took me 1 week to build the whole site

After the site was done.... It was time for the guy to pay up and it took almost 1 year for the guy to pay...in of which the payment never came through from the guy

Out of rage I logged in to the cpanel and deleted the whole project

This was my first experience with a client

My Dev Experience Season 1 Ep 1

TaqsBlaze — Thu, 21 Jul 2022 14:28:46 +0000

Hello World
I'm a 25 year old developer in a developing country Zimbabwe
I've always been a fan of technology being inspired by movies the likes of:

Iron Man
I-robot
Transformers
Matrix
Terminator and many more

I started learning coding when I was 18 years old that was back in 2015 my first actual OOP language I did was java after doing some basic HTML, CSS and a bit of JavaScript.

I wasn't really a Js fan and thought I would do away with without Js... as I did more and more of web dev I realized that I there was no escape from Js.
This then prompted me to switch to developing PC applications
Just as I was about to totally fall in love with java my laptop got stolen and went for a year without a laptop and then when I git another laptop... I had discovered python programming language
and fell in love with it that was in 2017
I've been a python developer ever since with a mix of C# and a little bit of Java

So basically I would say I'm a python developer at heart and also able to learn other languages as well. and I guess I find it very easy to learn new languages because before becoming a python developer I did a whole bunch of programming and scripting languages, trying to find the one I felt a connection with a list of languages I looked into where:

Php
c/c++
Ruby
Perl
shell
batch

I will be share my story to becoming a developer from being a total noob to being employed as a developer

Using network printer with python

TaqsBlaze — Wed, 24 Mar 2021 07:53:38 +0000

Hi guys so today I've decided to share my experience as I'm currently working on system

so I'm working on a system for centralizing data for an organization
so I got in and these guys didn't have any system or IT systems and I was tasked to build a system from the ground up

So I had to rename their machines for easy access across the network as default windows machine names are random something like DESKTOP-092N4

So after renaming this doesn't register across the network specially when printer drivers where installed before... so my program had to print using this network printer and it took me almost a week to get this working

Not that my code was wrong maybe that's why it took me so long to fix it... I thought the problem was code so my research was centered on code and everything was ok

So I then came across a snippet on the internet thankfully this was a bit detailed with comments as to what's going on
then something got my attention in this code a comment which described a step which wasn't in most examples and something that didn't cross my mind

in this particular snippet it explained setting a default printer win32print.SetDefaultPrinter("printer") so I then implemented this line in my code and finally I was able to use the printer on a network
Originally I was just setting a printer win32print.SetPrinter()
but this caused RPC error whenever I tried printing

Here is why I think it wasn't working:

Though I set the printer using new network path to the printer
\\server\printer this wasn't being used when initiating a print job... it would then use the old network path which is invalid now since I renamed the main PC connected to the printer
so the solution was to just set the default printer using new network path

DB Option

TaqsBlaze — Thu, 19 Nov 2020 07:40:22 +0000

Would like to know which is the best and easy to use database for nodejs + electron applications??

.NetX

TaqsBlaze — Sun, 24 May 2020 10:14:46 +0000

developing my own CLI tool for c# developing for running 1 liners and a module for shortening some system functions ( cut )