- dealing with a whole bunch of endpoints in a typical application
- performing multiple roundtrips to the server for multiple resources in order to get data for a single page of the UI
- getting the request parameters right
- dealing with api versions – coupling between the client and the responses from the server
- over-fetching of information that is not needed
It’s now easier and cheaper to build pub/sub architectures with AWS.
For any of you Node.js folks out there already using serverless frameworks like ‘The Serverless Framework‘ , you’ll definitely want to checkout the really cool Claudia.js framework…
A couple of months ago we reported on Google’s acquisition of our favorite natural language processing (NLP) platform – API.AI.
Well since then it seems that API.AI have gone from strength to strength in so many new areas, …so much so in fact that they have decided to rebrand in order to better describe their current more diverse platform which includes an analytics tools and 33 prebuilt agents
Full press release here
Need a good messaging queue but don’t want to tie yourself to AWS’s SNS/SQS or Google’s Pub Sub ? Then IronMQ from Iron.io might be the solution for you… Highly available and persistent by design, IronMQ is an industrial strength and cloud native messaging queue which helps to tie your distributed systems together.
Offering unicast and multicast ‘push’ queues , ‘pull’ queues , guaranteed ordering , error queues, super easy to use language libraries including Ruby, Python, PHP, .NET and Node.js – IronMQ has it all.
We love Serverless technology here at Boyle Software – being able to build applications comprised of microservices, which run in response to events, auto-scaling, being able to focus on the business problems rather than infrastructure, lower costs etc – the list goes on.
Reminding me slightly of early Java web applications that existed before Apache Struts came along, similarly, Node,js applications developed by different teams and developers can vary widely in terms of structure and style.
From wildly different index.js files to custom express() and mvc patterns it can be difficult moving from one project to another and learning the new style imposed.
I was always a bit skeptical of the whole Cloud IDE thing, that was until recently when I gave Cloud9 a shot. I must admit, I was surprised when I read the Engineering Orientation wiki page for one of our clients, Vroom.com, as it suggested I create a Cloud9 IDE account as part of my project setup. What??
I figured I’d give it a try…