On a recent client project, our team was tasked with setting-up local development environments for a new Node.js-based microservices system that would eventually be deployed on Red Hat’s OpenShift platform.
We have found a good approach by making use of the MiniShift project and we have put together a demo with some accompanying documentation about what we’ve learnt.
You can jump straight into the code and docs, or you can stick around for more on the journey that led us to this point.
Hi! I’m Matteo, and I’m a code pirate at nearForm. I’ve just been nominated to the Node.js Core Technical Committee, and I do a lot of Open Source, both in my daily job and for fun. I do not classify myself as a very productive person, and in fact I can get easily distracted. Whenever I’m “in the zone”, I can barely speak as I try to keep hold of all the context I am working on. The net result is that I am not very productive in an office environment, and I work from home when I am not travelling, more on that later.
James M Snell, Colin Ihrig
Node 8 is a major release with a lot of exciting features and is is the next release line to enter Long Term Support (LTS). In this post, we want to give you a quick summary of what it includes. For a more extensive description, please see our announcement post.
This is the fifth post in my microservices series and follows on from the previous articles:
- Microservices series #1: microservices are software components that work
- Microservices series #2: the state of enterprise software – analytical evidence
- Microservices series #3: enterprise software development is broken – the qualitative and quantitative evidence
- Microservices series #4: beware the monolith
In today’s post, I take a look at best practices, and ask whether the concept really is ‘best’.