So welcome, and first I have some questions for you. Who's using Carrefourly? More than 10 Carrefourly instances or not? Yeah, okay. So this talk actually is more a discussion than a talk. It's about how to set up and manage a large number of Carrefourly instances. By large number I mean something like more than 20, 50 or 100 instances. And how we can bootstrap these instances and sync all together. So we're going to discuss about Carrefourly quickly, what is Carrefourly, and what the different solution we have to set up this kind of cluster. So about me, so I'm JB, probably easier than my full name, because I'm French so it's pretty hard for you I guess. I'm a software architect or talent, I'm a member of the Apache Software Foundation and I'm working on some Apache projects, so from big data to integration and container. So especially on Carrefourly beam and so on. So Carrefourly, what is Carrefourly? It's a container, it's an application container. It's a container where you can deploy any kind of application. It could be web application, it could be spring application, it could be OHGI application, etc.  Is lightweight? I guess I hope. No, it's less than 20 megabytes just starting Carrefourly. And it depends what you're going to deploy on Carrefourly, of course. But by itself, Carrefourly is pretty light. And it's enterprise-ready. Enterprise-ready by the features it provides. We're going to take a look about the different services provided by Carrefourly, but thanks to this feature, you can implement your enterprise application. I think it's a great runtime for services and microservices platform, but also for IoT platform. I guess most of you use Carrefourly maybe to deploy some camera routes on it, maybe just to deploy web applications, maybe to deploy, let's say, small services applications, stuff like that. So thanks to the fact it's lightweight and enterprise-ready, you can combine these different features and exactly design the container you need. And if we take a look about the services it provides, obviously you need the OHGI framework. Basically, it's completely ideal for you. It's provided by Carrefourly itself. And thanks to that, you can leverage all the features provided by the OHGI framework if you want. You don't have to. On top of that, you have a feature resolver. Again, it's something completely ideal for you, but when you deploy a new application in Carrefourly, automatically, Carrefourly can install all the applications it needs for your application. Let's say you deploy someone in. You are not late. Let's say you want to deploy a rest services in Carrefourly. Maybe you want to use CXF to do that. In that case, without installing CXF by its own, your feature, your application can automatically install CXF as well. So it's very convenient. On top of that, you have some, let's say, ready-to-use programming model you can use in your application. Your application use Spring. Not a big deal. Spring is already supported by Carrefourly. You want to use CSR or DS, which is a OHGI way of deploying services. You can do that as well. You want to use Blueprint, which is an XML description of your services. You can do that as well. And you can combine all these different ways of setting your services inside the same container. And more than that, the blue boxes are services provided by default by Carrefourly. So of course, you can remove the services if you don't want to use it. But in the standard distribution, you already have it. So you have configuration. Most of the time when you design an application, you need some configuration where my database is located, where I don't know, my rest services is located. And most of the time, we are all developers. So maybe my friend developer has the idea to put the configuration in the com folder and another one to put in the config folder. And another one, it's a mess. So very quickly in Carrefourly, we decided to put all the configuration in the same folder. It's the ETC folder. And there are no... You can decide to change the ETC folder to another name. But basically, you know that all applications' configuration are located there. And it's dynamic. It means that if I change the configuration on the fly, Carrefourly will update the configuration in your application. So that's very interesting. Instances is the way that you can create internal instances of Carrefourly inside an existing instance. The purpose of this is to do some kind of snapshot system. So let's say you have a running instance. It runs fine and you want to deploy a new application in this instance. You don't want to pollute your existing instance because you know it's a good one. So instead of creating a new, let's say, folder, docker, and whatever, you can just create a new instance in Carrefourly, deploy your application, validate that it's okay. And if it's not, you just destroy the instance. And if it's okay, you can merge your configuration and your application to the existing instances. That's pretty convenient. Logging or deployment are going to be very fast on this, okay? I don't want to provide all the details. Maybe what I saw before is Carrefourly is enterprise ready. And you can see here JDBC, JNDI, JMS, JTA, JCA. So for example, for JTA, you need to deal with a transaction and you want to use with a persistence, let's say, I don't know, Ibernate, OpenJPA or whatever. You don't have to set up your persistence XML and all of this stuff multiple times. You just deploy the entity manager one time as a service and all the application and all part of your applications that use this persistence service will directly leverage what you deployed before. And more than that, so the blue one are provided by Carrefourly, more than that, you can extend Carrefourly with all the projects like Kamal, like CXF, like Senko, a bunch of other projects provide features that you can directly deploy in Carrefourly. So it means that you can extend, for example, this afternoon we have a talk about ActiveMQ. You can deploy ActiveMQ in Carrefourly if you want. You can mix different, let's say, typology and purposes of your container. But this is good for one Carrefourly instances, but pretty soon we want more than one Carrefourly instance. And there are different reasons why. The first reason is maybe isolation. I mean you want to dedicate your Carrefourly instance to one specific purpose. Maybe you want to deploy this kind of Kamal route only on one part of your instances. You want to be, to use one instances for an ActiveMQ broker. You want to deploy another instances just for your web part of your web application. So the first thing is isolation. The second thing, the second reason is failover. For any reason if my Carrefourly instances is failing, I would like to recover as soon as I can to limit the downtime. And pretty soon we want also scalability. So this instance, this application won't be deployed only on a unique Carrefourly instance. It will be spread to a bunch of Carrefourly instances and I can use any, let's say, part of these instances in my enterprise platform. It depends of your use cases and it depends of your applications. Okay? Maybe most of the time you're going to mix isolation and scalability. Maybe you will have a cluster of 20 instances and maybe 10 for Kamal routes and 10 for web application. Why not? But you want to manage all in the same platform. So failover. Maybe you know that in Carrefourly by itself you have a failover mechanism of a label based on the log system. You don't have to install anything else. You just start Carrefourly and you have just to set up this and you will have a failover system. So if failover system is out of the box and it's based on a log, this log could be on a file system or it could be on a database. Basically how it works, the first instance that starts take the log and become a master. The other instances try to acquire the same log that they are in slave mode. Okay? And if for any reason the log is released by the master the slave will take the log and become the new master. So you don't lose anything. All configuration, all application you deploy on your master are also deployed on the slaves. And pretty soon, as soon as the log is released or lost then a slave will become the new master and you will recover all your application. To do that, it's very easy to set up. You have one file to change in the system in the etc folder. You have one file named system.properties. And if you take a look at the bottom of this file you will see some comments about the log system. And basically it's where you store your log. So if you use a file system it means that all your Carrefourly instances have to share the same file system using NFS, CFS, whatever. Okay? So that's the only requirement. When you store the first instance you will see in the log file info log acquired. It means that the log has been acquired and this instance of Carrefourly is a master. It's the one you're going to use. And if you start another instance you will see in the log trying to lock. So it means he's waiting for the lock. He's a slave. Okay? There are no limit in the number of slaves. You can set up 10, 20 slaves if you want. The instances are all synced together. So if I deploy an application on my master this application will be deployed on the slave as well. If the master fails again the lock is released and the slave will become a master. The only drawback of this approach is an active passive system. So if you set up five slaves these five slaves are completely passive. You cannot log in on it. You cannot do anything on it. So only the master is active. So active passive is not maybe what you want but for failover it's pretty easy to set up. So another thing that you can do is instead of having active passive you want to do active active. So you want to set a bunch of carafe instances all active together and to sync the state of carafe instances on the fly. So if I deploy an application on one instance I would like to see this application deployed on all other instances. This time it's not provided by default in carafe. You have to install a new feature on top of carafe. The name is carafe cellar. So cellar is a sub-project of carafe. It provides to you the synchronization, discovery and active active setup of your cluster. It's powered by azelcast. So it means that any action you're going to do on one node will be sent to an azelcast data grid shared by all other nodes. So the state of the cluster is stored in azelcast. It's very easy to install. Feature install cellar. I'm not kidding, just this. You start your carafe instances, you do feature install cellar, it's done. Cellar is ready to be used. There are no single pawns of failure because the azelcast instances are embedded in each carafe instance. So it means that if I lose one instance the cluster state is still in sync because I have my azelcast instances running and synced together. So I need at least one node just to maintain my cluster. It's pretty convenient. You have different ways of discovering a node in your cluster. So when you start a new carafe instance to discover this node you have different mechanisms. The first one is multicast. So when a carafe instance starts it sends a multicast message on the network and the existing carafe instances running cellar so you can get this notification and update the cluster. But if multicast is not available of your network because your network administrator is a bit paranoiac for instance you can use static IP addresses. So you just list the netmask and the IP addresses where your carafe instance is running. But you can also mix instances running locally on your on-premise cluster with instances running on Amazon for instance. In azelcast you can send and broadcast messages with RWS for example and so you can discover nodes running on Amazon. Another thing that is not probably by azelcast but probably by cellar you can use Kubernetes. So it means that if you have a pod you can discover your nodes using Kubernetes. ETCD as well. There are different discovery mechanisms and you can extend and implement your own mechanism if you want. It's just one service to implement. Pretty easy. The core purpose of cellar is to synchronize the carafe instances all together but we also provide additional features like DOIGI, distributed OIGI. It means that one service is located on one carafe instance and is used remotely by all the instances. We also provide HTTP balancer. So it means that if you deploy a web application or a servlet in one carafe instance this servlet can be available on the whole cluster even if you don't deploy everywhere thanks to the load balancer provided by cellar. So how it works is pretty easy. We have a data read this one is probably by azelcast and in each cellar instances we have basically four core features these three ones are enabled by default and another one is disabled. Let's take a look. So here are my carafe instance my carafe instance I installed cellar feature and when I installed cellar I have three pieces installed the producer, the consumer and the synchronizer. What's the purpose of it? So the data read again is where I store my cluster no brainer, it's pretty easy. The producer is the pieces of cellar that send an event to the other nodes. Let's say you install an application on one node you have to notify the others but you install this application locally and they have to do the same. The producer send a cluster event from one node to another. And of course if I have a producer on one hand I have a consumer on the other hand so on the other node I have a consumer that receive a cluster event and react accordingly installing your application installing your configuration or whatever and I have one consumer but I have multiple endless and the reason is I have different cluster events depending of if it's a configuration if it's an application if it's a feature for the one who knows what is a feature in Karath it's different cluster events so I have different handle and the synchronizer I use when a new node join a cluster it has to synchronize the state of the cluster with its local state and here you can define different sync policies so for instance you can decide to do a merge first I retrieve from the cluster and so I update my configuration locally and then I push from my local node to the cluster or you can decide that the cluster is only the master so I retrieve from the state from the cluster and I override my configuration and my application locally on my node but I don't press anything on the cluster or on the other hand you can decide the node is the master and in that case you will override the cluster state with a local node state so this is possible just by configuration you can decide the sync policy you want the listener the last thing they are disabled by default but you can enable if you want is when you have a local event let's say you change a configuration in the ATC folder you can decide to broadcast this change to the cluster or not by default it's not but you can enable it it means by default when you want to install an application you have to use a dedicated cluster command cluster bundle install cluster feature install for instance if you enable the listener a simple feature install or bundle install is enough then it will be broadcasted to the cluster this is the different resources CELA can sync for you so first the features who knows the carafe features so for the others a feature in carafe is the descriptor of an application so basically a feature is a list of application components plus the configuration plus optionally some other feature that can be used in your own feature bundles is the OIGI components and configuration optionally you have OBR and even admin support it's not enabled by default it's very some specific use cases so you have different options like DOHDR, HTTP, balancer and stuff like that and another feature that you can use in CELA is the cluster group so let's say I have a big cluster of 50 instances and again I would like to mix my cluster with some isolation so I would like to deploy my application only on 5 nodes in my cluster and I would like to dedicate 10 of the nodes for let's say CXF REST services for instance in that case you can use cluster group so in cluster group you decide this is my cluster group Apachecon1 and containing these 5 nodes and I have another cluster group Apachecon2 containing 20 nodes and when you deploy an application you target to specific cluster group by default you have a unique cluster group named default containing all instances that you can dedicate some deployment you can also a node can be part of multiple cluster groups if you want so it could be for instance you can deploy 2 applications in the same node if the node is part of 2 cluster groups the purpose is just to target and isolate the deployment so CELA is good but you need a manual action first it means that first I have to install my CELA instance and then log on my CELA instance and do feature install CELA it's not really dynamic and more than that all the preparation all the setup has to be done by hand so what we want is to provide a ready to use CELA instance embedding already embedding CELA package as a docker image and be able to automatically bootstrap this so it's one approach I don't say it's the only one but it's the approach I propose here so here we're going to mix 2 things we're going to mix docker and marathon to bootstrap the instances plus CELA to synchronize all instances all together so we mix 2 technologies the first thing we're going to do it's to create a carafe distribution carafe distribution is basically carafe plus some application and CELA so I embed carafe and CELA all together by default and I create my custom distribution so here you can add your own application if you want and to do that in carafe we have a carafe method plugin that allows you to create very easily a custom distribution so to do that here I add some CELA the only thing I define in the dependencies is the location of my feature and the location of my applications and of course CELA by itself and then I just define this is the boot feature that I would like so the boot feature is as soon as I start carafe these applications will be started automatically so as a boot feature here because I would like to start CELA as soon as I start my carafe instances and so I just run mvn clean install and at the end I have a zip file and a tarboard containing my carafe distribution plus CELA plus eventually all my applications that I want first step so I have my custom carafe distribution embedding CELA in my application we are good but it's not enough now we would like to package my custom distribution as a Docker image to do that we create the Docker file so this Docker file is based on Java and it gets my my distribution of carafe plus CELA and installs in the Docker image okay then to do that the only thing that I have to do is the Docker build so the Docker build will take my Docker file and it will create a Docker image containing the Java base image plus my custom carafe distribution containing CELA and my application and here are my CELA instances we are good but now we have to bootstrap this Docker image okay the first thing to do that is to do Docker run again and again in a bunch of nodes it's not what we want it's not dynamic so it's where we are going to introduce mesos some mesos support Docker and so it can bootstrap the Docker images for you and it's mesos plus marathon so we are going to use this to do some kind of dynamic bootstrapping to setup your mesos and marathon you have to approach the first easy way so with DCOS you have all embedded so it's provided by mesosphere you have mesos plus marathon all together and it's pretty easy to bootstrap and to start with another approach you can do your own made DCOS if you want so basically you combine some mesos you start your zoom keeper you start your mesos agent you install marathon and you install marathon it's pretty easy it could be long to do bootstrap and configure and make depending on your machine but it works so it's up to you at the end it's exactly the same and after that we create a marathon JSON configuration for all applications so basically what I do here is an ID my name of my distribution is a character cellar in my case memory and the number of instances that's my initial setup so it means that here I will start with three instances of my custom character distribution and different locations so I say it's a docker this is the location of my docker image and this is the POR number and the way I expose my POR number nothing special there remember is the number of instances and after that I start my DCOS marathon dashboard so this is the initial status so I have let's say 6 CPU available on my cluster I have 7 GB of memory and for now I don't have any services so I'm in an empty let's say space now we deploy our character distribution so imagine again in my case it's character plus cellar but imagine you also add your application I do a run service and I provide my JSON configuration the one I show you before and so here you are the recap about all that we setup so especially the number of instances the number of CPU you can see the docker image CPU and all this stuff when I'm ready I just click on run and here you can see deploying free instances so it means that I'm going to take my docker image and bootstrap this images on different machines so imagine your marathon setup contains I don't know maybe 10 machines or whatever then it will spread the deployment machine again remember we use cellar so it means that these instances will be seen together from a car of perspective thanks to cellar and now we have a new task running containing multiple instances so you can see a different usage and stuff like that but now we want to scare so we started with free instances and we want to bootstrap let's say 10 instances or 20 instances so your use case is black friday you know you're going to have a lot of load during black friday and you want to bootstrap new instances very quickly so it's what we're going to do using marathon so in marathon you can go on the dashboard in the service and you can click on scale and define the new number of instances you want so you can go from 3 to 10 or from 10 to 5 whatever you want the new nodes, the key thing is the new nodes are pretty important they are synced all together again with cellar it means that if I change a configuration in one node all nodes, whatever it's new nodes or not it doesn't really matter these nodes will be synced together all together in terms of configuration and application so let's do that so I go on my service and I click on scale and then I update to 5 new instances so I go from 3 to 5 so it means that now you can see it's growing up I have more instances running and again these instances are synced all together so it means that we implemented dynamic scalability by dynamic it means that of course you still have a manual action to do is the number of instances but you don't care about if the application or deploy we don't care the only thing that you manage you is the number of instances increase or decrease it means that you may have one team dedicated for let's say your platform management and another team dedicated on let's say carafe management the configuration or whatever it means that one one thing that it's really interesting in cellar as well is you can log on one instance or another one it doesn't really matter all action we're going to do on one will be spread to the others there are no notion of cluster manager or whatever any instances is a manager of a cluster but now we can we can go forward I mean we can go further in terms of what we can provide in cellar we plan to provide a marathon scheduler by its own it means that if you set up the number of instances by hand you can define a policy in cellar that automatically deals with marathon to say I need three more instances depending on the loads for instance so it's something that we started in cellar it's not yet released it will be included in the next cellar release but it's a marathon scheduler and the purpose is again to automatically change the number of instances another thing that we plan is to provide an official docker image we have some carap docker images but they are not official and they don't embed cellar so we plan to provide two docker images one is basically different version of carap and one is carap plus cellar and of course as we can leverage DCUS in DCUS you have the universe so the universe in DCUS is the packages that you can easily bootstrap and install we plan to provide instances of this universe for DCUS for the one who knows humbun to juju you have charms in juju it's exactly the same and it's already done for juju it's not yet done for DCUS do you have any questions yes would you recommend this for like an edgey storm which in turn is distributed across my machine that's not exactly the same purpose I mean let's talk about storm or beam or whatever because I'm also working on beam they provide their own let's say providing system if you plan to deploy storm j storm or ignite or whatever in carap then it makes sense but it's not the first purpose the first purpose of this it's more to bootstrap non-applicated distributed application to a kind of platform second question obviously for non-java based network it's really java focused there's another question over there ah, that's a good question first point why docker honestly I remember I think it was two years ago we had a lot of discussion between why do you need docker when you use carap I mean carap by its own is a container so it means that deploying a container is a container maybe it doesn't make sense but why docker is just to leverage the existing let's say ecosystem like a swamp, like a mesos and marathon and all this stuff that's the only reason why there are no strong by itself carap could be a container and it was what we did at the beginning and it works, you can do the same for this the reason why is simply because docker image is very convenient just to package all together that's mostly the reason and now the second point is why mesos more than kubernetes for two reasons first reason is I take my apache cap and I prefer apache project that's not technical decision but now honestly one of the reason kubernetes in cellar in cellar we have the kubernetes pod ready for discovery and bootstrap so the reason why mesos is simply because we have the marathon scheduler available an alternative would have been to use apache overall for instance just to bootstrap the carap instances but what we did that can exactly work with kubernetes no bulb is using kubernetes in this project again this is not something it's just an example there are nothing nothing is hardcoded in cellar or carap to use only mesos of course you can switch to dnsd to etcd to kubernetes whatever using the beautiful infrastructure that you get how do you go through to decide this is a dynamic feature and this is something that I want to build for can you walk me through your process for that that's an interesting point in this approach the minimum piece in the custom distribution is just to bring cellar as part of the core let's say platform you don't have to package your application inside your custom distribution maybe and it's basically what I'm doing I just bootstrap cellar and then I use one instance in my cluster just to install my applications and then this application will be deployed on the cluster and the big advantage of doing that is just to update because when I do cluster feature update then it will update my features of my application in all nodes in my cluster that's probably the best approach to do not embedding your application in your carap distribution even if it's pretty convenient but it means that a team has to be dedicated for the installation of your applications the big advantage of using this approach and custom distribution you just provide the docker file or the tarball and the people who actually deploy the images on the cluster they don't care about what's the configuration, what's your application what's the version, they just deploy and that's all so it's some decision to take while I'm doing myself and package and while I'm leading the other team to do an update for configuration for example it could be some time problematic so yes exactly I mean the key point is your DevOps team I mean if your DevOps team is a bit focused on carap and your application and knows how to change the configuration and what's a feature and stuff like that then you as a development team you only focus on the feature you provide and that's all if your DevOps team is more my purpose and my goal just to deploy what I receive from the dev team in that case you you have to provide a package ready to run and the DevOps team doesn't care about what's the content of the image yes okay so that's a good question so basically the question is what why carap maybe where it comes from and what's the usage of carap for a developer I don't like to say that but I gotta say that carap is an OIGI container so it doesn't mean OIGI is a prime model in Java that allows you to deploy services so some components deploy services and all the components can use these services so it's a kind of SOA platform but very low level I don't like to say that because for a long time carap was only considered as an OIGI container and actually is more than that because you can deploy anything a large scope of application in carap what carap is providing to you is an environment providing services that you can directly leverage in your application you want to do logging in your application then normally let's take a concrete example you want to do some logging in your application means you have to use and define the dependency to the logging platform SLF4j, commands logging, log4j or whatever then you have to define the configuration of your logging system what's my appender, what's my category what's my different let's say basically connecting a lot of into the Java world it's a good description actually it's like an application server like we had in the past exactly so it's a mix between a container as you said it's a good style let's say application server like we had in the past weblogic, westphare and all this stuff but it's more let's say services oriented but yeah it's a container providing to you something that you can use and connect dots as you said and it's a glue between the different part of your Java component as I said it's a good platform for service and microservices application services all together so yeah it's a container so yeah there are different locking mechanism provided by configuration so you have a file based on the share file system you have JDBC you have zookeeper and you have azelcast as well so it means that the log can be on because the example for the example I use an NFS and if you take a look in the configuration file you will see different implementation yes instances yeah so this part is basically when you start carafe you have what we named the root instance okay it's the default one it's where you can interact you can type some commands because you have a complete shell commands where you can type your configuration your extra extra then what you can do is to do instance clone or instance create so instance create create a completely fresh new instances so it's a new JVM so it starts a new JVM with a dedicated file system so it dedicates directory where the files will be located if you decide to clone then you're going to take an existing carafe instances for instance the root and completely duplicate the same instance changing the port number and stuff like that and then you create a new JVM again where you can run your application so it's exactly instead of using this another alternative on your machine is just to copy the existing directory into a new directory changing the port number and it's starting yeah so basically yeah it's a new carafe instance inside your same operating system container yeah okay you're okay with the question you're done okay there's another one and Alex I will get back to you cellar is more swamp or marathon it's when you have an existing docker image cellar is more inside the docker image for synchronization so let me take a concrete example in your docker image you package cellar and that's all you bootstrap using marathon you create 3 instances or 10 instances whatever of your docker image on your cluster and then your DevOps team goes in one instance and you configure it and change foo bar to foo order in a configuration then this configuration change is not related to swamp or docker or whatever it's like internally to your application internally to docker to carafe in that case this is the purpose of cellar to sync this change to all of the instances so that's the different meaning oh yeah it happens a lot I mean in micro services platform it happens a lot if I would like to change the number of thread or if I would like to change the location of my elastic search of Cassandra database for instance because I don't know I may be set up new instances whatever in your cluster group and do the change yeah it's exactly the same question from Bob it depends what let's say what your DevOps team can do or not if you consider your docker image as a standalone and you cannot change that then it's not really useful but if you consider your DevOps team is able to change the location the number of thread or stuff like that in one cluster group then cellar is there cellar actually is very low level in carafe so if you deploy your command routes is basically packaged as a bundle or blueprint bundle or a feature whatever so in that case as soon as you install your command route so bundle or feature in one carafe instance then cellar will be able to spread the deployment no problem at all you're welcome Alex these four they are static in the docker image but they can be exposed dynamically with marathon it's not because I have in that case 8181 here he could be dynamic and managed by marathon actually that's why marathon is pretty interesting and Kubernetes and swamp does exactly the same so you're right static in the docker image but dynamic from a cluster perspective I didn't see that 0 0 means it's dynamic another question thank you so much


Hello everyone! Hello! Welcome back to another episode of Jurassic World The Game! I forgot to click the echo button for a bit there. It has been a hot minute and we are here because I love you guys. That's why we're here. Okay, we've settled though. We can say bye now. Bye! Play me off Johnny! There we go. I'm f- No! We're here to do- Serious business. I have been neglecting Jurassic World The Game. I'll apologize. Go by NSI. But if we go in here, we'll just collect our things. I mean you'll notice we still have like 900,000 DNA.  Oh, maybe you can. So, let's have a look. The event or the VIP that was on at the moment was the Dreadnaughtus. And this guy- I mean it was okay. I collected all the things because I didn't know whether I was actually going to make a video or not. And I got the pass for it.  The additional missions you can find in here, VIP Grand Premium. Now, open 25 packs. Okay, there's no way I'm going to be able to do that because I've only got one day. And I can't open 15 packs. I mean, maybe if I got lucky and I just did the PvP battles all the time, maybe I could? Or span the mods? Sometimes we need to do a little bit of that. But that's the most, the one that gives the most. Also, level one- oh, sorry. Have one level 30 Dreadnaughtus. I have a level 20. I think it's over. And it's over here. Oh my God. Where are you, son? There you are. So, I would need two more. Now, it's not impossible. But it's pretty hard. I've got one guaranteed. So if we do go- oh, they've also extended this. They made this so much longer because it used to be 10,000 points. And then that would be the end of it. That's a lot. But now, they've added even more. So you've got all of this and it keeps on going and going. So if you do the regular, you- I don't know if you unlock it with this. Right. Okay. So they've made the unlock even harder. You need to have 16,000 points without doing the Grand Premium Pass to get it, which is ridiculous.  And at the very end, you get two of these packs. We don't guarantee you. And then the- oh, 75 bucks. You know? Oh, just 75 bucks.  If you're going to ask me, pretty rubbish. But, but, but, but, we are here because I need to knock out some of these. We need to hatch seven creatures. But we don't want to look at this. The 50 battles thing isn't too hard. We can just- what was it? Close the game re-open. Close the game re-open. Watch the video ads. Yeah, that's not happening. Use 55 Tri-Nons. Well, we could do that at the same time as completing the 50 battles. We also need to hatch. Hey, it's just clocked over. Oh, sweet. Okay, these were all the random ones I got given. Because now they give away tickets in the VIP thing. So I don't know if any of them are very good. I got 15 on this one. So you could choose when to use the tickets, which is quite nice. I didn't even look at what these were. Apparently this was all food, that one. So that was pretty terrible. And this next one. Uh, well, 6- oh, well, 1600 of that. And 500 of that. Not very great. Um, but we'll do some of that. Um, we'll do, yeah, why not? We'll do, wait, I can do 20 of those? Oh, actually, you know, a bit of a waste of DNA. But at the same time, we get to spin the gold prize, which is worth it. And there is Dino Karras. Right, we've done that. Let's have a look. Oh, there we go. Purchase 30 prize tickets. Okay, that puts us over to the next one. Really, we want 10,000 points. And we're on 8,550 at the moment. So we've got, we've got some, some way to go. I think we need a tea break, guys. There we go, tea break. Hatch, hatch 15 Pteranodons. We can definitely do. Do the battles with Pteranodons as well. So, oh God, yeah.  What? That is ridiculous. 4,000 for a comment. I was like, you know what? I'll just spend some of that. But no, no, that's the case. I got Tropicopi, which is five minutes. Then, right, let's have a look at these because we've got some packs we could win from here. I'm not too interested in this. Gold rose any creature and you get... Eh, you get something that's all right, I suppose. Man, not too interested in that. But there we go. Common, which will give you dinner and will give you books. And that's pretty decent because all we need is what, like, our best carnivores. And we got this in the back, I would say. Oh God, I've just seen this attack. Just 8,000. Oh! Scorpius! My guy! You almost died there. It could have easily killed him. Wow. Also, I think someone commented in my last video was like, Beaver, please, please get to run all off the source. Please! I hear you. I hear you. I just don't want to waste my DNA. Because how expensive is it? It's far too expensive.  Eww! I wanted to keep an eye on what he went for. I will this time. Okay, he went for one. Okay, so he's got two blocks. Right, so one, two, one, two, and then three. So no matter what happens, which he did go for the blocks, so 8,000 attack turns into 2,000 attack. Right, he can kill me in two, which is fair enough. Oh! Even better! Going for the full out attack. Get in. Right now, how much damage does Carnotaurus do? Not too much, okay. Right. I'm going to go for that. I think I could probably have went for one block and two reserves. I could have swapped them. Because yeah. Yeah, I should have done that. I thought you'd get a bonus. I don't know why I thought you'd get a bonus. Now I'm in a tricky situation here. It's 4, 8.  Might be a push.  So I'm going to go for this. Right, he's got six. Please go for six, because two, four, six.  I think it's probably four. Oh! Oh, that's annoying. Okay, we'll go for the risky. We'll go for two reserves this time. Ha-ha! Yes! And then we'll do the same again. Two reserves. And then more blocks. No, three reserves, more blocks. That's what we'll do. So we'll split this down the middle. So three reserves. We're slowly building up for a big attack. That's what we're going to do. In comes the six. Okay. Well, let's see what he does. I hope the six does come in. I think that's done it. Yeah, that's done it. We've definitely killed him. One, two, three, four. Four kills him. He's only got two block. We've got three extra. Goes for the two block. And there it is, a pack. Oh, we should have used... I should have used Pteranodon. Damn. Damn. Because I can skip that. Ah, nuts. Because how much even is it? 50 bucks! Fantastic! Cool! Get it! Alright, 130. Well, I'll waste. Right, yeah. Do we have any other battles that we can just grind for, you know, Pteranodons? I think this might work. If I just go la-la-la-la. Go like that. And then quit. Let's give up. How's that counted? We should have checked that, actually. Let's have a look. I... No. No hatch? We need to use, right? Okay, so that was four out of 55. We'll have a check. Ah, that's rubbish. Okay, over there. Right, let's have a look. So, you're 666, you're even lesser. Right. So, one, two, and three. Yep, we'll use the six. Give up. I mean, this is counting as doing battles. It's costing me like 666,000. Let's have a look. VIP season. Yeah, that is counted towards doing battles and using Pteranodons. So, that's already 1,260 extra points, which takes us to 10,000. So, that's all we need. And then we've got the next red notice. Because we have an open up cards. Win battles without using reserves three times. Where do you need to? Hold on, hold on. It's got to be about like a do, which is just so easy, right? Like, if I do this, I just put in these guys, and then I put in an Indoraptor, right? Like, I should just... It's no reserves. Oh, God, you put a copy. Oh, well, actually, this is doable. I think. I think it's doable. So, I probably... You know, I'll make sure that he uses two attacks. Let's make sure it doesn't, because it will. It doesn't need to, but it will. Actually, maybe I should have blocked. Maybe it won't. Will it? Will it is the question? Balls. Damn it, I should have blocked. My cockiness got the better of me. Right, right, we'll just go for blocks. We'll just go for blocks. That way. It just, it assures that they have to go for the most amount of attack. I did damage to him, but I don't even notice it. I think he... I think I did four damage to him. Oh, you blocked, did you? All right, all right. I just, I need to get through this guy, and the rest is a cave walk. So, he should go for four, knowing that I've only got three. Okay, so he's got one block. I think I can kill him in two. Yes, almost one. Okay, so he's got one block, so I have to go for three. So, one, two, three. And because I can't reserve, I may as well just block it.  Look at them go. They're so cute. The only way to kill Compies, I think is to go for a seven or an eight attack animation. To go through all of them. So, unfortunately... I'm just going to go for three and one block. Yeah, there's one dead. There you go. If they swap out and swap back in, there's a chance that one of them could come back. Which could be broken if you had three Compies all on a team. And you could swap into attack, swap into attack, swap into attack. Oh, it went for four. My God. Oh! Okay. Right. I did not expect it. I took over that much. Oh, dear. Right, go on four. I can do... We got this. We got this. Come on. You want to... Hold on. This has done a bugger on me. I'm sorry to be real with you guys. I'm getting Uber Eats. And I don't know why it's put me in. Over there. When I'm nowhere near it. I don't know why... Okay. Just... Real about what for a second I was getting through and he's like, It's got a while to go. It doesn't give me a path to where I am. And I'm pretty sure I did not set the waypoint over there. Well, we'll find out. We'll wait if I get a call from them. Bam. Right, there we go. So that is one battle done. Not even a single one. I hope, right? I didn't... I didn't mess it up. Pretty sure I didn't mess it up. There you go. Boom. Do I want to spin for an hour? No. Let's have a look. Let's check this out. Did that count? Was it this one? Or was it VIP? Yay! Oh, so it's a VIP extra mission. Okay.  So what I'm going to do is I'm just going to put Indoraptor in first this time. That way, I should be able to easy kill. And if it really needs be... Witch... That's a harder team. Much harder team. Um... I mean, whether I go for one, like two single hits or one double hit doesn't make a difference. So I may as well just go for the one. Let's see what it does. Go on. What are you going to do? You swapped? Why? Why would you do... Okay. Um... Well... I'll just go for two hits, I suppose. Oh, I actually killed him. I thought he would at least plug for one. Okay. In comes the Quaking of my boots. Argentinosaurus. Yeah. Yeah. Oh, there we go. Okay, he's routed it properly now. Good. Update. Over-update, guys. Solid throwing. Right, okay. Yeah, I'll just go up for an all-out attack. Yeah, one, like I said, doesn't matter. Two singles, which it has been two singles. I think the Pteranodons also have a new defeated animation. Interesting that people have noticed. I didn't realize that, you know, you guys would still take attention. Okay, yeah, oh no. Not three. Anything but three. And we'll just go for... That's it. That's 500 extra points. Nice. Now, you only get that with the grand premium, which is interesting. They're trying to make it more... They're trying to coerce you more into getting that grand premium pass. A little prize. What do we get? It's garbage. It's coin. It's rubbish.  Right. Okay, let me collect my 500. What is that? Gorgeous. Gorgeous. All right. Now, all we need to do is just go into this one. Go into, well, Pteranodons, one, two, three, four, enter and exit like a million times. So, yeah, I'll be right back while I go get me Uber Eats as well and we'll be right back. Hello everyone and welcome back. That was a bit longer than I expected. How was the Uber Eats you're asking? It's quite nice actually. I really enjoyed it. Came in time, which is good. But I have been sat here for an hour trying to get this thing to bloody work. I was like, oh no. Why? Why? Why now? Anyway, we're here. While I was waiting for this to work and also my iPod was on the bar as we're charged and all things going wrong. What's the reason we don't make the videos anymore? I'm telling you. Anyway, but madness aside, while I was trying to get it to work, I was playing on my phone. So I did loads of missions. Haven't collected them because collecting them is the best part. We save that for the video so you can go where you want to go. Right. So I did.  I think it was a lot of triceratops because I had that for something else as well. I also collected like one little daily thing. I got two weeklies, had seven creatures and complete 25 battles because that was pretty easy. That was just going in. Stopping, going in, stopping, going, stopping. Very, very easy. Complete 50. Awesome. Very easy. Hatched 15 herbivores. All triceratops. Triceratops. Again, top 10 list have made it nowadays. It would definitely still be in there. A few seven herbivores. Five seratops. Use 55 of those. Boom. We are way more than I was expecting. I think 16,000 is what you needed to get another unlock for the dreadnoughters. At least I think it was. We'll have a double check of that. But the other ones are a little bit harder. Participate in any PVP, watch eight, adverts. And again, we're going to need another like 3,000-ish points. So it would have to be, you know, open up 25 packs. Or I need another 13? 13 packs? 40. I need 14 more packs. And we get close. But let's have a look. Beautiful. Yes. Claim all, dear. Yes, let's go. Also, because I love you, we'll get a new hybrid. We'll do that. Just for you. The person watching this video, which will also be me editing the video as well. Anyway, dreadnoughters, there's a chance of... Did we just get another one? Ah, Son of Argosaur. Dammit. Oh, little bugger. Little cheeky gate. Thought I got one there. Oh, 3,000. Oh, that's 5,000. That's only 4,000. 3 of the tickets. It doesn't show you what they go towards. Micro DNA, so that's 1,000 DNA. Might reimburse me for all of the triceratops I wasted. I did sell them, don't worry. So they were completely wasted. Right, what's next? And actually, right, this is going to be the dreadnoughters pack, right? It's got to be. It's got to be. It's got to be. Right, I think that's the one. Yeah, there we go. Okay, so we did get a guarantee. We're 2,600. Brilliant. Chance. We are actually opening a lot of packs, to be honest. I could probably just open up loads of solid golds and probably get the next one of them. 660,000 of that food. I know the dr- Right, are we going to get another one? Didn't want it anyway. 100,000. Right, there's 3. Oh, we got loads of rewards. Oh, 250. 300. 3. Right, there we go. We- you know what? I missed out on the first few weeks of this, but we have got so many. I got way further than I thought it was going to get. Yeah, we needed about 16,000 to get- unlock that one.  I mean, there's so many. 25,000. We're all about- we're just over halfway of getting all the rewards. Are we going to get them? No. But we do have a lot of DNA. We also got some missions to collect. It says to run- Oh, there you go. Open three packs. There's another one. This one, I'm not really that fussed on. I mean, we could get some because the- again, the rewards just generally for, you know, doing the missions is pretty good because you get the pack, which gives you guaranteed DNA. Also, this as well, I think gives you good stuff too. So generally- the general general generally doing the rewards. Oh, yeah. Also, hold on. Does this make a cool noise? It sounds like it makes a cool noise to me. How is that? How is that tea doing that noise? Okay, look, look guys. It's not tea.  It's like 35 degree weather.  Also, I'm in a room with no AC. Forgive me. I need all the cooling I can get. All right, another one. Boom. Do three trades and then do them later. Don't care. 21 hours to do those. Also, I've done another one of those. Okay, okay. Also, yeah. Another thing that changed with this update- there's a music- there's a weird loop. Okay. Is the trade harbor. They made it so you can no longer just refresh for 50 bucks. Oh, wait. You can. I thought it was just only adverse. Oh, I'll do the 50 bucks. Hell yeah. Oh, well, there you go. 50 bucks up. I'll take that. Anything good? Ooh. Okay. Yeah. The mega is still 50. That's good. I'm wondering if they've changed the rewards. Stegosaur for 84. Take it. That. Yeah. I'll take that. Oh, now it just says 50. Okay. So you can do two free trades by watching adverts. And technically, this is actually a better trade harbor because you want to do the videos, the adverts, because that unlocks more missions. And you don't really need to pay too much attention. A million food for 100? Yeah. Yeah, I'll do that. Nullify. Cool. I mean, Nullify is actually one of the best ones. Yeah. So no. We're up DNA. And books. Sorry, I think. Maybe not DNA. Maybe not DNA. We're up books. And then do three trades. All right. Okay, guys. Okay. I was also working towards doing another mission, which was hatch. God knows. What is it? Turandons. But at this point, I think I'm okay. What's my next reward anyway? Five golden tickets. Now, if I go into my lottery. Yeah. There you go. Plus nine plus five. So it's increased from your other. Ah, interesting. I wonder if you can get the other one then. You can get gold tickets. Can you get the other tickets? Just gold tickets. Is that the right one? Is that the... I think these are all gold. Yeah. They're just gold tickets. So it's none of like the platinum tickets. No. Okay. Whatever they are. They're like super shiny gold tickets. Yeah. It's that one. It's not this one. Paradise Lagoon. Okay. Right. We're going to have a look. To see what we can get. We need a good thumbnail. This is... This is the pricey bit because this is going to cost a lot. Now I could sell Indoraptors. I get them quite frequently. By frequently I mean not at all. But if I sell one Raptor it's the equivalent of 40,000. Which in the market in this economy is not much. I'm not going to lie to you. But let's have a look. No, I don't need that. Also this has just came up. We can get a double twin beta but I don't really care about. I've got to be honest. Right. So we don't have to love a boy. Don't care about that. Really what I was looking for was the Chroma Spino. Now technically we should go for the Crawler Borogina or whatever it's called.  That's over 10,000 DNA for a single one. How many do we have on that? Only 20. Only 20. We need another 6. So that is over 60,000 DNA saved if we were to do that. We could get that maxed up but even then at a max 11,000 health it would compare that to Chroma Spino. It's so cool. Then get an extra 1,500 attack and you know you're missing out on 600 health but you get 1,500 attack? Come on now.  I gotta go get that car now. But I want to look for Tyrannolophosaurus because people were asking for that one. They were whinging for it. But it actually might be cheaper. 82,000 in comparison to oh I don't even have it. How do I not have a stitch? Wait I have... Oh not owned. I don't have the Lophosaurus. Oh that's right I missed out on it again. It came back and I was like right let's do this. Proceeded to not do this. So we don't have a go. It will be Chroma Span. Wait it was 80,000 wasn't it? It was 80,000 hybrids. How many do I have? Oh 30. That's so bad. We need three more. Four more. Never mind. I can math. Don't judge me. Right four more. So that is... Oh here we go. 160,000 320,000 Alright fine. Instant hatch. You know what? At least I'm saving bucks on this I suppose. We've got a level 30. Now the reason why... I'm doing this is because we have the instant hatches. We may as well use them because we save bucks. And we need one more.  Chroma Span... Wait what is the code 19? A 90 bug off man. Call me when it's important dear. Wait when was Chroma... There it is okay. So it's also gonna cost a cro-ton of food. I don't know 40 millions enough guys.  I don't know if it's gonna be enough. Already... Just feeding the level 10s has taken me 5 million. It's gonna be like 2 million a pop when we get to level 40. Trust me. So we'll instant fuse because we've got some of those. Apparently I've accidentally used one. Which I definitely did not mean to do. Right. So there's 5 million for 4. Right. How much to get? Just one. Okay. Okay. 2 million an odd. That's not bad for level 20. We'll evolve this. So this is the strongest Spinosaur in the game. Oh technical Spinosaur. Okay. So then we'll instant fuse this. This is the level 30 that we already have. Boom. Look at this. Oh god. Not you again. What do you want? Oh to- No Owen. You can't tempt me. That was a good one. I will admit. He came back with a better offer. He was like I almost said yes. Right. Okay. So we'll level you up. Now it's a million. It's 20 million enough to level up. I don't even know. Let's instant fuse. 3 or 60. Look at it. Oh it's extra armor. Let's see it. Oh extra spiky design with the throat that closed.  There's a reason to stay for this video. Boom. Look at it. Oh. A bioluminescent fricking spider sword. That looks so cool. Now that should have been in Dominus Rex you know in Jurassic World. If this came out Boah. Could you imagine you would have got all the Jurassic Park 3 fanboys. So happy. They would have well they would have been so happy they would have done things that I can't say on the channel without being demonetized. Anyway it's four billion a pop. Four. Four. Four. Four. Okay I can't even do the last one. There you go. That's it's eating animation. Yes. Gum gum gum gum gum. Right. Yeah. We got it to level 35. Boom. Chromospinus. Love of fish and plant material was discovered when a lab tech lost their sushi lens to a juvenile dinosaur to the juvenile dinosaur. So we're talking very small. It's eating little sushi thing. Lost its lunch to it. Don't know how that happened. Kind of reminds me I went to freakin Miyajima island not too long ago. If you don't know it's a little island in Japan where deer are sort of roam free. Freakin tourists were feeding it feeding the deer sushi. It's like don't feed the deer there's plenty of sirens don't feed the deer but they were feeding the deer. Why? Instagram. Oh my god there was like one girl like oops oops I'm just oh no he's eating my sushi my girlfriend's like yeah yeah yeah okay it's a good shot God's hate humanity every time I interact with it makes me makes me more mad Anyway we have the power to do such great things and yet you do this Anyway look at Spina so this looks really cool I'm very interested to see where it stacks already 10,000 health and 3,100 attack but wait hold on we can feed it one more time alright Owen God I'll do it it's 305 it's gonna be a lot of DNA okay I appreciate you I see you it's like this good enough yes this one is good enough yes okay so this is one of the best ones to get with the highest payout already 30 okay now can be the 100% it is the question question I think so right come on then right one two three four everyone that's why you come here guys okay right let's not mess up the last one concentrate we did it was it like 309 or something 309 no skin off my nose boom are you happy Owen Jesus now we need to go feed the new baby where are you there you go I don't know why it said I couldn't unless I spent books on it by accident but I don't think I did anyway let's see the eating animation one more time at level 36 I love the universal and Jurassic World we're like you know what we're gonna put our logo in just so you know oh gorgeous yeah look at the sun rays man that's beautiful okay can we get it in the most prettiest arena which is the PVP arena not this one in fact if I do this battle because look even the picture is showing the pretty helipad but I bet if I do a battle it won't be the helipad it'll be the freaking dark visitor center stop it right because I know that'll be the case let's do this one we'll put in actually yes yes yes yes we'll put in you and then where's chromo-span not even level 4 it's gonna make the cut heck yeah when it's level 40 it's gonna be in the top it's a carnival it's a waste of DNA but for you guys anything now there should not be a centizo okay if there is a centizo I'm quitting and I'm not doing it there's a prior turd on there's a compi and there's a majum okay come on we wanna see the spinosaur victory what does he do it's an 8 animation oh yeah also I think people have said the tournaments now um the bots will go first randomly uh which never used to be the case because we know that they're bots so um here it is oh I like that chromo-spino chroma-spino sorry my bad I pronounced your name wrong there wobble up that's a new word wobble up it's a bit like Ron Atkinson there wobble up right not that I'm anywhere near as talented as the man talented my jungler switching into the compi okay so compi I wanna test out my theory to see if I can kill it by going for 7-8 animation I think that is the case hopefully the battery lasts I think I'll get one more message if I get 5% I thought it was 15% but it's 10% so we're gonna get 4 on the next one I'm pretty safe I'm I'm pretty sure even if it goes for 8 attack we're good it's cool oh go for a 7 do it do it oh 4 oh that looks so cool though I love that skin kind of makes me want to play down a hundred deadly shows again right I gotta go for an 8 I don't care now it doesn't matter if you block I'm not true let's see look at it hey even if it blocks as long as it's 7-8 and it will be enough to kill a wall it will kill me that's what we'd like to see and now the Majunga so the beautiful Majungabunga is going to die there's nothing it can do and there you have it now this should give me the best rewards I would hope so look at it there look at it in the broad daylight with the oh with the obscuring metal fence in front of it fantastic elite prize maybe not the best I don't know could be could be hundred does that turn to 200 it does and there we go guys we have done so much this episode so many missions also we've done PVPs as well to claim a little bit more next one I think there's only tickets yes there's only two okay anyway guys I know it's been a long time I appreciate your patience I just want to make sure that you know when I make a video it's interesting there's something that's going on and I want to make it as well because I feel like if I force myself into you know making a video when I don't feel like there's anything there then it puts me on this it puts me in like an awkward situation where I'm like hi guys we're gonna do a thing I don't know if it's really worth a video you know what I mean so it's gone it's interesting because this has went from video, video, video back in 2015 to now I feel like we don't need to do that we've got 500 episodes even more if you count the Cenozoic and Aquatic things God knows but we do it when there's something interesting to do and we have a Chroma Spinosaurus which we will get to level 40 eventually but it's maxed up you see it's animation it's glorious anyway guys I just want to say thank you so much for supporting me all these years it has been a wild ride I would have predicted my life would go this way that's for sure but I'm so glad it has and that you have stayed with me on this whole time I know there's some guy in the car I see comments every now and again that I sort of recognise and I just want to say that I see you I acknowledge you there you guys if you enjoyed this video leave a like and until next time I'll see you later a buh-bye


Live from the Oracle Conference Center in Redwood Shores, California. It's The Cube, at the Next Generation Engineered Systems launch event. Brought to you by headline sponsor, Oracle. Okay, we're back everyone. We are live in Silicon Valley at the Oracle headquarters. This is The Cube, our flagship program. We go out to the events and extract the signal from noise. I'm John Furrier. I'm Mike Coase, Dave Vellante. Our next guest is Neil Mendelson, who's the Vice President of Big Data. Just came back from the speech up on stage. Welcome to The Cube. Thank you. Big Data is big. We've been covering it for a long time. Oracle has, you know, is known in the industry for using data a lot, database, business, database, data. And I'll see you in a relationship with Oracle. It goes back, I think now over three years now, with Mike Olson, the CEO of Cloud Air, was excellent Oracle, sold Sleepy Cat. So you guys are in the ecosystem. So, and your background in data warehousing throughout the industry is known. And we've talked about it off camera. So my first question I want to ask you is, what is the big shift and an inflection point going on in the industry? Because there's a shift and an inflection point, right? So everyone's shifting to a new modern era, but yeah, there's some inflection point that deals with new technology. What's your take on that? Well, I think, you know, what we've seen over the last few years is we've seen this emergence of net new technology, right? And it's emerged in, you know, in the corner, right? It's emerged with a few really, really smart guys in the corner working on this special thing, right? It's different, it's special, it's separate, right? And now what you're seeing is that we're making a transition into the mainstream, right? Where now Hadoop and NoSQL and with the advent of appliances like what Oracle's offering with the X5, we're really able to take that into the enterprise to make it possible to operationalize, right, what was in the laboratory? So a couple of years ago, I think it was two years ago at Oracle Open World, Larry gave a demo and basically he positioned, you remember this, well, he positioned, he was the Twitter data, right? And he positioned sort of, do your filtering in Hadoop and then bring it into Exadata and we'll, you know, power it. And it was a pretty good presentation, as Larry always gives. Is that the general philosophy that you guys have?  Maybe a little bit more than Larry's talk two years ago, his sort of poo-pooing Hadoop, not poo-pooing it, but just sort of depositioning it as the filter and then doing all the powerful stuff here. Is that sort of the mode of operation today or do you see it differently? Well, we see these things as really being complimented, right, I mean, you know, some of the examples that we were talking about were, you know, in the relational side, we've got, you know, information about customers, right? Transactions and the like, right? And that's only growing, right? On the Hadoop side, we have, you know, new information that's maybe coming in from Twitter and the like, right? And really our opportunity is to combine these things together, right? To be able to seek a new insider, a new business model that we didn't have before, right? So it's not a question of one or the other. It's really a question of combining them together. Well, so you hear a lot in the big data circles, but it used to be batch and then there was spark and, you know, whatever yarn, everybody wants to go real-time. Where do you fit in that real-time nest? So are you the A key ingredient, D key ingredient, a compliment? So one of the things to enable real-time is to, you know, ensure that essentially you don't have any latencies built into your processes, right? So, you know, if you're taking a, you know, a one-platform-centric view, so everything has to be at Hadoop, right? Then you've got all these inherent latencies of having to move information from one part to another part to the third part in order to be able to, in real-time, provide a recommendation, right? What we're seeing is that the worlds of transactions, warehousing and Hadoop and big data collapsing, right? And becoming essentially the fabric that you see across the data center to enable you to be able to take a transaction, be able to provide a real-time response, right? Based on a predictive model that maybe was built in Hadoop. But it's not one where, you know, you're going to be taking months or quarters in order to figure out what you're doing anymore. And you've got to be able to cut down on the amount of moving of data and the number of moving parts. And that's really what we're striving to do. So let's talk economics. Five years ago, we had Jeff Hammabacker on and he told us, he went back to his Facebook days and said my mission was to break this model of the container where I had to pay all this money for the storage container.  You gave a customer case example where it was actually cheaper. So what's happened? What's evolved and changed since those early days or has it changed? Well, you know, Larry really talked about it today, right? Oracle has historically always competed on value, right? And, you know, in the Hadoop world, right? You have to first compete on price and then you can compete on value, right? We've actually been doing that, right? With the big data appliance for a number of years. But it's been a bit of an uphill struggle because when people think about, you know, the lowest possible cost, they haven't historically turned to Oracle. You know the short answer. Oh no, we haven't been, right?  I myself kept going through the numbers again and again, there's got to be something wrong here. Let's do it again. What am I missing? Wait a minute, what aren't you telling me? And the numbers are real, right? Now what we're doing is as a company, right? We're continuing to focus on performance. We're continuing to focus on value. But now we've got a tremendous focus on, you know, driving down the price, the initial price of whether you're talking about a virtual appliance to run an entire data center or a big data appliance. And I think that's going to help us tremendously to raise the awareness that Oracle's in this game, right, in order to compete on price and on value. I mean, there's two strategies you see with the engineer systems, the competing on prices. It's a good competitive strategy. But in emerging markets that are nascent like big data, there's not a lot of value demonstrated yet. So price is important for entry and ingratiating into the market. Okay, get that. So I got to ask you, where is that value now? And we see, you know, people will say the killer app and it needs to be a killer app in some market. But let's talk about that. In big data, what is the killer app? Is it the fabric? Is it the app? Is it analytics? Insight, you really can't put your finger on one killer app in big data or is there a killer app? I think the thing that are focusing on more often than not is the killer is not about looking at what's happened in the past, right? And looking about, you know, in order to understand what's happened historically. The killer at this point is in order to predict, right? It's to look into the future, right? How do I provide that next best offer so somebody picks up an additional product?  Instead, we're going to be using this new sensor technology and we're going to be gathering that data in and we're going to use it in order to predict what a failure might occur to get to it before it actually fails. And it's that prediction, right? That people are really looking for that provides that essentially killer. Well, that's a couple of different components but let's go back a little history. In 2011, we were at theCUBE in New York for a dupe world. Mike Olson and Ping Lee of Excel, we're announcing a $100 million venture fund for big data apps. Categorically, it sounds like there's an application market there. It should never materialize. When in reality, the market became, killer app was analytics, baseline analytics. So now you're talking to a whole another level about insight. So this is a fabric issue. It's not so much, this is a big data app. In visualization, Tableau, I can see things like that. Well, we are actually starting to see the emergence of big data apps. So we have, and we're not only seeking them out in order to partner with companies, we're beginning to augment our own applications with big data capabilities. And I'm sure you've seen recently, we've acquired companies that have big data fabrics, right? Like Blue Chi and others like that. So we are beginning to see companies begin to specialize. So in areas, for example of looking at churn prediction and network failures for telco, right? And we're seeing big data apps begin to emerge from companies like Emcentric and others like that to provide an app that specializes in this industry, in that case, telco, on that particular business problem. And that's an evolution. So would you say, I would agree with you by the way, I'm starting to see that as well. Certainly even you guys put the marketing cloud, you're seeing big data, big part of that. And the stacks developing. So do you attribute, and I bring up the reference of 2011 because it's a little bit premature in my opinion, but. Is the stack ready for prime time? Is the cloud ready? So is the sign that we're seeing the emergence of apps a signal that the application market's about to explode or coming on board? Because that means, would assume that underlying technology's ready. Well I think if you go back a few years and if you were an aspiring app vendor, right? And you want to build an app, right? What are your initial barriers? Well one barrier is people say, well what is this based on? Well it's based on this big data Hadoop stuff. People go, what is that, right? So you've got that initial objection to overcome. And then, right, scoop, right? All these funny names, right? This kind of thing. I don't recognize that stuff, right? And then you've got security concerns that people talk about, right? And if you're an application vendor, you need a stable platform in order to build on, right? You don't need one that's moving all over the place all the time, right? And when everyone is out there building their own Hadoop clusters one at a time, each one being completely different. You can't build an application business on top of a moving foundation, right? So you've got to have companies like Oracle and others that are beginning to essentially standardize that big data environment so that app vendors can have a solid foundation to build upon and companies can use that to build their own applications. This is the classic enabling technology platform. So you need a stable platform. You don't want a saying that's shifting all the time and you need an enabling technology. So I've got to ask you, what is the, in your opinion, disruptive enabler for that enablement that you guys are providing? And you compete with some other platforms that are trying to establish themselves as fast as possible. Table stakes is a platform and you need an enabling technology. So what would you guys consider as the disruptive enabler that you're developing? So table stakes is to begin with is cost, right? Because let's come back to the dollar, right? Because everyone's assumption, their working assumption is that, all this stuff is free and it's really, really cheap, right? So, and they think that they can fundamentally build it less expensively than they can buy it, right? And that's the working assumption that exists in the market. And what's interesting about that is that the people that are engaged in this, right, really take, I used to be one of those guys, right? Immense pleasure. Alpha Keys can do it, but they can't do it at scale unless there's a Facebook-like example. Exactly. Not everybody can be Facebook, right? Even Facebook struggles to be Facebook from time to time, right? Facebook has Oracle now, so, you know, but this is the point. Google would love to be the point. The Facebook Google Envy is now off the table because the cost to manage it just on the database side or is that what you, because that's kind of the big issue, right? Yeah, I was speaking to a customer just today, right? And it was talking about how difficult it is to be able to get his own people, right? To think beyond the notion that they can actually create value for the business by assembling the underlayment themselves, right? That he really needs to get them out of the weeds and up to focus on what is going to provide value to the business, because very few companies, if at all, right, can really compete with the likes of ourselves and others, right? That are innovating at that level. Instead, what they need to do is to build off of it, right, is to leverage what we're providing and what others are providing, that stable platform to leverage upon, right? And not focus their IT energy and time, which translates into money, and essentially assembling a jigsaw puzzle. So, Hype aside, would you agree, our research shows that most organizations are struggling to get real return on big data. You got the outliers that get killed, but on average, they're turning 55 cents on every dollar spent, and they're struggling to find their way. And what we're seeing is that those failures occur because they're trying to build stuff themselves, it takes them, you know, they think they can do it really quickly, right? And month after month after month, it takes them six or more months just to stand up that environment and then to essentially build upon it. And once they actually get something, right, wow, how do they actually operationalize it, right? We've seen example after example, where they actually have some real value that they've come upon, but then they take it to the operations group and they say, well, please operationalize this stuff. And they look at this and they go, are you kidding me, right? There's no- I think that's the biggest challenge.  When you want to scale it, it's very challenging. And that's really where we come in, right? We come in in really helping businesses, right? Not just get started really quick, but to move from the laboratory into production, right? With the same kind of guidelines that are necessary to operate today. You can't drop all your security and all your- Well, here's the problem that we see. I mean, I see, and I wrote a post on Forbes about this one, about the marketing cloud. And I use that in Oracle as an example and it's going to look more like Amazon than it's going to look like than prefabricated, bloated lights in the software, like the old jives of the world. But because big data hits every department. So it's not like the operational playbooks which are tried and true, and you go to certain companies, here's how we do it in manufacturing, so we do it in HR, I mean, they've been around. But now you have more of a horizontal integration that some companies just can't handle. Do you see that as well? And what can companies do to be prepared to integrate big data and have a data-driven mindset? So what we're suggesting, and you're beginning to see a lot of writings upon this, right? I was reading some things lately from Gartner and others like that, which talk about really the notion that you have an operational side of information technology and then you have an innovation side. The operational side has to be able to take ideas and move them into production quickly with the kind of standards and processes and procedures that you'd expect. But the innovation side needs to operate in a much more agile sense, right? In IT, we've learned to essentially eliminate risk, by essentially covering all bases, right? It's hard to innovate like that. So what we're suggesting is that companies essentially have an innovation laboratory, right? Where they combine their business analysts with data scientists, with data wranglers, from people with the business, where they can bring together disparate datasets and explore and try out things, right? While at the same time they embed big data in their operational infrastructure, so that when insights are derived, they can quickly operationalize this, right? Because if you, you know, one approach or the other, right? One extreme or the other doesn't seem to work, right? You can't have a completely agile infrastructure, that's chaotic, right? Nor can you have a completely structured innovation. That leads to nothing. So it used to be run the business, grow the business, transform the business, and they were sort of three separate investment silos. What you're suggesting is you connect those through insights and actually fuse them in some way, shape, or form. And it's hard for a lot of organizations, you know? In the Valley, we talk about, you know, failing fast, right? And how we learn from failure and that we appreciate failure. No one likes failure, by the way. No, but, you know. In a fail, go do it fast. How many things have you learned from your successes? Me, nothing, right? Only catastrophic failures went, oh my God, I actually learned something, right? Don't do that again. Don't do that again, ooh, that hurts, right? You know, it's only by the contrast that you learn, right? You know, and that kind of mentality has been driven out of us in the IT sector. So we have to bring that back, but we have to contain it, right? So that it doesn't essentially put at risk, right? The information that this is to tell. And the assets. Absolutely. So let's talk about, given that, let's talk about developers, because in order to have that flywheel going, you need to have some activity, which one of them is development. So, you know, a lot of people are developing apps and mobile apps and infrastructure and software to integrate in and build their business, grow the top line. So what is the developer's data mine right now? Because obviously, you're seeing apps come out. That's an operational issue as well as an innovation issue that kind of crosses over between them. So what's your view on that right now? Where are we with developers? I mean, data scientists, I would put it in different category, data wranglers are different categories, but like, developer's going to be for the mainstream users. Well, I think first and foremost, you know, you're seeing far less development happening within individual enterprises today than you have ever before, right? Because people are really opting to buy versus build across the board, right? So, you know, if they can buy it and assemble it and do it more quickly, right, why not do that, right? They're only going to build the things that they actually think that can provide them some kind of a strategic advantage, right? So, you know, you're seeing a growing community of developers outside of businesses, more so than you see it within businesses themselves, right? And, you know, that's kind of the way the world's going right now. My final question, we're getting the hook here and I appreciate you coming on, Neil. It's great to have you on theCUBE. We love talking about big data because it's for an hour. I could sit all day. The reception's outside, get a couple glasses of wine. The relationship with Cloudera is well documented, Michael Olson, we talked about it earlier, but now Intel has a relationship with Cloudera. You have a relationship with Intel. There's a lot of things going on with Intel on you guys and Cloudera. So, what is the relationship with Intel and Cloudera? Can you update us on what, is that important? Is it global? I mean, Cloudera was a startup and they have a huge valuation now, of course helping the Intel, but... So, it happens on different levels, right? At the pure engineering level, right? We've been working with Intel, right, for many years on optimizing, you know, the silicon, right, for the operations that are performed, right? In fact, you know, that's what we've been doing on Exadata platform and others, right? So, that work continues, right? And now with Intel tying up with Cloudera, providing that investment, they, too, are turning their attention into these newer technologies with Hadoop and NoSQL and the like. So, together, we think this forms an interesting triad, right? Where we can essentially work together as a team, right? To push the industry forward, right? And as Larry talked about, begin to use the force of gravity to embed more and more things down at lower, lower levels of the spectrum, right? And that's beginning to happen at an engineering level, right? At a, you know, at a field level, right? Intel's had their own distribution, right? And that distribution was, you know, mainly sold largely out of China, right? And now we're working with Intel and China, right? Together with Cloudera to move those customers that went with the Intel distribution, perhaps on a DIY platform, and to move them over to Cloudera on the big data appliance, right? And bringing that together. That brings a global consumption model to the table. Absolutely. For you, multinational companies.  All right, well, my final question is, you just came back to Oracle, so tell the story. So you came back, how long you had back now? A little over a year.  I mean, it's an industry now. Congratulations. It did pretty well. Why are you back? Okay, and why, do you have the pick of the litter? I'm assuming you can come back, you know, Larry probably was thinking, welcome you back with open arms. Why big data? And why are you back?  Well, so, you know, in the intervening time, I had done a number of startups, right? Mostly in the area of, you know, big data analytics and the cloud, right? And what I saw at the time that I was with Oracle is that, you know, you can do a lot of innovations by yourself, right? But it's hard to really attract enough attention to get enough traction fast enough to really change an industry, right? And Oracle's one of the few companies that actually has the kind of draw that allows that to happen, right? You just saw base, too. Huge, right? In Russell. I mean, customers that were using us for transaction processing turn to us for data warehousing. And we think that same opportunity exists for customers to turn to us for big data. And what better place, right, to go and explore the possibilities of big data than the original data company itself or, right?  Yeah. And kind of have some fun with it. Yeah, I mean, this is a tremendous amount of fun, right? Being able to see, you know, businesses transform themselves, right? Seemingly overnight. Who knows where this will end up? No, it's exciting. It's very intoxicating at a very intellectual level. Big data is certainly going to be a fabric, in my opinion. I think it's going to be a huge moneymaker for services for all the ecosystem. And again, we're first generation connected worlds. So, I mean, I think it's only going to get bigger. So this is theCUBE, of course. We're big data. We're all about sharing the data with you, stretching the seeds from the noise. I'm John Furrier with Dave Vellante. We'll be right back after this short break, live here at Oracle's headquarters at Silicon Valley. This is theCUBE.


Hello students, let's solve the following question of probability. It says three points are tossed once. Find the probability of getting three heads, two heads, it leaves two heads, at most two heads, no head, three tails, exactly two tails, no tail, at most two tails. Before moving on to the solution, let us first understand the formula for probability of any event E. If S is the sample space and E is any event, which is the subset of S, then the probability of E is equal to the number of outcomes favorable to E upon the total number of outcomes. So this knowledge will work as the idea. Whereas now proceed on with the solution, we are given that three points are tossed once. So the total number of outcomes will be equal to 2 to the power 3. Because when we toss a coin, there are two possibilities.  So it is 2 to the power 3 which is equal to 8. So let us now write the sample space for this experiment. The one of the possibilities that we get head, head, head, that is we get head on all the three coins. Another possibility is that we get head on the first two coins and tail on the last coin. Similarly, we can have HTH or we can have THH, then we can have TTH, then we can have THT. Another possibility is that we get head on the first coin and tail, tail on the last two coins. Then the last possibility is that we get tail on all the coins. So these are eight possibilities. Now in the first part, we have to find the probability of getting three heads. So here event E is getting three heads. From the sample space, we see that there is only one possibility of getting three heads that is HHHH. So the number of outcomes favourable to E is 1. So the probability of getting three heads is equal to the number of outcomes favourable to E upon the total number of outcomes that is 8. So the probability of getting three heads is 1 by 8. Now in the second case, we have to find the probability of getting two heads. So here E is the event of getting two heads. So the number of outcomes favourable to E. Here we can see that 1, 2, 3. There are three outcomes favourable to E, HHHT, HTH, THH is 3, 1, 2, 3. So the probability of getting two heads is equal to the number of outcomes favourable to E upon the total number of outcomes that is 8. So the probability is 3 by 8. Now in the third part, we have to find the probability of getting at least two heads. So here E is the event of getting at least two heads. Now we see that the number of outcomes favourable to E, we want to have at least two heads. That means we can have more than two heads. So one of the possibilities is HHHH. Second one is HHHT. Third one is HHHT. Fourth one is HHHT. And in other cases, we don't get HHHT more than one time. So the number of outcomes favourable to E are 4. So the probability of getting at least two heads is equal to the number of outcomes favourable to E that is 4 upon the total number of outcomes. So the probability is 4 by 8 which is equal to 1 by 2. Now in the fourth part, we have to find the probability of getting at most two heads. So E is the event of getting at most two heads. At most two heads means we should not get more than two heads. We can have one head or we can have two heads. So let's see the sample space and see which are the outcomes favourable to E. These are So the number of outcomes favourable to E are 1, 2, 3, 4, 5 and 6. Since we have to find the probability of getting at most two heads, we can have one more possibility that is we get tail, tail, tail that is we don't get head. So the number of outcomes favourable to E becomes equal to 7, 1, 2, 3, 4, 5, 6 and 7. So the probability of getting at most two heads is equal to the number of outcomes favourable to E that is 7 upon the total number of outcomes. Now we have to find the probability of getting no head. So the number of outcomes favourable to E is only one because this is the only case that is when we get tail, tail, tail on all the coins then we don't get a head. So the probability of getting no head is equal to 1 upon 8. Now in the third, sixth part we have to find the probability of getting three tails. And there is only one possibility of getting three tails that is tail, tail, tail. So the number of outcomes favourable to E is 1. So the probability of getting three tails is equal to 1 upon 8. Now in the seventh part we have to find the probability of getting exactly two tails. So here E is the event of getting at least two exactly two tails. From the sample space we see that which are the possibilities favourable to E we have to get exactly two tails. So this is the one of the possibilities that is tail, tail, head, tail and head, tail, tail. So the number of outcomes favourable to E are three. So the probability of getting exactly two tails is equal to 3 by 8. That is the number of outcomes favourable to E upon the total number of outcomes. Now in the eighth part we have to find the probability of getting no tail. We get no tails if we get all the heads that is the possibility when we get head, head, head. So the number of outcomes favourable to E is 1. So the probability of getting no tail is equal to the number of outcomes favourable to E which comes out to be 1 upon the total number of outcomes. Now in the last part we have to find the probability of getting at most two tails. At most two means we can have zero number of tails or we can have one tail or we can have two tails. But we cannot have more than two tails. So let's see which are the favourable possibilities. So this is the favourable possibility. This one, this one, this one and this we are getting two tails. And this also and this also. So these are seven possibilities. So the number of outcomes favourable to E are seven. So the probability of getting at most two heads its tails is equal to 7 by 8. That is the number of outcomes favourable to E which are seven upon the total number of outcomes. Hence answer to the first part of the question is 1 by 8. To the second part answer is 3 by 8. To the third part answer is 1 by 2. To the fourth part answer is 7 by 8. And to the fifth part answer is 1 by 8. To the sixth part answer is 1 by 8. To the seventh part answer is 3 by 8. To the eighth part answer is 1 by 8. And to the ninth part answer is 7 by 8. And this completes the question and the session. Bye for now. Take care. Have a good day.