The question remains how can businesses figure out which — if any — pieces of their stack can be transitioned into the cloud? Though this may seem a simple task, it can be daunting when one first realizes the work involved with moving from a legacy architecture over to a hybrid or fully cloud-based solution.
This is particularly true for organizations with a large quantity of data to process, or which may be facing unique situations in terms of their data which prevents switching to an entirely cloud-based architecture.
In this episode of The New Stack at Scale podcast embedded below, The New Stack founder Alex Williams and Fredric Paul, editor-in-chief at New Relic, sat down with Lee Atchison, principal cloud architect at New Relic to discuss the past, present, and future of cloud-based architecture. They are also joined by Kyle MacDonald, one of the original board members of OpenStack, who also served as Canonical’s senior vice president of cloud.
Though there are advantages to working with an entirely on-premise cloud, there are still places in which they can fall short of what an enterprise can achieve with a hybrid cloud solution, or transitioning to a 100 percent cloud-based architecture.
“You might have some processing of that data that requires some very unique compute requirements. Maybe God forbid some mainframe requirements or some other compute requirements that are still in your data center that are required or not easily moved to the cloud and those parts of the application would stay there at least for now,” Atchison noted.
Overall, the shift to hybrid architecture means adapting to change. This means enterprises must consider the fact that hybridization is something that occurs from the moment a developer chooses Amazon S3 to store their files. MacDonald explained that portability is the crux of today’s hybrid architecture — Developers can pick up and move aspects of an application from one platform to another and expect them to behave in the same way. Such portability, particularly within containers enable a simpler approach to the hybrid cloud.
With this comes the realization that architecturally, a business’s data can be in a hybrid cloud without CTO’s and CIO’s ever noticing — Though they should.
“It’s important that you understand that when it comes to knowing that you’re not completely in control of your data anymore. You’re not completely in control of your environment anymore. There are lots of other people in control. That’s really what hybrid means, is that you need to understand how all of this fits together and not just your own ops team,” said Atchison.
New Relic is a sponsor of The New Stack.
Feature image via Pixabay.