Data Serving or Serving Layer

Share this topic

Data Serving or Serving Layer

From the book I Am Datapedia!, published here free by the author.

Part of I Am Datapedia!

Data Serving is also known as the Serving Layer and it has been there since its inception but as technologies have matured, many new channels have been introduced to support this layer.

‘Serving Layer is last component of the Lambda Architecture.’

Diagram

Description automatically generatedLambda Architecture has been explained in separate topic, so we won’t go into details of it but referring to it, as mentioned above, it is the last layer which is exposed to End Users for reporting purposes. This Layer is, if not all the time but majorly designed based on business requirements.

We all know OLTP systems are not meant to be exposed for reporting purposes. In the current era, for reporting, there are many data stores available i.e., Data Warehouse, OLAP, Data Lake, NoSQL, Semantic layers but ideally Semantic Layer should be treated as Serving Layer.

To be more specific

  • If Serving Layer is designed for specific business requirement then Semantic Layer is last layer.
  • If the Serving Layer is designed for generic use then it can be Data Warehouse, OLAP, Data Lake, NoSQL etc.

Technologies to connect to Serving Layer

  • JDBC Connector: We know every system has at least Java, so this is the most generic way to connect to any system. Via JDBC, using other system’s Host Name, IP, Username and Password, it can connect easily.
  • ODBC Connector: ODBC is supported by Oracle and recently it’s also available, if not all, on most of the systems. Same as JDBC, using other system’s Host Name, IP, Username and Password, it can connect easily.
  • Native Driver: Host systems normally create internal drivers to connect to other systems. Please note, these internal drives are also made by using JDBC and OBDC connectors. The difference is, Native Driver can also include some security parameters.
  • API: Just like Native Drivers, APIs also use JDBC and OBDC connectors as back ends along with the inclusion of security parameters. Major difference between Native Drivers and API are, Native Drivers are used to connect databases from source with target whereas APIs are used to expose data on Online portals.

Express your reaction

Your Take on This Insight?

Share how this content resonates with you.

Comment
Useful0
Insightful0
Actionable0
Thought-provoking0
Inspiring0

0 reactionsSign in to react or comment

Comments (0)

No comments yet.

    Free account

    You can read every topic without one. A free account lets you react to this topic, comment under it and search the Knowledge Hub. Reacting and commenting need a confirmed e-mail address.