In a previous post, we discussed the basics of GraphQL and how it can be a great REST API alternative. In this one, weโll see how AppSync can be more than just a great API alternative โ it gives you a soft landing into the world of GraphQL.
Recall our Game API example? Letโs start with the basic type of a game. Follow along and we can implement a simple schema in AppSync together….
Keyhole Software is excited to once again be a Gold sponsor of the Nebraska.Code() Conference.
The 2018 conference is Wednesday through Friday, June 6th-8th with excellent technical talks on the schedule. Wednesday will consist of half and full-day workshops, while Thursday and Friday will consist of 100+ one-hour breakout sessions. This year, the conference has moved to the Mid-America Center in Council Bluffs, IA, right across the river from Omaha, NE.
Sessions To Watch
Numerous conference sessions will be led by Keyhole Software team members on a myriad of technical topics. Make sure to attend the following Keyhole sessions when setting your own personal conference calendar…
The basic premise of data transfer and involves requesting and receiving lists. This is simplistic, but it gets to the root of why weโve developed the technologies and best practices to pass data using web services. RESTful APIs have grown to serve the needs of numerous individuals, startups, and enterprise companies across the world. They are useful, productive, and the concepts surrounding them are relatively standardized. If you donโt know how to create one, you can quickly find information building a great API that can grow to fit your needs. Thatโs when things get complicatedโฆ
If you start digging into REST, youโll realize thereโs quite a bit more to throwing lists. There are common threads that many people encounter when developing an API, and you begin to encounter many of the same questions so many others have before, such as: How strictly should you adhere to the principles of REST? How should you handle versioning? Should you bother? How do you want to structure your objects? Are users able to easily figure out what API endpoints are available and how they should be used?
There are many ways approach these. It boils down to communicating the structures that a given endpoint will return or accept. The cascade of questions that results from the choices made here will ripple through from the back-end to the client. The secondary issue is that these questions and choices are not at all uncommon. There are answers to these that follow Best Practices. But there is still plenty of ambiguity involved when attempting to build a flexible API that works well. These are the Commonly Tolerated Situations.
If you hadnโt already guessed, there is a solution that frees us from the dogma of REST and allows us to solve all these issues in a declarative, powerful, and fun way. That solution is GraphQL. In this blog, Iโll provide an introduction to the GraphQL specification with code examples…
Machine learning is a hot topic these days because the biggest tech companies are focused on taking this technology to a new level. For instance, to help develop autonomous driving cars, better interaction between you and your house with products like the Amazon Echo.
Machine learning is a core sub-area of artificial intelligence. Machine learning enables computers to self-learn without being explicitly programmed. As new data comes available, the computer has the ability to learn, grow, change, and develop itself to make better decision in the future. This technology will help reduce the workload and possible incorrect diagnoses when radiologist read films, reducing the amount of accidents on our highways caused by human error, possible reduction of inappropriate message / images / videos from bullying on social network sites.
This article will touch on one of the many Artificial Intelligence APIโs that Microsoft has built for public consumption. We will specifically focus on the step-by-step process of uploading a picture, passing that picture onto the Microsoft Cognitive Services – Computer Vision API, and retrieving different attributes about that image. This is an aspect of AI technology that companies like Facebook & Google are using to try to stop bullying and other issue within social networking. Let’s get started…
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….