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.
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.
“A surprisingly large fraction of applicants, even those with masters’ degrees and PhDs in computer science, fail during interviews when asked to carry out basic programming tasks. “
When I first heard this years ago I initially thought it had to be inaccurate. I had seen a large number of developers flunk interview coding tests and write really bad code, including some of this. But how could that many career developers out there pass for great programmers, yet when it comes down to actually producing code couldn’t do it well.
In our upcoming MuleSoft webinar, “‘The Health Cloud’: Are we there yet?”, we’ll be talking all about healthcare and the cloud. There has been quite a bit of talk about a “Health Cloud” which promises to extend the point of care, improve patient outcomes, enable closer clinical collaboration and lower costs, but have healthcare organizations really embraced the cloud? Or is this another case of media hype? With such confidential information at risk, how are organizations dealing with data security and integration with third party applications and services?
Hot on the heels of the announcement of the RESTful API Modeling Language (RAML) by the RAML working group, I am very happy to announce the general availability of APIkit.
APIkit consists of a set of open source Maven and Mule Studio-based tools that enable developers to be massively productive in creating well-designed REST APIs. APIkit features include the ability to take a REST API designed in RAML, automatically generate backend implementation flows for it, and then run and test the API with a pre-packaged console.