During a recent development sprint our team was investigating frameworks in place to support Social Login for a RESTful application. In our research, we found that the common social login areas we were looking at Twitter, Facebook and Google all provided solid documentation on how to integrate into an application.
There are several cases where it is useful to be able to stand up additional WebSphere capacity for a limited time period, without needing to worry about data center server capacity and software licenses. Typical examples include batch type workloads, test of new code at infrequent intervals, maybe as part of an overall application modernization strategy.
On a recent project we were looking at rewriting a system which provides data-ingestion services into a DB2 instance. As we move more workloads into IBM’s cloud offerings we always stop, think, review to implement the most suitable technical approach to create the work product.
Do you have a modernized WebSphere application in your business running on your on-premise infrastructure? If you’ve migrated your old application code to the present-day WebSphere Application Server (WAS) version and updated your development environments / delivery pipelines to modern practices, it’s time to move your application to the WebSphere Application Server as a Service. In the last blog entry, we explained how you can modernize your existing WebSphere applications with minimal changes and migrate them to the cloud, lowering your costs and simplifying maintenance. This blog entry, we'll cover how to iteratively moving core pieces of compute-based business logic to cloud-based services.
Contrast Security is a revolutionary product that instruments your applications with sensors to detect security vulnerabilities in your code and protect your applications against attacks. Contrast Security LogoApplications on Bluemix that use the liberty-for-java buildpack can now use the Contrast Security buildpack to secure their applications. The buildpack utilizes the Contrast Security agent to instrument applications with sensors and monitor data flow in the application.
Do you have existing monolithic Java/JEE applications running on WebSphere Application Server? Is your application comprised of multiple business functionalities, but it’s packaged as a single application? Are there performance bottlenecks that you are not able to resolve because the application does not scale well? If you answered yes to any of these questions, read this post to learn how you can refactor your existing monolithic WebSphere application into a microservices-based application.
We just introduced The Bluemix Developer Console. Extending the current Bluemix Mobile Dashboard, this new experience goes beyond mobile and introduces new tools for quickly creating Cloud Native applications across web, mobile and backend. They aim to greatly cut down on development time by generating application starters with all the necessary boilerplate, build and configuration code, so that developers can start coding business logic faster.
In this article, we'll discuss our build pipeline in more detail. We'll talk about how we get from microservice source artifacts (including code) to deployable binaries, and scripts/metadata for configuring and deploying them.
For many developers, the Hello World starter applications on Bluemix are too basic and the sample applications on IBM-Bluemix.github.io page are a bit too advanced. If you agree with this, you'll find our recently released Runtime Getting Started guides extremely helpful.