Abstraction helps to keep things simple when developing projects at scale, while also allowing for flexibility. If the models abstracted adhere to their respective model, developers can then innovate on top of that while keeping overall complexity in check.
These were the words of wisdom offered by Murali Sundar, principal engineer in Intel’s Software Defined Infrastructure Group, during the most recent The New Stack Analysts podcast, embedded below. For this episode, the New Stack hosted a pancake breakfast at MesosCon, held last month in Denver. TNS founder Alex Williams and co-host TNS editor Benjamin Ball spoke with; Ben Hindman, Mesosphere founder and chief architect; and Jessica Frazelle, Mesosphere software engineer.
Listen to all TNS podcasts on Simplecast.
The conversation may also be heard on YouTube.
Frazelle offered a useful anecdote in regards to the benefits of abstraction. “With Linux security modules, you have to set communication profiles. This can get very complex because you have to identify the system calls themselves. Developers might not be as familiar with low-level system calls. A lot of abstractions in terms of making this easy and fun to secure would be great. When it comes to securing your cluster, it’s insanely difficult because there are a lot of things to manage.”
Keeping complexity in check while allowing for scalability has been something Mesosphere focuses on. Hindman noted that keeping Mesosphere as “non-complex as possible,” was built out of a desire to be able to easily debug a system and add new features, even if running tens of thousands of machines. Being able to get community feedback on new features has also been helpful throughout this process, Frazelle noted.
“Coming from open source, it’s nice to have a set of users you can get feedback from and test out new features on so you know if you’re going in the right direction or if you’re completely wrong,” Frazelle said. “Getting user feedback and listening to the community is huge. They’re the ones that use the product, probably know what’s best, and have to deal with it day to day.”
With companies continuously worried about vendor lock-in, both Murali and Frazelle explained that lock-in isn’t going to be a zero-sum game. Murali went on to note that different vendors have different areas of expertise, which will greatly influence which vendor a company selects for all or part of their stack. “Everyone says ‘Don’t drink the Kool-Aid,’ and get vendor lock-in. But almost anything is going to give you that no matter where you go unless you have a kind of hybrid environment. Someone at the end of the day is lying to you about lock-in. It’s more about the tools you build on top of your server. As long as you’re using something that works on multiple environments, you should be good,” Frazelle explained.
Hindman was also quick to note that developers can and should contribute where they can to projects they find interesting, noting there are a variety of opportunities for innovation in interfaces and APIs developers can utilize to their advantage. “Sometimes the standard common denominator doesn’t let you take advantage of the goodies under the abstraction. In the cloud sense, the same thing might apply. How can you sneak through and take advantage of the stuff you want without programming against that cloud?”
The challenges facing those looking to secure a multi-cloud environment continue to grow along with the innovation in the space. Frazelle implored developers to consider standardization across platforms, noting Mesosphere has faced its own difficulties when building security features such as certificate authority into DCOS: “There’s a lot still to be done in this area and a lot that hasn’t been done in terms of new technology for this. If there was some sort of standard we could build upon that too.”
— The New Stack (@thenewstack) June 1, 2016
Feature image via Pixabay.