There is nothing new in microservices. Many applications have already been designed and implemented as such for a long time. Microservices is just a new term that describes a style of software systems that have certain characteristics and follow certain principles.
When I first started migrating from IBM Message Broker to an open source solution, I was a bit overwhelmed with the seemingly daunting task. I quickly discovered that Apache Camel was a good replacement and started developing my first route.
DZone's 2014 Guide to Big Data was produced to help you discover emerging information about the Big Data landscape and learn about how the shifting needs of data scientists and developers are influencing new tools and technologies.
Make sure you didn't miss anything with this list of the Best of the Week in the Enterprise Integration Zone (Sept 12 to Sept 18). How to write a custom SAML SSO assigner signer, Java EE book uncensored, Java APIs, RESTful web services, and scaling RESTful microservice architecture.
In this post I would like to put my two cents in and talk about RESTful web services. First of all I don't intend to discuss the history of RESTful services. Neither this is a tutorial about implementing RESTful web services.
Moving from a traditional monolithic architecture to a microservices approach is an enormous change for any organization, and fraught with multiple challenges. I'll cover a number of these here, including an emphasis on a microservices approach that isn't to be taken lightly.
Make sure you didn't miss anything with this list of the Best of the Week in the Enterprise Integration Zone (Sept 5 to Sept 12). This week's topics include REST API security, SOA principles, REST services with Spring, designing RESTful APIs, and getting started with JHipster.
The benefits of applying the principles of SOA when catering to the IT needs of your organization are clear in a business-driven, vendor-neutral architecture. It considers all requirements from the perspective of the business process and delivers implementations in order to automate the same.
Since Camel version 2.10 there is support for CDI (JSR-299) and DI (JSR-330). This offers new opportunities to develop and deploy Apache Camel projects in Java EE containers but also in standalone Java SE or CDI containers. Time to try it out and get familiar with it.
Like the graphene example at the beginning of the post, thin stories have remarkable properties far beyond the fact that they are just "thin". The value gained by learning how to split Stories effectively is enormous owing to the flexibility it provides by deferring decisions as long as possible and the removal of the need to estimate at a granular level.
Make sure you didn't miss anything with this list of the Best of the Week in the Enterprise Integration Zone (August 14 to August 21). This weeks topics include microservices and enterprise architecture, REST API security, Spring Boot with Git and Gradle, jsonpickle and Python, and lambda architecture.
The recent release of the Anypoint Connector for .NET opens up many opportunities for plugging into .NET based rules engines. Since the .NET Connector allows developers to call out to native .NET code, these rules engines can be easily integrated as a result.
JDK 9 features have been announced, and we want to know what you think about them! Are these features something you've been waiting for, or are you a bit underwhelmed? Do some of these proposals seem to go against improvements that you want? Post a comment and tell us!
In this post, I'd like to summarize the key principles of the Lambda architecture, focus more in the underlying design principles and less in the choice of implementation technologies, which I may have a different favors from Nathan.