Adrian Cockcroft & The Pitbull

A new and interesting video by Adrian Cockcroft at AWS validates an approach we have had at Full 360. I like the way he describes the…

A new and interesting video by Adrian Cockcroft at AWS validates an approach we have had at Full 360. I like the way he describes the problem with monolithic databases. It’s something we’ve dealt with and built solutions to solve.

We have three components to our solution. The first is the structured data lake. In Cockcroft’s analogy, it is not the kitchen sink but the kitchen itself. Whatever kind of knife or spoon comes in, we have a cabinet for it. These are our built producers.

The second component is our database. Although we do all kinds of data management, we have our deepest experience in business intelligence and performance management. That means we are optimized for realtime queries on multidimensional models. So we’re experts at columnar databases. But we also backup websites and know a thing or two about NoSQL. In both cases we denormalize and get excellent performance. Additionally we decouple and optimize database ingestors and transformers. You can find details in our popular PITbull blog post.

The third component comes from our most demanding customers. They want their middleware to perform too. The old Java world doesn’t often cut it in horizontally scaling cloud architectures; after all that’s why Google invented and we build in Go. It’s not often that a systems integrator staffs developers that could build products but instead build applications for customers. That’s what we do. It keeps us on our toes.

These three components allow us to develop in ways that work well with containers and with new serverless architectures. That’s why we say we can future-proof your architecture. We’ve converted a lot of legacy apps.