Post Category → Architecture

AI, Hype, and Real-World Value: My Takeaways from Indonesia Product Conference 2025

It was great to be back in the buzz of a proper tech conference last week. I headed over to the Indonesia Product Conference 2025, an event Apiary has been running for a while now, and it’s clear they keep leveling up. It feels like forever since we’ve had these big, in-person gatherings post-COVID, so the energy was palpable.

Unsurprisingly, the theme this year was AI. But what I found fascinating was the undercurrent beneath the massive GenAI wave. While the conference was certainly riding the hype, most of the speakers on the Growth/Main Stage were actually focused on the practical, real-world applications of “traditional” AI—like machine learning for recommendation systems—rather than just the latest generative models.

It was a refreshing dose of reality, and I walked away with a few key takeaways that I think are crucial for any product leader looking to adopt AI today.

Continue reading →

Redis use-cases aside from Cache

Redis can be more impactful aside from caching. Here are a few other use cases :
1️⃣ As a persistent storage for use cases like shopping carts, user profiles, and social-media-related posts/newsfeeds. Easily sorted set simply by ZRANGE
2️⃣ Tracking state with Bitmaps, easily track and get states with boolean logic with SETBIT and GETBIT
3️⃣ Location Based with Redis geospatial, easily search and add geospatial data with GEOADD & GEOSEARCH. AFAIK it’s quite tricky to do this with Postgre
4️⃣ Distributed Lock, i.e., updating inventory stock to handle flash sale traffic
5️⃣ Analytics Funnel with Probabilistic easily store event and or merge with the HyperLogLog
6️⃣ Simple event-driven architecture with Redis Stream or as a Pub/Sub with SUBSCRIBE/PUBLISH commands, which can be seen as a message queue even with LIST

reference: https://blog.bytebytego.com/p/redis-can-do-more-than-caching

On Evolutionary Architecture Book

Evolutionary Pokemon Architecture is good architecture that adheres to the fitness functions of the company; fitness function terms emphasized by the authors help to define what characteristics define good architecture.

The author’s discussion revolves around evolvable change, a change that has little to no breaking changes to the existing feature or integration, and implementation coupling leaks.

Continue reading →