Andreas Krohn – Dopter. Nordic APIs World Tour 2015: May 11 – Copenhagen. As a product APIs are both different and similar to other types of products. In some ways an API is just like any SaaS product. But in some ways an API as a product has it’s very own set of challenges and opportunities. In this presentation Andreas Krohn goes through the entire lifecycle of an API, from ideation to production to retirement. He compares the API lifecycle to other product lifecycles and highlights important focuses for API providers to consider when publishing their APIs.
For thought provoking pieces on everything APIs, check out the Nordic APIs blog: http://nordicapis.com/blog/
The theme for the Nordic APIs World Tour was the API Lifecycle. Read these Nordic APIs articles for more information on managing an API’s entire Lifecycle:
via Share Xcode Projects with Bluemix DevOps Services – BlueMix Dev.
Building a native iOS app requires the Xcode integrated development environment (IDE). Sharing code with Xcode is made easy with the inclusion of a Git repository in Xcode projects. In this blog post, I document the basic steps required to integrate a local Git repository created by the Xcode IDE with a Git repository on IBM Bluemix DevOps Services. IBM Bluemix DevOps Services is a Software as a Service (SaaS) offering on the IBM cloud that supports continuous delivery. With IBM Bluemix DevOps Services you can develop, track, plan and deploy software in one place (visit the IBM Bluemix DevOps Services site to learn more).
I recently found myself with some time on my hands and decided to explore iOS app development with the Swift programming language. I created a very simple, getting started iOS app and wanted to share the source for my app using a Git repository provided by IBM Bluemix DevOps Services. I found the initial push of files from Xcode to IBM Bluemix DevOps services failed and set about understanding why. This blog post explains why this initial push fails in the Xcode IDE and how to work around this. I created the app and the steps that follow with Xcode 6.3.1 on OS X Yosemite.
via Working with the JMS Connector in WebSphere Cast Iron, Part 1: Configuring JMS in WebSphere Application Server.
Part 1 of this tutorial series explains how to configure Java™ Messaging Service (JMS) to create the Queue Connection Factory in WebSphere Application Server (hereafter called Application Server) and connect to the JMS Connector in WebSphere® Cast Iron Studio and Appliance. You will learn to configure JMS to send messages between two or more clients in Application Server.
IBM® WebSphere Cast Iron is an offering from IBM that provides clients with a platform for integrating cloud-based applications from leading SaaS (Software as a Service) providers with on-premise applications from IBM and others. IBM Cast Iron Studio (herafter called Studio) is a development tool that is used to design, test, and publish integration projects to an IBM Cast Iron Integration Appliance. Studio provides numerous entities that you can drag into a workspace and configure as part of one, or more, business-process orchestrations that comprise an integration project.
WebSphere Application Server offers options for a faster, more flexible Java application server runtime environment with enhanced reliability and resiliency for building and running applications, including cloud and mobile. Application Server implements two main messaging sub-systems. The default messaging provider is internal to WebSphere and the WebSphere MQ messaging system.
Java Message Service (JMS) provides a common interface to standard messaging protocols and also to special messaging services in support of Java programs. Messages can involve the exchange of crucial data between systems and contain information such as event notification and service requests. Messaging is often used to coordinate programs in dissimilar systems or written in different programming languages. By using the JMS interface, you can invoke the messaging services like IBM’s WebSphere MQ, formerly known as MQ Series, and other popular messaging products. In addition, JMS supports messages that contain serialized Java objects and messages that contain XML-based data.
Connectors provides the ability for the Cast Iron Appliance or Cast Iron Live to interact with the enterprise server and perform certain activities, just by configuration with no coding approach. Orchestrations are the main component of a Cast Iron integration solution. All functionalities in an integration solution are controlled by the orchestration. The orchestration contains a set of activities that are performed in an order that is defined within the orchestration editor or workspace.
What makes an application scale? What should you worry about early on and what can wait?
Over the last 3 years, Achievers has learned many lessons and gained fundamental knowledge on scaling our SaaS platform. CTO Dr. Aris Zakinthinos will present and discuss the decisions we’ve made including language choice, server architecture, and much more; join us while we share tips, tricks, and things to absolutely avoid.
Throughout the evening you will have the opportunity to talk to the development team behind the Achievers Platform and ask questions on scaling best practices.
Software as a Service (SaaS) projects often start with three main components:
- A browser-based dashboard surfaced to the end user
- A control server that interprets user commands
- Cloud machines that run the workload
“With Bluemix, I can stand up a service and try out code in a matter of hours. I can get a live dashboard out to my customers and team for quick evaluation. On SoftLayer, I can provision powerful workload machines to do the heavily lifting and easily add them to my SaaS application.”