Your customers, competitors, and suppliers are becoming digital. If you joined us for Ross Mason’s webinar, Connect Faster to Drive Value: A Strategy for Rapid IT, you’ll understand why you must digitally transform your own business. Now how do you cut through the hype and get started?
We’ll tell you in the next webinar in the Connected Company series: Top 5 Steps to Drive Your Digital Transformation Initiative. In this webinar, R ‘Ray’ Wang, Constellation Research, will discuss five simple steps market leaders are taking to lay a foundation for digital transformation and highlight a MuleSoft customer who has successfully taken these steps to accelerate IT’s ability to deliver business value.
Walk away from this webinar with:
- Questions to ask to identify your preparedness for digital transformation
- IT innovations that are driving business model disruption
- Tips to build collaboration between IT and business to drive faster results
Presenter: R “Ray” Wang, Principal Analyst, Constellation Research
If you’ve ever worked on performance issues with an IO- intensive app, there is a good chance you already know that the application performance degrades when the disks are stressed out. This fact is usually well known, but the reasons behind it aren’t always clear. I’d like to try and clarify what’s going on behind the scenes.
In a typical scenario, when data is written to a file, it is first written to a memory area reserved as the page cache. The page holding the newly written data is considered dirty. After a period of time per the kernel IO policy, the kernel flushes the dirty data to the device queue to persist to hard disk. Once the data gets to the queue, the rest is mechanical: The device driver reads the IO requests, then spins, seeks and writes to the physical disk block where the file is. The journal file is written first if enabled, then the actual file.
In a recent discussion with a few other engineers, an idea of disabling file system journaling came up to improve disk write latency. While this is certainly true because it is one less disk operation per write, the actual time gained is negligible because the journal file is in the same block as the file to be written. The benefits of having the journal file to restore the disk from a crash far outweighs the little latency saved.
Thanks to those of you who attended our webinar last week, “The API Love Triangle: Delivering Successful API Programs,” and we hope that you found the session valuable. Now you know that the API love triangle is composed of three key people and that the success of your API program depends on satisfying the needs of each:
The API Developer, who’s always looking for ways to be more efficient, to get their APIs to market faster, to re-use existing artifacts rather than re-creating things from scratch.
The Application Developer, who wants to know which APIs are available for use and when they find one that fits their project, how can they get started with it quickly?
The IT Leader, who wants to make sure that the APIs their team releases are properly secured and managed and that developers use those APIs instead of creating their own.
On the heels of Dreamforce, one thing is clear, there’s never been a better time to be an enterprise developer. The sheer number of technologies on display, not only by Salesforce but also by the sponsors—developer tooling companies, API providers, independent software vendors (ISVs), systems integrator partners and other complementors—make it abundantly clear that we’ve reached a critical mass of players competing for the hearts of the enterprise developer.
But it’s also a confusing time, in that the essential problem of choice looms large. If the smorgasbord of give-away shirts at Dreamforce was any indicator, there truly is an abundance of technologies upon which you can build your apps and business today. Whether you were coding all night at the Salesforce $1M Hackathon, or navigating the cramped aisles of the Cloud Expo that boasted over 300 sponsors, you probably weren’t alone if you asked yourself, where do I even start?
CloudHub Release 40 merges components of MuleSoft’s Anypoint Platform (CloudHub and Anypoint Platform for APIs) into a single seamless user experience. In addition, it delivers a host of usability features, including:
- Advanced identity and access management
- Support for multiple production environments
- Application resource monitoring
Read on for all the details.
MuleSoft has teamed up with DayCamp4Developers to put together one full day of API talks by today’s thought leaders. Best of all, this event takes place online. That means anyone with a browser can attend, and it’s FREE!
You’re not going to want to miss this exciting event where our speakers will be talking about the API landscape, building and designing your API, and ensuring that developers use it. So mark your calendars and join us on November 7th for this very special edition of DayCamp4Developers sponsored by MuleSoft.
Get your FREE ticket »
Anypoint Studio October 2014, Mule 3.6.0-M2 and 3.5.2 released
Today we’re releasing Anypoint Studio October 2014, Mule 3.6.0 – Milestone 2 (M2), and Mule 3.5.2. This release includes new HTTP capabilities which make it easy to connect to RESTful APIs with RAML, and productivity enhancements inside Anypoint Studio – such as DataSense for APIkit and a new Studio launcher.
Financial services information technology (IT) has transformed from order taker to strategic business partner. As part of this transformation, IT organizations are finding they must address key challenges with legacy modernization, data management and digital transformation.
MuleSoft is launching a three-part white paper series discussing these challenges and how financial institutions are overcoming them. At the core of each of these challenges is the need for a new level of connectivity. Financial services organizations must seamlessly integrate applications, data and devices and it is those organizations that are able to embrace these challenges–those “connected financial institutions”–that will win.
Companies who identify and expose core capabilities as well-defined, well-managed APIs are essentially making their business “programmable.” For these businesses, APIs act an innovation layer that allows them to quickly capitalize on new market opportunities, engage with their customers in more personalized ways and collaborate more effectively with partners. In essence, APIs are the new fabric enabling agility and fueling competitiveness.
While APIs are enabling strategic initiatives across the business, investment in API programs tends be driven by one of four strategies:
The world has officially gone mobile – global mobile traffic now represents 15% of all internet traffic (source: Flurry Analytics, Oct 2013) and Chinese e-commerce giant Alibaba now transact 30% of their revenue over mobile devices (that’s $2.5B in mobile commerce revenue in 2013). Today, every application that touches a customer, partner or even employee must be available as a mobile app. And the easiest, most efficient way to serve data from a backend system to a mobile app is through a RESTful API.
Citrix Modernizes BizTalk with Anypoint Platform
To stay relevant, today’s businesses have to adopt SaaS applications, cloud services, and API technologies and integrate them with their legacy systems. In SearchSOA this week, MuleSoft customer and Citrix integration developer Vinod Sangaraju discussed how Citrix has deployed CloudHub and is planning to use MuleSoft’s new solutions for Microsoft to fill BizTalk integration gaps.
Citrix Systems integration development manager Vinod Sangaraju found the MuleSoft Anypoint Platform when searching for an iPaaS solution to connect Citrix solutions with Salesforce, Marketo, Workday, and other cloud and on-premises applications. His search was driven by Microsoft BizTalk’s limited SaaS connectivity. His team had been filling that gap by using Microsoft BizTalk for on-premises integration scenarios and MuleSoft’s Anypoint Platform, in particular CloudHub, for cloud-to-cloud and cloud-to-ground integration. That wasn’t ideal, he said.