Bringing sanity back to Cloud Architecture

Now it’s easier than ever to explain our brand, “Logic Keepers”

Logic Keepers
Logic Keepers

We started our journey on that path a few years ago, in an effort to enable our clients to quickly adapt to the new digital era, we are bringing sanity back into Cloud architecture, hence; “The Logic Keepers”.

Moving to the Cloud without creating the proper Cloud-Native architecture proved to be problematic, many couldn’t visualize this in the past; today is a completely different story.

Our valued partner, Lightbend recently released their “Cloud Native Adoption Trends” survey, this is Gold, it is an eye opener and must read for technology and tech savvy business executives.

The survey showed a strong adoption on the business side, check the full report here.

Ironically, it highlighted unexpected point of view by the architects and the developers.

Quote from the report at the finding “number four”,

Developers and Executives Don’t Always Prioritize the Same Things
One thread that runs through all of the above findings is a discrepancy
between what developers and managers prioritize, despite a general belief
among most respondents that business leaders understand the benefits of moving to the cloud.

You would expect the opposite, right?

Where’s the gap then?

It’s easy to explain the business interest and value; in the Cloud you can find faster time to market and relatively reasonable start-up cost, however, faster time-to-market is not necessarily means faster time-to-value.

How about IT and the software development world?

The Cloud is completely different from the traditional data center environment. It’s distributed by nature, there’s no well defined boundaries and it presents several challenges right out of the gate. 

Scalability, elasticity, meeting the SLA, staying within the budget, most importantly security and keeping the promise of faster time to market.

Even Though, we made a lot of progress on containerization, container orchestration using Kubernetes, Microservices Architecture, Reactive Architecture, Cloud-Native Architecture and Reactive Technologies such as Akka; we still struggle with this.

Because it’s hard for us as architects and developers to adapt to this, it is definitely outside the comfort zone, this is not the way we have been building solutions for the last 15+ years.

The most common and traditional approach to migrate solutions to the cloud is lift and shift. Hopping that, we will migrate off this ball of mud, -the monolith- in the future, and you know the rest, right? It might never happen or it would take way longer than it should and that diminishes the value of moving to the Cloud.

To make things worse, whenever an organization suffers from this Cloud fatigue syndrome, they look to replace their technical staff with more cloud-savvy resources, which are really hard to find and that usually lead to a vicious circle of fire and hire or at times rehire. 

It’s true that, “The most dangerous prison is in our heads”, it’s hard to adapt and change, but we have to; this is how we evolve.

This is our mission at Logic Keepers, bringing back the logic into Cloud-Architecture and Fast Data, educating the development community about the tremendous value of Cloud-Native Architecture, Reactive Architecture and Reactive Microservices.

We accomplish this by following a balanced pragmatic approach, you can’t just introduce the concept without providing the use cases and the implementation.

If you lean too much on just the concepts, then it’s just theoretical or if you go too far on the infrastructure side of things such as K8S heavy, then it’s more of a DevOps exercise and leaving the developers behind.

Check for more information here on how we accomplish this in our Modern Application Architecture Workshops.

This is not just about knowledge, you have to include coaching and mentoring as well in your learning plans.

Together we can close the gap.

Happy hacking