Welcome to NodeCrunch, the nearForm blog. This is where we share information of all kinds, from Node.js news to new tool releases to our latest thinking on developing company values. We love to chat, so do post your comments below.
If you haven’t watched the videos from our recent Microservices Day New York event, I recommend that you do. In addition to the superb individual talks by those solving real-world problems, the panel sessions highlight common challenges and approaches.
One of my favourites is the talk given by Jason Melo, from ADP about The Asynchronous Enterprise.
ADP is responsible for processing the payroll of almost 90% of professionals in the US and is the largest payroll and HR provider globally.
Jason is VP for Product Development at Lifion, which is effectively a startup incubated by ADP with the mission of disrupting ADP from the inside out. His talk is very focused on organisational challenges and how technology is only one component of using microservices as a pattern. A critical aspect of that is how governance and process foster velocity and innovation at scale.
The resulting tech story is impressive! 160+ microservices, 4000 running containers, 700+ EC2 hosts and 45k Kafka messages per second.
Thanks to Nigel Hanlon from OpenApp for taking the time to write this blog post. Nigel has worked with Node.js to provide some amazing developments with the Air Ambulance Service.
It was Christmas six years ago when the spec for a new project came across my desk. Inside, it detailed a new emergency service that was to go live in the coming months and their requirements for a new mapping system. Little did I realise the gravity of what I was embarking on and how today, I would rank it as one of my most important and interesting projects.
In the above posts (particularly post two), I identified and discussed what I believe are the key problems with custom enterprise software development. Today, I take a closer look at one of those problems: the monolithic architecture.