This article is part of a series of articles about modern tooling and techniques for building distributed systems in DotNet.
In our first article, we saw how easy it was to set up a full ELK stack by leveraging pre-built containers. In this blog, I show how to leverage ELK in a .NET application and aggregate our logs into a single place. You will see just how simple it is to start getting some insights into your application. Let’s get started…
This is going to be the first post in a series of articles about modern tooling and techniques for building distributed systems. In this post, I will show how to use Docker for Windows to set up an ELK (Elasticsearch, Kibana, Logstash) server that we are going to use in future articles. The series is particularly geared toward traditional .NET developers. Let’s get started…
With the explosion of the internet of things (IoT), many companies are competing to create the best smart home ecosystem for consumers.
Amazon Echo, for instance, is a robust system that allows the user to interact with their smart devices via voice command. Alexa is the application that the Echo communicates with, essentially the brain of the Amazon Echo. It controls how your Amazon Echo communicates with your other smart devices and services. It can sync with a variety of smart devices including switches, thermostats, garage doors, sprinklers, door locks, music streamers, news outlets, and more. It also allows the third-party companies to create custom skills which are then accessible through the Amazon Echo.
In this blog I will discuss the Amazon Echo and its Alexa application. We will go through the process to create a custom Alexa skill about the Keyhole blog, paying particular attention to keywords you’ll need to understand when you create your own Skill. From there, we’ll show how to test a Skill via simulators and deploy it to your Amazon Echo.
If you are heading down the path of a Microservices style of architecture, one tenant you will need to embrace is automation. Many moving parts are introduced with this style of architecture. If successful, your environment will have a plethora of service APIs available that the enterprise can consume for application development and integration.
This means that there must be a way that available API documentation can be discovered. API information needs to be effectively communicated throughout the enterprise that shows where APIs are used, how often APIs are used, and when APIs change. Not having this type of monitoring in place will hinder and possibly cripple the agility benefits that a Microservice style of architecture can bring to the enterprise.
This blog will describe how Swagger/OpenAPI documentation can be applied to a Spring Boot implementation. We will show how API documentation and monitoring can be automatically published to an API documentation portal.
As an example, we introduce a reference Spring Boot API CRUD application (using Spring MVC/Data with Spring Fox) and set up the automatic publishing of API documentation and statistics to documentation portal GrokOla. In the example, we introduce two open source utilities to help and allow published APIs the ability to be searched and notify users when changed….
We’re excited to announce the release of a new, free white paper on the Microservices software architecture style.
Microservices is an architectural pattern gaining steam in the development community. A Microservices architecture addresses problems that modern enterprises often face, including responding to market demands, handling spikes in traffic, and being tolerant to failure. These benefits are achieved by functionally decomposing a business’ domain into microservices, services that handle only a single responsibility.
In this white paper, we discuss how Microservices came to be, contrasting architecture patterns, features of a Microservices architecture, established patterns, how to get started with Microservices, and suggestions for Microservices adoption.
Download the free Keyhole Software white paper today!