Session Smart Routing Demo: Connecting to Public Cloud Workloads
Rolling out cloud-based apps in a simple and controlled manner
When it’s time to introduce a new cloud-hosted application, our Session Smart Router lets you do so in a simple and controlled manner. Applying the example of a business upgrading their inventory app, this demo takes you step by step through the process.
You’ll learn
The two things needed to introduce a new cloud-hosted app (hint: first tell the WAN)
Why users needn’t change their behavior to use the new app
How Juniper optimizes the app experience from client to cloud
Who is this for?
0:01 this demonstration will show how to
0:03 introduce a new cloud-hosted application
0:05 to our users
0:06 in a simple and controlled manner our
0:09 branch users are accessing a legacy
0:11 inventory app
0:12 using the private address which is
0:14 routing to a nearby private data center
0:16 the network has been segmented for the
0:18 finance and engineering tenants
0:20 and both are allowed to access the
0:22 inventory service
0:24 the time has come for our enterprise to
0:26 roll out a next-gen
0:27 inventory app hosted in the cloud going
0:30 to our microsoft azure portal we have a
0:32 virtual machine created to host an
0:35 instance of the new inventory software
0:37 it is set to run in a workloads virtual
0:40 network using only a private address
0:43 let's go ahead and launch the virtual
0:45 machine with the workload running we
0:47 just need two simple things to introduce
0:49 it to the network
0:51 first we need to tell the entire when
0:53 about the app
0:54 this is done by describing it in a
0:56 service using the legacy inventory
0:58 service as a starting point
1:00 we clone it to a new inventory service
1:05 for a controlled introduction we only
1:07 want to migrate finance users to the new
1:10 app
1:12 second we need to tell the wan where the
1:14 app gets routed in the topology
1:17 this is done by giving only our last hop
1:19 router
1:20 the azure gateway router a service route
1:22 for the new inventory app
1:24 this means users won't have to change
1:26 their behavior at all to access the new
1:28 app
1:29 the network will simply route and
1:31 translate their sessions to the new
1:32 workload once they are given access
1:35 glancing back at our new configuration
1:37 we have now moved finance users over to
1:40 the new inventory app
1:41 while leaving engineering on the legacy
1:43 app
1:46 next there are desktops of two users
1:48 sitting in a remote branch
1:50 bob and finance and alice in engineering
1:53 as we refresh the browser for both bob
1:55 and alice
1:56 we can see that sessions from bob's
1:58 desktop are now securely routed to the
2:00 new cloud app
2:02 by simply making the network aware of
2:04 the new cloud app and giving a route to
2:06 it
2:06 the azure router advertised reachability
2:08 to all other routers in the topology
2:11 this was done using service and topology
2:14 exchange protocol
2:15 or step which is an innovative dynamic
2:18 routing protocol designed for
2:19 tunnel-free
2:20 session-oriented routing additional
2:22 cloud workloads can be spun up and load
2:25 balanced by the network to scale the app
2:27 as it grows
2:28 and the juniper wan solution is
2:30 optimizing the app experience from
2:32 client to cloud
2:36 you
