USING BAYWARE FOR CLOUD MIGRATION

Jumpstart Migration Services

 

Application Portability

With Bayware, applications become portable because the network implementation belongs to the application. You take advantage of the scaling, resiliency, and efficiency of multiple public and private cloud-based infrastructure with a single implementation.

Application Deployement Is Not Agile graph image V2

Cloud Migration Use Case

You can use Bayware to make migration from private data centers to the cloud much easier. With Bayware, DevOps makes a simple declaration of application intent based on the logical relationships of the application services.

Bayware creates portable policy as Network Microservices that require only Linux to execute and will govern the flows between your application microservices. These network microservices include identity, security, routing and telemetry. 

Revised Microservices image

Application services. Interaction logic, e.g. user interface. Business logic e.g. Core services. Data logic, e.g. databases. Network microservices. Network policy. ie identify, security, routing, telemetry. 

You declare these policies by creating a service graph for your application in minutes. Below is an example that you can see in our Product Demo Video for the Getaway Application.

Starting with their familiar standard UML diagram, DevOps can use our UI or YAML code to create a series of Network Microservices that we call Contracts based on Bayware templates for each flow. Together these contracts form the service graph. 

Steps to build a service graph image

Now all you do is deploy Bayware software into the target environments. You don't configure any of the Bayware software; it will implement your intent based on the service graph.

Bayware enables you to migrate quickly and remain agile. Bayware can help with our Jumpstart Migration Services.

Looking at an IOT example below, you can start by implementing Bayware in your private cloud. Now it has it's own, zero-trust, portable network.

Then, you simply copy and paste your application workloads along with the Bayware software from the your private cloud into the target edge data centers and cloud VPCs.  Bayware automatically recreates the same, highly secure connections.

Migrating to the cloud image

In this IOT example, your data sets remain in your private cloud. If you wanted to replicate them, you can create a Bayware contract between replicas that, based on a heartbeat, will automatically and securely connect them across clouds so they can sync.

 

Definition: Network Microservice, Contract, Service Graph, Flow Instance

Network microservice - Bayware's term to describe the lifecycle from declaration to execution of networking and security policies as code.

Network policy - a declarative framework to describe identity, security, routing, and telemetry-gathering policies as code. Bayware provides several templates for common patterns. Authorized users can modify templates, and define and save whole new patterns.

Contract - a declaration of which named application microservices are the relevant participants in a particular, named network policy. Users declare a contract by adding service names to network policy templates and naming the contract.

Service Graph - the related set of contracts that belong to a specific, named, application (to an application name space.)

Flow Instance - execution of an authorized contract, initiated by application workload instances, to create a particular flow instance. Each flow instance is a distinct, secure, and visible network segment instance.

 

Application Migration to Microservices

Note, that since Bayware is Linux based, it is also agnostic to your packaging. You can use any hypervisor for your VMs, and you can mix containers into your application microservices. It will all work exactly the same way.

You can also use Bayware to enable your migration to microservices. Each time you break a service off of your monolith, you simply add the new service to your service graph. Bayware takes care of all the rest.

 

Cloud Application Migration from One Cloud to Another

This same approach works to start using multiple clouds based on customer preferences or pricing differences.  You can use Bayware to create automatic or on-demand failover from one cloud to another.

In this 3-tier application example on Bayware, you can move and replicate your application microservices to any cloud.  They all will connect in exactly the same was as they did in your private cloud and as they would if you were on one cloud.

Migrating to multicloud image

 

This Seems Almost Too Good to be True.

This level of power and simplicity comes from very sophisticated underlying technology. Bayware's advanced architecture ensures pervasive application security from the Linux interface across the network.  

And it is all code to enable agile collaboration with security and networking teams for compliance, and agile, continuous code upgradability.

To get into the real details, you are welcome to read our product documentation.  Or try it today with no Bayware license charges at the Azure Marketplace.

Jumpstart Migration Services