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.
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.
Kinetise has added a new feature to its platform for the ultra-fast development of native mobile apps called Embedded API Adapter. To refresh your memory – Kinetise is a Rapid Mobile Apps Development Platform that enables you to develop custom, API-driven apps in just a few minutes. Imagine having a short workshop with a business owner who has an app idea and being able to complete the app ready for production deployment. That's the power of using Kinetise!
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.
In our last post, we took high-level view of our process for moving WebSphere applications to the cloud. In this entry, we'll look closely at the tools that help you with the first step, modernizing your existing WebSphere application.
In this post, I'll describe how to create two Spring Kafka applications that will communicate through a Message Hub service on Bluemix. One application will act as a Kafka message producer and the other will be a Kafka message consumer. We will deploy these applications to a Bluemix Kubernetes cluster.
In this blog post, I'll describe the process of connecting an IBM Graph service on Bluemix with a Spring application. Then we'll deploy that application to a Bluemix Kubernetes cluster, using Kubernetes secrets to securely pass configuration credentials.
With many traditional workloads moving to cloud-based infrastructures, now is the perfect time to assess your existing Java-based workloads and migrate them to WebSphere Application Server on IBM Bluemix. More commonly known as “WAS on Cloud”, this service provides a fully-configured, turn-key WebSphere-based application environment, supporting both Traditional WAS and Liberty applications. You use your same tried & true wsadmin automation scripts, same CI/CD techniques, but just point them at Bluemix instead of your own infrastructure! This post summarizes the steps from WAS to the cloud.
Based on our experience developing a sample storefront application as part of the IBM Garage Method Reference Architecture for Microservices, this post summarizes key design decisions to consider as part of a Kubernetes-based deployment and offers our recommendations.