Web application I have always dreamt of

May 23, 2015Download as PPTX, PDF1 like2,008 views

Through years of work have been trying many of Java frameworks which provides different level of abstractions on both server and client-side. Pure Servlet+JSP, JSF, GWT, Struts, Spring MVC, Vaadin, Play!, DWR, you name it. Sometimes it felt good, sometimes not, and with each year number of “good” applications reduced to the critical minimum. Later I tried to bring all the good points I had ever seen together to create “a perfect being” and after years of struggling I feel that I have reached the goal. Let me share it…

Web-application
I’ve always dreamt of
@JEEConf
2015

Victor Polischuk
Programming 26
Overall 32
Java 11
Web 11
Legacy 11
Professional 13
Has something to share

Overview
http://zeroturnaround.com/rebellabs/top-4-java-web-frameworks-revealed-real-life-usage-data-of-spring-mvc-vaadin-gwt-and-
jsf/

Prehistoric Era [...-1995]
• Static content only
• Interaction without server:
Impossible
Unthinkable
• Server-side HTML adjustments

Medieval Era [1995-2005]
• Static content mostly
• Interaction without server: cached resources
• Server-side HTML+CSS+JS adjustments
• Frames as asynchronous data loading
• Birth of:
Servlet API
JavaScript
DHTML concept
Flash
Browser-compatibility hell
RFC1925

Renaissance Era [2005-2010]
• Static content with dynamic “whistles”
• Interaction without server: simple functions
• Server-side HTML+CSS+JS adjustments
• Rising popularity of Rich Internet Applications
• Birth of:
jQuery
DOJO
AJAX and Comet

Modern Era [2010-...]
• Internet of Things
• Big Data
• Cloud Computing
• ???

Business Needs
• Integration with anything:
Mobile
Mainframe
Coffee machine
• High availability:
Hard to predict clients behavior
• Data is the TOP priority:
We make money out of it
• Client’s satisfaction:
Should be happier than those of our competitors

Idea
• “All problems in computer science can be
solved by another level of indirection” © David
Wheeler
• “Do One Thing and Do It Well” © Unix community

Business Needs
• Integration with anything
• High availability
• Data is the TOP priority
• Client’s satisfaction

Technical Needs
• Scalability
• Security
• Testability
• “Otherity”

Scalability
• Server is just a bunch of endpoints
• Independent client
• State
Client needs it
Server doesn’t
• SLA
Way to Nine-Nines
You do not want to lose clients, right?

Security
• Do you need it on each request?
• Do you know how it works?
• Do you think it is secure?

Testability
• Server side:
Unit
Integration
Contract
[optional] Load & Performance
• Client side:
Unit
Integration
Contract
[optional] Browser & Sanity

Responsibility
• Client:
Responsive
User-friendly
Pretty
• Server:
Scalable
Fail-proof
Redundant

Traffic
• Reduce useless to none
• De-increase useful:
Increase volume
Decrease size

Optimization
• Client
Caching
Pre-fetching
Incremental updates
• Server:
Caching
Pre-fetching
Incremental updates

Encapsulation
• Both parties can have their own secrets

Polygamy
• Is it moral if a client has many servers and vice
versa?

Summary
• Effectiveness: you have one job
• Security: you are limiting interaction to minimum
• Testability: test JSF page, I dare you!
• State: -less server, -ful client
• Elasticity/scalability: your data volume is growing
• Network optimizations: you know what you send
• Local optimizations: you know what you do
• Many-to-many connections
• SLA

This document discusses reducing JavaScript usage for backend developers by exploring web components, Polymer, and JavaServer Faces (JSF). It provides an overview of web components goals and standards, introduces Polymer and how it builds on web components, discusses JSF and the PrimeFaces component library, and demos how to use Polymer and PrimeFaces. The goals of web components, Polymer, and PrimeFaces are to reduce code, improve readability and reusability through composable elements. Browser support for the various web component specifications is outlined.

Spring Boot. Boot up your development. JEEConf 2015Strannik_2013

This document discusses Spring Boot, an open-source framework for building microservices and web applications. It provides an overview of Spring Boot's key features like embedded servers, auto-configuration, starters for common dependencies, and production monitoring with Spring Boot Actuator. The document also covers configuration, customization, security, and compares Spring Boot to alternatives like Dropwizard.

Spring cloud for microservices architectureIgor Khotin

I'm covering a new trend in distributed enterprise architecture – microservices. How the leading technology companies like Netflix and Amazon come to use that approach. How does it help them to scale their infrastructure. And how the newest set of tools in the Spring family would help you to apply those design principles in practice. Spring has always been about patterns and Spring Cloud brings you implementation of several widespread ones for distributed apps. And we'll try to show why DevOps should come in front of Microservices approach

Intro to spring cloud &microservices by Eugene HanikblumEugene Hanikblum

This document provides an introduction to microservices and Spring Cloud. It discusses the benefits of a microservices architecture such as improved scalability, failover, and team agility. It then covers the history and concepts behind microservices including Conway's Law. Finally, it demonstrates how to build a simple Spring Cloud topology consisting of a configuration server, discovery server, sample service, and API gateway for routing requests between services. Hystrix is also introduced as a way to add circuit breaking and failure tolerance between communicating microservices.

Microservices with SpringSoftware Infrastructure

This document discusses microservices and provides an overview of related concepts. It begins with definitions of microservices and comparisons to monolithic applications. Key features of microservices like independent processes communicating over HTTP are outlined. The document then covers reasons for using HTTP, REST, and JSON in microservice architectures. An example online shopping application is used to illustrate how it could be decomposed into microservices. Challenges of monolithic applications are contrasted with advantages of the microservice approach. The document concludes with a summary of Spring Cloud which provides tools to help implement microservices patterns.

Microservices with Spring BootRasheed Waraich

The document discusses microservices and their advantages over monolithic applications. It defines microservices as small, independent components that are built, deployed, and scaled independently. The document outlines characteristics of microservices like being organized around business capabilities, infrastructure automation, and evolutionary design. It also discusses tools that can help build microservices architectures.

Best Practices with WSO2 Developer Studio WSO2

The document provides an overview of WSO2 Developer Studio and its capabilities for developing enterprise applications. It discusses how Developer Studio allows developing, deploying, debugging and testing applications using services from the WSO2 Carbon platform. It then demonstrates through an example how to create a fault reporting system using Developer Studio to develop the various components like a data service, Axis2 service, ESB artifacts and a web application.

angular-wakanda ngParis meetup 15 at 42Alexandre Morgaut

Presentation of Web Applications development possibilities with Angular-Wakanda and an overview of its API usages not only to reach the WakandaDB databut also any kind of third party data sources. We'll see: - the creation of a NoSQL Object business Model adapted for the Web platform; - an integration in the Yeoman workflow; - dynamic JSON document controlled by the angular client; - with relationships between these server JS objects - and access to their server JS methods - an overview of SSJS multi-threading with mixte HTML5 / node.js APIs - notifications by Web Sockets

WSO2Con USA 2015: End-to-end Microservice Architecture with WSO2 Identity Ser...WSO2

This document discusses iJET International's migration to a microservices architecture using WSO2 Identity Server and API Manager for identity management and API integration. The key challenges addressed were replacing their legacy architecture with a scalable and agile system, and enabling single sign-on access across their applications. Within six months, they implemented a new infrastructure with federated SSO, API Store and Gateway, and rebuilt an application using REST APIs secured by WSO2. While documentation gaps caused issues, the migration was ultimately successful.

Full Stack Development With Node.Js And NoSQL (Nic Raboy & Arun Gupta)Red Hat Developers

In this session, we'll talk about what's different about this generation of web applications and how a solid development approach must consider the latency, throughput, and interactivity demand by users across mobile devices, web browsers, and Internet of Things (IoT). We'll demonstrate how to include Couchbase in such applications to support a flexible data model and the easy scalability required for modern development. We'ill demonstrate how to create a full stack application focusing on the CEAN stack, which is composed of Couchbase, Express Framework, AngularJS, and Node.js.

ASP.NET: Present and futureHrvoje Hudoletnjak

Michael North "Ember.js 2 - Future-friendly ambitious apps, that scale!"Fwdays

Ember.js is being adopted more and more broadly as time passes, and is an excellent choice for highly complex data-driven UIs. With the recent release of the "2.0" version of the framework, things are faster, smarter, and easier than ever. With a focus on productivity and reducing the number of trivial decisions developers must make while building an app, it's astonishing how quickly one can get up and running, and how well the abstractions hold up as the codebase scales in size and complexity. I'd like to give a general overview of Ember, and pause to reflect on some important differences that may be important when considering what the best tool is for your project.

Writing Java EE microservices using WildFly SwarmComsysto Reply GmbH

Check out the talk to the slides: http://bit.ly/1ReY8uJ Talk Abstract: Using Swarm, you can select “just enough app server” to support each of your microservices. In this session, we’ll outline how WildFly Swarm works and get you started writing your first microservices using Java EE technologies you’re already familiar with. You’ll learn how to setup your build system (Maven, Gradle, or your IDE of choice) to run and test WildFly Swarm-based services and produce runnable jars. We will walk from the simple case of wrapping a normal WAR application to the more advanced case of configuring the container using your own main(…) method.

MVC 6 - the new unified Web programming modelAlex Thissen

Presentation for Dutch Microsoft TechDays 2015: With ASP.NET 5 comes MVC 6 with a programming model that unifies Web Pages, MVC and Web API. Each of these has been rebuilt to reflect Microsoft's vision of lean and composable web applications. In this session you will see the changes that have been made to the programming model. We will cover topics such as the new POCO controllers, View Components, dependency injection and much more. Plus, you are going to see the significant changes to the ASP.NET runtime on which MVC 6 is built.

Microservices: Yes or not?Eduard Tomàs

Introduction to WSO2 Developer Studio WSO2

This document provides an introduction to WSO2 Developer Studio presented by Susankha Nirmala and Susinda Perera, software engineers at WSO2. It discusses the features of WSO2 Developer Studio and WSO2 Carbon including service hosting, message mediation, data access, authentication, composing business processes, and more. It demonstrates how to use Developer Studio to create projects like Axis2 services, composite applications, ESB artifacts, and BPEL processes and deploy them to WSO2 servers.

Microservices with Spring Cloud, Netflix OSS and Kubernetes Christian Posta

An Unexpected Solution to Microservices UI CompositionDr. Arif Wider

This document describes a company's transition from a monolithic .NET application to a microservices architecture hosted on AWS. It details their use of a UI composition pattern using Nginx, ESI, and Jigsaw to compose fragments from different services into complete pages. This allows independent deployment of features while maintaining performance. Key aspects include caching of assets and responses, combining stylesheets and scripts, and isolation of services through separate CSS and JS packages.

From Web App Model Design to Production with WakandaAlexandre Morgaut

There is many interesting platforms out there to develop Web applications, like .NET, Spring, ruby on rails, Django, LAMP, Meteor, and so on. In this presentation, you will discover Wakanda a Model driven NoSQL / SSJS platform built on Web standards. You will see how a project starts, can be designed, tested, developed by a team, debugged, administrated, maintained, and then how to update it in the future. We will compare to some existing platforms and why Wakanda could make you more efficient.

Devoxx 2018 - Pivotal and AxonIQ - Quickstart your event driven architectureBen Wilcock

Devoxx Belgium 2018 - Let Pivotal and AxonIQ take you on a journey into Axon Trader. Axon Trader is a new open-source reference architecture that demonstrates how to use Spring, Axon and Pivotal Cloud Foundry to deliver evolutionary microservice applications to prod in minutes. The accompanying YouTube video can be found here: https://www.youtube.com/watch?v=15hzHUI4WNA

The Dark Side of Single Page ApplicationsDor Kalev

JavaCro'15 - Secure Web Services Development - Askar AkhmerovHUJAK - Hrvatska udruga Java korisnika / Croatian Java User Association

This document discusses securing web services using Apache CXF. It covers using SSL and X.509 certificates for encryption, developing a JAX-WS service, managing keystores, implementing WS-Security with CXF and WSS4J interceptors, encryption algorithms, security policies, and includes a demo and references. The agenda includes topics on the use case, SSL basics, the JAX-WS service, keystores, interceptors, encryption identifiers, algorithms, writing policies, and a question period.

React.js - and how it changed our thinking about UIMarcin Grzywaczewski

This document discusses React.js and how it changed the author's thinking about building user interfaces (UI). It describes how developing UI was previously slow, error-prone, and not fun using Handlebars templates, jQuery DOM manipulation, and redrawing on every change. React.js introduced a declarative and component-based approach that is faster, less error-prone, and more enjoyable. Components have properties (props) and state, re-render only when needed for performance, and can be reused and remain independent. This new approach to UI development freed the author to focus more on experimentation rather than fighting the framework.

Building a Web Frontend with Microservices and NGINX PlusNGINX, Inc.

Watch the webinar on demand at: nginx.com/resources/webinars/web-microservice-controlled-stateless-and-connected While many articles and books have been written about service design, there is a scarcity of information about how to integrate rich, user-experience-based web development onto a microservice-based application. In many respects the web frontend is the most complex part of the application, but it needs to scale and interface with your system just like any other microservice. The question is, how will your frontend system access your backend microservices? What will you do to make the frontend as stateless and ephemeral as the rest of your microservices? How will you provide your JavaScript application components with access to your microservices? Watch this webinar to learn how to: * Build your frontend using Model-View-Controller frameworks * Implement session state as a cached component in an attached resource * Use NGINX Plus routing and load balancing to give JavaScript access to microservices

Introducing the WSO2 Developer Studio Tools for SOA DevelopersWSO2

WSO2 Developer Studio is an Eclipse-based integrated development environment for building applications that run on WSO2 products like Carbon servers, Axis2, and Synapse. It contains tools for configuring enterprise architectures, including an ESB editor, registry tools, and data services editor. Developer Studio allows developers to develop, deploy, debug, and test applications both on-premise and in the cloud using full Maven integration. The document demonstrates Developer Studio by walking through building a hospital application that uses various WSO2 services.

Lap Around ASP.NET MVC 5Lohith Goudagere Nagaraj

ASP.NET vNextAlex Thissen

Presentation for Stichting DotNed in 2015: Microsoft neemt ASP.NET op de schop. Het web applicatie framework uit .NET 1.0 wordt grotendeels herschreven om te voldoen aan de eisen die men tegenwoordig stelt aan het realiseren van een moderne web applicatie. Deze sessie kijken we naar de nieuwe opzet van ASP.NET. We zien hoe Microsoft daarmee een cloud geoptimaliseerd, cross-platform framework creeert, dat zij zelf sneller kunnen laten evolueren door kortere release cycles. Dit alles betekent wel dat ASP.NET anders is geworden. In deze sessie leer je daarom ook wat er is veranderd, hoe je aan de slag gaat en waarom ASP.NET vNext een revolutionaire stap is in Microsoft's framework.

Introduction to Micronaut - JBCNConf 2019graemerocher

BIG DATA: From mammoth to elephantRoman Nikitchenko

You run your SQL-centric infrastructure for 10 years and slowly starting to note you can’t do this way anymore – everything is getting too expensive but your business requires things which are simply impossible without radical changes. This is exact situation we had 2 years before. So we’d like to show our experience: - Why and how we came into Big Data? - Why we choose Apache and Hadoop? - What to do and what is already done? - What lessons were learned? - Hadoop and relational databases: fight or synergy? - Reactive Big Data manifest.

X textВладимир Кожаев

More Related Content

What's hot (20)

WSO2Con USA 2015: End-to-end Microservice Architecture with WSO2 Identity Ser...WSO2

Full Stack Development With Node.Js And NoSQL (Nic Raboy & Arun Gupta)Red Hat Developers

ASP.NET: Present and futureHrvoje Hudoletnjak

Michael North "Ember.js 2 - Future-friendly ambitious apps, that scale!"Fwdays

Writing Java EE microservices using WildFly SwarmComsysto Reply GmbH

MVC 6 - the new unified Web programming modelAlex Thissen

Microservices: Yes or not?Eduard Tomàs

Introduction to WSO2 Developer Studio WSO2

Microservices with Spring Cloud, Netflix OSS and Kubernetes Christian Posta

An Unexpected Solution to Microservices UI CompositionDr. Arif Wider

From Web App Model Design to Production with WakandaAlexandre Morgaut

Devoxx 2018 - Pivotal and AxonIQ - Quickstart your event driven architectureBen Wilcock

The Dark Side of Single Page ApplicationsDor Kalev

JavaCro'15 - Secure Web Services Development - Askar AkhmerovHUJAK - Hrvatska udruga Java korisnika / Croatian Java User Association

React.js - and how it changed our thinking about UIMarcin Grzywaczewski

Building a Web Frontend with Microservices and NGINX PlusNGINX, Inc.

Introducing the WSO2 Developer Studio Tools for SOA DevelopersWSO2

Lap Around ASP.NET MVC 5Lohith Goudagere Nagaraj

ASP.NET vNextAlex Thissen

Introduction to Micronaut - JBCNConf 2019graemerocher

WSO2Con USA 2015: End-to-end Microservice Architecture with WSO2 Identity Ser...WSO2

Full Stack Development With Node.Js And NoSQL (Nic Raboy & Arun Gupta)Red Hat Developers

ASP.NET: Present and futureHrvoje Hudoletnjak

Michael North "Ember.js 2 - Future-friendly ambitious apps, that scale!"Fwdays

Writing Java EE microservices using WildFly SwarmComsysto Reply GmbH

MVC 6 - the new unified Web programming modelAlex Thissen

Microservices: Yes or not?Eduard Tomàs

Introduction to WSO2 Developer Studio WSO2

Microservices with Spring Cloud, Netflix OSS and Kubernetes Christian Posta

An Unexpected Solution to Microservices UI CompositionDr. Arif Wider

From Web App Model Design to Production with WakandaAlexandre Morgaut

Devoxx 2018 - Pivotal and AxonIQ - Quickstart your event driven architectureBen Wilcock

The Dark Side of Single Page ApplicationsDor Kalev

JavaCro'15 - Secure Web Services Development - Askar AkhmerovHUJAK - Hrvatska udruga Java korisnika / Croatian Java User Association

React.js - and how it changed our thinking about UIMarcin Grzywaczewski

Building a Web Frontend with Microservices and NGINX PlusNGINX, Inc.

Introducing the WSO2 Developer Studio Tools for SOA DevelopersWSO2

Lap Around ASP.NET MVC 5Lohith Goudagere Nagaraj

ASP.NET vNextAlex Thissen

Introduction to Micronaut - JBCNConf 2019graemerocher

Viewers also liked (8)

BIG DATA: From mammoth to elephantRoman Nikitchenko

X textВладимир Кожаев

Jee confValerii Moisieienko

The main topic of slides is building high availability high throughput system for receiveing and saving different kind of information with horizontal scalling possibility using HBase, Flume and Grizzly hosted on Amazon EC2 low cost instances. Talk describes HBase HA cluster setup process with useful hints and EC2 pitfalls, Flume setup process with providing comparasion between standalone and embedded Flume versions and show difference and usecases of both versions. A lot of attention payed to Flume2Hbase streaming features with tweaks and different approaches for speeding up this process.

Generics Past, Present and FutureRichardWarburton

Generics are one of the most complex features of Java. They are often poorly understood and lead to confusing errors. Unfortunately, it won’t get easier. Java 10, release planned for 2018, extends Generics. It’s now time to understand generics or risk being left behind. We start by stepping back into the halcyon days of 2004 and explain why generics were introduced in the first place back. We also explain why Java’s implementation is unique compared to similar features in other programming languages. Then we travel to the present to explaining how to make effective use of Generics. We then explore various entertaining code examples and puzzlers of how Generics are used today. Finally, this talk sheds light on the planned changes in Java 10 with practical code examples and related ideas from other programming languages. If you ever wanted to understand the buzz around declaration site variance now is your chance!

Spring data jee confEvgeny Borisov

Statis code analysischashnikov

Developers want to make very few errors in their code and to spot them as early as possible: with the help of unit tests, or earlier, during compilation, or best of all, immediately after they typed something wrong in their IDE. This is what static code analyzers are for. Some of them are built-in, others need to be run separately, some check just about any code, the others require it to be annotated first, and there are tools that are a little bit of all. Do the ends justify the means? Is it even worth trying? What kind of errors can be spotted by static code analysis? How sure can we be if what an analyzer gives us is a real error or a false positive? This talk hopefully helps you answer these questions.

Scala Rock-PaintingGlobalLogic Ukraine

Do we need JMS in 21st century?Mikalai Alimenkou

JMS is known as standard way to implement distributed work with messaging in Java world. There are many JMS providers, both open source and commercial. Large percent of developers use JMS for almost every case when they want to sent message and process it on the other side. But now there are many alternative solutions to organize message queues: AMQP, Redis, ZooKeeper, Apache Kafka or even custom solutions based on Cassandra. Why not to use them instead of JMS? In this talk we will discuss key “issues” in any messaging system and then with this knowledge in mind look once again at JMS and alternative approaches using practical cases from my experience. May be after this talk some more people will stop using JMS and start using their mind. :)

BIG DATA: From mammoth to elephantRoman Nikitchenko

X textВладимир Кожаев

Jee confValerii Moisieienko

Generics Past, Present and FutureRichardWarburton

Spring data jee confEvgeny Borisov

Statis code analysischashnikov

Scala Rock-PaintingGlobalLogic Ukraine

Do we need JMS in 21st century?Mikalai Alimenkou

Similar to Web application I have always dreamt of (20)

Web-application I have always dreamt of by Victor PolischukJavaDayUA

Web application I have always dreamt of (Lviv)Victor_Cr

Web-application I’ve always dreamt of (Kharkiv)Victor_Cr

The document discusses the evolution of web applications from static content in the prehistoric era to modern dynamic applications. It proposes an architecture where the client focuses on the user interface and holds all state, while the server is stateless and provides scalable endpoints. This approach aims to achieve scalability, security, testability, and optimization through principles like encapsulation, limiting interaction to essential data, caching, and incremental updates.

Building a serverless appVinay Krishna

This document discusses the shift from traditional server-based applications to serverless architectures in cloud computing. It notes that in pre-cloud days, developers had to manage servers, provision resources, plan for scaling and availability, and deal with maintenance, which required spending on hardware and staffing. The cloud reduced these burdens by providing on-demand virtual machines and abstracting away the hardware. Serverless computing takes this further by allowing developers to run code without managing servers or infrastructure, paying only for the resources required to run their code. It provides examples of scenarios well-suited for serverless computing and walks through building a sample serverless application and linking it to cloud APIs and services.

Scaling wix to over 70 m usersYoav Avrahami

This document summarizes Wix's scaling efforts from 2006 to 2014 to support over 70 million users on its website building platform. It describes Wix's initial architecture and challenges with downtime from server updates. It outlines Wix's migration to managed hosting on Amazon and Google Cloud to address scalability issues. The document also discusses Wix's shift to microservices, continuous integration/delivery, test-driven development, and DevOps practices to improve development velocity and allow faster feature rollouts. It provides details on Wix's adoption of Scala, Angular, React, Node.js and establishment of technology guilds to further its engineering capabilities as it scaled its platform globally.

Scaling wix to over 50 m usersYoav Avrahami

Over the first 8 years of Wix, Wix infrastructure has gone a number of transformations, starting as a monolithic application server with MySQL, evolving to a service based architecture with with diverse infrastructure. Over this 8 years journey, we have learned a thing or two - some DOs and some DON'Ts. This presentation goes over the evolution of Wix architecture, with the different transformations we have done to support Wix at scale. We will share some of out insights about building a web infrastructure for over 50M users

Best Practices for Web Infrastructure on Amazon Web ServicesBrett Gillett

This document outlines best practices for web infrastructure on Amazon Web Services (AWS). It discusses challenges companies face with web infrastructure, and how AWS services can help address those challenges. The document recommends starting with security, using the smallest instances needed and scaling horizontally, leveraging platform-as-a-service where possible, and using reserved instances when appropriate. It also covers lessons learned, such as understanding costs, managing reserved instances, keeping up with innovation, and monitoring for "drift" in AWS infrastructure over time. Finally, it describes services available through Softchoice to help customers get started with and manage their AWS infrastructure.

Can Your Mobile Infrastructure Survive 1 Million Concurrent Users?TechWell

When you’re building the next killer mobile app, how can you ensure that your app is both stable and capable of near-instant data updates? The answer: Build a backend! Siva Katir says that there’s much more to building a backend than standing up a SQL server in your datacenter and calling it a day. Since different types of apps demand different backend services, how do you know what sort of backend you need? And, more importantly, how can you ensure that your backend scales so you can survive an explosion of users when you are featured in the app store? Siva discusses the common scenarios facing mobile app developers looking to expand beyond just the device. He’ll share best practices learned while building the PlayFab and other companies’ backends. Join Siva to learn how you can ensure that your app can scale safely and affordably into the millions of concurrent users and across multiple platforms.

Cloud-native Datacornelia davis

<November 2017 Updated from earlier presentations on Cloud-native Data> Cloud-native applications form the foundation for modern, cloud-scale digital solutions, and the patterns and practices for cloud-native at the app tier are becoming widely understood – statelessness, service discovery, circuit breakers and more. But little has changed in the data tier. Our modern apps are often connected to monolithic shared databases that have monolithic practices wrapped around them. As a result, the autonomy promised by moving to a microservices application architecture is compromised. What we need are patterns and practices for cloud-native data. The anti-patterns of shared databases and simple proxy-style web services to front them give way to approaches that include use of caches (Netflix calls caching their hidden microservice), database per service and polyglot persistence, modern versions of ETL and data integration and more. In this session, aimed at the application developer/architect, Cornelia will look at those patterns and see how they serve the needs of the cloud-native application.

Cloud-Native-Data with Cornelia DavisVMware Tanzu

This document discusses cloud-native data and patterns for managing data in microservices architectures. It describes using data services and APIs to interface with existing data sources. Patterns like caching data at the edge with various caching strategies are discussed. The document also covers using multiple small databases with each microservice rather than a shared database. Event sourcing and CQRS patterns are presented as ways to integrate data across services. Finally, the impact on roles like database administrators is considered in cloud-native data environments.

Headless cms architectureKevin Wenger

This document discusses headless CMS architecture, including its pros and cons. A headless CMS separates the content management system from the presentation layer, allowing content to be delivered via API to any device. Benefits include frontend flexibility, improved user experience through animation and components, and ability to take advantage of new technologies. Challenges include increased dependencies, need for synchronous releases, building interfaces from scratch, and requiring more skills. The document also provides examples of implementing headless architectures with WordPress, Drupal, and Symfony. It stresses the importance of common documentation and avoiding issues in the development process.

Cloud-native Data: Every Microservice Needs a Cachecornelia davis

Presented at the Pivotal Toronto Users Group, March 2017 Cloud-native applications form the foundation for modern, cloud-scale digital solutions, and the patterns and practices for cloud-native at the app tier are becoming widely understood – statelessness, service discovery, circuit breakers and more. But little has changed in the data tier. Our modern apps are often connected to monolithic shared databases that have monolithic practices wrapped around them. As a result, the autonomy promised by moving to a microservices application architecture is compromised. With lessons from the application tier to guide us, the industry is now figuring out what the cloud-native architectural patterns are at the data tier. Join us to explore some of these with Cornelia Davis, a five year Cloud Foundry veteran who is now focused on cloud-native data. As it happens, every microservice needs a cache and this evening will drill deep on that topic. She’ll cover a variety of caching patterns and use cases, and demonstrate how their use helps preserve the autonomy that is driving agile software delivery practices today.

Top 10 web application development frameworks 2016iMOBDEV Technologies Pvt. Ltd.

Rise and Fall of the Frontend DeveloperRafael Casuso Romate

Un breve viaje por la concepción del Desarrollo de Aplicaciones Web desde el clásico patrón de Aplicaciones Web de Servidor con renderización en servidor e interactividad limitada en cliente a la reciente era de las Single Page Applications con renderización en cliente, foco en la interactividad y desacoplamiento del backend hasta llegar a los actuales patrones híbridos de renderización en cliente y servidor en busca de la mejor performance, la mejor experiencia de usuario y el mejor SEO.

From Monoliths to Services: Paying Your Technical DebtTechWell

This document discusses transitioning from monolithic applications to microservices and serverless architectures. It begins by defining technical debt and explaining how microservices can help pay it down incrementally. It then covers different architectural styles like monoliths and microservices. The rest of the document discusses moving to cloud infrastructure, breaking apart monolithic applications into independent services, communication between services, leveraging third-party services, and security considerations for microservices.

Surrogate dependencies (in node js) v1.0Dinis Cruz

Big ideas in small packages - How microservices helped us to scale our visionSebastian Schleicher

Blinkist started as a monolith application but transitioned to microservices as the business scaled. This allowed each part of the application to scale independently and improved development speed. Key learnings included only migrating existing features if it provided value, embracing AWS vendor lock-in while acting wisely, and building new features as microservices adhering to standards like JSON API. The monolith validated their product vision while microservices helped scale the business through a stable, automated infrastructure.

Microservices - opportunities, dilemmas and problemsŁukasz Sowa

A night at the spaChris Love

This is the slide deck to introduce important topics to developer to build great, high performance Single Page Web Applications. The slide deck is used to setup a review of the code and architecture in my demonstration movie web application used in my latest book. The site is live at http://movies.spawebbook.com and the source code is available on GitHub https://github.com/docluv/movies. Single page application are a new frontier to the web development world. They require a completely different mindset than classic, server-side heavy web development. Not only do developers need to understand modular JavaScript and the DOM API they also need to understand good responsive design practices, performance optimization, touch and a mobile first approach.

Tech io spa_angularjs_20130814_v0.9.5Ganesh Kondal

This document provides an overview of single page applications (SPAs) and AngularJS. It discusses why SPAs are useful, how they work, and key aspects of AngularJS like data binding, directives, routing, and dependency injection. Code samples are presented to demonstrate basic concepts like data binding, controllers, filters, and building an e-commerce application with routing and services. Future sessions are proposed to cover integration with Node.js backends, testing with Karma, and custom directives.

Web-application I have always dreamt of by Victor PolischukJavaDayUA

Web application I have always dreamt of (Lviv)Victor_Cr

Web-application I’ve always dreamt of (Kharkiv)Victor_Cr

Building a serverless appVinay Krishna

Scaling wix to over 70 m usersYoav Avrahami

Scaling wix to over 50 m usersYoav Avrahami

Best Practices for Web Infrastructure on Amazon Web ServicesBrett Gillett

Can Your Mobile Infrastructure Survive 1 Million Concurrent Users?TechWell

Cloud-native Datacornelia davis

Cloud-Native-Data with Cornelia DavisVMware Tanzu

Headless cms architectureKevin Wenger

Cloud-native Data: Every Microservice Needs a Cachecornelia davis

Top 10 web application development frameworks 2016iMOBDEV Technologies Pvt. Ltd.

Rise and Fall of the Frontend DeveloperRafael Casuso Romate

From Monoliths to Services: Paying Your Technical DebtTechWell

Surrogate dependencies (in node js) v1.0Dinis Cruz

Big ideas in small packages - How microservices helped us to scale our visionSebastian Schleicher

Microservices - opportunities, dilemmas and problemsŁukasz Sowa

A night at the spaChris Love

Tech io spa_angularjs_20130814_v0.9.5Ganesh Kondal

More from Victor_Cr (14)

Data Wars: The Bloody Enterprise strikes backVictor_Cr

Sometimes developers loss or corrupt their production data under different circumstances. Sometimes it happens because of badly chosen data types. Moreover, it is not always some complex types: we will talk about pain in the neck (and below) from strings, dates, and some numeric types in Java. If you have no clue how these simple and very well known guys can hurt you and your applications – welcome.

Data Wars: The Bloody Enterprise strikes backVictor_Cr

Type War: Weak vs Strong [JEEConf 2016]Victor_Cr

It is well known that languages with weak typing are weaker than strong-typed ones. People fight on the matter so often and so passionately like the zealots of the past. I would like to open the wound again and bring a bit of clarity why and, more importantly, how we have to fight those battles from now on. Let’s compare what we have in Java with other languages and feel the difference. Pragmatic one. I will show a bit of pain which, nowadays, a compiler takes away from a developer so the latter can “safely” code. Also I will try to answer the questions “which one is better” and “where are we going”. It is always fun to see how little you know and how much is behind the curtains.

Types: Weak/Duck/Optional vs Strong/Strict. Let the War Begin!Victor_Cr

You probably have participated many times in those battles which language is better. Sometimes you definitely have been using "weak/strict typing" definition. I would like to talk about it. It is too important to ignore. I want to compare several different languages and show you how delusional those "weak/strong" definitions. We will meet some math along with Javascript, Java, Scala, C++, .Net, Haskel and several others on the way to the truth. We will spill some blood and may lose some comrades but as a reward survivors will touch the future (a bit) of nextgen languages (let's name it as features of Java 40.0).

Types: Weak/Duck/Optional vs Strong/Strict. Let the War Begin!Victor_Cr

Legacy: как победить в гонке (Joker)Victor_Cr

У вас древний проект? Все зовут его «Legacy», а вас «неудачник»? Возможно они даже смеются над вами. Давайте взглянем на ситуацию с другого ракурса. Все (все, Карл!) успешные проекты рано или поздно превращаются в Legacy-проекты. Я затрону тему Legacy не просто как явление, а как возможность быть постоянно в тренде, прослыть супер-спецом (даже если ты знаешь всего два фреймворка), сделать карьеру, как делать, то что ты хочешь, а не то что тебя просят. Ладно, ладно, я наврал про два фреймворка, но все остальное чистая правда. Я покажу, что вы можете творить, имея правильный подход к Legacy коду.    Суть в том, что Legacy — это не грустно/уныло/немодно, это просто/клево/весело, если с умом подойти к задаче!

Legacy projects: how to win the raceVictor_Cr

Jboss drools expert (ru)Victor_Cr

JEEConf WEBVictor_Cr

JEEConf JBoss DroolsVictor_Cr

This document provides an overview of JBoss Drools, a business rules management system. It discusses key concepts like production rule systems, the Rete algorithm, and rule structure with left-hand side (LHS) and right-hand side (RHS). It also introduces components of the Drools platform like Drools Guvnor, Drools Expert, and Drools Flow. The presenter is Victor Polischuk who has over 10 years of software development experience including 2+ years using Drools.

JBoss DroolsVictor_Cr

The document describes how JBoss Drools can be used to model business rules and requirements by defining rules using a domain-specific language that can validate objects like orders against the defined rules. Drools provides features like declarative rule patterns, object mapping, functions, queries, and templates to define complex validation logic in a more readable way compared to implementing the same logic in Java. Drools also supports defining metadata, classes and integrating with a rules engine and working memory to efficiently execute rules on facts.

XPDays Ukraine: LegacyVictor_Cr

This document discusses refactoring legacy code projects. It begins by introducing the author and their experience with legacy projects. It then describes different types of legacy projects using nicknames. It discusses whether a project should be rewritten or refactored. It lists requirements needed for refactoring a legacy project. It compares a developer and customer perspective. It then provides examples of techniques that can be used when refactoring like building procedures, inversion of control, regular expressions, transaction management, and integrating incremental changes. The overall message is that refactoring legacy projects requires an open mindset, establishing trust between developers and customers, and taking problems step-by-step through small incremental changes.

Club of anonimous developers "Refactoring: Legacy code"Victor_Cr

The document discusses various approaches to refactoring legacy code, including: 1. Migrating from an older build system (TOM) to a newer one (POM) by updating XML configuration files. 2. Introducing inversion of control (IoC) and dependency injection (DI) to reduce tight coupling in the code. 3. Implementing aspect-oriented programming (AOP) to separate cross-cutting concerns like transaction management and exception handling. 4. Updating older libraries to newer versions for performance improvements and richer APIs. 5. Cleaning up messy and difficult to read code through techniques like extracting methods and using regular expressions.

Data Wars: The Bloody Enterprise strikes backVictor_Cr

Type War: Weak vs Strong [JEEConf 2016]Victor_Cr

Types: Weak/Duck/Optional vs Strong/Strict. Let the War Begin!Victor_Cr

Legacy: как победить в гонке (Joker)Victor_Cr

Legacy projects: how to win the raceVictor_Cr

Jboss drools expert (ru)Victor_Cr

JEEConf WEBVictor_Cr

JEEConf JBoss DroolsVictor_Cr

JBoss DroolsVictor_Cr

XPDays Ukraine: LegacyVictor_Cr

Club of anonimous developers "Refactoring: Legacy code"Victor_Cr

Recently uploaded (20)

Quantum Computing Quick Research Guide by Arthur MorganArthur Morgan

This is a Quick Research Guide (QRG). QRGs include the following: - A brief, high-level overview of the QRG topic. - A milestone timeline for the QRG topic. - Links to various free online resource materials to provide a deeper dive into the QRG topic. - Conclusion and a recommendation for at least two books available in the SJPL system on the QRG topic. QRGs planned for the series: - Artificial Intelligence QRG - Quantum Computing QRG - Big Data Analytics QRG - Spacecraft Guidance, Navigation & Control QRG (coming 2026) - UK Home Computing & The Birth of ARM QRG (coming 2027) Any questions or comments? - Please contact Arthur Morgan at [email protected]. 100% human made.

Splunk Security Update | Public Sector Summit Germany 2025Splunk

Cybersecurity Identity and Access Solutions using Azure ADVICTOR MAESTRE RAMIREZ

Linux Professional Institute LPIC-1 Exam.pdfRHCSA Guru

HCL Nomad Web – Best Practices und Verwaltung von Multiuser-Umgebungenpanagenda

Webinar Recording: https://www.panagenda.com/webinars/hcl-nomad-web-best-practices-und-verwaltung-von-multiuser-umgebungen/ HCL Nomad Web wird als die nächste Generation des HCL Notes-Clients gefeiert und bietet zahlreiche Vorteile, wie die Beseitigung des Bedarfs an Paketierung, Verteilung und Installation. Nomad Web-Client-Updates werden “automatisch” im Hintergrund installiert, was den administrativen Aufwand im Vergleich zu traditionellen HCL Notes-Clients erheblich reduziert. Allerdings stellt die Fehlerbehebung in Nomad Web im Vergleich zum Notes-Client einzigartige Herausforderungen dar. Begleiten Sie Christoph und Marc, während sie demonstrieren, wie der Fehlerbehebungsprozess in HCL Nomad Web vereinfacht werden kann, um eine reibungslose und effiziente Benutzererfahrung zu gewährleisten. In diesem Webinar werden wir effektive Strategien zur Diagnose und Lösung häufiger Probleme in HCL Nomad Web untersuchen, einschließlich - Zugriff auf die Konsole - Auffinden und Interpretieren von Protokolldateien - Zugriff auf den Datenordner im Cache des Browsers (unter Verwendung von OPFS) - Verständnis der Unterschiede zwischen Einzel- und Mehrbenutzerszenarien - Nutzung der Client Clocking-Funktion

Role of Data Annotation Services in AI-Powered ManufacturingAndrew Leo

Electronic_Mail_Attacks-1-35.pdf by xploitniftliyevhuseyn

Linux Support for SMARC: How Toradex Empowers Embedded DevelopersToradex

Toradex brings robust Linux support to SMARC (Smart Mobility Architecture), ensuring high performance and long-term reliability for embedded applications. Here’s how: • Optimized Torizon OS & Yocto Support – Toradex provides Torizon OS, a Debian-based easy-to-use platform, and Yocto BSPs for customized Linux images on SMARC modules. • Seamless Integration with i.MX 8M Plus and i.MX 95 – Toradex SMARC solutions leverage NXP’s i.MX 8 M Plus and i.MX 95 SoCs, delivering power efficiency and AI-ready performance. • Secure and Reliable – With Secure Boot, over-the-air (OTA) updates, and LTS kernel support, Toradex ensures industrial-grade security and longevity. • Containerized Workflows for AI & IoT – Support for Docker, ROS, and real-time Linux enables scalable AI, ML, and IoT applications. • Strong Ecosystem & Developer Support – Toradex offers comprehensive documentation, developer tools, and dedicated support, accelerating time-to-market. With Toradex’s Linux support for SMARC, developers get a scalable, secure, and high-performance solution for industrial, medical, and AI-driven applications. Do you have a specific project or application in mind where you're considering SMARC? We can help with Free Compatibility Check and help you with quick time-to-market For more information: https://www.toradex.com/computer-on-modules/smarc-arm-family

AI and Data Privacy in 2025: Global TrendsInData Labs

In this infographic, we explore how businesses can implement effective governance frameworks to address AI data privacy. Understanding it is crucial for developing effective strategies that ensure compliance, safeguard customer trust, and leverage AI responsibly. Equip yourself with insights that can drive informed decision-making and position your organization for success in the future of data privacy. This infographic contains: -AI and data privacy: Key findings -Statistics on AI data privacy in the today’s world -Tips on how to overcome data privacy challenges -Benefits of AI data security investments. Keep up-to-date on how AI is reshaping privacy standards and what this entails for both individuals and organizations.

Heap, Types of Heap, Insertion and DeletionJaydeep Kale

HCL Nomad Web – Best Practices and Managing Multiuser Environmentspanagenda

Webinar Recording: https://www.panagenda.com/webinars/hcl-nomad-web-best-practices-and-managing-multiuser-environments/ HCL Nomad Web is heralded as the next generation of the HCL Notes client, offering numerous advantages such as eliminating the need for packaging, distribution, and installation. Nomad Web client upgrades will be installed “automatically” in the background. This significantly reduces the administrative footprint compared to traditional HCL Notes clients. However, troubleshooting issues in Nomad Web present unique challenges compared to the Notes client. Join Christoph and Marc as they demonstrate how to simplify the troubleshooting process in HCL Nomad Web, ensuring a smoother and more efficient user experience. In this webinar, we will explore effective strategies for diagnosing and resolving common problems in HCL Nomad Web, including - Accessing the console - Locating and interpreting log files - Accessing the data folder within the browser’s cache (using OPFS) - Understand the difference between single- and multi-user scenarios - Utilizing Client Clocking

tecnologias de las primeras civilizaciones.pdffjgm517

The Evolution of Meme Coins A New Era for Digital Currency ppt.pdfAbi john

Mobile App Development Company in Saudi ArabiaSteve Jonas

EmizenTech is a globally recognized software development company, proudly serving businesses since 2013. With over 11+ years of industry experience and a team of 200+ skilled professionals, we have successfully delivered 1200+ projects across various sectors. As a leading Mobile App Development Company In Saudi Arabia we offer end-to-end solutions for iOS, Android, and cross-platform applications. Our apps are known for their user-friendly interfaces, scalability, high performance, and strong security features. We tailor each mobile application to meet the unique needs of different industries, ensuring a seamless user experience. EmizenTech is committed to turning your vision into a powerful digital product that drives growth, innovation, and long-term success in the competitive mobile landscape of Saudi Arabia.

Build Your Own Copilot & Agents For DevsBrian McKeiver

IEDM 2024 Tutorial2_Advances in CMOS Technologies and Future Directions for C...organizerofv

Designing Low-Latency Systems with Rust and ScyllaDB: An Architectural Deep DiveScyllaDB

Want to learn practical tips for designing systems that can scale efficiently without compromising speed? Join us for a workshop where we’ll address these challenges head-on and explore how to architect low-latency systems using Rust. During this free interactive workshop oriented for developers, engineers, and architects, we’ll cover how Rust’s unique language features and the Tokio async runtime enable high-performance application development. As you explore key principles of designing low-latency systems with Rust, you will learn how to: - Create and compile a real-world app with Rust - Connect the application to ScyllaDB (NoSQL data store) - Negotiate tradeoffs related to data modeling and querying - Manage and monitor the database for consistently low latencies

Massive Power Outage Hits Spain, Portugal, and France: Causes, Impact, and On...Aqusag Technologies

Generative Artificial Intelligence (GenAI) in BusinessDr. Tathagat Varma

Special Meetup Edition - TDX Bengaluru Meetup #52.pptxshyamraj55

Quantum Computing Quick Research Guide by Arthur MorganArthur Morgan

Splunk Security Update | Public Sector Summit Germany 2025Splunk

Cybersecurity Identity and Access Solutions using Azure ADVICTOR MAESTRE RAMIREZ

Linux Professional Institute LPIC-1 Exam.pdfRHCSA Guru

HCL Nomad Web – Best Practices und Verwaltung von Multiuser-Umgebungenpanagenda

Role of Data Annotation Services in AI-Powered ManufacturingAndrew Leo

Electronic_Mail_Attacks-1-35.pdf by xploitniftliyevhuseyn

Linux Support for SMARC: How Toradex Empowers Embedded DevelopersToradex

AI and Data Privacy in 2025: Global TrendsInData Labs

Heap, Types of Heap, Insertion and DeletionJaydeep Kale

HCL Nomad Web – Best Practices and Managing Multiuser Environmentspanagenda

tecnologias de las primeras civilizaciones.pdffjgm517

The Evolution of Meme Coins A New Era for Digital Currency ppt.pdfAbi john

Mobile App Development Company in Saudi ArabiaSteve Jonas

Build Your Own Copilot & Agents For DevsBrian McKeiver

IEDM 2024 Tutorial2_Advances in CMOS Technologies and Future Directions for C...organizerofv

Designing Low-Latency Systems with Rust and ScyllaDB: An Architectural Deep DiveScyllaDB

Massive Power Outage Hits Spain, Portugal, and France: Causes, Impact, and On...Aqusag Technologies

Generative Artificial Intelligence (GenAI) in BusinessDr. Tathagat Varma

Special Meetup Edition - TDX Bengaluru Meetup #52.pptxshyamraj55

Web application I have always dreamt of

1. Web-application I’ve always dreamt of @JEEConf 2015

2. Victor Polischuk Programming 26 Overall 32 Java 11 Web 11 Legacy 11 Professional 13 Has something to share

3. Overview http://zeroturnaround.com/rebellabs/top-4-java-web-frameworks-revealed-real-life-usage-data-of-spring-mvc-vaadin-gwt-and- jsf/

4. Prehistoric Era [...-1995] • Static content only • Interaction without server: Impossible Unthinkable • Server-side HTML adjustments

6. Medieval Era [1995-2005] • Static content mostly • Interaction without server: cached resources • Server-side HTML+CSS+JS adjustments • Frames as asynchronous data loading • Birth of: Servlet API JavaScript DHTML concept Flash Browser-compatibility hell RFC1925

8. Renaissance Era [2005-2010] • Static content with dynamic “whistles” • Interaction without server: simple functions • Server-side HTML+CSS+JS adjustments • Rising popularity of Rich Internet Applications • Birth of: jQuery DOJO AJAX and Comet

10. Modern Era [2010-...] • Internet of Things • Big Data • Cloud Computing • ???

11. Business Needs • Integration with anything: Mobile Mainframe Coffee machine • High availability: Hard to predict clients behavior • Data is the TOP priority: We make money out of it • Client’s satisfaction: Should be happier than those of our competitors

12. Idea • “All problems in computer science can be solved by another level of indirection” © David Wheeler • “Do One Thing and Do It Well” © Unix community

13. Idea

14. Client

15. Client

16. Server

17. Server

18. Business Needs • Integration with anything • High availability • Data is the TOP priority • Client’s satisfaction

19. Technical Needs • Scalability • Security • Testability • “Otherity”

20. Scalability • Server is just a bunch of endpoints • Independent client • State Client needs it Server doesn’t • SLA Way to Nine-Nines You do not want to lose clients, right?

21. …We Design

22. …We Imagine

23. …We Build

24. Security • Do you need it on each request? • Do you know how it works? • Do you think it is secure?

25. …Of Course

26. …Safe JSF

27. …Safe Cookies

28. …Strong Password

29. Testability • Server side: Unit Integration Contract [optional] Load & Performance • Client side: Unit Integration Contract [optional] Browser & Sanity

30. …Client

31. Responsibility • Client: Responsive User-friendly Pretty • Server: Scalable Fail-proof Redundant

32. Traffic • Reduce useless to none • De-increase useful: Increase volume Decrease size

33. Optimization • Client Caching Pre-fetching Incremental updates • Server: Caching Pre-fetching Incremental updates

34. Encapsulation • Both parties can have their own secrets

35. Polygamy • Is it moral if a client has many servers and vice versa?

36. Summary • Effectiveness: you have one job • Security: you are limiting interaction to minimum • Testability: test JSF page, I dare you! • State: -less server, -ful client • Elasticity/scalability: your data volume is growing • Network optimizations: you know what you send • Local optimizations: you know what you do • Many-to-many connections • SLA

37. Questions • Thank you

Web application I have always dreamt of

Recommended

More Related Content

What's hot (20)

Viewers also liked (8)

Similar to Web application I have always dreamt of (20)

More from Victor_Cr (14)

Recently uploaded (20)

Web application I have always dreamt of