- If you are using Kafka to capture large quantities of events or transactional data, you are probably also looking for ways to enrich that data in real-time. Here is how to do it with TinybirdRead more...
- What do you do when your transactions table in postgres has grown way too big to handle analytical queries? How do you answer business questions when it could take minutes to even get a `SELECT count(*) FROM transactions` going?Read more...
- How to create an analytics API that deals with billions of rows in a matter of minutes.Read more...
Last April we had the pleasure to host the ClickHouse meetup in Madrid. Altinity’s team normally organize meetups in different cities where local developers talk about their experiences using the technology, to later have a session about the ClickHouse roadmap by Yandex and Altinity. As you might noted already, we are huge fans of ClickHouse (the core of Tinybird Analytics) and it’s awesome to be able to talk to the people behind the technology.
Time series predictions are one of the most common use cases you can find. Predicting the future, enables you to get ready for it (and act accordingly) so, as you would expect, it is something every company would love to do. Good news is that there are many methods to do it: from sophisticated Machine Learning algorithms or advanced forecasting libraries like prophet to simpler approaches based on simpler statistical foundations, like the one we describe below.
Typical challenges of building your data layer. Things we've learnt from dozens of growing companies
When you start a digital product you usually put your data in a database. It does not matter if it is a simple text file, an excel spreadsheet or a managed Postgres instance on the cloud, your data always lives somewhere. Data has been a key component of any digital product for a long time now, but it hasn’t been until recently that we’ve started to devote significant resources to aggregating and making use of it. Even if you think you are devoting enough energy to data within your organization, most probably you aren’t.