 Hello, everyone. Thank you for joining us today. My name is Sateesh Nimbwani. I'm from Customer Engineering from Tipco. And along with me, I have Rakesh and Chandra from T-Mobile. Thanks, guys, for joining us today. Before we get started, how many of you here do app integration build microservices APIs? Wow. Have you heard of Tipco before? Nice. A little bit more hands would probably do good, but we'll settle for this. So hopefully in the next 30 minutes, we'll give you a little bit of overview of what Tipco does and how Tipco has helped T-Mobile to in their digital transformation. Chandra and Rakesh from T-Mobile have been spending over a decade now for building apps using Tipco. They've started off with the traditional and the famous ESB services styles and they're slowly moving away to leverage microservices and APIs. Now, in order to meet the emerging needs and demands and for the vision of digital transformation, T-Mobile leverages, Tipco BusinessWorks, Container Edition, and Pivotal Cloud Foundry, not only to meet their customer volumes, but also to provide them a unified experience across all the channels. So Rakesh, over to you. Why don't you let us know a little bit more on the story? Thank you. Hi. My name is Rakesh. I'm Principal Engineer at T-Mobile. So just a brief introduction of what is T-Mobile. T-Mobile is one of the largest wireless 4G LT providers here. And we are based out of Bellevue, Washington. And we have about 73 million subscribers base in the last quarter reports as of. And we operate under two flagship brands that is T-Mobile and Metro PCS. So what is T-Mobile doing? T-Mobile, like you said, Uncarrier is redefining the way customers and businesses subscribe to the wireless services through this. And how are we doing? We have been redefining the way carriers provide the wireless services. And we have been doing so through our various Uncarrier moves, like our CEO, our famous CEO, John Ledger, calls out. This is the various Uncarrier moves that we provide to the customers that either solve their pain points or give them the features that they really need. So off of this wireless Uncarrier moves, if you see one, if you see, I'll call out a few of them. I think most of you would have used it, is the wireless, free wireless internet in Google in flight. And also we have this carrier freedom, where we are defined as no contracts at all. And the most and recent one is the Netflix on us, where you subscribe to a T-Mobile plan, you get a free Netflix. So what does this mean to us as an IT industry? So yes, we have been providing all this pain, solving all the pain points of the customer. But what does this do to our IT systems that we're running behind the scenes? It provides a lot of stress on the systems that we have to meet or cater to to meet the rise in the volumes and rise in the need for different APIs and everything. So for that, what are we solving? We wanted to be more agile in nature, for that matter. So for example, we need to get the code out of the front development into Prod to get to one of those Uncarrier moves in pretty fast. Like we used to do in traditionally in the ESB model, we used to do in several months. Now we wanted to get it out in weeks. And we also want an infrastructure to be more scalable. And we also want the environment stability and configuration. So how did we do it? So to achieve all this or to solve these problems, what did we do is that we established core pillars of which we call it as digital pillars in our world. Like in any company, it's not just IT being the digital is more important. It has to be all the way from digital marketing, business, and experience, and also up to the operations. So these are the things that we refer to as pillars of our digital transformation that we embarked a journey upon where digital marketing, you reach out to more customers using the more social media channels. And business would refer to more products and services that are more catered towards the exact need of the customer rather than giving the bulk load of all the products. And operational intelligence and digital service management is forefront of that to maintain the stability pain point. So to aligning to the digital pillars, we established a couple of design goals that we wanted to always meet when we are doing in this digital journey. Like you can see, things social, more analytical, and cloud native. And being experienced device APIs, meaning to say that always think from customer downwards, not from the system that you can provide the business from and provide an API for. And also going through all of the build elastic environment where you can meet the needs of the customers as and when from the infrastructure perspective. And always on is more forefront of it. Just to give, this is the more very high level reference architecture that we have. It's pretty much a cookie cutter architecture like any other thing. Just to show you what we have, different channels on the top and different billing systems and other BI and omni channels that at the bottom. And we have the selling and servicing channels. And we have our existing and modified typical container addition running on PURTL Cloud Foundry, which also adopts some DevOps or model of more CI CD pipelines as well. So what are the core capabilities that we try to achieve? Where model around being the capability and domain. So like I said, it should be always top down approach of the business services. So think to the, like what is the experience that you want to deliver to the channel or the customer and design your API around it, which we refer to as experience driven APIs. And there should be more stateless and dynamic to be discovered to the API so that you won't, people figure out the APIs that exists out there on their own from the gateways and also the deployment process and catalog. What is our end goal? Our end goal is to represent T-Mobile as a service. What does, from the slide, I could just take a moment to explain this. Like we want to, like at the core of T-Mobile as a service, we want to represent our core functionalities which are different capabilities provided by the various systems like the customer management, payment, selling, inventory and various billing systems. And we want to do, like I always said, we want to do an experience driven APIs. What does it mean is that if a customer is trying to do a payment through a social channel, right, through a Twitter handle, he doesn't need to know all the billing history and everything that you have. You rather give him an API that only delivers to that particular where he goes quickly and makes a payment. Likewise, you have a customer who's trying to buy a purchase, a particular plan or a phone on the smartphone that he has, right? So in traditional world, if you try to provide a service or an API that provides that capability, you would give him a detailed explanation of the features and everything and often the phone, right? But in this particular channel, we don't have the time or real estate on the phone to browse through all the content of it. So we rather cater him an API that is more specific to the smartphone that he's viewing it on so that it is an experience driven for that particular device he's using. Likewise, on the website where people want to use and see and feel of everything that he has and everything. So we have an experience driven API for the web content. Likewise, what does that do, right? To derive all this experience APIs if I push them down to the core systems like my billing systems or any other servicing systems that we have, it puts a lot of burden on them to maintain all that, right? So like the billing system has to maintain every channel specific API that the customer wants or the device and he has to keep track of it. So for that matter, what we said was, okay, we will do a core API layer which will encompass or abstract the billing systems from all these experiences, keep them more specific to what they really provide. Like for the billing system, it will always provide you me the billing history payments or anything for that particular capability I'm driving upon. And it's the experience API layer that derives the particular content to that particular channel that the customer is subscribing upon. This is how we abstract out this thing and it will allow us to provide our core systems as a service for all the channels that we have and which is our envision of goal of T-Mobile as a service. Now, what does this mean, right? This means that I need API driven architecture for my entire integration, app integration layer. So that's where our partnership with Tipco has helped us along. We have been on Tipco for a while and we have been running on the traditional infrastructure on the physical hardware and infrastructure. So that's where we started on this journey of containerization of APIs. On this containerization journey, we embarked upon, we chose Pivotal Cloud Foundry as our infrastructure provider or elastic runtime pass that is in-house. And we partnered with Tipco to come up with a Tipco containerized software which can be deployed and scaled and driven to that particular demand or needs. That's where our journey with Tipco Business Works Container Edition has started upon and we have been running successfully so far we are about 150 odd apps which is roughly about 500 containers that we are running upon and which service up to, we are doing a volume scales up to almost 125 million calls per day and this is all running on Pivotal Cloud Foundry and everything. So having said that, I would like to bring, so all this is from the development perspective how we have done it and how we have scaled upon the Pivotal Cloud Foundry and using the Tipco Business Works Container Edition. I also would like to invite my colleague who's from the app's perspective. What does he see? Did he see what we have delivered to the operational standpoint because this, like I said, system stability and configuration is in front of all of this to achieve our end goal as well. So Chandra. Thank you Rakesh. So I'm from, I'm Chandra. I'm from operational team. So I don't know how many people are from operational role here. Anybody does production support here? Okay, awesome. Okay, I mean my goal, I mean, I know you guys are, Rakesh has a developer, his goals. I mean, he wants to solve customer pain points. He wants to do microservices but as an operator I have different goals. My simple goal is I need to sleep when everybody, I mean, normal people sleeping time. I want to sleep, right? That is my primary goal. What does that tells you? I mean, if you're operating sleeping during his normal night times, that means your systems are available, right? I mean, his primary goal is your systems are highly available 24 by seven. You have all the data, right? 24 by seven. And you have all the telemetric data available. So that's why that person is able to sleep. But I mean, six to eight months ago, that was not my life. I mean, I used to work from, our maintenance window is from 10 p.m. till 2 a.m. in the morning. So I'm always up and running, always doing deployments during nighttime. Why do I need to do deployments when everybody is sleeping, right? So this is a kind of problem we want to solve as an operator, right? That is one primary goal. And the secondary, I mean, secondary issue is like, I had almost like 2,000 physical servers I had, right? And I have configuration files everywhere, right? And I might have had a proper configuration file on, let's say, 1,999 servers, but I missed on one server. That used to cause a lot of production issues, right? So we never had this configuration as code. We never had that philosophy in T-Mobile before, like six to eight months ago, right? And the other problem we used to have is, like logging, right? I mean, it's on your developer, Mercy, if he's writing logings, you have the telemetry. Otherwise, God knows what's happening in the production, right? So all these kinds, I mean, these are the different problems we have. And you know what happens in, we are in telecom world and there is a big events happen every year, September. I don't know why people go crazy, but the Apple promo is a nightmare for us. I mean, you don't believe I got a call just like 20 minutes ago from a network engineer saying that, hey, we need to get ready for Apple promo for this year. I was like, what the heck, we are, I don't know what. So we are like six months away from that even, but during every iPhone promo, we used to worry about the capacity, right? We used to order this hardware. We used to rack it up, stack it up, right? Deploy a code for performance testing and still my boss who is here, he never had the confidence. Like, dude, is it going to work? I don't know, right? We prepared for 3X load, but what if 5X load comes, right? All these are the different problems we had. I mean, six to eight months. This is the real story, guys. I mean, I'm not making up. I mean, as an operator, I lost the sleep, right? We are always constantly worried. We have zero confidence in our systems, but beautiful things happen, right? I mean, things change. So that's when PCF came. And along the way, I mean, we invested in Tipco from last 10 years, right? We had a lot of people. I mean, developers, operators, our operations team, right? They were all over the place and luckily, Tipco came over to see, right? If not, it would have been a big learning curve for everyone, right? I mean, we would have need to train these people on different technologies, but luckily, Tipco came with Tipco CE and PCF is there. I mean, Rob used to ask me, who is my boss? He used to ask me, Chandra, I want to have a single-click button where I can increase the capacity. Now, Rob, your dream is fulfilled now, right? So that's where our journey started. I mean, PCF solved our problems in the capacity-wise. And also, it brought an immense change in our mind-shift happen in the T-Mobile, right? Previously, I don't know. I don't know Jenkins before. I don't know what is CI CD, right? But all those things, I mean, because these products are so, I mean, the principles of these products are like CI CD, like telemetry, like circuit breakers, right? I mean, circuit breakers. I mean, that's a big deal, right? I mean, the back-end system slows down. I got a call two o'clock in the morning. I was like, dude, what can I do? Back-end system is slow, right? But still, the front-end guy says, dude, I don't care, back-end system fails or not. I want a proper response, right? If I had circuit breakers, I wouldn't have got the call at two o'clock. I would have been sleeping still, right? But these are the problems, right? So to solve all these problems, I mean, Tipco and PCF, right, they came up with these bells and whistles. And that's when we started embracing PCF. So if you have any of these problems in your company, go for it. Go embrace PCF. They solve all these problems. Of course, you need to have a strong infrastructure team, like we have, right, who made everything possible. I mean, everything is self-servable, right? So if you have any of the problems I mentioned, go for PCF, and if you invested in Tipco, go embrace that technology too. So that's the benefit as an operator, right? So now I'm able to sleep, right? Now I'm pressing the single button, I mean, expanding the containers without worrying about the capacity. So as an example, right? So this is how our Tipco CE plus PCF look like when we did iPhone 8. So I'm with T-Mobile from last 10 years. We did, I did a bunch of iPhone launches so far. And this is the first iPhone launch. I was not before, I was not in the office. I was not before my boss. I was attending another conference, and still we were able to successfully launch this product using PCF. How did we do? So I think our conference was still 5.30 p.m., right? We came to hotel. We put a bunch of auto-scaling rules. I think we had a couple of drinks, Rob. I don't want to say that. But see, we had a couple of drinks, but still the traffic was, you see the traffic ramped up. I see the PCF containers was ramping up, right? And we were successfully able to launch the product. So that's the beauty. I mean, we were always used to worry about the capacity, but we no longer worry about those capacity. Right now, as Rakesh was mentioning, this is the old picture, but right now we are doing around 225, 120 million, I mean, 120 million transactions within the TIPCO platform, but we have other middle-level platforms where, I mean, combining we are doing around 220 million transactions and 150 applications around 700 to 800 containers are there. It's a great story. The other thing, again, this is the next one. iPhone X launch, again, the same story. We never worried about capacity any longer. I mean, even the network engineer who called me earlier, I said, don't worry, we are on PCF. So I don't need to order any new hardware. I don't need to worry about anything, right? But that's awesome. That's the story. There's one more. Oh, there's one more, sorry. Oh, okay. This is awesome. So by adapting to PCF, right? I mean, we are able to now gather more telemetric data. So with the Splunk integration, native Splunk integration within the PCF and TIPCO CE, right, now we are able to get more data out of systems and we are catching those issues much earlier before they become high critical issues on our environment, right? And as I said before, right, now we have a configs code, right? So now we no longer keep property files on Unix boxes any longer. You don't, I mean, a couple of years ago, you were hearing the config drift. We don't talk about config drift anymore, right? So because you have all these property files in a config server, now the property files are same everywhere. That is the one problem we solve. Second problem we solve the capacity issues we solve. We solve the telemetry issues, right? And I don't need to, I mean, we did the PCF, I mean, the only learning curve is we had to learn couple of PCF commands, right? CF push, a few commands and we are not able, we are now able to support. I mean, even my offshore team, right? We don't have to train them, even though we moved from an archaic legacy 10 years whole system to this wonderful system, but we are still running with the same people, same skills, that's the learning curve, right? Only the PCF was the learning curve for us. So that's how something, Hitesh? That's pretty interesting insights, Tandra and Rakesh. Thanks guys. Like we're really happy, we are really happy and proud to be a part of this journey with you guys, I mean, we keep talking about this story, we hear about it many times and every time we feel it's like really thrills us. Thanks again for all this. So we've heard both Rakesh and Chandra say the integration needs are evolving, right? Right from the building enterprise applications, the monolith applications to moving to a microservices driven architectures, to API driven microservices, all in all to adopt the digital transformation. Now, what we've seen or observed is pervasive integration is driven by different sorts of audience. The business users actually need business apps to digitize the processes and improve the work stream efficiencies. The enterprise IT users need to provide access to data and systems across various channels, be it on cloud, on-prem and on-edge devices too. And as a developer, I would want to be focused on building my application components in a faster and efficient way, with more openness, connectivity, and adaptability as well, right? Now, the good news is, Tipco Cloud integration supports all of these personas' use cases in a different way. Now, what we've also seen is three main focus areas is for driving a digital transformation, we need APIs. Providing an API is a key enabler for it. So with API modular capability of Tipco Cloud integration, which I'll be probably talking in a few minutes, we let you follow an API-first approach to define your API flows for easier maintenance. The second main focus is to embrace modern application development and integration techniques, which is why as a developers, again, we want to build services faster. We want to lower the operation cost by even being able to deploy it on serverless or fast architectures. I also want the flexibility to be able to deploy anywhere right from on-prem to hybrid to even on-edge devices. The last point is to simplify integration and connectivity. This is where you can leverage the pre-built connectors, not just for any application data, but also for network technologies. So connecting to all these different endpoints using your applications within your enterprise and beyond your enterprise has become much more easier and faster now with Tipco Cloud integration. So, Tipco Cloud integration also provides you a future-ready foundation. When we say future-ready foundation, it is also powered by open-source flow-guided score, which not only ensures you have a zero lock-in with any cloud, but also gives you an ability to leverage the open community for innovation. It also has native support to be deployed on serverless platforms like AWS Lambda. And also, you can directly deploy on every edge devices, so you're ready for all the IoT transformations coming up. And lastly, it also has the capability and the tooling support for integrating with flows like Google TensorFlow. So, in the interest of time, I'll actually skip to a demo flow which we have. So what we're doing is we have a Tipco Cloud integration where we are defining the API contract using the API Modular. I'm implementing the API using Business Studio. Now, once my APIs are implemented, we actually publish or push these services both on Pivotal Cloud Foundry and Kubernetes, which is managed by the Pivotal Container Service. And all of this is done through the open-source Maven plugin. Again, this is where life for Chandra has become easier with the CI CD operations we've talked about, right? So, and all of these, or my APIs have been published to a product called Tipco Mastery, which lets you do all the API management, things like enforcing any policies, throttlings, and all that stuff. Now, that's on the service side. And as a client, what we're doing is we are invoking Flogo Flow as a function in Project RIF. So we'll be showing more about that. Depending upon where the request comes in, if the request is coming in from a US region, the request is routed to Pivotal Cloud Foundry, and if it's coming from a UK region, it is routed to my Kubernetes service. So I'll show this sum of it in action now. So cloud.tipco.com, this is our Tipco Cloud Integration website. So I've already defined my API spec here for a service where we are able to want to fetch the account details depending upon the customer details and the regions we are in. So if you look at the CF Summit app here, that's my API spec, we have a path parameter for customer ID and a query parameter for a region. And so you can export this simply in two different formats and actually use them to implement your APIs. You can preview this to look like how it looks. And you can go back, create actually mock applications. That's what makes this even more powerful. So you can make, create mock applications, create a logo app. For this demo specific purpose, I'm using the Tipco Business Studio, which is from BusinessWorks Container Edition, and that's the component which the friends from T-Mobile have been talking about. So once I connect to my, once I build my API, I connected to the API Explorer view in my Business Studio and actually use all these drag drop capabilities gestures if you see here. I can do this and I can create a service out of it. So once you create a service, this is the actual service which it was created, the stub is created, and then if you fill in up this, if you look at this customer details, it's actually connecting to a backend database system, which is on the cloud. So we are creating a bunch of services, tying them all together. We're doing all these API choreography using Business Studio. Now, once my services is created, we've deployed them to PCF and Kubernetes cluster. So I'm going back to this. So this is what I've deployed and my API is also now published to TIP-Comachry. This is where we are doing all the management, API management part over here. Now, on the client side, we have a project flow-go flow. So this is the request which we're talking about is invoking the PCF service depending if the condition is saying that the requests are coming in from the US region. If the condition says it's from the UK region, then it is routed to the PKS side of it. So that's pretty much on the flow here. It's a simple logic, simple branching based on where the request is coming and routes the request. Now, to do this, to trigger this flow, right, we've created a trigger for Project RIF. Now, this can be any AWS Lambda function or any fast service here to trigger this. But for this demo, we've used the RIF trigger because that's been recently announced. Now, I've created the functions. I have actually deployed everything. I have a setup here. We'll just do a quick RIF list to see the commands. So we've already created a function called CFSummit 2018, that this is the one. Now, we are publishing the request. So I'm doing it. It's actually a bit slow. It's not responding to the command plus commands. So I'll actually show you the demo if it's at the bootpot as well. So what you're doing now is we're publishing a request to the RIF function. So I want to invoke the flow go flow as a function on Project RIF. So we are triggering this request with the region UK. Like you see, we've had a response back here. Now, similarly, what we are also doing is we are invoking the same flow with the region US now. And this invokes my service, which is on PCF here. That's the one. So pretty much all these capabilities, like we've talked about, Project FlowGo, purely open source, Maven plugin, open source here. Again, we have the capabilities of monitoring your applications at the application level. Bunch of things you can look at, the process instances, active instances, the jobs created, and all that data into it. So to sum it up, the key takeaway is, right, you heard and seen Tipco helping T-Mobile leverage all the app launch time from months to days, savings in millions for infrastructure. So Tipco has a true consistent, pervasive integration and API platform in terms of deployment, consumption, and the expansion flexibility as well with CCI. That's it. Thank you. Thank you.