{"id":74,"date":"2016-10-28T17:11:27","date_gmt":"2016-10-28T17:11:27","guid":{"rendered":"http:\/\/67bricks.com\/blog\/?p=74"},"modified":"2016-10-28T17:11:27","modified_gmt":"2016-10-28T17:11:27","slug":"dev-meeting-intellij-idea-xquery-and-aws-lambda","status":"publish","type":"post","link":"https:\/\/blog.67bricks.com\/?p=74","title":{"rendered":"Dev meeting – IntelliJ IDEA XQuery, and AWS Lambda"},"content":{"rendered":"

Reece talked about the work that he’s been doing on an improved XQuery plugin for IntelliJ IDEA. This was inspired by some annoyances he was encountering with the existing XQuery plugin – although it’s generally good, it doesn’t have complete support for MarkLogic’s brand of XQuery, and it doesn’t correctly parse all XQuery.<\/p>\n

Reece’s implementation covers more areas of the XQuery language, has better error reporting for issues in your XQuery code, can check for file encoding issues, supports Find Usages, and has a number of other features.<\/p>\n

Reece is uploading his XQuery plugin to the Jetbrains repository this weekend, so it should soon be publicly available.<\/p>\n

Joe and Chris talked about the work that we’ve been doing with AWS Lambda. AWS Lambda is what Joe hoped that cloud computing would be all along. AWS EC2 is a server in the cloud, but not fundamentally different from having a server on your own network. However, AWS Lambda is effectively serverless – you upload a piece of code, and then it runs without you worrying about the infrastructure at all. However, the underlying infrastructure can make a difference to you, in terms of the latency of invoking it when it hasn’t recently been called.<\/p>\n

We are using AWS Lambda as part of a filter for an Amazon SQS queue. We’re testing it using an SBT plugin – SBTMocha. The challenges with testing it are:<\/p>\n