Good afternoon, everyone. Welcome to building event-driven serverless applications. We are very happy to have Gunnar Brasch with us. Gunnar, thanks a lot for joining us in doing this for us. And without further ado, over to you, Gunnar. Take it over. All right. Thank you very much, Adip. Hi, everyone. Very happy to be here, even though I'm right now in Sweden instead of India. All right. So welcome to building event-driven serverless applications. My name is Gunnar Grosch, and I am a senior developer advocate with AWS. So serverless is one of the differentiating capabilities of the cloud. And it basically means that there are still servers in serverless, but AWS manages those servers for us. So customers using serverless technologies, they've found that they can be more productive and agile when they're bringing new workloads to the market. So today we're going to talk about how to use the technique of using events as the driver for building our serverless applications. So let's jump into it and look at what we're going to talk about. So this is the agenda. I'm just short going to cover what serverless is. Perhaps most of you already know what it is, but just a few slides talking about that. Before we move over to the event-driven part, the core part of this presentation, we'll look at what events are and the different type of events we can see and how we actually use those in our architectures. We'll look at one of the core services from AWS, Amazon EventBridge, that we use when building our event-driven applications. Look at some common use cases and some patterns that we can use. All right, so just short about me first. As I said, I'm a senior developer advocate at AWS. My background is, well, it's hard to believe perhaps. I've been in the industry for 20 years now. I started out as a developer way back in 1999 and have worked my way through development, operations, different management roles within IT. And I'm really happy to be here now as a developer advocate for AWS. I am a community builder in that I help organize and drive events in the Nordics, mainly focusing on serverless. And also, I have three kids. They are definitely keeping me on my toes all the time. All right, so let's get to the first part. What is serverless? And these are the main tenants that define serverless as an operational model. First off, we talk about that there is no infrastructure provisioning, no management for us. So there's no servers to provision. We don't have to operate them. We don't have to patch them. So it's basically about not having to do this heavy lifting that's involved with running servers. Next up, we have the automatic scaling. Our serverless workloads, they scale by the unit of consumptions. By that, I mean a unit of work rather than the actual number of servers in the background. So we're able to scale as we need. And we also talk about paying for value. The model is that we're paying for value. So if we want consistent throughput or we have a specific execution duration, we pay for that unit rather than, once again, the number of actual servers in the background. And perhaps most important is that we have these built-in capabilities for availability and fault tolerance. So we don't have to think about the availability and the fault tolerance of the underlying services. It's more about how we put these services together to have these reliable serverless applications. So it's about removing that heavy lifting part of server management and server operations. So it's an important distinction in what building and running these applications mean. So when we build our serverless applications, we usually talk about it in these three headers. So we have our event sources. That might be a different type of changes in the data state or different requests to endpoints where a client or user calls specific endpoints. Or it might be changes in the resource states and state of the different resources we're using within our application. And then we usually build our applications around a function using AWS Lambda as our service for functions. And the function, well, that contains our business logic, the code that actually does what we want it to do. And we usually talk about our functions that they should be processing data rather than transporting data. So we build our business logic to do some sort of processing of our data. And the functions we build, they can use different type of runtimes as seen on the screen now, Node.js, Python, and so on. So use the runtimes language that you are familiar with. And this you're able to mix and match since you are dividing your applications into the different functions that is involved in the applications. You can have certain functions using Node, certain using Python, and so on. And then we connect our functions to other services. And that can be other AWS services, for instance, our data stores as DynamoDB or the object storage Amazon S3, or it might be third-party services that we're using as a downstream service. So that's the main way that we build our serverless applications with the event source, the function, and the services. So that was a really brief description of serverless, what serverless means and how we build those applications. So let's get to the good part. Let's get to event-driven architectures. So what we want to do is we want to build our applications. They should be scalable, resilient, and so on. And event-driven is a way that we use to build our applications. And Lambda as the function service, that is what we say is an event-driven service. In that every time a function, a Lambda function is invoked, it is invoked with a payload containing an event. So even your basic web service that we use, which is more or less a request-reply type service, it contains a sort of event. And the event in that case is the API request that's sent to it. So we talk about our applications in different ways. In many cases, we build our applications around APIs. And the APIs, they are basically the front door of our microservices. So they are the primary mechanism through which our services communicate with each other. So let's think about how we build applications usually today. Using microservices is a common practice today, that we split our application into smaller pieces. Each of these pieces contain a service or a microservice, and they communicate to each other using these APIs. So we set up different API contracts between these services, how they are supposed to communicate with each other. And the other way that we integrate our services, it is using events. So the events, as it says, is the connective tissue of modern applications. And we use these events instead to get our different services to talk to each other. And the events, it can be changes in state or updates and so on. So think about an event like something being placed in a shopping cart in an e-commerce site, or changes in state of a support ticket in a support system. So our event-driven architectures, they can help us improve scalability, fault tolerance and so on, by reducing the dependencies between different processes and teams. We'll look a bit more about how that can look. So when building our applications, we want to have them be decoupled, as we say. And a decoupled application means that the different parts, the different services of our application, they should have as little knowledge about each other as possible, so that they don't rely on each other to be there. So think about, once again, an e-commerce site where you have an order service. The order service for it to be decoupled means that it shouldn't have to rely on other services to be there to work as intended. So there are different ways of decoupling our applications. And the one is by using APIs. And that's what we call the contract decoupling. So we have this API contract between service A and service B. And then that is more or less all that those services know about each other. How should this API call look? And an API contract, or using contract decoupling, it means that we can make changes in implementation, how service A works and how service B works, as long as the API calls still remain according to the contract. And another way of doing it is what we call a runtime decoupling. And runtime decoupling, that is done by switching from having synchronous calls to what we call asynchronous calls. And those are asynchronous invocations of the services. We'll look at the details about these invocations in a bit. But what that means is that we are able to decouple the service A from service B even further. So we have less risk of what we call cascading failures. If there is an issue with service B, it shouldn't affect service A and vice versa. So the basic part of an event-driven application is the event. And in the simplest of terms, an event is a signal that a system state has changed in some way. So the definition is a thing that happens, particularly one of importance. So the events are the key in our event-driven applications, obviously. So we can compare it to what we perhaps previously or in many cases normally build our applications with, and that is the command. So comparing those, we can see that a command, it has an intent. It is directed specifically to a target, and it is personal one-to-one communication. An event instead, that is more of a fact. So it is something that happens that others can observe. And by having it as a fact, we're able to broadcast it. So it's one-to-many communication instead of one-to-one. And examples of that, for instance, commands, they can be create product or add product or create account, for instance. Looking at it from an event perspective instead, it can be then that account created and product added. So those are things that happen in our system that others can observe. So this is the key to how we want to build our event-driven applications. So having an event-driven architecture, it means that we're able to drive reliability and scalability. Since these events are asynchronous, you don't have to wait for a response to move on to the next step compared to the command-driven one, where we're actually telling one to add a product, for instance. Instead, when it's asynchronous, we don't have to wait for the response to add the product. So it improves resilience and reduces dependencies. And we talk about different parts of our event-driven architecture. And one tool is what we call the router. And that is something that then abstract the producer of an event and the consumer of an event from each other. So the router is where the events are actually routed. And we'll look at that, how we can use different services to act as this router with Amazon Event Bridge later on. So we can publish events to the router, and then others can consume those events without actually knowing anything about other producers or other consumers. And then we have the event stores. And the event stores, they act as buffers so they can hold on to events until the consumer is ready to use them. And examples of event stores can be our different queue services, for instance, AWS Simple Queue Service, SQS, where we're able to store our events or queue them then, and then consume them when we're ready to consume them. All right. And in the middle of this, we have the asynchronous event. It means that as the example shows, a client is pushing an event that then ends up at Service A. The client doesn't have to wait for a reply from Service B. Instead, it just gets a notification back or a response that Service A has received the event. Then Service B is able to then fetch the event and use it when it's ready to consume that event. So these are the three different invocation methods that we talk about with AWS Lambda. So the synchronous one, the one that we see in our most common APIs, for instance, is the one where the client needs to wait for a response. So the Lambda function in this case needs to perform its processing of data, perhaps even wait for downstream services like data stores and so on to do what it's intended to do with the data before it's able to send a return back or a response back to the client. And synchronous calls or synchronous invocations means that since the client is waiting for a response, we might have this different type of latencies or be more dependent on what's happening downstream in the service. But when we have a synchronous invocations instead, as I said, the client gets a response back just that it has been received and doesn't have to wait for the actual processing of the event or the event data. And the asynchronous invocations, they use services like Amazon SNS, the simple notification service, or, for instance, Amazon S3, the object storage. So think about storing an image in an S3 bucket. Your client is uploading an image to the S3 bucket. That is then invoking a Lambda function that is supposed to process that image. And the client gets a response back that it has been uploaded in S3 before Lambda starts processing that file. And so that is a synchronous invocation. Then we have what we call the pole-based invocations as well that are based on streams. For instance, Amazon DynamoDB streams and Kinesis streams where it's... Well, the events are grouped into batches and then sent for invocation. So to be able to simply start using events within our applications, we can use a feature with AWS Lambda that's called event destinations, which is a really neat feature in that we can really easily get started to using the actual events in our applications. So when we have an AWS Lambda function that is processing data of some sort, we can use the event that is created when that is invoked or executed and then act upon that. And the event that is happening when our Lambda is executed, it contains details about both the request and the response stored in JSON format. So that is data that we then can send as an outcome either on success or on failure. So let's look at it in another picture. So we have different type of services that can invoke our Lambda function. I've mentioned that. When the Lambda function then processes that data, it then emits an event that we can use to then do the next step within our application. So on success, for instance, we have fetched the image from our S3 bucket. We have processed the image and it was successful. The event that is created when we have a successful execution of our Lambda function, that can then be sent to do something else, to another Lambda function, to a queue, to a notification and so on. And on the other hand, if it was unsuccessful, we had a failure to process that image. Well, we can do something with that message as well. Basic pattern there is that we take the event on failure, store it in a queue, and then we're able to inspect that event either automatically or manually, of course, and use that event to reprocess the image to make sure that it actually is being processed later on. Since we're using a synchronous invocation and the client isn't waiting for a response, so we are able to then process it again later on. So those are basic steps to get started building with event-driven architectures, to use the actual events that are emitted from our Lambda functions as what's called a service feature that's called Lambda destinations. Then we have other services. I mentioned some of them already, but that we use within our event-driven applications. First off, we have Amazon SQS. I mentioned SQS before as a queue service, a simple queue service. It is a fully managed message queuing service that enables us to decouple and scale our applications in that we're able to store events and use them later on. So we can have other services pick up these events from the event storage that we're using. Then Amazon SNS, that is a fully managed notification or messaging service. So it can be both system-to-system, so different parts of our application, different services, for instance, can talk to each other using this as a pub-sub, a classic pub-sub service, or it can be apped to person as well. So we can use SNS as a way of sending messages to clients through SMS, email, and so on. So using this pub-sub pattern enables us to use messaging patterns between our decoupled microservices. And then we have Event Bridge, which we'll dive a bit deeper into later on. But that's the way that we route our events inside our application. And it is basically what we call choreography, where we're then able to filter and route events within our application. And then the last service, which we won't cover now, but that is Step Functions, which is also an event-driven service that's used for orchestration. So you can use it to build workflows and then process events and objects within our workflows using these state machines that are involved. So let's look at an example of how we can build our application in an event-driven way. So let's have the example of us launching an e-commerce site. We'll try to make this scalable, but still as simple as possible from an architecture standpoint. So looking at the example on screen right now, this is our standard synchronous API-based service. So when a client makes a request to the order service, the order service has to make a downstream request to the fulfillment service. When the order service gets a reply back from the fulfillment service, it can then respond back to the client with a success message and give the client order number, confirmation number, and then we have a happy customer, hopefully. And this is a great pattern to use, this simple web service, as long as we have this simple small system as on screen right now. But that's usually not how our applications look. They usually might start out this way, but then they grow. We need to add more features to it. So how do we support these growing number of services that our store operations or e-commerce service needs? What happens when we add the next service? Now we have an invoicing service as well, and we have a forecasting service. And there is actually nothing wrong with building it this way and just adding more downstream services. But what's problematic with this API-oriented design is that the order service needs to know about all of these other boxes. So the client submits or creates an order, and the order service needs to talk to the fulfillment service. It needs to talk to the invoice service. It needs to talk to the forecasting service and so on. And it means that our application that started out in a simple, easy way has now become more complex because these microservices that we have, they aren't really decoupled anymore. We are starting to get these hard couplings between services so that the order service needs to rely on the invoicing service to be there. So we need to build in retry logic. We need to have error handling and so on for it to work as intended. So next up, perhaps, we need to have even more services. We need to have other services within our application, and it becomes more and more complex to maintain and have this working successfully. So that's when event-driven architecture is a great way to actually maintain this decoupled architecture where the different services doesn't really have to know that much about each other, as little as possible. So using an event router like Amazon EventBridge, it means that instead of having these services talk directly to each other, they can talk through this event router. So we can keep or we can move to an asynchronous model for our application. So the order service receives an order from the client and replies back, thank you, I've received your order. And that event then, order received, that's not a command, it's an event. Order received is then sent to Amazon EventBridge as an event. And then we can have different consumer services use that event to do its processing of the event, to do the things it needs to do, the fulfillment service and so on. And basically, this is what the event would look like. It's a JSON containing the different details of our order that we're then able to route through EventBridge and other services can then consume it. And using EventBridge as a router, we can then of course also filter this. So not every service needs to use this order data. So only the downstream services that need the data can then use it. So EventBridge is first ingesting, then filtering and delivering these events to our client or our downstream services. And we don't even have to build any complex custom data for it because that's part of the managed service instead. And then when we want to add new features to our service, well, we can simply do that. We can just add data within our event and we can add new rules to the event router. So for instance, in this case, we have a loyalty service added. Well, as long as we have that data in the event, we can have that new service act as a consumer using that event. So let's look a bit more about how EventBridge looks or works then. So this is the basic overview of it. We have on the left our emitters. Those are different services and so on that can create events that are sent into Amazon EventBridge. Then we have the actual event bus, the part of our application that handles the events where they are pushed into. I'll dive into those shortly and then to the right we have our receivers. So based on the rules we set up, we can have different receivers and they can be more or less any type of AWS service or other services as well. It can use these events. So the different event buses that we can use, first off, we have the default bus. That's the one where events that come from other AWS services, for instance, S3 or other services, they are pushed into this event bus or routed into that bus. Then we can create our custom buses as well, which means that instead of using EventBridge only for events that come from other AWS services, we can create custom events that come from any type of application. So even if it's another application we have built within AWS, some legacy system perhaps, or it's something that is running somewhere else, a system that we have on-premise even, we can then push events into this custom event bus that we create in EventBridge. Then we have the different SAS buses and those are third-party software services service events that we can push into EventBridge. So there are already a lot of different third-party events or third-party integrations available that can be used. So depending on the type of system you're using, there might already be different integrations in place. Think about different monitoring systems, your ticketing systems and so on that can easily integrate with EventBridge. So when a ticket is created or something happens within a monitoring system, that event can be pushed into EventBridge. So those are the three different type of event buses we have. And then looking at the structure of an event, it contains some basic parts. We have the source of the event. We have where the event originates. We have details of what type of event it is. We have the detail about the event and the detail is where we enter our data, the data that is important for our service, the order data for instance, the customer data and so on. And the resources, any type of identifiers that are related to this event. So this is sent in JSON data and is then delivered into EventBridge. The roles that we can set up within EventBridge in our router, we can use different patterns to match against different events. So we find patterns in our JSON data and match against these for our consumers to get the right events. We can also do transformation of the event using JSON path. So we can transform the event and then we have a list of targets. So the targets are the consumers that will receive these events. So for each rule that we can set up, we can have up to five different targets for each event. So for instance, when we create a rule, we can write our different patterns. For instance, that I want to be notified for EC2 instance state changes. Then we create a rule for that when the source is EC2 and the detail type is instance state change notification. That will then be captured by this rule. We can make it even more narrow in that I want to be notified for EC2 instance termination. So in this case, we set up a state of terminated in our JSON rule. So we fetch events only for EC2 instance termination. Or for instances that are in specific states. If we want to track specific orders, for instance, we set up these patterns within our rules. And then the targets are the consumers. Well, it can be many kinds of different AWS services that we can set up as target that can then capture these events that are sent through Amazon EventBridge. There is a neat feature in EventBridge that's called a schema registry and discovery because creating these events, even though the basic structure is easy, the details of it, well, that depends on what you want to have within your event. And when you perhaps build different services with different teams, it means that the teams need to know what are the details of these specific events. Using what's called a schema registry, we're then able to store the patterns for how our events look, the schemas for those. So other services, other teams can then use that as their source of truth for how the event should look. And there's the discovery feature where you're able to automatically discover the schema for different type of events. And there is built-in integration for VS Code for this and JetBrains, which makes it easier for teams to work with it as well. So let's look at some common use cases for how to use event-driven architectures. An easy one is where we want to take action. So a SaaS application emits an event, a ticket is created, and that is then pushed into Amazon EventBridge. And we have a rule where it passes through to a target, in this case AWS Lambda, a Lambda function that takes the event as an invocation, processes the event, and then uses that downstream of some sort. So basic take action use case. We can use it to run workflows. So the same setup, we have a SaaS application emitting an event, a ticket is created, pushed to EventBridge, which then invokes a step functions workflow. So our state machine takes the event and is able to then continue doing the next steps with that event. Or we can apply different type of intelligence. Event is sent through EventBridge, which invokes a Lambda function, which in turn uses downstream AI services like Comprehend or SageMaker to process the data and have an output of that data. We can audit and analyze is a common use case, where the event is pushed through EventBridge, and this might be a large number of events. So they are then using Amazon Kinesis Data Firehose as the downstream service to then push these large number of events through the service and store them in an S3 bucket, and then we're able to use other services with that data or those objects. In this case, Amazon Athena to use that as a query for the data stored in S3. Or perhaps use it as a way of synchronizing data is quite common as well. So think of it as your basic web service that we saw early on, where we have Lambda using DynamoDB downstream. But in this case, we've built it asynchronously using events. So we have an event sent through EventBridge, Lambda is processing it, and then fetching other type of data from the SAS application in this case. So based on the event, Lambda is able to do other things with data from that upstream service. So those are quite common use cases, and based on how you filter the events and so on, many of these of course can be used within the same bus and based on what the event actually is. So for instance, if we have a ticket created as the event, well that might mean that we both synchronize data and we audit and analyze based on that. But those different patterns, they don't have to know anything about each other. So let's look at some more patterns for this. And this is our decoupled messaging that we can use for event driven. We're not using Amazon EventBridge in this case. Instead we have a client that is sending a message to an SQS queue, and SQS as we know, that's our hosted fully managed queue service. The message is stored in SQS, and we have a Lambda function that is pulling the queue for data and received the data, is then processing that data and stores it within DynamoDB. So that's an asynchronous invocation of our decoupled messaging. We can even use these dead letter queues to store events that fail to process. And so that we once again are able to then reprocess them, inspect them and so on. Or the PubSub way of working. I mentioned the SNS as a PubSub service earlier on. In the same way where we have a client then publishing something to an SNS topic, and we can then have different subscribers to that topic, where different services use that event as a way of processing the data within the event. So these are examples of when we're building event-driven applications, but not using Amazon EventBridge. Even though Amazon EventBridge is a great service for routing our events, we can build event-driven services without using Amazon EventBridge. Sorry, there we go. This is another example. Where we have data stored in S3 bucket, which then invokes a Lambda function. And the Lambda function is invoked by using this event that we saw earlier that is created based on the upload to S3. And these have now been a few examples of how we can use our event-driven architecture with serverless and how we can start building with event-driven architectures. If you want to get started using it, think about using that basic method that I mentioned earlier on, using Lambda destinations, where you're able to use the on-success or on-failure method of creating events that you're then able to use. Look at using SNS and SQS as ways of storing events within your applications. And look at using Amazon EventBridge as your event router, as it is a very powerful tool for creating event-driven applications. And a simple way of getting started, if you haven't used these services before, is by doing this hands-on workshop that AWS offers. So it is hands-on with serverless messaging, with a few different scenarios that you can build on. You can use both SNS EventBridge, do filtering and have this asynchronous processing for decoupled applications. And it's available on the URL seen on the screen right now. And it's a great way to get started building event-driven serverless applications. And with that, my name is Gunnar Girosh. I want to thank you for joining me in building event-driven serverless applications today. I have a session tomorrow as well on chaos engineering for serverless applications. I'd be happy if you joined me then. All right, thank you very much.


One of the new aspects, I think, of contemporary deployments is the importance of direct communication with the key audiences. And this is a real shift in many ways, that the traditional way of doing communications for peace operations and for a lot of institutions is essentially one-way communications, that you put out a press release or you issue something and that gets distributed or not and it has an impact or not. That 21st century style of communications is really quite circular. It's about building a dialogue rather than simply getting across points. And that sense of building a dialogue, that sense of creating a constituency that is involved in a discussion, that takes a lot of acceptance of this shift because it requires giving up control of the message. And that shift is one that our new leadership needs to be very fluent in. The idea of your constituency being a digital one. The expectation of the access to information is almost immediate, even in some of the poorest places in the world. And that has changed things quite a bit, that expectation that you will have a direct interaction, whether or not that would be through access to broadcast text messaging or through social media if you're in a context where social media is relevant. But those points matter quite a bit and getting your message out is increasingly an important aspect of all international deployments and not one necessarily that was a key component of traditional peace operations. That right now because of the expectation of instantaneous communication, because of a 24 hour news cycle, there is a really a requirement and that's the word, a requirement that you communicate simultaneously with timely, accurate information and timely, accurate and impartial information. Behind the scenes, behind closed doors style of doing businesses is not exactly concurrent with how digital media journalists expect things to be explained to them. And leaders today need to understand that distinction and be able to address it. It doesn't mean that they need to go one way or the other, but it does mean that they need to be sensitive to that dynamic, that there is an expectation that everything will be laid bare, while at the same time a requirement for confidentiality. And this is one of the fundamental tensions of communicating in the modern era and it's why we need leaders that are trained in modern communication techniques.


The cloud is evolving. You know, it's no longer just a set of remote services accessed through a public cloud. Rather it's expanding to on-premises, to multiple premises across clouds and eventually out to the edge. The challenge for customers is how to treat these locations as one. The opportunity for technology companies is to make that as simple as possible from an operational perspective. Welcome to this CUBE program where we're featuring pure storage in its latest innovations and bringing infrastructure and applications more closely together, fusing them, if you will. And today we have a two-part program. First, we're going to hear from Rob Lee, who's the CTO of Pure Storage and then my colleague John Walls is going to talk to Scott Sinclair of Enterprise Strategy Group. Scott will provide his expert analysis on infrastructure modernization and what to expect in today's changing world. So joining me right now is Rob Lee, CTO of Pure Storage. Welcome, Rob. Good to see you. Good to see you again too, Dave. Hey, so take us through the announcements from today at a high level. What's most exciting about what you're delivering? Yeah, absolutely. So as you know, many announcements today, many things to discuss, but overall, I think what's most exciting is it's the expansion of our ability to help customers along the modern data journey. We've always thought of the journey to modern data as being formed by three pillars. If you will, certainly modernizing infrastructure, modernizing operations and applications. And today's announcements are really in that kind of middle category of, like you said, bringing infrastructures and applications a lot more closely together. We've been modernizing infrastructure since day one. Probably people best know us for that. And today's announcements are really about tackling that operations piece, bringing infrastructure and code and applications more closely together. So when we think about Pure Fusion, for example, that's really a huge step forward in how we're enabling our customers to manage large fleets of infrastructure products and components to deliver those services in a more automated, more tightly integrated, seamlessly, transparently delivered way to the applications that they serve. Whether these services are being delivered by many different arrays in one location, many different arrays in different data center locations, or between the premise, on premise environment and the cloud environment. Likewise, in the application front, when we think about today's announcements in Portworx data services, that's really all about how do we make the run and operate steps of a lot of the application building blocks that cloud native developers are using and relying on the database applications that are most popular in open source, Cassandra, Mongo, so on and so forth. How do we make the run and operate pieces of those applications a lot more intuitive, a lot more easily deployed, scaled, managed, monitored for those app developers? And so a ton of momentum is a big step forward on that front. And then right in the middle, when we think about today's announcements in Pure One, that's really all about how do we create more visibility connecting the monitoring and management of the infrastructure running the apps and bring those closer together. So when we think about the visibility we're now able to deliver for Portworx topologies, allowing developers and DevOps teams to look at the entire tech stack, if you will, of a container environment from the application to the containers to the Kubernetes cluster to the compute nodes all the way down to the storage and be able to see everything that's going on, root cause any sort of problems that come up. But again, that's all in service of bringing infrastructure and applications a lot more closely together. So that's really how I view it. And like I said, it's really the next step in our journey of helping customers modernize between infrastructure operations and their applications. Okay, so you've got the control plane piece, which is all about the operating model. You've got Pure One, you mentioned that, which is for monitoring. You've got the Portworx piece, which brings sort of development and deployment together and both infrastructure as a code and better understanding that full stack of, like you say, from applications through the clusters, the containers all the way down to the storage. So I feel like it's not even a storage anymore. I mean, it's cloud. It is, and I chuckle a little bit because at the end of the day, we deliver storage, but what customers are looking for is and what they value and what they care about is their data. Now, obviously the storage is in service of the data. What we're doing with today's announcements is, again, just making it extending our reach, helping customers work over their data a couple more steps down the road beyond just serving the bits and bytes of the storage, but now getting into how do we connect the data that's sitting on our storage more quickly, get it in the hands of developers and the applications more seamlessly and more fluidly across these different environments. How does this news fit into Pure's evolution as a company? I mean, I don't see it as a pivot because the pivot's like, okay, we're gonna go from here and now we're doing this. Now we're doing this. Right, so it's more like a reinvention or a progression of the vision and the strategy. Can you talk to that? Absolutely, and I think between those two words, I would say it's a progression. It's the next step in the journey as opposed to a reinvention, right? And again, I go back to the difference between storage and data and how customers are using data. We've been on a long-term path, long-term journey to continue to help customers modernize how they work with data, the results they're able to drive from the data. We got our start in infrastructure and just, if you wanna do bleeding edge things with data, you're not gonna do it on decades old infrastructure. So let's fix that component first. That's how we got our start. Today's announcements are really the next couple of steps along that journey. How do we make the core infrastructure more easily delivered, more flexible to operate, more automated in the hands of not just the DevOps teams, the IT teams, but the application developers? How do we deliver infrastructure more seamlessly as code? Well, why is that important? It's important because what customers are looking for out of their data is both speeds and feeds the traditional kind of measures bandwidth, IOPS latency, that sort of thing. But they're looking for a speed of agility, right? You look at the modern application space around how data is being processed. It's a very, very fast moving application space. The databases that are being used today may be different than the ones using being used three months from now or six months from now. And so developers, application teams are looking for a ton more flexibility, a ton more agility than they were three, five, 10, 15 years ago. The other aspect is simplicity and reliability, right? As you know, that's a core component of everything we do. Our core products, our arrays, our storage appliances, we're very well known for the simplicity and reliability we drive at the individual product level. Well, as we scale and look at larger environments, as we look at customers' expectations for what they expect from a cloud-like service, there's the next level of scale and how we deliver that simplicity and reliability, right? And what do I mean by that? Well, a large enterprise customer who wants to operate like a cloud wants to be able to manage large fleets of infrastructure resources, be able to package them up, deliver infrastructure services to their internal customers. They want to be able to do it in a self-service, policy-driven, easy to control, easy to manage way. And that's the next level of fleet level simplicity. And that's really what Pure Fusion is about, right? It is allowing operators that control plane to specify those attributes and how that service should be delivered. Same thing with Powerworks, right? If we think about simplicity and reliability, containers, cloud-native applications, microservices, a lot of benefits there, right? Very fast-moving space. You can mix and match components, put them together very easily. But what goes hand-in-hand with that is now a need for a greater degree of simplicity because you have more moving parts and a greater need for reliability because, well, now you're not just serving one application, but 30 or 40 working in unison. And that's really what we're after with Portworks and Portworks Data Services and the evolution of that family. So getting back to your original question, I really look at today's announcements as not a pivot, not a reinvention, but the next logical steps in our long-term journey to help customers modernize everything they do around data. Right, thanks for that, Rob. Hey, I want to switch topics. So virtually every infrastructure player now has an as-a-service offering. And there are lots of claims out there about who was first, who was the best, et cetera. What's Pure's position on this topic? You claim you're ahead of the pack in delivering subscription and as-a-service offerings in the storage industry. You certainly were first with Evergreen. That was sort of a real change in how folks delivered. What about as-a-service and Pure as-a-service? What gives you confidence that you have the right approach and you're leading the industry in this regard? Yeah, absolutely. I mean, I think first and foremost, we think of everything we do Pure as-a-service and whether that's delivering products and helping customers to run and operate in an as-a-service model internally or whether it's Pure taking on more of that run and operate as-a-service ourselves with Pure as-a-service. And so the second part of your question, which is what is it that sets us apart? What are we doing differently? What gives us confidence that this is the right path? Well, fundamentally, I think the difference is, obviously this is a hotter topic in the industry of late, but I think the difference between us and the competitive set is we really look at this as a product and technology-led philosophy and strategy, and we have since day one. And I think that's different than a lot of others in the industry who look at it as a little bit more of a packaging exercise between financial services, professional services, wrap it up in T's and C's and call it a service. And what do I mean by that? So if you look internally at Pure, everything we do, we think of as a service, we have a business unit organized around it, we have an engineering team, significant resources dedicated to it and building out service offerings. When we think about why this is technology-led, I think of a service for something to be thought of as a service, it's got to be flexible, it's got to be adaptable. I've got to be able to grow as a customer and evolve as I need, whether that's changing needs in terms of performance and capacity. I've got to be able to do that without being locked into day one rigid kind of static swim lanes of having the capacity plan or plan out what my user is going to look like 18 months from now. I've got to be able to move and evolve and grow without disruption. It's not a service if you're going to make me do a data migration or take a downtime. And so when I net all that out, what are the things that you need, the attributes you need to be able to deliver a service? Well, you need a product set that is going to be able to be highly malleable, highly flexible, highly evolvable. You need something that's going to be able to cover the entire gamut of needs, whether it's price performance, tiers, high performance, capacity, lower cost price points. You need something that's got a rich set of capabilities, whether it's access protocols, file block object, whether it's data protection properties, replications, snapshots, ransomware protection. So you need that full suite of capabilities. But in order to deliver it as a service and enable me as a customer to seamlessly grow and change, that's got to be delivered on a very tight set of technology that can be repurposed and configured in different ways. You can't do this on 17 different products and expect me to change and move every single time I have a service need change. And so when I net that out, that puts us in an absolutely differentiated position to be able to deliver this. Because again, everything we do is based on two core product families, Portworx adds a third. We're able to deliver all of the major storage protocols, all of the data protection capabilities across all of the price performance and service tiers. And we're able to do this on a very tight code base. And as you know, everything we do is completely not disruptive. So all of the elements really add up in our favor. And like I said, this is a huge area of strategic focus for us. So these offerings, they're all part of the service-driven component of your portfolio. Is that correct? Absolutely, yeah. Great. You talk all the time about modern data experiences, modern application, modern data, changing the way customers think about infrastructure. What exactly does that mean and how are you driving that? Well, I think it means a couple of different things but if I were to net it out, it's a greater demand for agility, a greater demand for flexibility and optionality. And if we look at why that is, when I talk to customers, as they think about infrastructure, largely they think about their existing application demands and needs, what they're spending 90% of their time and budget dealing with today. And then the new stuff that they're getting more and more pressured to go off and build and support, which is oftentimes the more strategic initiatives that they have to serve. So they're kind of balancing both worlds. And in the new world of modern applications, it's much more dynamic, meaning the application sets that are being deployed are changing all the time, the environments and what the infrastructure needs to deliver. It has to change more quickly in terms of scaling up, down, growing, it has to be a lot more elastic. And it has much higher variance. And what I mean by that is, if you look at a modern cloud native microservices architecture type application, it's really 20, 30, 40 different applications all working in concert with one another under the hood. This is a very different infrastructure demand than your more traditional application set. Back in the day, you have an Oracle application, you go designing an environment for that. It's a big exercise, but once you put it in place, it has its own life cycle. These days with modern applications, it's not just one application, it's 20 or 30. You've got to support all of them working in unison. You don't want to build separate infrastructures for each piece. And that set of 20 or 30 applications is changing very rapidly as open source ecosystem moves forward as the application space moves forward. And so when customers think about the change in demands on infrastructure, this is kind of what they're thinking about and having to juggle. And so that at the end of the day drives them to demand much more flexibility in their infrastructure, being able to use it for many different purposes, much more agility, being able to adapt very, very quickly, and much more variance or dynamic range, right? The ability to support many different needs on the same set of infrastructure. And this is where we see very, very strong demand indicators and we're very invested in meeting these needs because they fit very well with our core product principles. Great, thank you for that.  You actually put some substance on it, Rob. We're going to have to leave it there. Thanks so much for joining us today. Thank you. And look forward to having you back soon. Now, in a moment, Scott Sinclair, who's a senior analyst at Enterprise Strategy Group, speaks with theCUBE's John Walls to give you the independent analysts take. You're watching theCUBE, your global leader in high tech coverage.


Don't want it all the way. OK, so everybody can hear me at this point? Yes. OK. First of all, a little housekeeping. There is a registration book that Michelle and Maria have been organizing. Please sign in right neatly. And your email address is the most important thing, because I've got a couple of spammers that will pay big. So what you really need to do is write neatly. The list, excuse me, gets read. That email list will be used to send out news as it happens. And I'll talk a little bit about that before. But first of all, again, as Phil said, thank you, everybody, for coming. This was kind of on the spur of the moment. I only had about, I guess, a month and five weeks to plan. And it's very, very amazing that so many people came from so far away. And I understand the circumstances are not the happiest, but would you rather be looking at my ashes or me personally? Don't answer the question. Because I know my stepbrother will say ashes. And I'll be talking about him in a minute. First of all, as Phil said, there's a lot of people from different parts of my life. We have, of course, my family. We have my brother, my father, and my stepbrother here. And I have to give thanks to my father for, well, the obvious reasons. But he's been a very steady influence in my life over the years. I've never seen him angry. He is a Viking by descent handsome. He does not swim the sword around nearly as much as he used to. And he's given up the helmet with the forms coming out of it. But he has a Scandinavian extraction and has shown quiet strength through all my zaining is over the years. And he's shown incredible support. I've been up until very recently in my life when I needed some additional support. Always. Also, of course, my brother, who, as simply rivalry goes, we were almost at the MMA level, close. Weapons weren't involved. Fire was involved. So we fought bitterly growing up. He's even been through divorce and all that fun stuff. But as we got older, we got to be much closer friends. We had a lot of adventures together. We bummed around Asia for a couple months at one point. We did some pretty cool things. And during one of his high school, going on camping trips, he was off in my chauffeur. He bitched in a moment about it, but we still managed to get the main friend who we went into the woods. And my brother drove back home. Thank you, little brother. His little brother was out of the scene for a week. He's giving knowledge to my step-brother. Now, that's the Jewish side of the family. OK, this is, OK, it gets a little confusing. OK, I have a mother and a father. They divorced when I was seven. My step-mother, a lovely woman from Maine named Sally Hansen. Not that person. And so they got married. And then my mother married her regal. She was the nice Jewish boy from Newton, Massachusetts. And that's where I actually spent most of my teenage years in the regal household. Now, Herb had three kids from a previous marriage. Wow, this is confusing. I'm getting older, too. So they were the three regal kids. And David was one of them. David, are you the youngest? Yes, I am. David had a unique gift. David is an entertainer, by the way. He's having a Hollywood movie. But he could make people laugh. And I noticed that because I first met David when I was, I guess, 12 or 13 years old. Maybe even younger than that. And he had this unique ability to have the perfect, awful, witty, retort, quip, whatever you want to call it. And it disarmed people all around him in this situation. And here's David with the right thing to say at the right time, perfect timing. That was a joke, by the way. And I secretly emulated that for a year. David doesn't know this, by the way. But I secretly emulated that for years. And I finally got good enough in high school to avoid a potentially expulsionary event by disarming somebody with the right quip and a witty retort to make them laugh. So I give David a lot of credit for that. OK, now we come to a gap in my life. There's nobody from my college days here right now. This is the realm of my first marriage. Didn't get married then, but that kind of took all my social time. And that marriage ended, of course. And now we come to my local friends from here in South Florida. We all remain friends through your college years, because that's one of the great reasons we have this moment. So very, very valedictory. Disappeared after I had been married. Right, so for the high school folks, as Phil had said, we have Phil Schwartz. We have Clayton Adams, who has actually been in school briefly. But I was a four-year student briefly. And he was my roommate. Then we had Higham, who we went to for a whole length of time. And there's a fourth guy named Sebastian Younger, who could not make it, because at 55 he had a newborn. Stop asking. Now, Sebastian will ultimately be seeing this video. And God love you, Sebastian. But you're really pushing your judgment. He wrote a couple of really good books. He wrote the book Perfect Storm, by the way. No, I was kidding.  He's a good writer. He's a very good writer.  There's a very small high school called Concord Academy. There was only 63 kids in the graduating class. They're very well. And then, of course, I don't have any friends from college. And now we're just coming into my adult life here in South Florida. And I have all my adult friends from here in South Florida living here about 14 years, 13 years longer than I thought I'd live down here, because you never end up in New South Florida. I can't believe I'm down here so long. And I didn't just show up. I came here for a job.  And I had a full relocation the whole line yards. So I have this whole crew. And you know, you've all got name tags. Thank God. I can't read them, but still. Now they're coming. Can't read anything at this point in my life.  And for those of you who don't know, I think most of you know, is that I've had a pretty active online life through my blog and my Twitter account this past about five and six years. And I've met some wonderful people online. And there are some people here that I've met for the very first time in real life. My friend Matt, for instance, who flew in from Austin, Texas. I'd seen him via some video chat programs. But I've never actually seen him. He is. Yeah, he's sitting over in a corner. My name is Joe Business. He's from Texas. So he's there for the dangers. But he was for helping me. We did some various errands. I did not find my kilt. I was going to wear my kilt tonight, but it was a lot of storage somewhere. And I couldn't find it. And so these are the people that are sort of representational of this, of who's here right now. I have to give thanks. This is going to be hard. Tracy. Hey, baby. Tracy and I were just in relative terms less than a year ago. And our first date was just over there, but an ice cream place, which, by the way, for you single guys, I recommend ice cream for the first date. No, seriously, I really do. And I told her about my condition, my cancer. First of all, you've got to have a real reason to wear an ice cream. OK, so for a real reason, I only have a little ice cream. And I told her I had oculomabinoma. I've lost my ball about two years ago. It's part of the treatment regime. But there's never a 100% chance that it's going to disappear. She took a chance. Now, I thought I had a couple of three years left in me. She did, too. Well, it turns out I don't. But she's there. I've seen her cry once, just once over this. Remarkable, absolutely remarkable. And frankly, I've been married twice. I won't talk about my Venezuelan period. Venice. I just got to Florida. I mean, what did I know? She was Venezuelan. They raised them on ranches to look good. They shipped them into Caracas for the various beauty hedges. I swear to God, that's the truth. So anyway, so then I met Tracy. And it's been an amazing, amazing experience. Because this shows me that the best realm of love really is unconditional. And I think the most might, though, life, realizing that love is conditional, which was finished. And then, Tracy, how dare you upset my worldview? I had a streak of cynicism going that was this thick going real well until you came along. So they're going to burn my cynicism along my ashes. So anyway, that's all I have to say at this point. Again, I am very, very grateful. This is a celebration. Don't talk about what's going to happen to me. Talk about what's happening right to second. And right to second, I feel pretty good. Now, that being said, we have to be brutally honest. I am not seeking any kind of therapy at all, because there are not. And I know you people mean well when I'm getting the emails for marijuana treatment, yoga, finding faith in God, a diet. Somebody recommended that I freeze my head. Is there news on the radio? Thank you, David. That's impossible. I know. It's already too cold. No, I mean, so I'm getting very, very, very happy. I like that. I don't want to treat it. We'll talk later. But so I've been getting a lot of well-meaning wishes about feeling with this particular type of cancer. What I have is a melanoma that is a blood-borne cancer. It is resistant to pretty much everything out there, with the exception of small elements of immunotherapy. Again, I have declined many of my three decisions to have three and a half years of care for this. And I know people mean well. But I'm just going to say, yes, thank you for the advice. And I'm not going to do anything. And I don't want to move like a bank. But I also want to make my decisions. And so it has been affecting my body and my choice. That being said, in the future, if you want to get news on my condition, best place to hit it is my blog, www.brivenpan.wordpress.com.  I want the words that I've written for to be the defining element of who I am. There's a lot of videos that have come out on me recently that's got hundreds of thousands of views. I'll be assembling it all back in one spot. When things get really bad, there will be an email list. What'll happen is is that eventually, probably sooner rather than later, I'll start experiencing symptoms of liver failure. And this is the reality on the ground. I'm not going to lie. What will be a matter of days of most weeks? So we have to be aware of that. This is why I'm having a party today. I mean, what a great reason to have a party. Thank you. At that end, drink, take Uber, or walk, or whatever people have you. The staff here is very good. I know the staff. I know Skyler and I are back there. Tip heavily and tip often, because whether they don't know it or not, they're actually paying for my cremation services. No, I'm just kidding, go on and pay for it. No, no, it has. I've already paid for it. It's already taken care of. And the good folks at the hospitals have already been talking to me. They're really efficient. They want me dead. Well, think about it, it's hospice. So they want me dead. But they're very nice. They're just a little too efficient. Keep wondering about my bowel movements.  They're really curious about my bowel movements. So on that happy note, enjoy the rest of the party. We'll be here until midnight. Or maybe later, who knows. Oh, we're combining this with something else. Tracy. No, no, no, no, you say the words.  OK, fine. All right, do people know that my birthday is coming up? I didn't know that. I didn't know. It's March the 7th. It's like in just a few days. Right, so there's a cake over there in the bottle of scotch. And leave the scotch behind. Don't touch the scotch. The cake your everybody's welcome to. So yes, I mean, I suppose we could say happy birthday, but it seems kind of. Let's do that. Let's do that. I can't do that. I can't have what's happy birthday to me. Yeah. Oh, my god. Happy birthday to you. Happy birthday to you. Happy birthday dear to you. Happy birthday to you. South Florida? Suddenly, I have many more housing options available. Because everywhere down here is 55 plus, so here we go. OK, so anyway, so we're going to be cutting cake. We're going to be handling. And if you all haven't met each other, just walk around and meet each other. Pretty cool, huh? Yeah, thank you. And Paulette, by the way, the microphone can be yours at any time tonight. So it's up to you. I'll leave it at that. Paulette is actually a professional singer. Some years ago, she won the Best of the United Kingdom for a singing contest on TV, sort of like Merritt Highwood. Say that by the way. Yeah, she's from Birmingham, so speaks low. So, and again, if you have any questions about what I'm dealing with or whatever, just give her up to me. That's about it. And thank you. Thank you.


At the University of Greenwich, our Faculty of Engineering and Science is where excellence collaboration and inclusivity converge. We have a commitment to academic excellence, to impact students' lives by preparing them for graduate level employment. We believe in the power or knowledge of innovation and discovery so that our learners are fully equipped to thrive in their careers and help us all tackle societal challenges. We aim to change people's lives and we believe that we do change people's lives. We have a strong reputation for research and our collaborative learning sets us apart. The research that's needed to address these challenges requires a multidisciplinary and an interdisciplinary focus. Partnerships are so important to us. All of our courses are co-designed with industry, so we get industry professionals in to talk to us about what's changing in the sector. So the Faculty is actually connected by two campuses, the Greenwich campus and the Midway campus. It has always been my dream to study in London, especially University of Greenwich because of its rich heritage. We have a huge history. The School of Engineering at the Midway campus has been offering engineering degree programmes since 1935. You'll engage in interdisciplinary programmes. Having diverse perspectives and innovative thinking. Students in our programmes are extremely privileged to have the hands-on experience of scientists who work across the world. We have the philosophy of learning by doing and so to do that we have continuously been investing in very advanced state-of-the-art analytical tools. They can practice on equipment that actually they'll be using in the real world, in industry. Most of our courses in the School are accredited, which means that our courses have been looked at, they've been verified and they've been acknowledged as preparing students ready for industry. Employability is a key aspect of what we do within the Faculty. We are constantly being put in contact with large companies that are doing apprenticeships and internships. It really develops their skillset and it makes them more employable. The University of Greenwich champions a supportive and culturally diverse community. We prioritise inclusivity, making all students feel welcome. It's a very friendly environment. We do have immense number of supports that are available out there, starting from a well-being team, employability team to the academic service team. It has been a big part of my success story, having been given me the opportunity to come into the UK to study, to learn. Choose the Faculty of Engineering and Science at the University of Greenwich.


Welcome to the School of Finance and Management. Welcome to our webinar on the various postgraduate programmes that we offer. I'm Dr Richard Alexander. I'm the Learning and Teaching Coordinator of the School of Finance and Management and I also personally oversee the postgraduate programmes in particular and even more specifically I'm the Program Coordinator of the MSc Finance and Financial Law programme. All three pathways we'll go into a little later on. So at a glance we offer not just in the School of Finance and Management, across the whole of SOAS we have over 100 graduate programmes. Our library is one of the UK's national research libraries. There are only four of them and these are specialist libraries for particular areas and in the case of SOAS we are the national research library for studies in African, Asian and Middle Eastern studies. We offer, it says on the slide I'm paralleled, it is a parallel range of non-European languages. We literally teach Yoruba to Korean and everything in between. In total degree combinations that might be single armours, law, it might be degree combinations double armours, it might be Arabic and History, more than 400 combination of degrees are taught across SOAS and we have one of the most diverse student bodies anywhere in the UK. 50% of our students are from outside the UK and I can say within the School of Finance and Management when you look at our postgraduate programmes, any of our postgraduate programmes that number goes up to well over 50%. So we have currently in one class we have students from Bulgaria, from Egypt, from Hong Kong and in keeping with that we have the largest concentration of specialist staff of any university, not just in the UK but anywhere in the world. Now we were formerly known as DEFIMS, the Department of Financial Management Studies. We became the School of Finance and Management in 2016. Just after the 2016 Guardian League table came out and we were ranked sixth in the United Kingdom and first in London for Business and Management and yes that means that for Business and Management we were ranked above the LSE, we were ranked above Queen Mary's and other universities and colleges you may or may not have come across. In the latest National Student Satisfaction Survey, this is a survey of final year undergraduates, 96% of final year undergraduates in the School of Finance and Management said satisfied with the overall quality of that course. That put us fourth out of the 116 Business and Management departments across the entire United Kingdom and within the School of Finance and Management we ran a range of master's degrees. Most of them MSc but in one case an MRI as a master's of research are coming to that. We teach MSc international programs with regional specialisms in China, Japan and Middle East and North Africa. We have an MSc finance program. We have an MSc finance and financial law program with three different pathways. We have an MSc public policy management and an MSc public financial management and finally we have a master's of research and MRES in finance management. Now the MRES as we'll see focuses more on research skills. So let's look at the three regional international management programs. They focus on finance and its environment in China, Japan and the Middle East and North Africa respectively. So we combine the core principles of international management which would apply wherever you're managing a corporation with specific regional modules training you how to manage an enterprise in China, Japan, the Middle East as the case may be and also incorporating a number of finance disciplines. So how does that work in practice? When we move to the next slide. Right we start off with two generic core modules international management and research methods in management. We teach you how are the key research methods that will feed in to your dissertation that you take at the end of the program which is a piece of extended research, extended writing of 10,000 words and to put that in context the assignments that are that you will write one for each module that's 2,500 words. So 10,000 words is an extensive dissertation. The research methods in management module is designed to teach you the skills that you'll need to complete that. Then there are regional core modules depending obviously on the region we're talking about. Management in China are two of them, the first looking at domestic perspectives, the second international perspective management in Japan, one management in Japan, two there rather than taking two distinct perspectives what we have is we have two regional core modules the second building on the first over two towns and finally for the Middle East and North Africa again two regional modules economic business and institutional environment for the Middle East and North Africa and management perspectives and sectors and then we offer a range of optional modules and we offer we offer several of them and in total in total you will take four of these making eight modules in total all our programs all our MSC programs consist of eight modules and the balance between core modules and optional modules or electricity like they vary slightly from program to program. So as we see in the international management programs there are four core modules for optional modules and you choose from this list and you can see on the slide bank and capital markets, Chinese commercial law, corporate finance, corporate governance, cross-cultural management, international business strategy, international resource management, just to warn you incidentally before I go on to the second part of the list that we do we do not guarantee that in any particular year all every optional module on this list will be running it varies slightly from year to year but this gives you an idea of the range of options we offer that international marketing, international securities regulation, Islamic bank and finance management and topics in the Chinese economy. We also offer a range of language optional modules now here I should be clear that the language modules are optional so if you wish to take international the MSC international management in China for example and you don't want to take any language options that is perfectly possible we do not require you to learn Chinese in order to complete the program however several of our students do want to take this advantage so those that already have a significant knowledge of Chinese would take advanced or could take advanced Chinese for business we also offer a range of special courses in Chinese of various levels going up from level one basic up to level four quite advanced and for Japan again we offer a range of Japanese language options starting with basic Japanese one going right up to higher advanced Japanese. Moving on to the MSC finance program now if the object of the MSC international management programs is to train you in the particular skills that you will need to exercise a management function in business enterprise in either China or Japan or the Middle East and North Africa or alternatively play a management role in an enterprise or corporation had courted in China, Japan, Middle East and North Africa in a different part of the world the MSC finance program as it says on the tin focuses on the finance sector and the object is that you will acquire the key analytical tools either for career in finance or to go on to join one of my colleagues undertake further research at PhD level and become a researcher in finance and so we teach you the main issues and methods they're not the same thing so the issues of theory the methods of practice in corporate finance risk management banking financial econometrics the idea is that you apply these in a profession and so we start off with a with a pre-sessional introductory module robotics and statistics for for finance and this is this is a pre-sessional course so you take that at the beginning over three weeks in September before the the main part of the MSC gets going at the beginning of October and again as with all our MSC programs you finish with the 10 000 word dissertation in between you take four core modules corporate finance economic principles and data analysis finance and the market risk management and then again we offer a range of optional modules now all the we don't offer language options on the MSC finance program what we do offer is all other non-language options on the but you could take on a management program so all those international marketing international securities regulation topics in the china's economy all of these are offered plus advanced quantitative research methods if you really want to get into quantitative finance bank regulation and resolution of banking crisis i mentioned already that we offer international securities regulation we also complement that with a separate module on banking regulation and blockchain and distributed electronic measures moving on to my own program the msc finance and financial law now this was created excuse me this was created very much as you know as a specialist program addressing a key gap a key key lacuna in the financial sector what we found was with a typical bank you will have a group people in the various departments of the bank who were experts in the finance and principles of finance were experts in the financial products that they worked with but had no significant knowledge of the law regulation relating to their work for that they relied on the compliance department but if you asked about that and they said yes the compliance department deals with that just as you were leaving to talk to compliance they would say but the problem is that the people compliance do not understand our business they don't understand what finance is actually about then when you got to the plans department you would find that this was broadly speaking true uh that they were typically lawyers they had a good law or regulatory background not such a good knowledge of the principles of finance but they would say just as their finance just as their colleagues in the other department said if only the compliance officers had an understanding of our core business the compliance department would say if only my colleagues in the other department had a reasonable understanding of the law and regulation certainly don't have to come to us every five minutes so the finance and financial law programs created to train a new breed of financial professional somebody with an understanding of both sides so we prepare students for employment in international banks and investment funds number of graduates from the program have taken up positions in banks in London in Hong Kong in Singapore legal practice a number of a number of them have gone into law firms incidentally I mentioned in terms of the international banks and investment firms either big financial centers London, Hong Kong, Singapore but you also other more regional centers such as Lagos and Nigeria others have taken up positions in regulatory institutions some of them started in one move to another I think of one former student who worked for Deutsche Bank for some years in Beijing and then moved to the Hong Kong Securities and Features Commission and some have gone into academia we train you for all these potential different careers and then you in terms of the specific modules and study path you take you move into one or one of the others and we look at both national and international finance modules and more domestic in nature others and more international and we look at how financial and legal principles are applied in the context of actual case studies so again we start off with pre-section introduction modules again over three weeks in September introduction to financial analysis introduction to law and legal method to teach you the key principles of law and finance that the other modules will build up then as I mentioned there are three pathways there's what I called a generic pathway with about MSc financing financial law which is pretty much evenly balanced between the finance side and the law side you can alter that balance a bit through your choice of electives but it's designed to be more or less MSc finance and financial law with a major on finance or MSc finance and financial law majoring on the law side so for the generic program if you like we start off with we have five core modules you take three electives core finance funds in the global market financial law legal aspects of corporate finance and legal aspects international finance all of these are core modules compulsory modules then on the for the electives again all the non-language modules were offered as electives or optional modules on the international management programs are offered as elective or optional modules on finance and financial law in addition we offer bank regulation and resolution of banking crisis and there are some students who take both the international securities regulation module and the bank regulation module and finally again blockchain and distributed electronic ledgers on the finance side you take four more four core modules now even where you major in finance or law we feel it's important if you're going to graduate with a degree with with the title MSc finance and financial law you should have studied something of both sides so you take as your core modules corporate finance financial law risk management and finance the global market so three finance modules one one law module then again on the elective side all the non-language management options plus bank regulation and resolution of bank crises blockchain and distributed electronic ledgers and legal aspects of corporate finance what's the legal one of the legal issues involved in how corporations finance themselves and on the law side again it's four core modules but it's weighted more on the law side financial law legal aspects of corporate finance and legal aspects of international finance plus one finance core module corporate finance and the similar list of elective modules moving on MSc public policy and management public policy and management and it's just of course if you like MSc financial management what these do is they offer both the technical education but also critical and comparative material how is public policy developed and implemented how is the public sector managed across the world in particular in the MSc public financial management how are public finances responsibly managed so starting with public policy and management there are four there are four core modules public policy and management perspectives and issues public policy and strategy managing organizational change and research methods and management again finishing up at the end with a 10 000 word dissertation and a range of optional modules and these modules are aimed more at the public policy side so we don't simply say we offer all the non-language management electives as we do on the MSc finance and on the MSc finance and financial law we focus more on on management and policy so we do offer blockchain and distributed electronic ledgers cross-cultural management what's involved in either managing an office an enterprise in this particular case a public sector enterprise in in a culture different to the one you grow up what is involved if perhaps you're working in an international organization where with people under you from a variety of different cultural backgrounds international human resource management some issues but more on the human resource side managerial accounting macroeconomic policy and financial markets and two public financial management modules planning and performance and revenue meanwhile the public financial management programmers would expect focuses more on the public finance side and there are there are three core modules in public financial management as you can see financial reporting planning and performance revenue again finishing in order to prepare you for the dissertation research methods and a range of optional modules blockchain and distributed electronic ledgers international securities regulation macroeconomic that's important because because government also engage in securities trading and investments macroeconomic policy and financial markets managerial accounting and then public financial management audience and compliance now you might say well why is that an elective module because not everyone in gay training for public financial management will want to specialize to that degree in audit and compliance but some well and then public policy and management perspectives and issues public policy and strategy and finally the masters in research now this is not an msc it is designed to train you in the skills that you're going to need to undertake extended and more in depth research it's designed to do one of two things either for those who know that they want to go on to do a phd and understand that that their bachelor's did not provide them to not prepare them with sufficient research skills and furthermore an msc will get them partway there but memories will give them greater preparation specifically in research skills or maybe it you know or maybe it's it's for for someone who says i don't want to be an academic but i do understand that in my future career i will be in charge of a major research project and i want to gain the skills that they put me to do that so we have four core modules analyzing qualitative and quantitative data theories in management and finance research design and epistemology and advanced quantitative research methods so what if you like one theory module meet others rule about analyzing data research the dissertation is not 10 000 words it's 20 000 words and there are a range of optional modules with a smaller range uh by a bank regulation resolution of banking crises corporate finance corporate governance international securities regulation islamic bank and finance address management and just to flag up so far i've been talking about our on campus programs uh our our on our on campus programs provided over one year full time or two years or occasionally three years three years is right normally two years part time here at the so-as campus in london but we also run a number of distance learning or online programs and we offer those at msc level they can make a list of eight modules and we also offer postgraduate diploma six modules uh unlike the on campus programs where each module is 15 credits on our distance learning or online programs these are 30 credit modules so so rather so rather more rather will study uh over the week and indeed there are two assignments as we'll see rather than some p1 and you can take an msc finance or or postgraduate diploma with four different pathways first pathways are economic policy banking financial sector management and quantitative finance you can take a msc or postgraduate diploma in finance and financial law in international business administration public financial management or public policy management and we offer postgraduate certificate programs uh so uh so these would be so these would be two module programs in banking economic policy financial law specifically financial or rather finance and financial or financial sector management public policy public management and quantitative finance and if you're particularly interested in our distance learning programs details of those are set out on a separate website which we created dedicated to our online learning programs and the the link is there on the screen www.saphems.ac.uk and also i thought it'd be useful uh if any of you already aware that you want to vote you're interested in these specific program i've put on this slide a list of all the program conveners and and yes uh i will be making these slides available uh to my colleague who can who can send them out to those who've registered for the webinar so uh so in answer to claudia's question yes we can do that these are the uh the slide gives you the email address of each of your each of the conveners and very briefly application process we ask for the equivalents at first degree about this degree with good grades in any subject and what we mean by good grades is equivalent to a uk upper second class honors degree or in the us system a gpa of 3.3 more or less and the chinese system we would look for an hour for an average average grade of 80 very slightly if you if you come to us with a with a bachelor's degree from stanford with a gpa of 3.1 that's not could be a major problem similarly if you come if you come to us from central university finance economics from futan with or another or even any of the project 211 universities with uh with an average of 75 it'd be likely to be uh be successful we consider relevant professional qualifications and experience but we don't require them so if anyone's watching this webinar and thinks just i'm just coming to the end of my bachelor's degree i don't have any professional experience yet don't be put off what uh what this is saying is if you have professional experience we will take that into account particularly if and it happens your first degree didn't go quite so well a relevant professional qualification or work experience can compensate for that but if you've come straight out of your bachelor's degree please do apply to us and our application system is online we don't some universities have a formal closing date we don't but we would encourage you to apply early uh particularly those of you who be required to use your visa the early you apply the easier it is to get your feet to go through the visa process in good time in order to to start the program in the in the autumn so finally are there any questions over to you uh a very interesting question just came in uh from the who is who is not a speaker of arabic and was asking about the islamic finance the islamic bank and finance module and would the problem is that would it be a problem taking that module if you don't have a knowledge of arabic no not at all the islamic bank and finance module does not assume any prior knowledge of arabic it's true some it's quite popular with students from the middle east who who may well have knowledge of arabic but all the necessary arabic language terms are explained to you as concept in the course of the module so no if you don't if you don't speak read or write arabic don't be put off do if you're interested in role for that module and you certainly uh what what i would say is although some students from the middle east from a muslim background uh take islamic bank and finance others don't with no with no arabic at all and they do very well in the module so if you're interested in the concept sign up for it uh is the is the literature uh that i could send out uh to help help people help potential students to start reading up uh certainly when you enroll on a particular program you will then be sent a reading list uh either by admissions or by the department and student support officer a reading list that is tailored to that particular module um you uh all all those who enroll will get one of those um be difficult really because of the breadth of the range of the programs that i've gone through it'd be difficult to come up with a list of literature relevant to all of them but if you got in touch with me or with the convener of a particular program you're interested in we could certainly send you a preliminary reading list yes uh uh you somebody asked uh are are my contact details are the contact details uh are our email addresses also on the soas website yes they are if you go to the soas website and you'll see uh departments uh you then click on funds and management and then then you click on staff and there you've got uh are various are various contact details or alternatively from the school funds and management website a web page if you like a section of the website you can click on the degree program you're interested in op will calm the name and email address of the content of that program okay i think uh that pretty much uh brings us out of time so i i'd like to finish by thanking you very much for your attention and i do hope to be seeing some more hopefully even all of you hear it so us in the autumn so thank you very much


lots of loyal friends and family. It's rare by the way. And we felt we were onto something because it was genuine and it felt real and it motivated us to keep going and it made us wanna keep doing it. And in under a year we were approached by, you know, Fred Siegel, Planet Blue, by big name stores that we grew up shopping from and they're like, they want our product, of course. And we were just a few months old. And at that, you know, I think the first year or two for a brand entrepreneur. Yeah, it's important but maybe you don't get that yet. Maybe you don't get that you're onto something quite yet in that, just in that time. And we're lucky to have felt that and to have just so much motivation to keep going and so much excitement and passion.