And as its key consumption model.
So what type of interface we are going to use inside the NSX.
You can see that we are going to use NSX to to work for and afterwards means could work for 2.5 which
said that those release will come.
And this product for is nothing but simplified declarative interface is still we have NSX to or tree.
It is used with some of the use cases for example cloud management platform.
So if we want to do a user interface to aggress upgrade and close managment up platforms so CMBS and
others feel use cases are there for the imperative model.
But we will has announced that they are going to add all those things which they are going to migrate
everything from Google three.
And it will be use inside to guard for Paragon say that all deployment except few of the use cases like
CMB and others is supporting container.
It is supporting open stack.
You can see the new feature from 2004 onwards.
The DNS servers June's VPN Endpoint Protection Network introspection context profile creation like L7
app or if Gurian new distributed firewall Gateway firewall layout different category aka plumbed rules
etc..
So everything will be handy from simplified UI or API and you can see that how many new features and
add ons are there so going forward two point four and onwards we have this interface that these simplified
UI are declarative interface that we are going to use now this particular slide we have seen in the
previous recording that what are the new terms we have inside NSX these two point four onwards.
So a logical switch replaced by segment here Zillow Gateway Tier 1 gateway with easy low key T1 logical
routers we have service the service interface group service security policy and Gateway firewall.
So these are rectums even we are also going to use in the upcoming sections.
Now what's the advantage is when we have the declarative or simplified UI.
So on that case you can see and it's actually use and you can see the perspective you can see the future
and wireless and it 60 will gain the popularity and then still it's actually really hard and popular
in the market.
So you can see this declarative market is outcome given means a reduced number of configuration a step
by allowing user to describe what is the end goal and letting the system figure out how to achieve it.
So you declare what you want and this system will tell you how to do it.
So what we want you to clear how to do it system will tell you this is the outcome driven and because
system will do it.
So in that case you can see the prescriptive that it reduces potential potential for user error.
So because system is being so it will reduce the error in the system and we have the big independency
chicken side so we'll check.
Okay.
What's the logic.
A B C D it will check all the flow through it has built in dependency checks this dependency check is
very much like in programming languages the interpreters are the other compilers they are checking all
this tense what's the dependency you are calling this function to have these functions or routines etc.
So they have the dependency check this is order independent in any order you can create update delete
touch object.
Actually this is really much API type of term where you have put get post and delete methods.
So here you can see you can update the object put.
You can get the information so it is not here but you can see that you have put you have delete and
you have post post for create.
So those methods are there and those methods.
They have the consistency frequency that in any order and always arrive at the same constraints.
Consistency you can do these operations in any order but you have the consistency.
Finally policy lifecycle management.
Similar can it's simpler with the single API call.
Call a mark to get flag in the Yes on form it requires body to manage lifecycle of the entire application
topology so it's a policy argument.
You can see policy given and if I write somewhere so you can see is the policy given it's a consistent
it's error free.
And it's the whole outcome driven correct.
So this is actually the declarative models of why we move from the advanced UI to simpler UI or why
we move from the imperative interface with the clear declarative an interface because we have these
features or BP outcome order.
Prescriptive and policy lifecycle management.
Yeah right.
So let's stop here.