About the Author
David Pitt

David Pitt

Twitter

David Pitt is a Sr. Solutions Architect and Managing Partner of Keyhole Software with nearly 25 years IT experience. Recent projects involve speaking, writing, and training developers in enterprise JavaScript​/single-page application​ development best practices​, as well as the development of GrokOla, the Q&A-based wiki software​ for development teams.​

My Reaction To React

David Pitt JavaScript, React, Technology Snapshot, Tutorial 2 Comments

We at Keyhole have been helping our clients adopt JavaScript-based single-page applications for over five years. We have been impressed with the adoption and advancement of the ever-changing JavaScript ecosystem.

Server side, headless JavaScript (Node.js) has led to good tooling and packaging options along with server side remaining available. Additionally, the new ECMA6 standard has turned JavaScript into a viable general purpose programming language, that is arguably, on the same plane as C# or Java. It certainly has a large number of available frameworks and tooling options.

React differs from the other frameworks I’ve worked with in a handful of ways. In this blog, I will show tangible examples of React’s unique features and capabilities, particularly how it handles HTML-based Components.



Auto-Publishing & Monitoring APIs With Spring Boot

David Pitt Keyhole Creations, Microservices, Technology Snapshot, Tutorial Leave a Comment

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….



Implementing A Bounded Context

David Pitt Microservices 4 Comments

Arguably one of the most difficult Microservices patterns to apply and implement is the bounded context. The bounded context concept originated in Domain-Driven Design (DDD) circles. It promotes an object-model-first approach to a service, defining a data model that a service is responsible for and is “bound to.” In other words, the service owns this data and is responsible for …



Trouble Maker

Failure As A Use Case: Introducing Trouble Maker

David Pitt Keyhole Creations, Microservices, Programming, Technology Snapshot, Testing Leave a Comment

For too many reasons to count, it is nearly a guarantee that your production software systems will fail in some way. We attempt to QA our software, which essentially tests application “business” function, but it’s very difficult to test what can go wrong in an actual production environment. Things like memory utilization and leaks, port exhaustion, connection pool timeouts, too …



Partitioning SPA Resources and API Implementations in Separate WAR Components

David Pitt HTML5, Java, JavaScript, Opinion Leave a Comment

Single Page Applications are quickly gaining traction as a way to implement rich, robust, and mobile friendly web-based applications. Essentially, this requires a shift in application architecture where the entire application user interface is implemented using JavaScript and the server side code supplies a RESTful, JSON-based API for  server side application logic and data access. This model is shown below: …