It has been a while since my last post. In my defence, Paremus have been incredibly busy on a number fronts.
Adoption of OSGi through 2013 / 2014 has been significant and continues to accelerate. While interest in ‘MicroServices’ and Container Technologies like Docker are undeniable; Paremus are increasingly finding that mature organisations realise that complexity, technical debt and maintenance costs can only be addressed if the in-house Java applications are either mothballed or reengineered. Assuming the business functionality is still required, the former simply ignores the problem. In contrast the latter, to avoid repeating the same mistakes, requires structural Modularity; for which the only industry standard is OSGi.
For organizations that appreciate this, and aspire to their own internal distributed Cloud runtime; then BNDTools and the Paremus Service Fabric are no longer a curiosity but a increasingly compelling Build / Release / Run / proposition.
My intent over the next few posts will be to revisit Service Fabric concepts and capabilities and compare and contrast these against current IT industry fashions.
Something along the lines of…
- An introduction to Service Fabric 1.12 and our ‘Entire’ management framework. A really cool demonstration of the use of OSGi RSA and DTO specifications – crafted by some of the Grand Masters of the Art 🙂
- A look at the Service Fabric with respect to the Microservices trend: (well the name fits!)
- Also what about the Service Fabric and non OSGi artefacts? What about Docker? How is the Service Fabric different to solutions like Mesos and Kubernetes?
And then we’ll get onto the interesting stuff…