In the first installment of this series, we used the SpringTrader application as an example of an existing legacy Java app, and we outlined an approach to do two things—migrate the app to Pivotal Cloud Foundry and prepare it to run in a microservices architecture. In this post, we dive into the refactoring and modernization of one key service, enabling it to deal with real-time market data.
Migrating legacy, monolith apps on to Cloud Native architectures is a challenge. In this post, we delve into the details of taking an existing Java app, refactoring it, and deploying it on Pivotal Cloud Foundry. This is the first part in a series, and uses an actual legacy application, SpringTrader, as an example.
In this article, Pivotal Cloud Foundry platform engineer and consultant, Guido Westenberg, gives us a deep look towards an integration between Cloud Foundry and various configuration servers. The automation he explains also requires no application code changes, removing a lot of config issues from the plate of both development and operations teams. A source code example and YouTube demo is provided as well.
In the first part of a two part episode on Spring Boot and Spring Cloud, Josh Long and host Coté talk about the Spring Initializr and Spring Boot. They discuss the idea of doing process-based design (a key part of cloud native application development) in Java and how Initializr and Boot help with that. Also, they discuss how Boot can help with more governance and controls, while at the same time giving developers more autonomy and speed.
The Spring XD engineering team has some big announcements regarding Spring XD 1.2 and 1.1.3 along with Flo for Spring XD. Focusing on developer experience and productivity, the new features cover Flo, performance optimization, new sources/processors/sinks/batches, runtime refactoring to act as native apps in Pivotal Cloud Foundry, Apache Ambari installed clusters, resiliency improvements, registry HA support, improved integration with Pivotal HAWQ, Pivotal Gemfire, Pivotal Greenplum Database, Pivotal HD, and Sqoop.
The latest version of the Cloud Foundry Eclipse plug-in contains various enhancements for managing services in Cloud Foundry. Cloud Foundry Eclipse is a joint collaboration between Pivotal Software and IBM. Version 1.7.2 of the plug-in contains an updated UI that improves Cloud service management in Eclipse. In this article, we will cover service management for a Pivotal Web Services (PWS) server instance using the new UI. We first start by showing how to install Cloud Foundry Eclipse and create a server instance to PWS. We then show how to create a service, and how to bind that service to an application. Finally, we show how to unbind a service from an application as well as delete the service.
In this post, Pivotal Developer Advocate, Johannes Tuchscherer, explains how to use Maven with a Cloud Foundry plugin to run a Java app with Java 8. He provides several references and tips on how to get an environment running with this plug-in.
This post summarizes where to find Pivotal at JavaOne. Come see us at booth number 5201 for demos on the internet of things, Apache Hadoop®, microservices architectures, PaaS, and more. Sessions will cover running Spring in the cloud, open source identity and access management, security, REST, IDEs, APIs, and more.
The consumerization of IT is no longer restricted to consumer products. Born from the idea that “it should just work,” the new release of the Spring IO Platform 1.0 will consumerize Java for developers. With this release, there are a significant number of improvements and benefits. Pivotal will migrate the Spring.io website, as a reference application, to the new Spring IO Platform in the coming week and expects the Spring IO products supporting this important application to just work.
Pivotal CF is continuing to deliver on the mission of a cloud-portable agile platform for applications and services. Pivotal CF minor releases are increasing in frequency due to Pivotal applying the same agile methodology that the platform enables customers to use to decrease time-to-market. There was a three month gap between Pivotal CF 1.0 and 1.1 and for Pivotal CF 1.2 the gap between releases has shrunk to under two months. Despite the smaller release cycle, there are many new capabilities which are being delivered more quickly to customers.