Email subscribers / beta users get this a week or two early so if you can't wait, then sign up to our beta!
We’re pleased to announce that Brian Luff will be joining Senseye in an advisory capacity. Brian brings with him a wealth of experience having set up and grown a number of successful companies in the defence and aerospace sectors. He is aware of the commercial and market challenges that lie ahead and will help us develop a sustainable strategy to grow Senseye to become a market leader in the growing Internet of Things space. Being well connected across UK and international businesses, he will also bring his extensive network to bear. Brian is currently the Chairman of the UK subsidiary of Critical Software – a rapidly growing specialist software services company. We look forward to working with Brian on our journey to success.
Are you serious?
If someone told me 12 months ago that we’d be talking to farmers and walking through winter wheat fields I’d have told them they were crazy. The only thing farmers hate more than technology is talking to people trying to sell them technology, right?
This post concentrates on farming, or smart agriculture to be precise, but I don’t think I’m going out on a limb to suggest that these thoughts will no doubt repeat themselves in other industries (in-fact I’m struggling to think of any exceptions and am open to suggestions!). There is so much feverish discussion on how the Internet of Things will change everything (from clever refrigerators to sensored-up pigs); having as much or more impact as when we started to adopt the Internet into our day-to-day lives. It’s easy to get caught up in the excitement and hype (after all, the IoT is currently at the top of the Gartner's hype cycle) while not considering where we actually are and where we need to get to.
Our simple predictive analytics product, Sensight, is using a microservice architecture partly linked together with RESTful HTTP interfaces. It’s common now to see applications, websites, services and databases being loosely coupled in this way to aid maintainability and allow for better technology selection. This communication between API consumers and providers forms a functional contract; with the consumer expecting the provider to expose a consistent interface and maintain a number of things such as endpoints, query parameters, expected request bodies, allowed verbs, returned status codes and data representations. If the API changes, consumers may no longer be able to exploit the API or could find their application behaving in unexpected and bizarre ways. Like all good applications then, it’s critical that web APIs are well-tested to ensure that they function correctly and deliver a consistent interface for consumers.