After a long day, there is no place like home. Home represents comfort, relaxation, and being surrounded by loved ones. The document expresses joy and contentment with returning home after being away.
A Lap Around Developer Awesomeness in Splunk 6.3Glenn Block
?
The document discusses new developer features in Splunk 6.3, including the HTTP Event Collector for sending events directly to Splunk, custom alert actions for integrating with external systems, and improved custom search commands. It also demonstrates some of these features, such as sending events using the HTTP Event Collector and creating custom alert actions. Additional sessions are recommended for learning more about modular inputs, reference apps, and other developer tools in Splunk.
Splunk, a smorgasboard for developing big data solutions Glenn Block
?
This document discusses developing big data solutions using Splunk. It provides an overview of Splunk's capabilities for collecting, analyzing and visualizing machine data from various sources. It also describes Splunk's developer platform for building custom apps and extensions, searching data, and sending data to Splunk from various platforms and languages. The document directs readers to Splunk's online resources for tutorials, code samples and support.
This document discusses Edge, an open source module for Node.js that allows Node.js applications to leverage .NET capabilities by calling .NET libraries and services. Edge allows Node.js code to call into .NET code and .NET code to call back into Node.js code in a non-blocking way within the same process. It supports multiple .NET languages like C#, F# and Powershell. Edge enables access to Windows capabilities like the event log, registry, performance counters and more. It is extensible via additional Edge modules for SQL, Powershell, and other languages/platforms. The document provides code examples and links to the Edge GitHub repository and additional Edge modules.
My Hypermedia and ASP.NET Web API talk from Oredev
RestBugs sample (for of Howard Dierking's repo) using templates: https://github.com/glennblock/RestBugs
Collection+Json: https://github.com/glennblock/collectionjson
Node.js is gaining significant interest for building scalable web applications. Several large companies like LinkedIn, eBay, and Walmart are using Node.js in production for its performance and scalability benefits when handling input/output bound workloads. Node.js allows non-blocking event-driven programming which helps simplify building applications that interact with services, databases, and handle many concurrent connections using little memory. Its large ecosystem of open-source modules also helps speed up development.
Building Systems with REST discusses how HTTP differs from RPC and how it enables intermediaries through its use of resources and representations. The document outlines how HTTP is a transfer protocol rather than a transport protocol and how following its semantics allows functionality through firewalls. It advocates for building systems according to REST principles by decoupling concerns and focusing on resources, representations, and hypermedia.
The document discusses hypermedia and how it can be used to help clients navigate an API. It defines hypermedia as control information provided by an API to clients through links and forms. These controls allow clients to identify available actions and activate them to move between states. The document provides an example of how this could work in a issue tracking API, allowing clients to retrieve, open, close and search for issues. It also recommends implementing hypermedia with ASP.NET Web API and provides additional resources for further information.
Deploying web apis on core clr to dockerGlenn Block
?
This document provides an overview of .NET Core, ASP.NET 5, and Docker. It introduces .NET Core as a cross-platform version of .NET that allows side-by-side app versioning. ASP.NET 5 is the new version of ASP.NET that is modular and runs on .NET Core, supporting Web UI and APIs. Docker is a tool that allows packaging apps and dependencies into standardized containers to enable portable development environments. The document provides links for additional information on these topics and an example contact API project using these technologies on GitHub.
In this presentation, Glenn Block discusses how Splunk uses node.js in its products. Surprising, huh? Node shows up in various islands of Splunk¡¯s architecture from the Splunk Server, to middleware components, and finally in the SDKs. The focus here is on real world usage, the specific places where we chose to use node and why, as well as the team¡¯s experiences deploying it into production. What¡¯s Splunk? It¡¯s a product designed for data ingest and query for massive realtime data work loads. It is used by some of the largest organizations in the world.
Node.js is gaining significant interest for building scalable web applications. Several large companies like LinkedIn, eBay, and Walmart are using Node.js in production for its performance and scalability benefits when handling input/output bound workloads. Node.js allows non-blocking event-driven programming which helps simplify building applications that interact with services, databases, and handle many concurrent connections using little memory. Its large ecosystem of open-source modules also helps speed up development.
Building Systems with REST discusses how HTTP differs from RPC and how it enables intermediaries through its use of resources and representations. The document outlines how HTTP is a transfer protocol rather than a transport protocol and how following its semantics allows functionality through firewalls. It advocates for building systems according to REST principles by decoupling concerns and focusing on resources, representations, and hypermedia.
The document discusses hypermedia and how it can be used to help clients navigate an API. It defines hypermedia as control information provided by an API to clients through links and forms. These controls allow clients to identify available actions and activate them to move between states. The document provides an example of how this could work in a issue tracking API, allowing clients to retrieve, open, close and search for issues. It also recommends implementing hypermedia with ASP.NET Web API and provides additional resources for further information.
Deploying web apis on core clr to dockerGlenn Block
?
This document provides an overview of .NET Core, ASP.NET 5, and Docker. It introduces .NET Core as a cross-platform version of .NET that allows side-by-side app versioning. ASP.NET 5 is the new version of ASP.NET that is modular and runs on .NET Core, supporting Web UI and APIs. Docker is a tool that allows packaging apps and dependencies into standardized containers to enable portable development environments. The document provides links for additional information on these topics and an example contact API project using these technologies on GitHub.
In this presentation, Glenn Block discusses how Splunk uses node.js in its products. Surprising, huh? Node shows up in various islands of Splunk¡¯s architecture from the Splunk Server, to middleware components, and finally in the SDKs. The focus here is on real world usage, the specific places where we chose to use node and why, as well as the team¡¯s experiences deploying it into production. What¡¯s Splunk? It¡¯s a product designed for data ingest and query for massive realtime data work loads. It is used by some of the largest organizations in the world.