Valentina Manea

Redis has officially returned to open-source licensing with the release of Redis 8 under AGPLv3, marking a significant shift from the controversial SSPL licence that divided the community for years. The decision represents a victory for open-source advocates, driven by internal discussions at Redis and the recognition that SSPL failed to gain acceptance from both the Open Source Initiative and the broader software community. Why This Matters for Rails Developers: 🔹 Redis remains the most popular caching and session store for Rails applications 🔹 AGPLv3 provides clearer licensing terms than the ambiguous SSPL 🔹 Open source status ensures continued community contributions and ecosystem growth 🔹 Rails developers can confidently build on Redis without licensing concerns 🔹 Vector Sets data type and other Redis 8 features are available under true open source terms Redis creator Antirez played a key role in advocating for the licence change, expressing his commitment to writing open source software and ensuring his new Vector Sets implementation would be truly open. His influence helped build internal momentum for the switch across the Redis company hierarchy. Rails applications heavily rely on Redis for caching, background job processing with Sidekiq, and session management. The return to open source licensing removes the uncertainty that enterprise Rails teams faced when evaluating Redis for new projects. Redis 8 also brings performance improvements and new features alongside the licensing change, reinforcing Redis's position as the go-to data structure server for modern web applications. What role does Redis play in your Rails application architecture? We're connecting with Rails developers who understand distributed caching and performance optimisation strategies. #Redis #OpenSource #RubyOnRails #CachingStrategy #TechRecruitment

5

If you fancy a change of pace from the latest blog on AI incantations, we've written about - what I think is - a nice pattern for our Rust AWS Lambdas. https://lnkd.in/ejwc4RqC

8

How do you convince an organization to let automation manage Kubernetes workloads at scale? Yasmin from CloudBolt explains why the real challenge isn't the tooling — it's building enough trust to act on it. Data points, guardrails, preview modes, rollout gates. "You can only go as fast as the speed of trust." Watch the full interview: https://ku.bz/bvr2-nv4P Meet the CloudBolt Software team at Booth 438 at KubeCon Europe 2026 in Amsterdam 👉 https://ku.bz/5pwF68l6Q

36

As always the Kroxylicious team are very pleased to announce the release the 0.19.0 release (https://lnkd.in/e5sRC4EU). Kroxylicious will now bite down on Kafka 4.2 RPC calls, snack on idle connections and other quality of life improvements.

19

2 Comments

Your CI/CD bill is not exploding because of “expensive runners,” it is bleeding out through flaky tests, over-parallelized jobs, and slow feedback loops that quietly tax every deploy This piece shows you how to redesign pipelines so you cut compute waste, shrink queues, and speed up developer flow without adding yet another approval gate or YAML religion Full breakdown in the comments. #DevOps #CICD #PlatformEngineering

8

1 Comment

Excited to share blog I wrote at Addepar on using jOOQ for more precise, SQL-first database interactions. At scale, moving away from heavy ORM abstractions helped us gain better control, predictability, and performance. Would love to hear how others are approaching this trade-off. #SoftwareEngineering #BackendDevelopment #Java #jOOQ #DatabaseDesign #SystemDesign #TechEngineering

36

1 Comment

JSON-structure is a modern practical alternative or replacement for JSON-Schema by Clemens Vasters - it's a draft IETF standard and the SDK now includes a Perl implementation after some not so gentle nudging. Clemens has been enthusiastically responsive to feedback and knows his stuff, if you're working with JSON and Perl (or other languages) this is well worth taking for a spin and sending any bug reports or suggestions.. code is at https://lnkd.in/e5fZvw_F and I'm looking forward to seeing the perl library on cpan shortly. #JSON #perl #javascript

8

I've been doing some research lately into the Model Context Protocol (MCP), and how to build MCP enabled products at scale. As part of my research into the protocol, I wanted to get a good understanding of how it operated at the network level. `tcpdump` was really handy for this, and I've written up a blog post about how I used it to inspect MCP traffic at the network level to understand the "nuts and bolts" of the client/server communication. If you're interested in doing the same, you can find the write-up here: https://lnkd.in/eVyakGpM #mcp #tcp #ai #debugging

42

2 Comments

New blog post on progress in directed graph hashing. Here I discuss the new concept of directed graph language, which is very similar to DFAs/NFAs: https://lnkd.in/eazxiQUN

13

1 Comment

At the weekend, I published a new write-up on squeezing even more performance out of static sites built with Eleventy and deployed on Cloudflare ✨ In this latest post, I take the idea of compression further by pre-compressing HTML to the highest Brotli level (11) at build time and serving it at the edge via a Cloudflare Worker instead of relying on on-the-fly compression. Why it matters: • Even small edge gains matter at scale – smaller HTML means faster Time to First Byte and quicker overall loads.  • Pre-compressing during the Eleventy build shifts compute away from the edge and into your deployment pipeline.  • A lightweight Cloudflare Pages Function does smart content negotiation so browsers that support Brotli get the most efficient assets. I walk through how this works, the quirks of serving pre-compressed HTML alongside normal files, and how it fits into a modern edge-centric deployment. If you care about taking static site performance that extra mile, this might be worth a look. https://lnkd.in/e5iM62Sh

20

4 Comments

The UK wanted a digital strategy. We were just gifted one: Offer a visa to everyone in tech who currently holds a H-1B. Decision in a week. All the top companies have a UK presence already, and it would net us tens of thousands of excellent people who have trained at the best companies. "Opportunities come infrequently. When it rains gold, put out the bucket, not the thimble" - Warren Buffet

123

23 Comments

🚀 Visualizing Flows with Sankey Traces Ever wondered how to clearly show how inputs flow into processes and branch out into outputs? That’s where Sankey diagrams shine. 🔹 Sankey traces map flows between nodes with widths proportional to their magnitude. 🔹 matplotlib has very limited support — but Plotly makes it interactive and powerful. 🔹 All you need: define nodes, links, and values, then build the diagram in a few lines of code. I’ve shared a step-by-step guide (with code from my GitHub notebook ) to walk through the process. 📊 Perfect for customer journeys, process flows, or resource transfers. 👉 Check out the full blog post for details! - https://lnkd.in/gGXucm-9 or https://lnkd.in/gBcrUE3h

28

3 Comments

What kind of guidance does an LLM need to write a direct-style #Scala 3 application? At the baseline - not a lot, e.g. Claude is quite good both in Scala 3 & direct-style. For finer details - some additions to the prompt might be useful. Read more: https://lnkd.in/dxwy-WdD

20

5 Comments

Most in-depth technical walkthrough of KIP-1150 What Diskless Topics (KIP-1150) - Diskless Topics = no local broker disk for user data. Instead, data is written directly to cloud object storage (e.g. S3, GCS).  - Cost savings are dramatic — up to 80% reduction in TCO (storage + cross-zone network costs) for many cloud-deployed Kafka clusters.  - Instant elasticity & autoscaling: since data isn’t pinned on brokers, you can scale brokers up or down quickly without rebalancing data segments or copying logs. #ComputeStorageSeparation #DecoupledArchitecture #CloudNativeData #StreamingArchitecture #ScalableDesign #ModernDataInfra #DataEngineering #DistributedSystems

2

Exciting to see the Arm ecosystem continue to expand with news of their latest partnership with Octopus Deploy. Together Arm and Octopus are working together to transform how developers build, test, and deliver software. By bringing Arm-based infrastructure into Octopus’ unified delivery platform, teams can manage deployments across architectures seamlessly—improving reliability, accelerating time to market, and enabling true multi-architecture agility. It’s an important collaboration that empowers developers to focus on innovation rather than infrastructure! 💪 https://okt.to/wESlo2

4

CAP trade‑offs don’t start in theory class; they start the moment your data leaves a single SSD and has to be agreed on across a network. ​ In Part 2 of “The Physics of Databases”, I break databases into two layers—the local storage engine vs the distributed consensus protocol—and show how the same LSM‑Tree can behave very differently in Cassandra vs Spanner depending on how the network is wired. ​ The post also brings together popular databases (Postgres, Spanner, DynamoDB, Cassandra, Bigtable, Cosmos DB, HBase, BigQuery/Snowflake) into an information‑rich comparison, showing how their storage + consensus choices should shape your primary keys and data‑modelling strategy. ​ 🔗 Read Part 2: The Physics of Databases – The “Two‑Layer” Secret to Navigating the CAP Theorem ​ Link in the comment section👇 💬 I’d love to learn from your side: What stories or hard‑won lessons do you have from choosing between “availability first” vs “consistency first” databases in real systems—and how did those decisions show up later in production or during incidents?​ #SystemDesign #Databases #DistributedSystems #CAPTheorem #StorageEngines #Cassandra #Spanner #Scalability #BackendEngineering #Architecture

5

1 Comment

✨✨✨ We have been working with Michal Klein at Apple MLR on pushing a module to train *flow matching* models using JAX. This is shipped as part of our new release of the OTT-JAX toolbox (https://lnkd.in/etJYGjPv) We do so by also introducing the two changes we advocated over the summer to improve FM training, using either (very) large sharp Sinkhorn couplings (https://lnkd.in/eJ6DnF-U) or, even better and efficient, using our semidiscrete coupling approach (https://lnkd.in/e2aBg27a), proposed with Alireza Mousavi-Hosseini and Stephen Zhang. The tutorial to do so is here: https://lnkd.in/e-BAVejK The tutorial doesn't cover yet the conditional FM problem, but the code does, so give it a try, and as always, we welcome your feedback!

205

2 Comments