On 22nd September, the MicroProfile group held a panel event in San Francisco to discuss the current and future situation. Albeit not being part of JavaOne, the fact that it coincided in time and city made it easy for conference-goers to attend. The panel included representatives from RedHat, Payara, SouJava, Tomitribe, IBM, and the LJC, and speculated about the shape of future Java development.
Microsoft announced the first release of Project Bletchley, which is Microsoft's approach to building a cloud-based enterprise consortium blockchain ecosystem. This first release is primarily focused on a questionnaire based automated deployment along with roadmap details for the Cryptlet middleware tier.
Refactoring helps to move towards cleaner code that is easier to understand and maintain. It takes practice and experience to recognise code smells: symptoms of bad design which indicate deeper problems in the code. Tools can be helpful to refactor in small steps and prevent breaking the code.
People stopped seeing the need to define the architecture or do software design due to incorrect interpretation of the agile manifesto, argued Simon Brown. Many software developers don’t seem to have a sufficient toolbox of practices and the software industry lacks a common vocabulary for architecture. A good architecture enables agility with just enough up front design to create firm foundations.
Derek Ashmore details the different types of monoliths he has come across with a view to subsequently describing how they may be broken down into more manageable components/microservices.
Yahoo! has made available Pulsar, their publish-subscribe messaging platform used internally in production by several services.
Moving towards microservices means moving towards distributed systems where you have to deal with latency, authorization and authentication, and messages that do not arrive, argues Sander Hoogendoorn. With microservices you can break down large systems into smaller components to regain control over the architecture.
Almost five years in the making, Dropwizard's Java RESTful Web Service framework version 1.0.0 offers a host of new features including Java 8, Http/2 and Scala support, and the latest versions of supporting Java APIs.
One of the hardest problem when creating and developing microservices for an enterprise is their data. Analysing the business domain using Domain-Driven Design (DDD) and reason about what your data represents will help in achieving a microservices architecture, Christian Posta claims in one of a series of blog posts about microservices implementations.
Spring Boot 1.4 and Dropwizard 1.0 were both released at the end of July, using fat JARs. As adoption of such frameworks and microservices increases, fat JARs are becoming a more common deployment mechanism. Earlier HubSpot cited issues where Fat JARs deployments experienced problems with the maven-shade-plugin, and efficiency problems when packaging 100,000 tiny files as a JAR.
IBM recently announced a cloud service for organizations looking to adopt blockchain technologies. The service is underpinned by the IBM LinuxONE platform which hosts a series of underlying services for blockchain processing. IBM is positioning this platform for organizations in regulated industries which require secure environments for testing and running blockchain projects.
In the webcast entitled "What's Better Than Microservices? Serverless Microservices," Alan Williams (Autodesk), Asha Chakrabarty (Amazon) and Alan Ho (Apigee) discuss the architecture of a serverless microservice built with lambda functions with Apigee end-points running on AWS.
Increasingly, software developers have the ability to not only maintain and architect code, but extend their expertise to providing direction to the business. By using domain driven design, developers can discover customer behaviors and recommend practices that change the nature of the business.
We live in a distributed world, but that doesn’t mean we have to tackle every single problem that comes along with that. We only need to tackle those that really need to be solved; develop a sense of where value lies in your business and where it’s reasonable to take risks. This will make building distributed systems much easier, Camille Fournier claimed, when interviewed by Stefan Tilkov.
At QCon New York 2016, Etsy software engineer Stefanie Schirmer told how her company successfully transitioned to an API-first architecture that supports multiple devices, addresses server-side performance problems, and was quickly adopted by development teams.