JavaEE Microservices platforms

Presented during Payara Japan Tour 2019 (https://blog.payara.fish/payara-on-tour-in-japan). In this session, you'll learn how to develop applications that evolve according to your needs, can easily run in the cloud and integrate with common cloud technologies. We'll start with a simple application, focusing on business logic. MicroProfile framework, powered by a lightweight opensource Payara Micro runtime, will get us started quickly and allow gradual improvements later. MicroProfile contains a lot of components that make developers productive. It allows separating business logic from common concerns like configuration, failure-recovery, REST service calls, context propagation across service calls and securing services. Adding all of these to existing code is easy. It's also easy to introduce new microservices as needed and adopt cloud technologies as your application grows. I'll show you how, in a step-by-step demo. And if time allows, I'll also show how to run and scale your application effectively with Kubernetes in the cloud.

3 hour deep dive presentation by Micronaut creator, Graeme Rocher, at Devoxx Belgium 2019 showing how to use advanced features such as Aspect Oriented Programming (AOP), compiler plugins and so on. Associated YouTube video can be found at https://www.youtube.com/watch?v=S5yfTfPeue8

The document discusses microservices and how Azure supports the microservices architecture for modern applications. It defines microservices and service-oriented architecture as an approach to building applications as independent, interoperable services. It then describes the various Azure PaaS options for hosting microservices, such as App Service, Functions, and Service Fabric. It also covers supporting Azure services for state management, caching, storage, and monitoring microservices applications. Finally, it provides an example topology of a photo sharing solution built with multiple Azure microservices.

Presentation by Micronaut creator Graeme Rocher on how frameworks like Micronaut are evolving Java for the Microservice and Serverless Era through the use of innovative techniques like Ahead of Time Compilation (AoT)

Microservices architecture has many benefits. But it comes at a cost. Running microservices and monitoring what’s going on is tedious. That’s why MicroProfile adopts monitoring as a first-class concept. In this session, learn how MicroProfile runtimes collect metrics and how to seamlessly collect them with tools like Prometheus and Grafana. Learn how MicroProfile makes it easy to connect information about interrelated service calls, how to gather the information and analyze system bottlenecks, how to deploy and scale MicroProfile applications with Kubernetes and how to react to their health status to detect and automatically recover from failures.

The document discusses microservices and Spring Cloud. It defines microservices as small, autonomous services that work together to build distributed systems. It then explains key Spring Cloud Netflix components like Zuul for routing, Eureka for service discovery and registration, and Hystrix for circuit breaking. The document also discusses other challenges in building microservices architectures like distributed tracing, polyglotism, and alternative solutions to Eureka like Consul and Zookeeper.

This document discusses lessons learned from real-world deployments of Java EE 7. Key points include increased developer productivity through features like batch processing, concurrency, simplified JMS, more annotated POJOs, and a cohesive integrated platform. Specific technologies used include JSON, WebSockets, Servlet 3.1 NIO, and REST. Real-world examples of implementations include an application for a UN agency to support refugees and a running social network application for runners.

The world is moving from a model where data sits at rest, waiting for people to make requests of it, to where data is constantly moving and streams of data flow to and from devices with or without human interaction. Decisions need to be made based on these streams of data in real-time, models need to be updated, and intelligence needs to be gathered. In this context, our old-fashioned approach of CRUD REST APIs serving CRUD database calls just doesn't cut it. It's time we moved to a stream-centric view of the world.

This presentation, given at the Fort Worth .NET User Group on 19 Sept. 2017, talks about serverless technology: What it is, when it's best to use, its features and limitations. It specifically focuses on Azure Functions and Azure Logic Apps.

High availability is a core enterprise requirement in any modern deployment. This ensures that systems can continue to function correctly even when there are failures. Ideally such systems should continue to function correctly and provide services while there are several failures. Another important aspect is that system deployment architectures should ensure there are no single points of failure. Redundancy is the most widely used technique in designing such fault tolerant systems. This includes data redundancy, information redundancy, time redundancy etc. However, redundancy always comes at a cost and hence there is a cost vs. availability trade-off. Certain availability techniques may also result in performance overheads. In this webinar, Afkham Azeez, Director of Architecture, will take a look at how these techniques are employed in the WSO2 platform to achieve high availability and fault tolerance, while taking the cost and performance factors into consideration. We will also look at some key aspects which will enable enterprise architects to make deployment topology decisions based on availability requirements at an optimum cost.

The document summarizes the development of a small product by a team to search social networks and report results. It describes their motivation to create new software products after maintaining various systems. They developed a minimum viable product in JavaFX that searched Twitter and reported results. Over time they expanded it to add real-time search capabilities and considered new sales approaches. However, the company then required following an older standard, which went against the team's agile approach, leading to the end of the project.

Micronaut is a new framework designed from the ground up for microservices and serverless computing. It uses ahead-of-time compilation to have ultra-lightweight runtimes with low memory footprints. This allows micronaut applications to start very quickly and run with small jar sizes. Micronaut natively supports features important for microservices like service discovery, configuration sharing, load balancing, and serverless functions. The documentation, examples, and community resources are available on the micronaut website.

This document provides an overview of building microservices with WSO2 technologies. It introduces microservices architecture and the WSO2 Microservices Framework for Java (MSF4J). MSF4J allows developing microservices using Java annotations in a lightweight and high-performance way. The document demonstrates hands-on examples of creating microservices with MSF4J and deploying them to Kubernetes. It also discusses the current and future state of the WSO2 Application Server, including its integration with other WSO2 products.

10 tips to make ASP.NET apps faster including: 1. Enabling kernel caching in IIS for static and dynamic content to reduce context switches. 2. Using asynchronous code, handlers, and modules to prevent thread blocking on I/O-bound operations. 3. Configuring the CLR thread pool to optimize thread usage. 4. Switching to integrated pipeline mode for a unified request processing pipeline. 5. Optimizing static file handling by selectively running managed modules. 6. Understanding the ASP.NET pipeline and placing modules strategically. 7. Avoiding direct SQL connections by using a data source. 8. Removing unused view engines to reduce overhead. 9. Avoiding

Setting up a cluster is important when developing enterprise software and deploying them in production environments. Distributing deployment artifacts & related metadata to all nodes in a homogeneous cluster is a typical requirement for a clustered deployment of any middleware platform. In such a cluster, all nodes should contain the deployed artifacts as well as the related metadata. The Deployment Synchronizer (DepSync) is the mechanism used in the WSO2 platform for distributing these artifacts and metadata across all nodes in the cluster. It provides the ability to synchronize data between the worker nodes of a product cluster. When used with the WSO2 Application Server, or the WSO2 ESB, you can synchronize your deployable artifacts like web services, and web applications etc. across the cluster nodes. In addition, with the latest WSO2 Carbon 4 release, WSO2 provides the ability to synchronize service metadata which includes service policies, transports, and service-type specific data. Now you only have to deploy and configure services in one node - called the manager. Then, DepSync will replicate those to other nodes - workers. In this presentation, we present how this is done in the WSO2 Cloud-enabled middleware platform. Typical deployment artifacts will include webapps, JAXWS/JAXRS apps, data services, proxy services, and BPEL processes . The WSO2 platform also natively supports multi-tenancy. Tenants & tenant artifacts are loaded on demand. We will demonstrate how DepSync works efficiently with multi-tenancy. Kasun Gajasinghe did the demonstration section of this webinar presentation while Pradeep Fernando provided technical aspects of Deployment Synchronizer