Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customize your settings, hit “Customize Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

This article is more than 1 year old

Nexenta catches micro-services bug, slings its Edge into containers

It's what all the cool kids are doing, right?

Nexenta is supporting containerised servers by having its NexentaEdge product nodes run as microservices along with application microservices on any scale-out Linux server cluster.

NexentaEdge is scale-out block and object storage. Containers are a more efficient form of server virtualisation, having thinner "wrappers" than virtual machines, as guest operating system features are shared instead of being present in every container. This enables more of a server's memory and CPU resources to be devoted to running application code than internal infrastructure code.

Containers can be stateless, needing little or no persistent storage, or stateful, in which case they use persistent storage such as that which NexentaEdge supplies.

Nexenta believes that the "simplicity and efficiency of microservices and container-based architecture have established them as the de facto standard for developers building cloud applications at scale." It is working with partners to help customers deploy cloud-native applications, whether they require persistent storage or not.

By running NexentaEdge microservices, containerised apps get access to its block and object storage services, inline deduplication and compression, unlimited snapshots, clones, etc. Also there is "low latency data access between application microservices and NexentaEdge storage microservices running concurrently on the same server infrastructure, eliminating the overhead associated with traditional iSCSI block access methods."

Container mobility across a cluster is helped by using "NexentaEdge's scale-out architecture for any time, any server access to any container image or any application back-end data."

Kubernetes can be used to manage NexentaEdge microservices, and these microservices will be compatible with Canonical's Juju, Charms, and LXD.

ClusterHQ Flocker volume plug-ins for NexentaEdge and NexentaStor will be built to support customers who prefer to keep compute and storage running on separate physical infrastructure.

Nexenta is joining the Open Container Initiative (OCI) and Cloud Native Computing Foundation (CNCF). It will be in good company, as other members include: Apcera, AT&T, AWS, Cisco, ClusterHQ, CoreOS, Datera, Docker, EMC, Fujitsu, Google, Goldman Sachs, HP, Huawei, IBM, Intel, Joyent, Kismatic, Kyup, the Linux Foundation, Mesosphere, Microsoft, Midokura, Nutanix, Oracle, Pivotal, Polyverse, Rancher, Red Hat, Resin.io, Suse, Sysdig, Twitter, Verizon, and VMware.

Storage suppliers have to provide data access to applications in servers, and if these apps are containerised then, intuitively, it's best if the storage access app in the server is containerised too. ®

 

Similar topics

TIP US OFF

Send us news


Other stories you might like