Java IoT Authors: Pat Romanski, Liz McMillan, Yeshim Deniz, Elizabeth White, Carmen Gonzalez

Related Topics: Microservices Expo, Java IoT, Industrial IoT

Microservices Expo: Article

SQL Transparent Hierarchical Processing of Relational, XML and IMS Data

Every ANSI SQL processor contains a powerful hierarchical processor

Current SQL support of relational, XML and hierarchical legacy data such as IMS is driven by flattening the hierarchical data in order to integrate it naturally with relational (flat) data so that it can be processed relationally. Unfortunately, this strips out the natural semantics in hierarchical data which has the capability to dynamically increase the value of the data being processed and to perform powerful hierarchical operations.

The SQL-92 standard introduced the LEFT Outer Join which offers a powerful alternative to standard relational processing that can be used to perform full hierarchical processing naturally and inherently. This enables SQL to seamlessly and transparently integrate relational data at a full hierarchical structured data processing level with XML, IMS and other forms of legacy hierarchical data. This means there is no data loss for the integration of hierarchical and relational data while increasing the level of powerful automatic hierarchical operations.

It is important to note that current SQL access to XML via the SQL/XML standard is through XML semistructured data processing. This is a very relaxed hierarchical principled fuzzy process for processing markup and requires user specified data structure navigation. The natural navigationless hierarchical processing performed by SQL shown in this article always following precise hierarchical principles and restrictions. This keeps the hierarchical structures unambiguous for automatic processing. This will all  be covered in this article.

Also significant to SQL full hierarchical processing is its automatic support of multipath processing. This was a powerful hierarchical processing used for querying IMS databases four decades ago before the advent of relational processing.This utilizes the naturally occurring semantics in multipath queries to transparently perform powerful nonlinear hierarchical processing. This enables non technical users to easily specify more powerful internally complex dynamic queries than are available today. This article will explain and demonstrate this advanced SQL hierarchical multipath processing capability and its advantages that break away from the current relational flat mindset and its limitations. The SQL hierarchical processing examples described in this article have been tested on a hierarchical processing middleware prototype which uses a standard ANSI SQL processor as its hierarchical processing engine.

Basic Hierarchical Data Modeling
The following SQL view definition in Figure 1 uses a sequence of standard SQL LEFT Outer Joins to model the shown hierarchical structure. This hierarchical view is modeled at the node level to define basic physical structures like IMS or XML. It also defines logical hierarchical structures using flat data like relational. The LEFT Outer Join hierarchically preserves the left data argument over the right argument. This allows the left data argument to exist when there is no matching right data argument. These LEFT Outer Joins can be strung together along with the ON clauses to define and build full hierarchical multiple path structures.

The ON clause was also introduced in the ANSI SQL-92 Outer Join to offer more local control over the WHERE clause for specifying join criteria. Notice in Figure 1 that the ON clause is specified at each specific join point to control its specific join operation. All of these capabilities allow the LEFT Outer Join syntax to exactly model hierarchical structures unambiguously. This was not previously possible using a single WHERE clause for join control. The WHERE clause is still used to specify global data filtering described later.

    Basic Hierarchical Data Modeling

    LEFT JOIN D ON R.r=D.d /* Extend path from node R to node D */
    LEFT JOIN B ON R.r=B.b /* Start new Path from node R to node B */

    Basic Structure
        /  \
      D   B

   Figure 1: SQL Hierarchical View

The corresponding hierarchical semantics to the LEFT Outer Join data modeling syntax shown in Figure 1 defines exactly how this data structure definition operates hierarchically. It performs hierarchical data preservation when processed directly by the ANSI SQL processor. As shown in Figure 1, this hierarchical data definition can be specified in an SQL view. The R, D, and B items in the hierarchical view structure in Figure 1 are relational table names which also represent nodes in the hierarchical structure.

The hierarchical structure defined in Figure 1 above follows basic hierarchical principles supplied by the SQL Outer Join semantics. Nodes D and B can not exist without the higher level R node. But node R can exist without nodes D and B. Node D can exist without node B and visa versa because hierarchical pathways are independent of each other.

Static Hierarchical Structure Combining
Basic structure views like the one in Figure 1 above can be joined together hierarchically to create larger more powerful views that combine hierarchical structures. This is also performed by using the LEFT Outer Join and ON clause as shown in Figure 2 below. The only difference is that the view structures are being joined instead of isolated nodes. In this example, two additional basic views, IMS and XYZ, are used. They represent a physical IMS and XML data source modeled in the same way as the logical RDB view was defined in Figure 1 by using the LEFT Outer Join. In the IMS view, Segments I, M, and S represent nodes. In the XML view, Elements X, Y, and Z represent nodes. These common nodes allow seamless heterogeneous hierarchical data structure integration. Not being relational data, the non relational views contain additional specific physical meta information needed for their specific physical processing. They will also require an external process for retrieving their non relational data into rowsets when needed. These processes will be covered further later.

      Logical Data Structure

      CREATE VIEW TestView AS
      LEFT JOIN XYZ ON B.b=X.x

     Full Heterogeneous Structure

          /   \
        D    B
             /   \
           I      X
          / \     / \
        M  Y Z

  Figure 2: Logical Data View

The combined view named TestView in Figure 2 above consists of views RDB, IMS and XYZ. This makes TestView a heterogeneous view consisting of multiple data structure types defined seamlessly to ANSI SQL by using the LEFT Outer Join data modeling operation described above. When joining physical view structures together, the result is a logical structure. Logical structures can be joined with other logical or physical structures. Logical structures can also be directly processed by the ANSI SQL processor. This is because the logical view defined by TestView in Figure 2 with its corresponding relational rowset hierarchically maps to the combined and expanded LEFT Outer Join views RDB, IMS and XYZ. This supplies the natural hierarchical data modeling syntax and semantics needed for SQL to automatically perform hierarchically on the now homogeneous flattened rowset.

While the hierarchical data has been flattened in the rowset, it still automatically represents hierarchically preserved multiple variable length pathways using null filled data. The null data is used to fill out the variable length paths keeping the data aligned properly in the rowset. This allows hierarchical structures to be still operated on hierarchically by SQL. These views are temporarily materialized when processed, so they do not take up space when not used and avoid replicated data problems.

Global Hierarchical Data Filtering
As already mentioned, the newer ON clause is used instead of the WHERE clause for the purpose of specifying separate and specific uses of the join criteria. The WHERE clause operation is still responsible for data filtering. The difference between the ON clause and the WHERE clause is that the ON clause operation is local to its position in the structure affecting only pathways linked below it, while the WHERE clause filtering operation is global, operating on the entire structure. This means the entire hierarchical structure is processed as shown by the flow direction arrows in Figure 3 below. In Figure 3, node B is filtered directly by the WHERE clause. This can affect the data occurrences above and below node B removing data occurrences of nodes R and X. Notice also that being a hierarchical structure, node D a cousin relationship of node B, is also affected because if an R node data occurrence is filtered out, so is its descendant node D data occurrences. This hierarchical operation can cascade which can affect the entire global structure.


    Hierarchical Data Filtering Direction

    R        SELECT R.r, D.d, B.b, X.x
   ↓        FROM TestView
   D B ßWHERE B.b=5

  Figure 3: Global Hierarchical Data Filtering

The global hierarchical filtering operation in Figure 3 above is taken care of automatically in SQL because entire rows in rowsets are filtered out by the WHERE clause. When performing the more flexible and data preserving Outer Join ON clauses, only portions of rows are affected. These are the pathways linked below the ON clause being processed as mentioned above. The SQL ON clause operates while the hierarchical data structures are being built, while the WHERE clause operates  after the data structure is complete. In this way, the entire structure is available to operate on. Optimization does allow concurrent WHERE clause processing as long as the result is the same.

This data filtering example is a very simple case. When multiple data items are used in data filtering, the processing is still automatic and correct. It becomes more internally complex and more complicated to explain. For example, this can be seen in the filtering criteria of: WHERE B.b=5 OR D.d=4 which is different than WHERE B.b=5 AND D.d=4. The OR condition combines the results of each data filter. The AND condition combines the results of each filter when both sides find a match otherwise no data is selected. This operation occurs for each data occurrence. With this complex WHERE clause processing, it may be easier to grasp this operation as data qualification. Data filtering and data qualification are the same.

Hierarchical Data Processing Optimization
By supporting only hierarchical structured data which is necessary for standard SQL processing, a powerful generic semantic hierarchical optimization can be applied by middleware before the standard relational optimization is performed. This hierarchical optimization is useful because it will not be fully recognized by the standard relational optimization. This hierarchical optimization will dynamically remove all unnecessary pathways from a queried SQL hierarchical view or virtual heterogeneous view. Because of hierarchical data preservation principles, only referenced nodes including the root node and their intervening nodes need to be accessed. Since ON clause data references are part of the structure definition process, they are not considered query references for this optimization and do not influence optimization.

This hierarchical optimization is demonstrated in the query example in Figure 4 below where nodes D, X, Y, and Z are not specified on the SELECT list and are not accessed without changing the hierarchical semantics of the query. This hierarchical optimization also has a positive effect on the following relational optimization by enabling it to operate on a smaller structure making its operation easier to recognize optimizations.


       SELECT R.r, I.i, M.m 
       FROM TestView 
       WHERE S.s=5

   TestView   Optimized 
   Structure   Structure

      R               R
      / \                |
    D B              B
       /  \     è | 
     I     X           I 
    / \    / \          \
  M S  Y Z     M   S

  Figure 4: Hierarchical Optimization

Notice in Figure 4 above that node B was not referenced in the query, but required access because it is on the path to a referenced node I keeping the semantics of the structure accurate. Hierarchical optimization greatly reduces data access and relational data explosions without changing the hierarchical structure semantics and output. Standard Inner Joins can not use this optimization because they can not define hierarchical structures with their lack of data preservation. In addition, Inner Join use will destroy existing hierarchical structures. Most queries are still using the older Inner Join operation as their primary join operation. This means the Inner Join operation should not be used with hierarchical structures because it is missing the needed hierarchical processing principles.

Global Views and Their Usage
The additionally supplied hierarchical optimization described in Figure 4 above allows all views to be global views because there is no overhead for unused nodes in a dynamic view execution. This allows the use of larger views making much fewer views possible. This makes queries easier for the user to specify. This is because the specific view knowledge is not necessary for the user to specify efficient queries. This also reduces or eliminates join operations by the user because they are abstracted (hidden) in the global view.

Variable Processing and Output Data Structure Aggregation
SQL's powerful variable SELECT list operation allows its hierarchical optimization to be dynamically and automatically controlled from query to query by its flexible SELECT list. This also enables automatic dynamic tailoring of the necessary processing from query to query. A view invoked with a variable SELECT list can specify entirely different queries specifically tailored to the desired output as shown in Figure 5 below. This example is actually a continuation of the query shown in Figure 4 above to show its third and final state, this is its result structure. This automatic variable processing and dynamic output structure flexibility offers advanced new capabilities and uses such as dynamic publication support.

       SELECT R.r, I.i, M.m
       FROM TestView
       WHERE S.s=5

  Optimized    Result
   Structure   Structure

      R              R
       |                |
      B      è I
       |                | 
      I               M
     / \
   M S

   Figure 5: Variable Processing with Output Aggregation

In Figure 5 above, the hierarchical result structure is shown which contains only the dynamic SELECT list's specified nodes. This has the effect of dynamically controlling the desired output structure. Notice that the S node used in the WHERE clause was not output because it was not selected for output which is valid. Also note that the B node that was not referenced, but was necessary for internal database navigation, was not output as expected. This had the output result of closing the gap between nodes R and I. This is normal in hierarchical processing and is called node promotion which aggregates (condenses) the result nicely around the desired output data. This automatic reconnecting of pathways correctly preserves the remaining hierarchical semantics of the structure. Interestingly this is also standard in relational processing where it is known as projection produced naturally by the relational SELECT operation. So this mapping is both relationally and hierarchically accurate.

Multipath Query Data Qualification
Specifying multiple paths on a data qualification query requires nonlinear processing logic. These multipath queries using the SQL WHERE operation are incredibly powerful and extremely complex to process. They correlate references across pathways that interact with each other. This processing is hidden by SQL's automatic and inherent hierarchical structured data processing capability.

There are two different usages of a SQL multipath query data qualification. These are: 1) Selecting data from one pathway of the hierarchical data structure based on data from another pathway or: 2) WHERE clause searches comparing data on or across multiple pathways. These multipath queries use the naturally occurring structure semantics that exists between the concurrently processed pathways to solve this query. This significantly increases the number of different queries possible. This enables a new level of powerful hierarchical processing available to uncover new more deeper meaning in the data without requiring additional query syntax or knowledge of the structure for the user. The previously mentioned global view capability magnifies the usefulness of these multipath processing capabilities further by making unlimited combinations of pathways more available and easier to specify.

Dynamic Hierarchical Structure Combining
It is important to point out that SQL processing can perform all of its hierarchical processing capabilities dynamically. This means that SQL can dynamically and hierarchically join hierarchical structures in an ad hoc or interactive way (instead of limited to a static view). This is shown below in Figure 6 below where views RDB and IMS are dynamically joined at runtime to combine structures.


    SELECT B.b, M.m, S.s 

    Result Structure

      /  \
    M   S

    Figure 6: Dynamic Structure Joining

The example of node promotion in Figure 6 above also demonstrates node collection occurring. This can be seen when nodes M and S from separate pathways collect under the common B node. Notice that node promotion can occur across the entire virtual structure. In this case, node promotion occurs across a relational and IMS structure.

Extending SQL's Inherent Hierarchical Processing
To fully utilize SQL's inherent hierarchical processing correctly, the SQL must be specified hierarchically as described in this article. For SQL to control automatic I/O capabilities that use non relational access, SQL must be extended. This extension automatically uses the structure information supplied from the Left Outer Join hierarchical structure modeling and the access meta information supplied in new non relational views describe previously. For testing and proof of concept, this extended operation has been isolated and provided in a hierarchical processing enabler middleware prototype. It operates on top of ANSI SQL processors to support hierarchical data types such as IMS and XML to automatically and seamlessly enable this inherent hierarchical processing capability in the user's SQL processor. This extended capability supplied by the hierarchical processing enabler middleware is described in the next section.

The ANSI SQL Hierarchical Middleware
The hierarchical processing middleware prototype uses a standard ANSI SQL processor as the full multipath hierarchical processing engine. It is required to seamlessly power the hierarchical middleware prototype. The middleware consists of a Preprocessor, Post Processor, and Non Relational Data Access Backend components shown below in Figure 7 below. This middleware supports the new capabilities needed to extend SQL's natural hierarchical processing to non relational data such as XML and IMS including other legacy data such as VSAM and IDMS.

The Preprocessor automatically analyzes the LEFT Outer Join SQL source input to dynamically determine the virtual hierarchical structure to be processed. This also makes hierarchical structure-aware processing available to the other following phases of the middleware. The SQL input describing the data structure is hierarchically optimized to remove unneeded node pathways for the active query by analyzing the hierarchical structure and SELECT list as previously described. The modified optimized SQL is then submitted to the standard ANSI SQL Processor for full multipath level hierarchical processing.

The Real-time Non Relational Data Access Backend is used to retrieve non relational data and convert it into a hierarchically preserved relational rowset for the ANSI SQL Processor. It is invoked when a needed non relational data type is requested from the ANSI SQL Processor using an external table or UDF call. This external table or UDF mechanism will include pointers to the non relational processing information specified from the non relational hierarchical view and runtime optimization information. This enables a hierarchically preserved relational rowset to be returned efficiently by the backend which is hierarchically mapped into the LEFT Outer Join defined for this non relational view. This makes its SQL hierarchical processing seamless.

The Post Processor takes the completed relational result set from the ANSI SQL Processor removing the relationally introduced replicated data from the result and converts the result to the desired hierarchical structured output format. Duplicate and replicated data are treated differently. Duplicate data is meaningful and is preserved by uniquely tagging it on input; this also preserves the data order if necessary, such as for XML. The output structure format was determined from the structure information extracted in the Preprocessor. These three additional sections added for hierarchical support that make up the hierarchical middleware prototype are shown mapped around the ANSI SQL processor as shown Figure 7 below.

                                 Hierarchical Processing Middleware Design

                                             SQL Source
   Real-time Non                        
   Relational Data çè ANSI SQL Processor Performing Hierarchically
   Access Backend                     
                                          Post Processor
                                   XML Hierarchical Output

           Figure 7: Hierarchical Processing Middleware

The hierarchical processing middleware prototype laid out in Figure 7 produces hierarchically formatted XML output automatically which can be easily changed to produce any type of hierarchical data structure output. The hierarchical processing middleware has proven the powerful ability of operating directly on top of in place ANSI SQL processors at the customer's site to automatically support transparent hierarchical processing. This description of the hierarchical processing middleware should indicate how the Preprocessor, Real-time Non Relational Data Access Backend, and Post Processor functions can be moved into the ANSI SQL processor as an alternative implementation.

Benefits of Full  Multipath Hierarchical Processing
SQL's ability to naturally perform full multipath hierarchical processing has many new benefits listed below. This inherent automatic hierarchical processing allows the dynamic access of legacy data at a hierarchical level. With this capability and the beforehand knowledge of the entire query processing necessary derived from the preprocessor step described previously, extremely optimized dynamic data access is possible. This can be optimally applied to IMS data access by utilizing its database multiple positioning and dynamic SSA (Segment Search Argument) construction used for database navigation. This advanced hierarchical processing of IMS can be integrated with relational and tabular data as well as other hierarchical databases and data such as XML at a seamless hierarchical processing level. This can be performed on mainframes to supplement IMS data or it can be used to supplement Internet XML data with seamless and transparent access of IMS data. New features and capability include:

  • Improved SQL performance when processing IMS by using hierarchical optimization
  • Increases value of the data by utilizing the natural existing hierarchical structure semantics
  • Improves processing correctness and accuracy using principled hierarchical processing
  • Increases processing capabilities to include advanced hierarchical processing capabilities
  • Improved ease of use for hierarchical processing requiring no technical knowledge to use
  • Extends SQL navigationless structured data support to XML processing missing today

This article explained how SQL can now perform full hierarchical processing and what the advantages and new capabilities are and how they operate. The automatic utilizing of the natural hierarchical structure semantics can perform many new capabilities as described in this article. SQL hierarchical queries can now specify more powerful data value increasing queries that freely specify multiple pathways allowing more internally complex processing to be performed inherently. These multipath queries require special processing known as LCA logic which is performed automatically by SQL to control the range of hierarchical processing across pathways to keep the result meaningful and correct. See the Multipath LCA Logic sidebar for more information on this. The SQL hierarchical processing shown in this article can be tested using the hierarchical processing prototype available for online interactive testing at: www.adatinc.com/demo.html. The previous article published under this topic also included a set of powerful automatic hierarchical data value increasing capabilities.


Multipath Lowest Common Ancestor (LCA) Logic [Sidebar]

Multiple path processing requires logic involving the hierarchical distance between the referenced pathways data to determine the range of processing in order to keep the result meaningful. This range of processing is controlled by Lowest Common Ancestor (LCA) logic. It uses the LCA node between referenced pathways shown in Figure 6 to define the range of control to keep the result meaningful. Too high a level introduces meaningless data into the result, too low a level will miss meaningful data. This LCA processing logic is very complex and is not practical to be performed manually and procedurally. Fortunately, we found SQL's inherent hierarchical processing performs this LCA processing indicated below in  Figure Sidebar1 automatically as part of its relational Cartesian product processing when performing hierarchical data processing.

     SELECT R.r, M.m, D.d
     FROM TestView
     WHERE Y.y=1 AND Z.z=2

       Processed Structure

      R ß SELECT D.d WHERE Z.z=2 --- LCA Node =R 
     /  \
   D   B ß SELECT M.m WHERE Z.z=2 --- LCA Node = B
        / \
      I    X ß WHERE Y.y=2 and Z.z=1 --- LCA Node = X 
     / \   / \
   M S Y Z

   Figure Sidebar1: Lowest Common Ancestor (LCA) Processing

Figure Sidebar1 above shows SQL's different LCA uses. The WHERE clause in this example has a compound data filtering condition that spans two pathways on nodes Y and Z. This means that all combinations of the two conditions across the different paths need to be tested under the current LCA X node data occurrence until a match is found. The SELECT LCA operation involves the use of the SELECT operation with WHERE filtering as in SELECT D.d WHERE Z.z=2 taken from the example in Figure 6. The D and Z node references produce the LCA node of R. This operation will select all D.d data occurrences under the current LCA R node data occurrence when Z.z=2 is true. The SELECT operation can use a different LCA for each of its data items as in SELECT M.m, D.d WHERE Z.z=2. It produces LCA node B for SELECT data item M.m, and produces LCA node R for SELECT data item D.d. Current hierarchical querying of hierarchical data outside of SQL does not automatically support multipath LCA processing and it is too complicated to specify manually.

More Stories By Michael M David

Michael M. David is founder and CTO of Advanced Data Access Technologies, Inc. He has been a staff scientist and lead XML architect for NCR/Teradata and their representative to the SQLX Group. He has researched, designed and developed commercial query languages for heterogeneous hierarchical and relational databases for over twenty years. He has authored the book "Advanced ANSI SQL Data Modeling and Structure Processing" Published by Artech House Publishers and many papers and articles on database topics. His research and findings have shown that Hierarchical Data Processing is a subset of Relational Processing and how to utilize this advanced inherent capability in ANSI SQL. Additionally, his research has shown that advanced multipath (LCA) processing is also naturally supported and performed automatically in ANSI SQL, and advanced hierarchical processing operations are also possible. These advanced capabilities can be performed and explained in the ANSI SQL Transparent XML Hierarchical Processor at his site at: www.adatinc.com/demo.html.

@ThingsExpo Stories
Bert Loomis was a visionary. This general session will highlight how Bert Loomis and people like him inspire us to build great things with small inventions. In their general session at 19th Cloud Expo, Harold Hannon, Architect at IBM Bluemix, and Michael O'Neill, Strategic Business Development at Nvidia, discussed the accelerating pace of AI development and how IBM Cloud and NVIDIA are partnering to bring AI capabilities to "every day," on-demand. They also reviewed two "free infrastructure" pr...
With billions of sensors deployed worldwide, the amount of machine-generated data will soon exceed what our networks can handle. But consumers and businesses will expect seamless experiences and real-time responsiveness. What does this mean for IoT devices and the infrastructure that supports them? More of the data will need to be handled at - or closer to - the devices themselves.
New competitors, disruptive technologies, and growing expectations are pushing every business to both adopt and deliver new digital services. This ‘Digital Transformation’ demands rapid delivery and continuous iteration of new competitive services via multiple channels, which in turn demands new service delivery techniques – including DevOps. In this power panel at @DevOpsSummit 20th Cloud Expo, moderated by DevOps Conference Co-Chair Andi Mann, panelists will examine how DevOps helps to meet th...
NHK, Japan Broadcasting, will feature the upcoming @ThingsExpo Silicon Valley in a special 'Internet of Things' and smart technology documentary that will be filmed on the expo floor between November 3 to 5, 2015, in Santa Clara. NHK is the sole public TV network in Japan equivalent to the BBC in the UK and the largest in Asia with many award-winning science and technology programs. Japanese TV is producing a documentary about IoT and Smart technology and will be covering @ThingsExpo Silicon Val...
SYS-CON Events announced today that Juniper Networks (NYSE: JNPR), an industry leader in automated, scalable and secure networks, will exhibit at SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY. Juniper Networks challenges the status quo with products, solutions and services that transform the economics of networking. The company co-innovates with customers and partners to deliver automated, scalable and secure network...
Grape Up is a software company, specialized in cloud native application development and professional services related to Cloud Foundry PaaS. With five expert teams that operate in various sectors of the market across the USA and Europe, we work with a variety of customers from emerging startups to Fortune 1000 companies.
Financial Technology has become a topic of intense interest throughout the cloud developer and enterprise IT communities. Accordingly, attendees at the upcoming 20th Cloud Expo at the Javits Center in New York, June 6-8, 2017, will find fresh new content in a new track called FinTech.
SYS-CON Events announced today that Interoute, owner-operator of one of Europe's largest networks and a global cloud services platform, has been named “Bronze Sponsor” of SYS-CON's 20th Cloud Expo, which will take place on June 6-8, 2017 at the Javits Center in New York, New York. Interoute is the owner-operator of one of Europe's largest networks and a global cloud services platform which encompasses 12 data centers, 14 virtual data centers and 31 colocation centers, with connections to 195 add...
In his keynote at @ThingsExpo, Chris Matthieu, Director of IoT Engineering at Citrix and co-founder and CTO of Octoblu, focused on building an IoT platform and company. He provided a behind-the-scenes look at Octoblu’s platform, business, and pivots along the way (including the Citrix acquisition of Octoblu).
SYS-CON Events announced today that CollabNet, a global leader in enterprise software development, release automation and DevOps solutions, will be a Bronze Sponsor of SYS-CON's 20th International Cloud Expo®, taking place from June 6-8, 2017, at the Javits Center in New York City, NY. CollabNet offers a broad range of solutions with the mission of helping modern organizations deliver quality software at speed. The company’s latest innovation, the DevOps Lifecycle Manager (DLM), supports Value S...
NHK, Japan Broadcasting, will feature the upcoming @ThingsExpo Silicon Valley in a special 'Internet of Things' and smart technology documentary that will be filmed on the expo floor between November 3 to 5, 2015, in Santa Clara. NHK is the sole public TV network in Japan equivalent to the BBC in the UK and the largest in Asia with many award-winning science and technology programs. Japanese TV is producing a documentary about IoT and Smart technology and will be covering @ThingsExpo Silicon Val...
@GonzalezCarmen has been ranked the Number One Influencer and @ThingsExpo has been named the Number One Brand in the “M2M 2016: Top 100 Influencers and Brands” by Analytic. Onalytica analyzed tweets over the last 6 months mentioning the keywords M2M OR “Machine to Machine.” They then identified the top 100 most influential brands and individuals leading the discussion on Twitter.
The 20th International Cloud Expo has announced that its Call for Papers is open. Cloud Expo, to be held June 6-8, 2017, at the Javits Center in New York City, brings together Cloud Computing, Big Data, Internet of Things, DevOps, Containers, Microservices and WebRTC to one location. With cloud computing driving a higher percentage of enterprise IT budgets every year, it becomes increasingly important to plant your flag in this fast-expanding business opportunity. Submit your speaking proposal ...
The age of Digital Disruption is evolving into the next era – Digital Cohesion, an age in which applications securely self-assemble and deliver predictive services that continuously adapt to user behavior. Information from devices, sensors and applications around us will drive services seamlessly across mobile and fixed devices/infrastructure. This evolution is happening now in software defined services and secure networking. Four key drivers – Performance, Economics, Interoperability and Trust ...
The Internet of Things is clearly many things: data collection and analytics, wearables, Smart Grids and Smart Cities, the Industrial Internet, and more. Cool platforms like Arduino, Raspberry Pi, Intel's Galileo and Edison, and a diverse world of sensors are making the IoT a great toy box for developers in all these areas. In this Power Panel at @ThingsExpo, moderated by Conference Chair Roger Strukhoff, panelists discussed what things are the most important, which will have the most profound e...
Multiple data types are pouring into IoT deployments. Data is coming in small packages as well as enormous files and data streams of many sizes. Widespread use of mobile devices adds to the total. In this power panel at @ThingsExpo, moderated by Conference Chair Roger Strukhoff, panelists will look at the tools and environments that are being put to use in IoT deployments, as well as the team skills a modern enterprise IT shop needs to keep things running, get a handle on all this data, and deli...
SYS-CON Events announced today that Grape Up will exhibit at SYS-CON's 21st International Cloud Expo®, which will take place on Oct. 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. Grape Up is a software company specializing in cloud native application development and professional services related to Cloud Foundry PaaS. With five expert teams that operate in various sectors of the market across the U.S. and Europe, Grape Up works with a variety of customers from emergi...
@ThingsExpo has been named the Most Influential ‘Smart Cities - IIoT' Account and @BigDataExpo has been named fourteenth by Right Relevance (RR), which provides curated information and intelligence on approximately 50,000 topics. In addition, Right Relevance provides an Insights offering that combines the above Topics and Influencers information with real time conversations to provide actionable intelligence with visualizations to enable decision making. The Insights service is applicable to eve...
DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm.
Five years ago development was seen as a dead-end career, now it’s anything but – with an explosion in mobile and IoT initiatives increasing the demand for skilled engineers. But apart from having a ready supply of great coders, what constitutes true ‘DevOps Royalty’? It’ll be the ability to craft resilient architectures, supportability, security everywhere across the software lifecycle. In his keynote at @DevOpsSummit at 20th Cloud Expo, Jeffrey Scheaffer, GM and SVP, Continuous Delivery Busine...