For the last several years, microservices has been an important trend in IT architecture. Technology consulting firm Thoughtworks has declared that “a microservices architecture as programming model” is one of the four rising trends of 2017, whereas others in the press are expressing their endorsement of microservices––making architects and IT executives feel a fear of missing out on the next exciting trend.
Microservices is one of the hottest buzzwords in tech right now. But just because something is buzzy doesn’t mean we cannot be pragmatic about it. It is important to think about how you can get the hype to work in your organization.
The consumer landscape continues to rapidly evolve, but it is clear that a consistent brand experience across all purchasing channels is no longer just expected, it is required. This is not just true for retail, but for industries across the spectrum – from manufacturing and CPG to finance and high-tech.
The importance of a consistent, connected brand experience is demonstrated in MuleSoft’s recent Connected Consumer Report, which found that over half of consumers experience an inconsistent,
A recent trip to Istanbul got me thinking about enterprise IT architecture. Seriously! If you’ve ever been to Istanbul, you’ll know that it’s a fast-growing, vibrant, and dynamic city. Unfortunately, the roads can also be very congested at times, taking hours to get from one side of the megacity to the other.
The worst is when you’re stuck in a taxi without a safety belt, no AC, it’s the summer, and you’re trying to cross the Bosphorus (millions of people cross the grand total of two bridges across the two sides of the river every day).
Multi-channel retailing has multiplied the opportunities for Retailers to do more business with their customers by going beyond their bricks and mortar in order to sell over the web, through smart phones and tablets, perhaps soon on smart TVs and through Partners and Resellers.
I wish to help you see how you can achieve a significant increase in revenue by adopting an IT architecture that will bring you a rapid return on investment and help put your retail business right at the helm of a fundamental change in the industry.
Let’s imagine you’ve been working as an architect in a large company for several years and are very proud of the now mature Supplier Relationship Management (SRM) application you specified, formed, and delivered to the business, as it continues to provide value.
Functionally, the SRM is a web application that allows for managing relationships of suppliers and materials, maintaining hierarchical structures, uncovering unwanted dependencies and helping your clients significantly reduce supplier costs.
The general guiding principles of the Zen philosophy can actually be quite helpful in designing the Anypoint Platform for APIs‘ deployment architecture. The emphasis on having a holistic approach, while striving for simplicity, symmetry, and minimalism, works as well for meditation as for coming up with a stable, robust and secure architecture. Here, we will outline the four most common models in use today that dovetail with the teachings of the Zen philosophy.
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.
Why do I want to do this?
Utilizing a rules engine promotes efficiency in system interfaces where some business logic needs to be executed and this logic can be frequently updated.
Picture cool kids in startups, cranking code as if their lives depend on it, focusing on the proverbial MVP above all else. At this stage, who cares if technical debt accumulates as fast as code gets written? It would be a waste of time and focus to try to keep the field as green as it was initially. Then the worst happens: the cool kids have it right, people love their new app and traffic starts to surge.
In his “To ESB or not to ESB” series of post, Ross Mason has identified four common architectures for which Mule is a great fit: ESB, Hub’n’Spoke, API/Service Layer and Grid Processing. In this post we are going to detail an example for the latter architecture. We will use Mule to build a scalable image resizing service.
Here is the overall architecture of what we intend to build:
MuleSoft provides the most widely used integration platform for connecting any application, data source or API, whether in the cloud or on-premises. With Anypoint Platform®, MuleSoft delivers a complete integration experience built on proven open source technology, eliminating the pain and cost of point-to-point integration. Anypoint Platform includes CloudHub™ iPaaS, Mule ESB™, and a unified solution for API management™, design and publishing.