Schedule a Call

Transcript

We live in a in a time where everyone really expects instant gratification and each of us as consumers we expect businesses now to really respond to our needs in real-time these expectations have been fueled by the e-commerce giants who are increasingly raising the bar if the item we need is not in stock we simply go elsewhere you know you look at someone like amazon and items there are picked packed and ready to ship within two hours of placing an order and we can get same-day delivery in metro Sydney, Melbourne and Perth now to compete on the retail side sort of the traditional bricks and mortar they've really raised their game as well critical to their success is the time it takes to turn an idea into merchandise actually sitting on the shelf and the retailers that are able to respond faster to consumer demands they're the ones that are a capturing market share but they're also getting the increased margins as well you know take Zara for example they know the faster they can respond to new trends the more likely it is to succeed in supplying you know the right fashion merchandise at the right time across its global retail chain just for example in 2015 you know a lady named Miko she walked into Zara store in Tokyo and asked for a pink scarf and they didn't have any in store so she walked out empty-handed the same thing happened almost simultaneously to you know Michelle in Toronto, Elaine in San Francisco, Giselle in Frankfurt all who walked in asked for a pink scarf and again left empty-handed seven days later more than two thousand sorrow stalls globally started selling pink scarves 500 000 were dispatched to be exact they sold out in three days now Sarah has a sophisticated technology event-driven system in place which enables information to travel very quickly from the stores back to its headquarters in Spain enabling rapid decisions and then enabling them to respond very rapidly to getting produce manufactured and onto the uh the shop shelves and what we're seeing is you know as retailers ramp up their own service levels whether you know online or in-store they're expecting their suppliers to shoulder their share of the load and this is putting pressure on manufacturers third-party logistic providers to be able to respond faster whilst at the same time meeting tighter service levels often with stiff financial penalties for orders that are either incomplete or miss agreed delivery windows and a key enabler here is the ability to rapidly share information across all participants within the supply chain so that each party can play their part and this isn't limited to consumer produced goods you know in healthcare the ability for stakeholders to share adopt and apply medical knowledge in real time enables proactive and accelerated care this provides better base patient outcomes whilst at the same time optimizing the use of assets to deliver that care you know in finance money now moves in real time it doesn't take three days to transfer your money to another bank account and so the ability to detect prevent and respond to either mistakes or suspicious activity in real time is critical to prevent fraud and ensure you know compliance and even in the utilities and resources sector except for example reducing the unit production cost of whether it's you know a resource or electricity is key to being able to both respond rapidly to change in what could be very volatile markets and provide having that sustainable profitability so what we're really seeing is the need for business to operate in real time is pretty much critical across almost every industry so with that I'd like to go to a poll and just get your initial feedback on you know is it important for yourself in your industry to respond in real-time to your customers.

The votes are coming in - about half of you voted would encourage you all to vote - simple yes or no just get your thoughts on this.

So, if we look at the results there yes I mean the vast majority of you agree there's probably a couple of you who think not yet that it's important to respond in real time but really what we're seeing from this and from what we're seeing elsewhere is it's becoming very, very important to be able to respond in real time to your customer needs so if we move on to the next slide many of you are probably familiar with the with this article that appeared in the economist about three or four years ago now and it really is data that is the new oil that is powering um the real-time business but there are certain things where you know oil and data actually quite different you know data itself is not a limited resource you know indeed it's expanding at an incredibly exponential rate so there's more and more data to available to us all the time um and with oil as more oil enters the market then the value of oil tends to go down you know the reverse is true for data the more data we have the more value that we can typically derive from it and again the value of oil is not you know based on how fresh it is you know typically all has been stuck underground for thousands of years but with data as data ages its value can diminish and conversely real time data what's happening right now is often extremely valuable particularly if that can then be supplemented with appropriate data from other sources so really you know what we're seeing is the most valuable data is the right data but having that in the right place at the right time to enable organizations to make you know take the right decision or the right action accordingly

So when we look at data well actually data is derived from events you know you take something as simple as your bank account you know every transaction in there is either you know it's either you're spending money which is money leaving your account or you're receiving money so money is coming into your account but that balance at any point time is the sum of all the events that have had occurred against that account over a period of time and events are happening everywhere you know obviously in our applications in cars in supply chains in appliances machinery etc and what we're finding now though is as more and more of these devices and things become connected to the internet it's becoming a lot easier to collect those data about those events from just about anywhere.

If we look at this in terms of from a business perspective what does this mean well when events occur what's critical is how we respond to that event because that's what's going to drive the outcome and obviously from a business perspective it's how we can do that at scale because that's going to determine the outcomes that we get from a business perspective you know whether that's good or bad so again you know as we've seen recently obviously you know last year with covert et cetera we can't necessarily control the events but our ability to control our response and respond accordingly is what's going to determine whether we're successful or not from a business perspective and this is really where the role of the real-time digital backbone comes in and there's two key components to this there's Solace which we'll talk about in a moment which provides the event mesh and that's about getting that those events that data the right data getting it to the right place at the right time so that then you can initiate and control the outcome that all the response that you want to perform and that's where MuleSoft comes in it's about being able to essentially initiate the right decisions the right actions across your it infrastructure in order to deliver that outcome so with that I’ll hand over to Phil who can tell you a bit more about Solace.

Thanks Matt. So before we go into to Solace I'm just going to cover a little bit of what's been happening in the industry around what has led to event driven but really just some of the trends and the themes and some of the things that have changed to allow us to get to where we are today which is being able to do event uh event-based systems at scale across many industries so if we look at where integration and application developments come from you know over the years obviously, as we've moved away from sort of mainframe centralized systems trying to you know earlier releases of RPCs and calling across different systems and through SOA there was really an inflection point around 2010 and one of the one of the key things that you helped us with for example with APIs was the adoption of wire line standards so the rest standard which basically meant we moved away from this RPC was very proprietary APIs really exploded five to ten years ago based on the ability to change different systems at different times so now that that wire line standard meant that you weren't tied to a single vendor's platform you could mix and match different technologies to achieve outcomes and that was very important across organizational boundaries um around that sort of time as well there were also some event-driven APIs which are MQTT and MQP which we can cover a little bit later on but that evolving standards really paved the way for adoption the second thing that happened around 2010.

That's roughly when some of the early internet giants sort of really grew they really approached this scale and distributed architecture what's now known as the cloud-native architecture and that started to grow and really started to enable this building systems that work at scale and scale is very relevant but one thing it really meant is that you could be much more dynamic much more agile in how your system grows so rather than having to you know your traditional build a massive data center build all the applications build a monolith that meets your peak you're able to with cloud native architectures respond to growth or shrinking assets so you know and the cloud platforms like amazon google azure kind of have grown very well out of that agile infrastructure the third trend was really around this whole taking the monoliths and moving towards event driven microservices so breaking apart these very very large applications and making them smaller now that was really only made possible especially in a distributed manner when the network in around 2010 became faster than disc so all of a sudden rather than having this you know database at the center of the world where everything gets persisted we're able to move information across the network between components and to scale out in a very very distributed manner so and that that network changing uh may meant that you know when you're looking at events when you look if something happens it's much quicker to work off the event rather than waiting for something to have gone through a you know disc or a store um so moving on to the next slide so so tying this back to what matt was mentioning earlier so  business in real time there are a number of different business opportunities it's really you know what we've seen.

10-15 years ago really it was only capital markets and a few kind of very large deployments that were very much event driven but we've really seen this adoption very broadly and it's been driven by this need for real-time interaction real-time customer you know customer satisfaction but also

With bringing along with that the data has to be current so we can't build new event driven systems unless we can get access to the information and event driven thinking allows us to synchronize that that data that information across many parts of the value chain so the kind of initiatives that we see, the use cases at the technology level so we have things like event driven integration which is what we'll cover today so you know evolution of the at the SOA approach to integration moving much more towards event-driven integration and this is moving away from orchestration SOA was a heavily orchestrated process more towards choreography process or coordinated processes and being able to distribute that across different platforms, so IoT has been you know as we've digitized more things as we've put sensors on things we've instrumented more things IoT is inherited inherently event driven you know sensors emit emit events and but we also do you know things like remote control I’ve got an IoT device it just happens to be a vehicle these days so how do I unlock that vehicle remotely how do it securely how do I do it at scale for my fleet of millions of vehicles so IoT has a lot of these requirements around distributed and event-driven interaction from the microservices perspective so looking at event-driven microservices payment orchestration flows or provisioning flows when sort of people looking at these rather than an orchestrated process breaking down to microservices the flow of information the flow of tasks of those microservices um is very well-governed by an event-driven platform um finally the last two so analytics and event streaming so what we've seen there is you know analytics and getting streams of events that's really important for working out and getting insight but seeing that you know when I have an event I can drive the analytics stream off that event so I don't need to go off to all of my different data stores to replicate data across to a data repository and then start doing queries I can actually use event streaming to attach to those events in real-time as they happen so I've got this duality of transactional systems using eventing in my microservices platform but also streaming that off to events so you have multiple uses of events and then finally we talked about rest as being one of these early API pieces event driven APIs are becoming much more common so people are looking at rather than having people poll me and work has something changed being able to go off and stream or push information beyond their organization to other to other areas um so the platform that controls that that powers all of this really comes into a number of different components and we'll dive into those dive into those next.

So, in these components of my event driven architecture

The main thing right so my event event-driven architecture is really this pattern um promoting the use of events as the first class citizen so we mentioned the use cases they're part of and really the concept is my applications emit events there's those applications could be an IoT device could be a person it could be an application um they emit events and I have other applications that subscribe to or listen to those events with eventing those applications can be both transactional and analytical so we're seeing things like the convergence of OLTP and OLAP into this area but the core component in the eventing technology is called an event broker so this sits between the producers and the consumers and it does things like routing and filtering to make sure the right information gets the right place when I sort of take a step back from the broker and look at a global network or a network where I'm starting to do hybrid cloud some of my components may be in a cloud platform or maybe in a different part of my network so when I join all these brokers together they form what's called the event mesh and the event mesh takes .

That routing and filtering within a broker to a global scale so very dynamically allows me to filter and route events and then the final piece when we start getting into these event driven patterns being able to see what's going on being able to design what my applications look like we have a concept called the event portal and that really is very similar in nature to an api portal where you may describe your APIs people can reuse APIs are very similar however with an event-driven architecture because things are decoupled and you publish and subscribers don't know who each other are it's even more important in the governance space so just quickly on the next slide just wanted to run through some high level concepts to help people be successful with eventing um so that the concept of pub sub uh which essentially is this decoupling publishers from subscribers allowing it to be to be done independently of each other so adding later on subscribers um the concept of topic routing so being able to tag events with information and be able to use that information to filter and route without having to open the event without and see what's going on um eventing gives us the capability of a shock absorber so you know often we're dealing with legacy systems plus modern systems and they work at different paces or I may have some burst of traffic a burst of orders of my e-commerce application so the event mentioned event brokers can provide this shock absorption between systems eventing the stream distribution so your Solace take a view that this is network up so the event mesh is really an extension of the network with some um intelligence around information distribution there are other eventing technologies and the likes of Gartner and IDC and the analysts are covering the different types of eventing technologies in this space but we're often deployed with other technologies such as Kafka MQ series, compute streaming, compute engines in the cloud these are all nodes of the mesh and then finally as I mentioned the event portal for success really to understand and govern what's happening that's a key component.

So, my final slide just really wanted to give some pointers about getting started we're not normally dealing with greenfield environments we're dealing with complicated IT systems that are built 10 15 years ago even those built in the last five years can be not event aware but the first thing I may want to do is get access to the events so the first step is really to allow those applications to emit events to publish events and I can do that in parallel to what's already running so I don't need to replace everything that's there I can leave everything I've got more often than not in the second part Im actually interested though in building new applications so I'm doing some innovation I'm taking advantage of modern cloud platforms I've got an API gateway I'm talking about events within and across my value stream so being able to allow this platform modernization but most importantly where we have events happening in my legacy the events need to be shared and my event mesh gives me that ability and then finally when I'm modernizing my platform I may decide that I want to extend those events in real time out to my partners my customers and my line of business so at the point of sale at the point of boarding an airplane at the point of interacting with it with a website and that website may be a complicated set of relationships with different parties being able to share those events is really where becoming event driven sort of takes off so that the piece that obviously covers all this is the event mesh the pub sub platform that underpins all of those components so with that I'd like to just draw the line so Solace is really taking care of the events the distribution now I'll hand over to Carlos who's going to talk about what we can do with those events.

Thank you Phil, so far we have heard that in order for companies to be proactive in making informed real-time decisions they need to be event-driven ready and they achieve that by using solicit broker as the digital backbone to receive, consolidate, manage and distribute events from any part of an organization what i want to talk about now is how the MuleSoft iPaas can leverage the events from the Solace event broker to reliably and securely onboard new business initiatives allowing message reliability with order and guarantee delivery and in a way that these business initiatives can be completely decoupled so that we can minimize testing phases or any other type of disruption but at the same time allowing internal api discoverability reusability and consumption the goal here is simple we want to achieve business speed and agility let me show you how.

We heard from Matt earlier in this webinar that amazon is able to pick and package items and have them ready for shipment within two hours after an order has been placed by a customer that's pretty impressive let's analyze a way in which we can achieve this same type of business agility and automation let's say that for this example we are in the business of selling products and services to end users and because we want to be able to proactively respond to events in real time across any part of our organization we have invested establishing solace event broker as the backbone receiving any type of event this can be events coming from backend systems or applications from manufacturing partners machines trucks refrigerators people you name it now once we have this streaming of events in place let's analyze how is that then we can easily onboard new business ideas as initiatives or projects without compromising security with speed and agility let's analyze the first use case from a retail perspective we may want to onboard a new business initiative around let's say same-day delivery for all of the orders placed within a specific area like in the news at walt cbd or merbon cbd or even based on a range of latitude and longitude coordinates so what we are going to do is using must to subscribe and ask Solace by using a flexible way to tag the events that match specific criteria you can see here how easily I am using an API like approach to filter out these events and how I can make use of wildcards in in the latitude and longitude coordinates to include a wider range of events what Solace is going to do next is analyze these tags and filter out only those events that match the criteria and distribute them by giving us access to them using a dedicated queue from which we can consume and process the events once mules of reach these events in real time it is going to coordinate the business flow interacting with any type of backend system or application as part of the business flow then probably a few months later there is a new business initiative so now this time from a supply chain or inventory management perspective let's say that our company now wants to simplify and modernize the logistics and warehouse operations to be more proactive and trigger automated business processes at the time orders are being placed so this time with MuleSoft we are going to request from Solace all orders regardless of the location and type once again Solace  will distribute these events in real time and once MuleSoft reads them it will coordinate the business flow interacted again with any type of application in the backend finally from a marketing perspective in the next in the next example the company now might want to be interested in launching a new loyalty program this time we are interested in getting all the orders placed with credit card and on local currency across all areas why well maybe because this is part of a mobile application and we want to be able within a minute after a purchase has been placed to thank a customer and suggest an upgrade or a special product or service that then will improve the customer satisfaction or even help us upsell in a more effective and targeted way so in this solution we are using solace and MuleSoft to onboard multiple business initiatives quickly and easily without disrupting or having to retest existing solutions in place and allowing a secure integration to back-end applications whether they are on-premise or in the cloud with speed and agility to make better informed decisions faster over to you matt

Thanks Carlos, thanks Phil for that. So what I'd like to do now is take you through a real world case study in the the resources sector so this is the mining organization and they were implementing a modern digital backbone and they had a number of key drivers for this so from a business perspective as we mentioned earlier, driving down the unit production of cost is absolutely key so being able to increase the efficiency of the overall supply chain and you know reducing the amount of stockpiling minimizing redundant handling minimizing waste etcetera so being able to respond to either equipment coming online or going offline orders changing and so forth all that is happening on a real-time basis so being able to feed that into the supply chain and then just on a real-time basis is key.

The second area was asset optimizations obviously these are very asset heavy organizations and these are very expensive assets so being able to firstly maximize the life of the asset is key but also at the same time reduce the amount of time that they're spent being offline whether it's planned or unplanned so again being able to proactively take events from those assets understand how they're performing and then arrange the service to be exactly on time to prevent a breakdown is a key component of that. Finally, then worker safety and environmental factors are key all of these organizations obviously operate under a license and they need to make sure that they are you know within those terms around you know dust levels pollution water usage etc so again being able to monitor what's happening real time in the environment and respond to that in real time again is key

 

from a technical technology side again they also had a number of key business drivers so key thing here is a separation between the it network and the OT so the operational technology network so the OT is where you're controlling all the machines you know trucks blasting control systems and they are kept very segregated for both security concerns and reliability as well so distributing data between these is actually quite challenging requiring a lot of network configuration firewalls etc you know using technology replicating one database from the OT network to the it network so being able to upgrade that and do that in real time and simplify that was a key driver here the other key requirement was really around how do we bring the integration platform physically closer to the end system so again this builds reliability from you know network outages and it don't affect OT it enables you to bring the controlling system close to the devices that it's been controlling which makes it simpler and easier to build and manage um and then we have sort of the more you know run-of-the-mill things such as having the API enabled key systems and um building out the loosely coupled asynchronous integration again building resilience into the platform so in terms of the solution that we implemented there essentially it's a stack built on both MuleSsoft and Solace with a layered approach to integration from system APIs and system events providing a wrapper around the underlying systems and machinery and components they're then consolidated into you know business APIs or business events giving you reusable integration components that have a meaningful business outcome and obviously that's then fed up through the api gateway in the event gateway to provide that sort of stack that's running either in the IT network or the OT network or the external facing network next slide please drills and then basically using the event mesh to really pull those pieces together in a way that enables events to flow freely across those different networks but in a way that still ensures that they're segregated and that the security is in place to only allow the appropriate data the appropriate service calls to flow between them so hopefully that gives you an overview of what they put in place and how that really that backbone is enabling them to make real-time decision making at scale which is significantly improving business agility and really driving efficiency and reducing costs at the end of the day and driving down that unit of production cost which is so critical in the resource sector.

So with that we'd like to go to a second poll question, in terms of implementing real time today what is the business the biggest obstacle that you're facing within your organization.

I'll give you all a chance to read the uh the different options there. Why are you doing this if you do want to put any questions in the Q&A as we'll look to address them shortly

i think yep we're probably there so if you want to show the results and a number of different things but yeah in terms of how best to get started um i think obviously coming to this webinar is hopefully giving you some clues and obviously we'll talk about potential next steps at the end as well um next slide please drills

So, in terms of questions one of the questions that we had is around you know how long does it take to implement an event-driven platform and is it available on the cloud um Phil I'd ask you to maybe respond to this.

Thanks matt so, it's a “how long is a piece of string question” but from the technology perspective i mean MuleSoft and Solace available in the cloud you can get things spun up very quickly on the technology side is relatively quick the bigger piece and it's around this how to best to get started it's really wrong yeah what are you trying to do so um one of the interesting things about looking at event driven um you know previous previously with integration it was always sort of seen as a you know don't do it on your most critical processes first and make sure it works before you sort of potentially break the system what we see with event driven because it runs in parallel to transactional systems it's really around providing um insight visibility you know interaction um runs in parallel but it can be done some of the most critical critical things first so if people are looking at you know how do i um provide real-time visibility of inventory and that that's always better than what's there so you know something like that it's really then looking at okay what yeah what are the systems are involved how do i get to those events um how do i then you know surface those events um and then you know go from there so we look we do also you know there's methodologies around you know becoming event driven we share our our view partners like yourself are you fantastic for knowing you know taking the what's happening industry and helping customers really take those first steps.

Thanks Phil and I just add to that you know very much taking that agile approach I think the benefit of this overall approach enables you to actually get something relatively quick and easy simple up and running and then continue to iterate around that in following a sort of typical agile methodology that enables you to continuously deliver value to your business as you learn more from the type of events you'll see that actually helps you guide helps guide you in the process itself um okay i think there are no more questions and I don't realize we're running slightly over so apologies for that i get some really key takeaways here you know um responding real time to events is becoming increasingly key to be competitive and the ability to do that in an agile way is key and agile both in terms of just how the business operates but also to deliver new capability that enables the business to be more responsive is equally important um what i would add to that is data loses value rapidly um and therefore getting access to those events in real time and being able to action them in in real time is is really um important and really as we've talked about today you know it's putting in place that modern digital backbone that enables you to get better and faster access to those events and therefore make better and faster decisions and that will then deliver the agility and the reduced cost so in terms of next steps um would encourage you know each of you just to go to the Rubicon Red website you can literally click on the schedule a call and arrange a short sort of 15 to 30 minute conversation with ourselves and we can have a little chat about your requirements and talk about well how you could potentially get started on your you know on your event driven journey,

Thanks for your time today I hope you found this informative and look forward to talking to you in the future about your event driven journey bye for now and bye from Phil and from Carlos as well thank you guys.