As has been mentioned in past blog posts, there are security concerns with IoT systems. When discussing distributed ledger technology (DLT) we investigated how a blockchain approach could address the security concerns, but introduces system demands in terms of memory and computing power that do not appear practical for many of the simple IoT devices on the market today. Enter the permissioned blockchain; a network where only specific nodes are required to maintain the transaction ledger and determine which transactions are allowed. This addresses the problem with strict centralized control discussed in the first blog post in this series and the issue of memory demands discussed with a completely decentralized model in the second blog post.
What we have to say, what you want us to hear.
That’s how our blog works. It’s interactive. Let’s learn together.
One of the staple technical practices of agile software development is Continuous Integration (CI). A continuous integration environment provides fast feedback on the state of your code. In a typical configuration, the CI tool is configured with a "job" that monitors the source code repository for commits. When a commit is made, the job:
Welcome back to the Meet Our Team Q&A series. My name is Daniela Williams, Project Manager at ISE, and I’ll be asking ISE team members questions to help give insight into what makes us tick.
Today I'm interviewing Jon Opdahl, Software Engineer, and one of our Web App gurus.
One of the great leveling factors of cloud technology is the ability for small companies and individuals to do things that, not that long ago, would have required the support of a larger IT organization’s infrastructure, and doing them quickly and affordably. One of the most powerful yet simple of these technologies is ad hoc querying of data offered by Amazon Athena.