It had just turned 2 a.m. on April 18th, 2003. I was getting ready to release my first open source project, and I was about to pull the trigger on a name. I settled on MULE as I was trying to solve the hard, unrelenting work of connecting applications and data—MULE was going to take the “donkey work” out of integration. What I didn’t know was that I was choosing the stock ticker symbol for a company that would go on to solve much bigger problems for companies globally. It’s pretty cool to reflect on that now, and it has been an amazing experience getting here.
If you share your code on GitHub with other developers, you may want to be notified about commits. GitHub has a built in feature to provide notifications or send an e-mail about these commits. I wanted to see, if I could leverage MuleSoft to introduce notifications through alternative channels, particularly through Twitter.
I implemented two solutions. Each has some pros and cons. You need to decide, which one works better for you. The description of the first one comes in this post.
New year, new tips! But, before sharing this week’s Training Talks question, here’s a fun fact about one of our technical instructors, Poornima Sundararaman.
In grad school, Poornima worked on a software project for NASA to engineer a plant gardening robot that monitors and gardens hydrophobic plants (tomatoes and strawberries to start with) in outer space for astronauts to consume. How cool is that?
2016 has finally come to an end, and that means an opportunity for your IT teams to start fresh and do great things for the business in 2017. But where’s the best place to start? Here are our top 7 r resolutions for your teams to consider in the upcoming year.
Don’t take security for granted.
High profile security breaches this year highlighted just how important security practices are when doing business. Don’t wait until the last minute to implement security best practices when delivering projects; consider implementing security by design.
A convergence of digital forces – notably mobile, SaaS, cloud, big data, IoT and social – is creating massive disruption in the market and pushing businesses to move at much faster speeds. However, with a fixed set of resources and a constrained capacity to deliver on new projects, IT is often accused of holding the business back rather than enabling it.
As Andy Williams’ popular song reminds us, the holiday season really is ‘the most wonderful time of the year’. The same is true for retailers, with UK shoppers expected to spend £42.2 billion in December 2016, a 2.5% increase from last Christmas. However, without adopting an appropriate API strategy to respond to increasing customer pressure for friction-free online and in-store experiences, many stores will be left out in the cold.
How should developers and employers get the most from each other?
There is growing pressure for IT to deliver on business demands in real time—but there is often a gap between what they need to do and what they can do. So, how can they close the IT delivery gap? For starters, they should make everyone in the company a developer.
This is part 3 of my API security blog series. I will be showing an example scenario of how Anypoint platform can be a vital component of a secure API-led architecture and the capabilities to securing the API.
If you missed part 1 and part 2 here they are:
- API security: Ways to authenticate and authorize
- API security: Keeping data private but accessible
The vast majority of RESTful APIs follow a simple “request-response” message exchange pattern, but that pattern is often too limiting and is not sufficient to achieving robust and reliable application performance. We frequently get questions from customers asking: ‘How I design asynchronous APIs?’ and ‘How I design an API that allows for the concurrent modification of the same API resource without bringing the resource into inconsistent state?’. In this blog post, we present two approaches answering these questions using standard HTTP headers and status codes. Further, we provide RAML snippets that can serve as a starting point when designing such APIs.
Download our Best Practices for Microservices whitepaper to gain a deeper perspective about our approach to microservices written in this post.
If IT today has a watchword, that word is “speed.” At the same time, IT is expected to protect the organization’s crown jewels (company finances and private customer records) and to keep services available and responsive. The message: Go faster, but don’t break anything important. Even Facebook has modified its motto on this front from “Move fast and break things” to “Move fast with stable infrastructure.”