background preloader


Facebook Twitter

Setting Up Swagger 2 with a Spring REST API. 1.

Setting Up Swagger 2 with a Spring REST API

Overview When creating a REST API, good documentation is instrumental. Moreover, every change in the API should be simultaneously described in the reference documentation. Accomplishing this manually is a tedious exercise, so automation of the process was inevitable. GitHub - livelessons-spring/building-microservices: Building Microservices with Spring Boot. How Spring Boot Autoconfiguration Magic Works.

Spring Boot with Docker. Now you can create a simple application. src/main/java/hello/ package hello; import org.springframework.boot.SpringApplication;import org.springframework.boot.autoconfigure.SpringBootApplication;import org.springframework.boot.bind.RelaxedPropertyResolver;import org.springframework.web.bind.annotation.RequestMapping;import org.springframework.web.bind.annotation.RestController; @SpringBootApplication@RestControllerpublic class Application { @RequestMapping("/") public String home() { return "Hello Docker World"; } public static void main(String[] args) {, args); } } The class is flagged as a @SpringBootApplication and as a @RestController, meaning it’s ready for use by Spring MVC to handle web requests.

Spring Boot with Docker

Centralized Configuration. You’ll first need a Config Service ( configuration-service) to act as a sort of intermediary between your Spring applications and a typically version-controlled repository of configuration files.

Centralized Configuration

You can use Spring Cloud’s @EnableConfigServer to standup a config server that other applications can talk to. This is a regular Spring Boot application with one annotation added to enable the config server. configuration-service/src/main/java/hello/ package hello; import org.springframework.boot.SpringApplication;import org.springframework.boot.autoconfigure.SpringBootApplication;import; @EnableConfigServer@SpringBootApplicationpublic class ConfigServiceApplication { public static void main(String[] args) {, args); }}

OmniGraffle - diagramming and graphic design for Mac, iPhone, and iPad. Async systems with sync clients. As the Reactive Manifesto says Reactive systems are: Responsive Resilient Elastic Message Driven The last principle often goes together with non-blocking async protocols.

Async systems with sync clients

This style of communication "allows recipients to only consume resources while staying active, leading to less system overhead". This fits perfectly with new demands of efficiency derived from the elastic model of cloud providers. Reactive Programming in the Netflix API with RxJava. By Ben Christensen and Jafar Husain Our recent post on optimizing the Netflix API introduced how our web service endpoints are implemented using a reactive programming model for composition of asynchronous callbacks from our service layer.

Reactive Programming in the Netflix API with RxJava

This post takes a closer look at how and why we use the reactive model and introduces our open source project RxJava – a Java implementation of Rx (Reactive Extensions). Reactive Programming in the Netflix API with RxJava. What Architects Should Know About Reactive Design Patterns. It is widely understood that our software needs to become reactive; we need to consider responsiveness, maintainability, elasticity and scalability from the outset.

What Architects Should Know About Reactive Design Patterns

Not all systems need to implement all these to the same degree, as specific project requirements will determine where effort is most wisely spent. But, in the vast majority of cases, the need to go reactive will demand that we design our applications differently. Modern applications present incredible design challenges: we expect near-realtime performance while managing petabyte-scale data and distribution across environments ranging from traditional servers to cloud systems to mobile devices.

Developing Reactive Microservices: free O'Reilly mini-book by Java Champion Markus Eisele. As we continue to help organizations modernize their legacy systems with Microservices architecture, our latest mini-book arrives right on time.

Developing Reactive Microservices: free O'Reilly mini-book by Java Champion Markus Eisele

We are happy to announce the availability of Developing Reactive Microservices: Enterprise Implementation in Java, a new O'Reilly mini-book authored by Java Champion and Lightbend Developer Advocate, Markus Eisele (@myfear). Download a free copy in PDF, EPUB or MOBI format (or all three!) With microservices taking the software industry by storm, traditional enterprises running large, monolithic Java EE applications have been forced to rethink what they’ve been doing for nearly two decades. Next Generation Session Management with Spring Session. Session management has been part of enterprise Java for so long that it has faded to the background of our consciousness as a solved problem, and we have not seen any major innovation in that arena in recent memory.

However the modern trend towards micro services and horizontally scalable cloud native applications challenges the assumptions upon which session managers have been designed and built for the past 20 years, and exposes flaws in the design of modern session managers. This article will demonstrate how the recently released Spring Session APIs help surmount some of the limitations of the current approach to session management, traditionally employed by enterprise Java. We will start with a summary of the problems with current session managers, then dig into the details of how Spring Session solves each of those problems.

Spring Data Redis. Next Generation Session Management with Spring Session. Tutorials. Autoscaling. Packer by HashiCorp. Immutable Infrastructure Made Easy. Boxfuse is free to use in development and for one application in production.

Immutable Infrastructure Made Easy

Run more applications with any of our paid plans. 1application 3images 100AMI builds/month 1instance. A Journey into Microservices: A Cloudy Beginning. This is the second part of a three-part article.

A Journey into Microservices: A Cloudy Beginning

Start reading at part one, A Journey into Microservices. From the start there were a number of guiding principles we wanted to instill into our new platform. One of these was taking a Cloud Native approach, something which had been been pioneered by Netflix. Adrian Cockcroft has talked about the approach Netflix took, with their aim during this process being to: “Construct a highly agile and highly available service from ephemeral and assumed broken components” –Adrian Cockcroft. Dystopia as a Service. Microservices with Spring. Functional Reactive in the Netflix API with RxJava. Creating an Asynchronous, Event-Driven Application with Reactor. Reactor - a foundation for asynchronous applications on the JVM. We’re pleased to announce that, after a long period of internal incubation, we’re releasing a foundational framework for asynchronous applications on the JVM which we’re calling Reactor.

Reactor - a foundation for asynchronous applications on the JVM

It provides abstractions for Java, Groovy and other JVM languages to make building event and data-driven applications easier. Why REST Keeps Me Up At Night. This guest post comes from Daniel Jacobson (@daniel_jacobson), director of engineering for the Netflix API. Prior to Netflix, Daniel ran application development for NPR where he created the NPR API, among other things. He is also the co-author of APIs: A Strategy Guide and a frequent contributor to ProgrammableWeb and the Netflix Tech Blog. With respect to Web APIs, the industry has clearly and emphatically landed on REST as the standard way to implement these services. Time to Move to a Four-Tier Application Architecture.

The new year is well underway and, like many others, you are probably planning upcoming projects to enhance your existing digital experiences or build completely new websites and applications. As you do so, the most critical fact to keep in mind is that “web” no longer means “web browser.” Pundits have been espousing a “mobile first approach” to application development for years, but with an annual mobile traffic growth rate of nearly 60% this is not negotiable any longer. The explosion in the number of connected devices, the shift of traffic from desktop to mobile, and the rising tide of the internet of things means that projects must now be rooted in the diversity of user experiences available on different devices.

To build and deploy apps that effectively attract and retain customers on a range of devices, you need to embrace a new way of thinking about app design. Why is the Standard for Application Architecture Changing? Immutable Infrastructure: what is it? - HighOps. If you haven’t read our first post Immutable Infrastructure: 6 questions to 6 experts containing the context and the full highlights of our little Q&A with 6 experts I suggest you do that first. Also remember you can always download the full 14-page PDF with the full transcript at the bottom of this page. So what is an Immutable Infrastructure? Introduction to Microservices. Embracing the Differences : Inside the Netflix API Redesign. As I discussed in my recent blog post on, Netflix has found substantial limitations in the traditional one-size-fits-all (OSFA) REST API approach.

Spring Cloud Series - Microservices using Spring Boot, Jersey, Swagger and Docker. Guiada por instructor. OpenShift 3 Roadshow. Overview · Netflix/archaius Wiki. Build Newsletter: Smarter Apps Need Data Microservices. The world is tired of dumb apps. Making the Netflix API More Resilient. By Ben Schmaus The API brokers catalog and subscriber metadata between internal services and Netflix applications on hundreds of device types. AppFog Makes 12 Factor Apps Easier. But What Are 12 Factor Apps? - CenturyLink Cloud. Businesses have a mandate to gain a competitive advantage from IT. Invariably, this discussion turns to cloud-native apps. Leaders ponder questions like “How can we create, run, and scale new applications quickly and easily?”

“How do we experiment, get to market faster, and reduce the cost of trying new things?” The answer: embrace the development and operational principles behind “12 Factor Apps.” Introduction to Microservices. A Reference Architecture for the Internet of Things. This is the first article of a two article series in which we try to work from the abstract level of IoT reference architectures towards the concrete architecture and implementation for selected use cases.

This first article will cover the definition of a more concrete and comprehensible architecture whereas the second part will then apply this architecture to actual use cases. Creating a Microservice? Answer these 10 Questions First. This post was originally published on the Datawire blog. Microservices appear simple to build on the surface, but there’s more to creating them than just launching some code running in containers and making HTTP requests between them. Build Newsletter: Serverless Applications, Containers & Microservices. Creating a Microservice? Answer these 10 Questions First. How Serverless Applications Will Change Your Business. Auto Scaling with the AWS Management Console. (SOV204) Scaling Up to Your First 10 Million Users. AWS Tips I Wish I'd Known Before I Started - W(e)blinks. An operations model for Microservices. API Directory. Building Microservices With Java - DZone Java.

Building microservices with Spring Boot – part 1. Microservice Design Patterns. Service registry pattern. Microservice Registration and Discovery with Spring Cloud and Netflix's Eureka. Paulc4/microservices-demo. Netflix/eureka. Kubernetes by Google. Load balancing Kubernetes – Paul about software development. Microservices : Building Services with the Guts on the Outside - Gary Olliffe. Microservices with Spring. Building Cloud Native Apps With Spring – Part 6 - DZone Cloud. Kubernetes by Google. Spring-cloud-samples/customers-stores. Introduction to Microservices. 12 Reasons Why NGINX is the Standard for Containerized Apps.

Microservices, Conway’s Law, and More.