Googlier.com News Article Search
Googlier.com Precious Metals Exchange Smart Contracts
Googlier.com Document Services





          Latest Tech Trends, Their Problems, And How to Solve Them      
https://blogs.oracle.com/infrastructure/latest-tech-trends%2C-their-problems%2C-and-how-to-solve-them

Few IT professionals are unaware of the rapid emergence of 5G, Internet of Things or IoT, edge-fog-cloud or core computing, microservices, and artificial intelligence known as machine learning or AI/ML.  These new technologies hold enormous promise for transforming IT and the customer experience with the problems that they solve.  It’s important to realize that like all technologies, they introduce new processes and subsequently new problems.  Most are aware of the promise, but few are aware of the new problems and how to solve them.

5G is a great example.  It delivers 10 to 100 times more throughput than 4G LTE and up to 90% lower latencies.  Users can expect throughput between 1 and 10Gbps with latencies at approximately 1 ms.  This enables large files such as 4K or 8K videos to be downloaded or uploaded in seconds not minutes.  5G will deliver mobile broadband and can potentially make traditional broadband obsolete just as mobile telephony has essentially eliminated the vast majority of landlines. 

5G mobile networking technology makes industrial IoT more scalable, simpler, and much more economically feasible.  Whereas 4G is limited to approximately 400 devices per Km2, 5G increases that number of devices supported per Km2 to approximately 1,000,000 or a 250,000% increase. The performance, latency, and scalability are why 5G is being called transformational.  But there are significant issues introduced by 5G.  A key one is the database application infrastructure.

Analysts frequently cite the non-trivial multi-billion dollar investment required to roll-out 5G.  That investment is primarily focused on the antennas and fiber optic cables to the antennas.  This is because 5G is based on a completely different technology than 4G.  It utilizes millimeter waves instead of microwaves.  Millimeter waves are limited to 300 meters between antennas.  The 4G microwaves can be as far as 16 Km apart.  That is a major difference and therefore demands many more antennas and optical cables to those antennas to make 5G work effectively.  It also means it will take considerable time before rural areas are covered by 5G and even then, it will be a degraded 5G. 

The 5G infrastructure investment not being addressed is the database application infrastructure.  The database is a foundational technology for analytics.  IT Pros simply assume it will be there for their applications and microservices. Everything today is interconnected. The database application infrastructure is generally architected for the volume and performance coming from the network.  That volume and performance is going up by an order of magnitude.  What happens when the database application infrastructure is not upgraded to match?  The actual user performance improves marginally or not at all.  It can in fact degrade as volumes overwhelm the database applications not prepared for them.  Both consumers and business users become frustrated.  5G devices cost approximately 30% more than 4G – mostly because those devices need both a 5G and 4G modem (different non-compatible technologies).  The 5G network costs approximately 25% more than 4G.  It is understandable that anyone would be frustrated when they are spending considerably more and seeing limited improvement, no improvement, or negative improvement.  The database application infrastructure becomes the bottleneck.  When consumers and business users become frustrated, they go somewhere else, another website, another supplier, or another partner.  Business will be lost.

Fortunately, there is still time as the 5G rollout is just starting with momentum building in 2020 with complete implementations not expected until 2022, at the earliest.  However, IT organizations need to start planning their application infrastructure upgrades to match the 5G rollout or may end up suffering the consequences.

IoT is another technology that promises to be transformative.  It pushes intelligence to the edge of the network enabling automation that was previously unthinkable.  Smarter homes, smarter cars, smarter grids, smarter healthcare, smarter fitness, smarter water management, and more.  IoT has the potential to radically increase efficiencies and reduce waste.  Most of the implementations to date have been in consumer homes and offices.  These implementations rely on the WiFi in the building they reside. 

The industrial implementations have been not as successful…yet.  Per Gartner, 65 to 85% of Industrial IoT to date have been stuck in pilot mode with 28% of those for more than 2 years.  There are three key reasons for this.  The first are the limitations of 4G of 400 devices per Km2.  This limitation will be fixed as 5G rolls out.  The second is the same issue as 5G, database application infrastructure not suited for the volume and performance required by industrial IoT.  And the third is latency from the IoT edge devices to the analytics, either in the on-premises data center (core), or cloud.  Speed of light latency is a major limiting factor for real-time analytics and real-time actionable information.  This has led to the very rapid rise of edge-fog-cloud or core computing.

Moving analytic processing out to the edge or fog significantly reduces distance latency between where the data is being collected and where it is being analyzed.  This is crucial for applications such as autonomous vehicles.  The application must make decisions in milliseconds not seconds.  It may have to decide whether a shadow in the road is actually a shadow, a reflection, a person, or a dangerous hazard to be avoided.  The application must make that decision immediately and cannot wait.  By pushing the application closer to the data collection, it can make that decision in the timely manner that’s required.  Smart grids, smart cities, smart water management, smart traffic management, are all examples requiring fog (near the edge) or edge computing analytics.  This solves the problem of distance latency; however, it does not resolve analytical latency.  Edge and fog computing typically lack the resources to provide ultra-fast database analytics.  This has led to the deployment of microservices

Microservices have become very popular over the past 24 months.   They tightly couple a database application with its database that has been extremely streamlined to do only the few things the microservice requires.  The database may be a neutered relational, time series, key value, JSON, XML, object, and more.  The database application and its database are inextricably linked.  The combined microservice is then pushed down to the edge or fog compute device and its storage.  Microservices have no access to any other microservices data or database.  If it needs access to another microservice data element, it’s going to be difficult and manually labor-intensive. Each of the microservices must be reworked to grant that access, or the data must be copied and moved via an extract transfer and load (ETL) process, or the data must be duplicated in ongoing manner.  Each of these options are laborious, albeit manageable, for a handful of microservices.  But what about hundreds or thousands of microservices, which is where it’s headed?  This sprawl becomes unmanageable and ultimately, unsustainable, even with AI/ML.

AI/ML is clearly a hot tech trend today.  It’s showing up everywhere in many applications.  This is because standard CPU processing power is now powerful enough to run AI / machine learning algorithms.  AI/ML is showing up typically in one of two different variations.  The first has a defined specific purpose.  It is utilized by the vendor to automate a manual task requiring some expertise.  An example of this is in enterprise storage.  The AI/ML is tasked with placing data based on performance, latency, and data protection policies and parameters determined by the administrator.  It then matches that to the hardware configuration.  If performance should fall outside of the desired parameters AI/ML looks to correct the situation without human intervention.  It learns from experience and automatically makes changes to accomplish the required performance and latency.   The second AI/ML is a tool kit that enables IT pros to create their own algorithms. 

The 1st is an application of AI/ML.  It obviously cannot be utilized outside the tasks it was designed to do. The 2nd is a series of tools that require considerable knowledge, skill, and expertise to be able to utilize.  It is not an application.  It merely enables applications to be developed that take advantage of the AI/ML engine.  This requires a very steep learning curve.

Oracle is the first vendor to solve each and every one of these tech trend problems. The Oracle Exadata X8M and Oracle Database Appliance (ODA) X8 are uniquely suited to solve the 5G and IoT application database infrastructure problem, the edge-fog-core microservices problem, and the AI/ML usability problem. 

It starts with the co-engineering.  The compute, memory, storage, interconnect, networking, operating system, hypervisor, middleware, and the Oracle 19c Database are all co-engineered together.  Few vendors have complete engineering teams for every layer of the software and hardware stacks to do the same thing.  And those who do, have shown zero inclination to take on the intensive co-engineering required.  Oracle Exadata alone has 60 exclusive database features not found in any other database system including others running the same Oracle Database. Take for example Automatic Indexing.  It occurs multiple orders of magnitude faster than the most skilled database administrator (DBA) and delivers noticeably superior performance.  Another example is data ingest.  Extensive parallelism is built-into every Exadata providing unmatched data ingest.  And keep in mind, the Oracle Autonomous Database is utilizing the exact same Exadata Database Machine.  The results of that co-engineering deliver unprecedented Database application latency reduction, response time reduction, and performance increases.  This enables the application Database infrastructure to match and be prepared for the volume and performance of 5G and IoT.

The ODA X8 is ideal for edge or fog computing coming in at approximately 36% lower total cost of ownership (TCO) over 3 years than commodity white box servers running databases.  It’s designed to be a plug and play Oracle Database turnkey appliance.  It runs the Database application too.  Nothing is simpler and no white box server can match its performance.

The Oracle Exadata X8M is even better for the core or fog computing where it’s performance, scalability, availability and capability are simply unmatched by any other database system.  It too is architected to be exceedingly simple to implement, operate, and manage. 

The combination of the two working in conjunction in the edge-fog-core makes the application database latency problems go away.  They even solve the microservices problems.  Each Oracle Exadata X8M and ODA X8 provide pluggable databases (PDBs).  Each PDB is its own unique database working off the same stored data in the container database (CDB).  Each PDB can be the same or different type of Oracle Database including OLTP, data warehousing, time series, object, JSON, key value, graphical, spatial, XML, even document database mining.  The PDBs are working on virtual copies of the data.  There is no data duplication.  There are no ETLs.  There is no data movement.  There are no data islands.  There are no runaway database licenses and database hardware sprawl.  Data does not go stale before it can be analyzed.  Any data that needs to be accessed by a particular or multiple PDBs can be easily configured to do so.  Edge-fog-core computing is solved.  If the core needs to be in a public cloud, Oracle solves that problem as well with the Oracle Autonomous Database providing the same capabilities of Exadata and more.

That leaves the AI/ML usability problem.  Oracle solves that one too.  Both Oracle Engineered systems and the Oracle Autonomous Database have AI/ML engineered inside from the onset.  Not just a tool-kit on the side.  Oracle AI/ML comes with pre-built, documented, and production-hardened algorithms in the Oracle Autonomous Database cloud service.  DBAs do not have to be data scientists to develop AI/ML applications.  They can simply utilize the extensive Oracle library of AI/ML algorithms in Classification, Clustering, Time Series, Anomaly Detection, SQL Analytics, Regression, Attribute Importance, Association Rules, Feature Extraction, Text Mining Support, R Packages, Statistical Functions, Predictive Queries, and Exportable ML Models.  It’s as simple as selecting the algorithms to be used and using them.  That’s it.  No algorithms to create, test, document, QA, patch, and more.

Taking advantage of AI/ML is as simple as implementing Oracle Exadata X8M, ODA X8, or the Oracle Autonomous Database.   Oracle solves the AI/ML usability problem.

The latest tech trends of 5G, Industrial IoT, edge-fog-core or cloud computing, microservices, and AI/ML have the potential to truly be transformative for IT organizations of all stripes.  But they bring their own set of problems.  Fortunately, for organizations of all sizes, Oracle solves those problems.




Array ( [span] => 224 [style] => 132 [nbsp] => 128 [the] => 97 [and] => 64 [to] => 62 [is] => 51 [of] => 45 [line-height] => 43 [pt] => 43 [font-size] => 43 [p] => 40 [px] => 40 [G] => 31 [The] => 29 [be] => 28 [or] => 26 [a] => 26 [database] => 26 [in] => 23 [Oracle] => 23 [It] => 21 [are] => 20 [sans-serif] => 20 [Calibri] => 20 [font-family] => 20 [margin-bottom] => 20 [margin-top] => 20 [justify] => 20 [text-align] => 20 [data] => 19 [ML] => 19 [that] => 19 [AI] => 19 [application] => 19 [for] => 18 [as] => 16 [b] => 14 [Database] => 14 [not] => 14 [it] => 13 [performance] => 13 [more] => 12 [with] => 11 [have] => 11 [This] => 11 [microservices] => 10 [infrastructure] => 10 [IoT] => 10 [can] => 10 [latency] => 10 [rsquo] => 9 [s] => 9 [Exadata] => 8 [X] => 8 [no] => 8 [by] => 8 [computing] => 8 [problems] => 8 [c] => 7 [edge] => 7 [than] => 7 [has] => 7 [on] => 7 [same] => 7 [problem] => 7 [they] => 6 [There] => 6 [algorithms] => 6 [devices] => 6 [applications] => 6 [will] => 6 [IT] => 6 [approximately] => 6 [do] => 6 [color] => 6 [fog] => 6 [all] => 6 [time] => 5 [required] => 5 [even] => 5 [another] => 5 [Autonomous] => 5 [solve] => 5 [Each] => 5 [up] => 5 [its] => 5 [core] => 5 [smarter] => 5 [antennas] => 5 [must] => 5 [solves] => 5 [those] => 5 [make] => 5 [analytics] => 5 [That] => 5 [an] => 4 [different] => 4 [match] => 4 [technology] => 4 [volume] => 4 [ODA] => 4 [where] => 4 [their] => 4 [enables] => 4 [from] => 4 [cloud] => 4 [been] => 4 [And] => 4 [implementations] => 4 [one] => 4 [key] => 4 [being] => 4 [example] => 4 [M] => 4 [at] => 4 [Km] => 4 [new] => 4 [tech] => 3 [any] => 3 [take] => 3 [investment] => 3 [other] => 3 [But] => 3 [there] => 3 [because] => 3 [very] => 3 [If] => 3 [needs] => 3 [co-engineering] => 3 [then] => 3 [go] => 3 [system] => 3 [first] => 3 [own] => 3 [usability] => 3 [smart] => 3 [hardware] => 3 [management] => 3 [They] => 3 [may] => 3 [organizations] => 3 [microservice] => 3 [PDBs] => 3 [edge-fog-core] => 3 [improvement] => 3 [series] => 3 [frustrated] => 3 [too] => 3 [storage] => 3 [network] => 3 [access] => 3 [working] => 3 [every] => 3 [simply] => 3 [become] => 3 [simple] => 3 [limited] => 3 [makes] => 3 [mobile] => 3 [technologies] => 3 [them] => 3 [learning] => 3 [per] => 3 [just] => 3 [industrial] => 3 [between] => 3 [scalability] => 2 [was] => 2 [homes] => 2 [grids] => 2 [running] => 2 [increase] => 2 [water] => 2 [delivers] => 2 [potential] => 2 [including] => 2 [date] => 2 [Industrial] => 2 [years] => 2 [this] => 2 [few] => 2 [out] => 2 [multiple] => 2 [ingest] => 2 [throughput] => 2 [becomes] => 2 [Both] => 2 [consumers] => 2 [business] => 2 [users] => 2 [cost] => 2 [need] => 2 [databases] => 2 [box] => 2 [white] => 2 [reduction] => 2 [transformative] => 2 [Fortunately] => 2 [rollout] => 2 [unmatched] => 2 [building] => 2 [complete] => 2 [latencies] => 2 [providing] => 2 [lower] => 2 [aware] => 2 [second] => 2 [experience] => 2 [suited] => 2 [XML] => 2 [over] => 2 [edge-fog-cloud] => 2 [administrator] => 2 [parameters] => 2 [requires] => 2 [rapid] => 2 [value] => 2 [JSON] => 2 [object] => 2 [provide] => 2 [expertise] => 2 [compute] => 2 [Few] => 2 [vendor] => 2 [utilized] => 2 [two] => 2 [these] => 2 [showing] => 2 [trend] => 2 [Microservices] => 2 [outside] => 2 [Most] => 2 [utilize] => 2 [real-time] => 2 [such] => 2 [led] => 2 [promise] => 2 [processing] => 2 [distance] => 2 [analyzed] => 2 [advantage] => 2 [These] => 2 [shadow] => 2 [typically] => 2 [designed] => 2 [decision] => 2 [cannot] => 2 [create] => 2 [manner] => 2 [machine] => 2 [requiring] => 2 [intelligence] => 2 [does] => 2 [prepared] => 2 [sprawl] => 2 [cables] => 2 [broadband] => 2 [architected] => 2 [today] => 2 [based] => 2 [increases] => 2 [networking] => 2 [going] => 2 [deliver] => 2 [many] => 2 [coming] => 2 [magnitude] => 2 [document] => 2 [considerable] => 2 [waves] => 2 [when] => 2 [major] => 2 [simpler] => 2 [PDB] => 2 [K] => 2 [seconds] => 2 [before] => 2 [microwaves] => 2 [intervention] => 1 [changes] => 1 [should] => 1 [Any] => 1 [automatically] => 1 [fall] => 1 [looks] => 1 [learns] => 1 [correct] => 1 [situation] => 1 [desired] => 1 [human] => 1 [easily] => 1 [using] => 1 [accessed] => 1 [without] => 1 [particular] => 1 [production-hardened] => 1 [availability] => 1 [stale] => 1 [licenses] => 1 [used] => 1 [curve] => 1 [ETLs] => 1 [movement] => 1 [steep] => 1 [engine] => 1 [islands] => 1 [developed] => 1 [merely] => 1 [runaway] => 1 [able] => 1 [skill] => 1 [knowledge] => 1 [accomplish] => 1 [require] => 1 [tools] => 1 [nd] => 1 [DBAs] => 1 [tasks] => 1 [obviously] => 1 [Data] => 1 [st] => 1 [service] => 1 [configuration] => 1 [pros] => 1 [kit] => 1 [tool] => 1 [configured] => 1 [determined] => 1 [so] => 1 [now] => 1 [truly] => 1 [tool-kit] => 1 [purpose] => 1 [specific] => 1 [stripes] => 1 [defined] => 1 [variations] => 1 [engineered] => 1 [bring] => 1 [run] => 1 [enough] => 1 [powerful] => 1 [power] => 1 [latest] => 1 [CPU] => 1 [standard] => 1 [everywhere] => 1 [inside] => 1 [Not] => 1 [onset] => 1 [set] => 1 [hot] => 1 [clearly] => 1 [unsustainable] => 1 [ultimately] => 1 [unmanageable] => 1 [trends] => 1 [systems] => 1 [No] => 1 [tasked] => 1 [matches] => 1 [Edge-fog-core] => 1 [solved] => 1 [duplication] => 1 [test] => 1 [public] => 1 [policies] => 1 [QA] => 1 [protection] => 1 [placing] => 1 [patch] => 1 [well] => 1 [enterprise] => 1 [implementing] => 1 [documented] => 1 [pre-built] => 1 [comes] => 1 [side] => 1 [capabilities] => 1 [An] => 1 [leaves] => 1 [some] => 1 [task] => 1 [manual] => 1 [Engineered] => 1 [automate] => 1 [Taking] => 1 [each] => 1 [Appliance] => 1 [selecting] => 1 [parallelism] => 1 [results] => 1 [Machine] => 1 [exact] => 1 [utilizing] => 1 [Rules] => 1 [mind] => 1 [keep] => 1 [Series] => 1 [conjunction] => 1 [away] => 1 [built-into] => 1 [Extensive] => 1 [unprecedented] => 1 [pluggable] => 1 [Another] => 1 [superior] => 1 [Feature] => 1 [noticeably] => 1 [DBA] => 1 [skilled] => 1 [most] => 1 [faster] => 1 [Time] => 1 [orders] => 1 [Clustering] => 1 [Association] => 1 [Anomaly] => 1 [Indexing] => 1 [turnkey] => 1 [server] => 1 [Nothing] => 1 [capability] => 1 [exceedingly] => 1 [headed] => 1 [implement] => 1 [Analytics] => 1 [Regression] => 1 [operate] => 1 [runs] => 1 [appliance] => 1 [manage] => 1 [play] => 1 [Detection] => 1 [plug] => 1 [servers] => 1 [combination] => 1 [SQL] => 1 [commodity] => 1 [TCO] => 1 [ownership] => 1 [Attribute] => 1 [Importance] => 1 [total] => 1 [ideal] => 1 [response] => 1 [occurs] => 1 [Automatic] => 1 [copies] => 1 [memory] => 1 [co-engineered] => 1 [OLTP] => 1 [warehousing] => 1 [middleware] => 1 [hypervisor] => 1 [Support] => 1 [operating] => 1 [graphical] => 1 [scientists] => 1 [spatial] => 1 [interconnect] => 1 [starts] => 1 [Mining] => 1 [R] => 1 [Packages] => 1 [Statistical] => 1 [Functions] => 1 [uniquely] => 1 [Predictive] => 1 [better] => 1 [mining] => 1 [Queries] => 1 [virtual] => 1 [Exportable] => 1 [Models] => 1 [together] => 1 [type] => 1 [unique] => 1 [extensive] => 1 [Extraction] => 1 [Take] => 1 [off] => 1 [Classification] => 1 [stored] => 1 [container] => 1 [CDB] => 1 [library] => 1 [found] => 1 [features] => 1 [exclusive] => 1 [Text] => 1 [alone] => 1 [vendors] => 1 [intensive] => 1 [inclination] => 1 [zero] => 1 [shown] => 1 [who] => 1 [thing] => 1 [stacks] => 1 [software] => 1 [layer] => 1 [develop] => 1 [teams] => 1 [engineering] => 1 [others] => 1 [Latest] => 1 [which] => 1 [work] => 1 [generally] => 1 [interconnected] => 1 [Everything] => 1 [assume] => 1 [Pros] => 1 [foundational] => 1 [addressed] => 1 [degraded] => 1 [covered] => 1 [areas] => 1 [rural] => 1 [means] => 1 [also] => 1 [effectively] => 1 [optical] => 1 [What] => 1 [demands] => 1 [therefore] => 1 [difference] => 1 [apart] => 1 [far] => 1 [meters] => 1 [Millimeter] => 1 [instead] => 1 [millimeter] => 1 [utilizes] => 1 [completely] => 1 [optic] => 1 [fiber] => 1 [focused] => 1 [order] => 1 [happens] => 1 [roll-out] => 1 [would] => 1 [still] => 1 [lost] => 1 [Business] => 1 [partner] => 1 [supplier] => 1 [website] => 1 [else] => 1 [somewhere] => 1 [When] => 1 [bottleneck] => 1 [negative] => 1 [seeing] => 1 [considerably] => 1 [spending] => 1 [anyone] => 1 [upgraded] => 1 [volumes] => 1 [actual] => 1 [user] => 1 [improves] => 1 [marginally] => 1 [fact] => 1 [degrade] => 1 [overwhelm] => 1 [understandable] => 1 [ndash] => 1 [mostly] => 1 [both] => 1 [modem] => 1 [non-compatible] => 1 [costs] => 1 [primarily] => 1 [dollar] => 1 [momentum] => 1 [transforming] => 1 [expect] => 1 [Users] => 1 [LTE] => 1 [times] => 1 [great] => 1 [how] => 1 [but] => 1 [subsequently] => 1 [processes] => 1 [introduce] => 1 [like] => 1 [realize] => 1 [important] => 1 [customer] => 1 [enormous] => 1 [ms] => 1 [hold] => 1 [known] => 1 [artificial] => 1 [Things] => 1 [Internet] => 1 [emergence] => 1 [unaware] => 1 [professionals] => 1 [Them] => 1 [Solve] => 1 [How] => 1 [Problems] => 1 [Their] => 1 [Trends] => 1 [Gbps] => 1 [large] => 1 [multi-billion] => 1 [feasible] => 1 [non-trivial] => 1 [cite] => 1 [frequently] => 1 [Analysts] => 1 [A] => 1 [introduced] => 1 [issues] => 1 [significant] => 1 [transformational] => 1 [called] => 1 [why] => 1 [supported] => 1 [number] => 1 [Whereas] => 1 [economically] => 1 [files] => 1 [obsolete] => 1 [videos] => 1 [downloaded] => 1 [uploaded] => 1 [minutes] => 1 [potentially] => 1 [traditional] => 1 [telephony] => 1 [much] => 1 [essentially] => 1 [eliminated] => 1 [vast] => 1 [majority] => 1 [landlines] => 1 [scalable] => 1 [starting] => 1 [expected] => 1 [thousands] => 1 [near] => 1 [extremely] => 1 [couple] => 1 [tightly] => 1 [months] => 1 [past] => 1 [popular] => 1 [deployment] => 1 [ultra-fast] => 1 [resources] => 1 [lack] => 1 [Edge] => 1 [analytical] => 1 [resolve] => 1 [however] => 1 [examples] => 1 [only] => 1 [traffic] => 1 [cities] => 1 [Smart] => 1 [timely] => 1 [collection] => 1 [closer] => 1 [pushing] => 1 [By] => 1 [wait] => 1 [immediately] => 1 [avoided] => 1 [hazard] => 1 [dangerous] => 1 [person] => 1 [streamlined] => 1 [things] => 1 [actually] => 1 [extract] => 1 [hundreds] => 1 [about] => 1 [what] => 1 [handful] => 1 [manageable] => 1 [albeit] => 1 [laborious] => 1 [options] => 1 [ongoing] => 1 [duplicated] => 1 [process] => 1 [ETL] => 1 [load] => 1 [transfer] => 1 [via] => 1 [neutered] => 1 [device] => 1 [relational] => 1 [inextricably] => 1 [linked] => 1 [combined] => 1 [pushed] => 1 [down] => 1 [element] => 1 [moved] => 1 [difficult] => 1 [manually] => 1 [labor-intensive] => 1 [reworked] => 1 [grant] => 1 [copied] => 1 [reflection] => 1 [road] => 1 [until] => 1 [cars] => 1 [yet] => 1 [hellip] => 1 [successful] => 1 [reside] => 1 [WiFi] => 1 [rely] => 1 [offices] => 1 [consumer] => 1 [waste] => 1 [reduce] => 1 [efficiencies] => 1 [radically] => 1 [fitness] => 1 [healthcare] => 1 [Smarter] => 1 [Gartner] => 1 [unthinkable] => 1 [previously] => 1 [automation] => 1 [enabling] => 1 [pushes] => 1 [promises] => 1 [consequences] => 1 [suffering] => 1 [end] => 1 [upgrades] => 1 [planning] => 1 [start] => 1 [However] => 1 [earliest] => 1 [Per] => 1 [stuck] => 1 [whether] => 1 [actionable] => 1 [decide] => 1 [milliseconds] => 1 [decisions] => 1 [vehicles] => 1 [autonomous] => 1 [crucial] => 1 [collected] => 1 [reduces] => 1 [significantly] => 1 [Tech] => 1 [analytic] => 1 [Moving] => 1 [rise] => 1 [information] => 1 [factor] => 1 [pilot] => 1 [rolls] => 1 [mode] => 1 [three] => 1 [reasons] => 1 [limitations] => 1 [limitation] => 1 [fixed] => 1 [issue] => 1 [limiting] => 1 [third] => 1 [either] => 1 [on-premises] => 1 [center] => 1 [Speed] => 1 [light] => 1 [sizes] => 1 )

© Googlier LLC, 2019