Spring Team
Ben Wilcock

Ben Wilcock

Product Marketing Manager for Spring

Bristol, United Kingdom

Ben is hugely passionate about Spring and the many ways in which it changes peoples lives for the better. Having had a long career in software, spanning roles in development, analysis, design, and consultancy, he’s experienced first-hand the many challenges that face producers of software at all levels. As Pivotal’s Principal Product Marketing Manager for Spring, Ben hopes to promote the advantages of Spring to the widest possible audience so that they too can benefit from its incredible flexibility, diversity, interoperability, and productivity.
Blog Posts by Ben Wilcock

Hiding Services & Runtime Discovery with Spring Cloud Gateway

Ben Wilcock – Spring Marketing, Pivotal.
Brian McClain – Technical Marketing, Pivotal.

It’s rare for a company to want every API to be publicly accessible. Most prefer to keep their services secret by default, only exposing APIs publicly when absolutely necessary.

Spring Cloud Gateway can help. Spring Cloud Gateway allows you to route traffic to your APIs using simple Java™ instructions (which we saw in the last article) or with YAML configuration files (which we’ll demonstrate in this one). To hide your services, you set up your network so that the only server accessible from the outside is the gateway. The gateway then becomes a gate-keeper, controlling ingress and egress from outside. It’s a very popular pattern.

Read more...

Getting Started with Spring Cloud Gateway

Microservice architectures are great, but as your application programming interfaces (APIs) start to grow, so do the challenges related to their maintenance.

For example, as an existing API matures and adds new features it will need to take its clients along with it on the journey. When the details of an API change, clients need to adjust in order to work with these changes. This process takes time and can really slow your APIs evolution and interfere with your ability to iterate quickly.

Offering multiple APIs brings with it its own set of challenges. How do you route requests and responses to the correct API? How do you manage any message disparity? How do you support clients when your endpoints can move around?

Read more...

Pivotal Cloud Foundry is 5 years old, here’s how it changed my life...

Josh Long often says that “production is the best place on the Internet.” But where I used to work, developers needed to negotiate with operations, networks, and security before their code could go anywhere near this promised land.

Understandably, each of these disciplines seemed to have the same hidden agenda: change is bad. Experience had taught us that change was difficult and error-prone, so as a company we’d become risk-averse and cautious about our deployments. Releases were infrequent and large. There was plenty that could go wrong.

Read more...

Event-driven Java with Spring Cloud Stream and Azure Event Hubs [Guest Post]

Asir Selvasingh | Principal PM Architect | Microsoft – Java on Azure

Spring Cloud Stream Binder for Azure Event Hubs is now generally available.

It is simple to build highly scalable event-driven Java apps using Spring Cloud Stream with Event Hubs, a fully managed, real-time data ingestion service on Azure that is resilient and reliable service for any situation; this includes emergencies, thanks to its geo-disaster recovery and geo-replication features.

Spring Cloud Stream provides a binder abstraction for popular message broker implementations. It provides a flexible programming model built on already established and familiar Spring idioms and best practices, including support for persistent pub/sub semantics, consumer groups, and stateful partitions. Now, developers can use the same patterns for building Java apps with Event Hubs.

Read more...

Has there ever been a better time to become a Java developer?

Surely there’s never been a better time to become a Java developer?

There are productivity tools available these days that would have been mind-blowing just five years ago.

Take Spring Boot for example. Many people reading this on the Spring website may be familiar with Spring Boot. But let’s take a moment to acknowledge its awesomeness.

Years ago, if you were going to use the Spring Framework in your application, you had to be OK with a certain amount of configuration toil creeping into your day. But it wasn’t nice friendly configuration like, (ah, actually, sorry, I can’t think of an example of ‘friendly configuration’), it was nasty XML configuration with a side order of XSD, eww!

Read more...