For this week’s Meet a Muley post, we’re switching things up a bit and introducing you to someone from the marketing team! Dan Ahmadi not only has the longest title in the company (Marketing Programs and Demand Generation Manager), he’s also a jack of all trades. He works across account development, product marketing and digital marketing teams, all to drive global demand generation initiatives and marketing operations.
First thought that came to mind when you looked into the mirror today?
To achieve growth, insurance firms must move from multiple isolated applications to service-based integration. Systems such as billing management, policy management and claims management must be made extensible to support new applications. By doing so, firms can augment existing distribution channels and capture new business; more deeply serve and engage their customer; and develop new products to address market whitespaces. The net effect is better customer acquisition, retention and profitability.
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. Though strong, the duct tape that olds the application together starts to show signs of fatigue. Maintenance becomes painful, adding new features is excruciating. The blood of the architecture that has been sacrificed on the altar of time-to-market is calling for revenge.
One of the most typical architectural mishap that comes back to haunt startups is tight coupling: the whole system is a monolith where coupling manifests itself both from a temporal manner (everything is synchronous) and a lack of abstraction in the interactions between the subsystems (everything knows the intimate details of everything else).
The good news is that there is hope: the giants of past time, upon whose shoulders everything is built, have fought these problems and won. Take Hohpe/Woolf’s Enterprise Integration Patterns (EIP) for example. They discuss how messaging can be used to alleviate coupling issues. Sure enough, the “enterprise” term in the name is dubbed “run away!” by our startups’ cool kids. So in this post we’ll look at a few of these patterns and how they could be used beneficially in modern applications. And hopefully these patterns will feel more lovely than enterprisey!
Besides the upcoming World Cup and Olympic Games, Brazil will also be hosting the first MuleSoft Summit in Latin America. Yes, now the cariocas and paulistas have another reason to celebrate!
On December 5th, our Muleys including our founder, Ross Mason, will be visiting Sāo Paulo for our first integration event in South America. It’s no surprise for anyone that Brazil is a hot spot for new technology trends, and our developer community in this country is proving to be one of the biggest worldwide.
APIs are causing a huge technology disruption. Developers armed with APIs are changing the enterprise IT landscape. The tech world is being turned upside down as developerAPI access is changing banking platforms, airline systems, e-commerce platforms and much more.
He discusses the importance of micro-features and how they fuel disruptive applications, as well as how companies with API strategies will be the ones to succeed. But how exactly do you arm yourself? By opening up existing platforms and API-enabling them, companies can start putting API strategies in place.
Importing records to your Salesforce account from Box is now easier than ever. No installation needed, all you need are your Box and Salesforce credentials and a CSV file with the records you want to send to Salesforce.
Let”s go through the steps to do it:
1 – Log in into your Box account
2 – On the top menu you can find a cloud icon, the Apps section. (This is the only time you will need to add an application, after is added you can just skip to step 6).
In this installment of our MuleSoft webinar series, we discuss how to identify legacy assets within your organization, synchronize data between modern and legacy systems, and service-enable legacy applications with APIs built through MuleESB.
A little bit about SOA
Effectively implementing a Service Oriented Architecture approach within your enterprise can help deliver faster time to ROI through increased agility.
The reality of legacy systems
Today, a large amount of business data and processes are tied up in legacy systems, which are difficult to access and modify due to a lack of modern interfaces and a scarcity of available expertise to work on the system. Legacy systems house critical information and functionality that need to be accessed by other systems and people.
In case you missed last week’s Meet a Muley post (featuring Eva, our Senior Java Developer) we’ve started a new weekly series! Every Friday we’ll introduce you to a new member of the MuleSoft team to give you some insight into what we’re all about.
This week we’ll be chatting with James Donelan, our VP of Engineering. When we chose James for this post, we immediately agreed that there needed to be some sort of voice recording for you all to truly understand why everyone loves to listen to James. And we found one!
Dreamforce is approaching fast and as we near, we thought it would be a good idea to elaborate on MuleSoft’s presence at Dreamforce, as well as what you can expect from us at our booth this year!
It’s no secret that SaaS and cloud, social and mobile have changed the game for many businesses. Organizations have stated time and time again that integration is one of, if not the main hurdle to overcome when adopting SaaS. Companies need to connect to numerous SaaS and on-premise applications and services such as Salesforce, SAP, NetSuite and many more to keep their business running.