@KileNiklawski with @IpponUSA presents on how we built a job board in one week using JHipster.
About JHipster:
Our goal is to generate for you a complete and modern Web app, unifying:
- A high-performance and robust Java stack on the server side with Spring Boot
- A sleek, modern, mobile-first front-end with AngularJS and Bootstrap
- A powerful workflow to build your application with Yeoman, Bower, Grunt and Maven
JHipster is a widely used and exponentially growing platform to create Angular + Spring web applications and micro services. We recently started working on adding react support for JHipster and in this quick session, we would like to showcase the Beta version and show how to generate full-fledged React apps with JHipster.
Victor introduces Swagger, an open-source framework for describing, producing, consuming, and visualizing RESTful APIs. Swagger allows API developers to describe the structure of APIs, including operations and models, using JSON or YAML files. It also generates documentation from these files and allows for testing API operations in interactive documents.
This document provides an overview and introduction to React Native, including:
- What React Native is and the problems it solves like enabling cross-platform development using a single JavaScript codebase.
- The technologies that comprise React Native like ReactJS and how it binds to native platforms.
- Getting started with a basic React Native app and examples of extending it with custom modules.
- An overview of the React Native component library and APIs.
- Recommendations to get familiar with related technologies like JSX, Flow, and Node.js.
- Thoughts on the benefits and challenges of developing with React Native.
This document discusses GitHub Actions for continuous integration and continuous delivery (CI/CD). It provides an overview of GitHub Actions, why they are useful, core concepts, and pricing. The key points are: GitHub Actions allow automating workflows from development to production using Linux, Windows, and macOS runners. They offer built-in secrets management, matrix builds, multi-container testing, and live logs. Pricing is free for public repositories and includes a generous monthly allowance for private repositories. The presenter then demonstrates GitHub Actions in a live demo.
This document discusses using GitHub Actions for continuous integration and continuous delivery (CI/CD) workflows. It begins with an introduction and agenda, then discusses the basics of GitHub Actions including what problems it solves and why CI/CD is important. Several key aspects of GitHub Actions are then covered at a high level, including how it compares to AWS CodePipeline, examples of GitHub workflows, and the core components of actions, artifacts, events, jobs, runners, steps, and workflows. The document concludes with an overview of creating a GitHub Actions workflow and exploring further possibilities.
The document discusses React Native for Android. It covers topics like React Native, JavaScript environment, ES6 syntax, JSX syntax, Node.js/NPM, React, rendering, debugging, running demos, delivering packages, examples, performance considerations, and what can be learned from building cross-platform mobile apps with React Native. Building native mobile apps for both iOS and Android from the same codebase allows shipping updates faster and reusing code, though it also has challenges to overcome.
Using GitHub Actions to Deploy your Workloads to AzureKasun Kodagoda
This presentation provides an introduction to GitHub Actions and the core concepts of GitHub Actions. Then dives into details about how you can use GitHub Actions for Azure to deploy your workloads to Azure Cloud Platform.
GitHub Actions is an automation platform for GitHub repositories that allows users to build workflows to automate software tasks. It was introduced in 2019 and is based on Azure Pipelines. Workflows are configured using YAML files and can be triggered by events like push commits, pull requests, or scheduled times. Actions, which are reusable code components, can be used in workflows and are sourced from the GitHub marketplace or created by users. GitHub Actions is free for public repositories and offers paid plans for private repositories.
Get Hip with JHipster: Spring Boot + AngularJS + Bootstrap - GeekOut 2016Matt Raible
Building a modern web (or mobile) application requires a lot of tools, frameworks and techniques. This session shows how JHipster unites popular frameworks like AngularJS, Spring Boot and Bootstrap. Using Yeoman, a scaffolding tool for modern webapps, JHipster will generate a project that uses Java 8, SQL or NoSQL databases, Spring profiles, Maven or Gradle, Gulp.js, WebSockets and BrowserSync. It also supports a number of different authentication mechanisms: classic session-based auth, OAuth 2.0, or JWT. For cloud deployments, JHipster includes out-of-the-box support for Cloud Foundry and Heroku.
GitHub Actions allows developers to build automated workflows to build, test, and deploy code. It consists of triggers that initiate workflows containing jobs made up of individual steps or actions. Current GitHub Actions for Power Platform include actions for cloning, packing, and importing Power Apps solutions using a Windows runner and the Power Apps CLI. The documentation, an Actions lab, and demo repos are resources for learning more about Power Platform GitHub Actions.
This document discusses setting up a CI/CD pipeline using GitHub Actions. It begins with an introduction to CI/CD pipelines and their importance. It then provides an overview of GitHub Actions and how they can be used to automate builds, tests, releases and deployments. The document demonstrates a sample GitHub Actions workflow file and explains its key components like jobs, steps and actions. It also covers topics like workflow events, jobs and steps/actions that can be used in GitHub Actions.
Focus on what matters: code
How to use and develop a GitHub Actions workflow using Node.js
With GitHub Actions (https://github.com/features/actions) you can automate your workflow from idea to production.
Actions can be written in any language, but we will take a closer look in how to write our workflow using Node.js and interact with the full GitHub API.
Während das JDK 8 auf März 2013 verschoben wurde, arbeitet das JDT-Team bei Eclipse mit Hochdruck an der Unterstützung für Java 8. In dieser Session demonstrieren wir anhand von Live-Coding den aktuellen Stand des Java-8-Toolings in Eclipse, natürlich inklusive der vielen kleinen nützlichen Content Assists, Quick Fixes und Refactorings.
1. The document discusses the author's experience with native iOS development and introduces React Native as a way to write mobile apps using JavaScript instead of Objective-C or Swift.
2. It provides an overview of how React Native works by using JavaScriptCore and Node.js to render components while allowing developers to use familiar Flexbox syntax for layouts instead of Autolayout.
3. The author demonstrates how to install React Native, create a basic app, add components and styles, and use tools like the Inspector and Perf Monitor.
Веб-технологии продолжают штурмовать мир мобильных устройств, а React Native - очередная попытка JavaScript распространить свое влияние и захватить мир.
Для тех, кто что-то слышал о React Native, но все никак не находил времени попробовать. На семинаре мы попробуем, пощупаем, посмотрим.
Angular vs React Smackdown - Devoxx BE 2017Matt Raible
This talk discusses the pros and cons of Angular and React and shows how they're similar, as well as how they're different. Deepu defends React, Matt defends Angular. We'll even show you the same app created with React and Angular via JHipster.
YouTube: https://youtu.be/qYEEuiI4l10
Example projects are on GitHub:
Angular: https://github.com/hipster-labs/devoxx17-jh-angular
React: https://github.com/hipster-labs/devoxx17-jh-react
And they're deployed to Heroku:
Angular: https://devoxx-17-angular.herokuapp.com/
React: https://devoxx-17-react.herokuapp.com/
In this talk we will learn how to use GitHub Actions to define the steps of your CI/CD process as containers. Additionally, we will use a tool called "act" to validate the CI/CD workflow by running the containers locally for fast feedback.
This document discusses software architecture patterns for iOS applications. It compares approaches like MVC, MVP, and MVVM, as well as concepts like dependency injection and clean architecture. It also provides references to additional resources on these topics, including links to slide presentations and articles about iOS application design.
The document discusses best practices for building microservices including:
- Focus on rapid development of features over infrastructure optimization.
- Deploy prototypes and experiments quickly using serverless architectures with auto-scaling and zero server management.
- Design microservices as independent, stateless services that communicate asynchronously through a service bus.
- Instrument services with logging and metrics to monitor performance and observe issues.
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.
This presentation will be useful to those
who would like to get acquainted with lifetime history
of successful monolithic Java application.
It shows architectural and technical evolution of one Java web startup that is beyond daily coding routine and contains a lot of simplifications, Captain Obvious and internet memes.
But this presentation is not intended for monolithic vs. micro services architectures comparison.
This document provides an agenda and information for moving a website project to Bluemix. It discusses setting up a local development environment, using JSON and REST APIs, and introduces Project 3 which involves adding a database and chatbot to an existing website project. Students are asked to deploy their Project 2 website to Bluemix, set it up locally, and submit links to the Bluemix site and GitHub repository for homework.
Jeremy Tammik, Forge Program Development
Combine the Forge Data Management, Model Derivative and Viewer APIs with REST and socket.io to implement a real-time round-trip BIM editor. Selected data only! Free choice!
Vasudeo Rao Vaka has over 5 years of experience developing Microsoft technologies such as SharePoint 2013, 2010, ASP.NET, C#, SQL Server, and InfoPath. He has experience on projects involving requirements gathering, design, development, testing, and implementation. He is proficient in technologies like JavaScript, jQuery, and has experience customizing SharePoint sites for various clients in industries like banking, insurance, and utilities. He is Microsoft certified and has worked on projects of various sizes as both an individual contributor and team member.
Drew Madelung will give a presentation on SharePoint Designer workflows at an online conference on June 17-18, 2015. He will discuss the evolution of SharePoint Designer, upgrading workflows from 2010 to 2013, new and deprecated workflow features between versions, and provide examples of workflows including tasks, stages, and using REST services. The presentation will also cover tips for custom actions, debugging workflows, and recommend some good starting workflow ideas.
UX Week 2007: CNN.com Relaunch Case StudyAdaptive Path
The document summarizes CNN's relaunch of their website CNN.com in 2007. It describes the multi-step process they took which included discovery research, defining design principles, creating prototypes, gathering user feedback, implementing the new site, and conducting a public beta test. The relaunch process spanned over a year and involved cross-functional teams working to modernize the site and improve the user experience based on new technologies and changing user behaviors.
Presentation about Oracle Application Express - getting started to getting productive. Check out http://bdb.intelivideo.com for a full ApEx education for just $49.99!!!!
Envision IT - Application Lifecycle Management for SharePoint in the EnterpriseEnvision IT
SharePoint has become mission critical, complex, and wide-ranging in most enterprises. How do we apply the best practices of ALM in this environment?
Learn more from this presentation, delivered by Envision IT, Leaders in SharePoint Solutions
Introduction to angular with a simple but complete projectJadson Santos
Angular is a framework for building client applications in HTML, CSS and TypeScript. It provides best practices like modularity, separation of concerns and testability for client-side development. The document discusses creating an Angular project, generating components, binding data, using directives, communicating with backend services, routing between components and building for production. Key steps include generating components, services and modules, binding data, calling REST APIs, defining routes and building the app.
This curriculum vitae is for Vishal Laljeet, an Indian national born in 1990 who specializes in DevOps with over 3 years of experience. He has worked as a Java developer, CI/CD developer, and UI developer. He has extensive experience in CI/CD pipelines using tools like Jenkins, Nexus, Artifactory, and Sonar. He has worked on projects involving Java, Spring, databases, testing, and DevOps skills including Docker, AWS, and monitoring tools.
Replace Angular with React. Make the move from the MEAN stack to the powerful MERN Stack!
Come and learn about the MERN stack. No, that isn't a typo. The MERN stack is Mongo, Express, and Node, with React instead of Angular. While both React and Angular are remarkable JavaScript technologies, React comes with less baggage. There is no TypeScript, no annotations, no bossy framework telling you how to do everything.
This document provides an overview of Project Server 2013 for SharePoint architects. It discusses the architecture of Project Server, including how it is implemented as a service application with various Windows services. It highlights key features like portfolio analysis, task aggregation across systems, and workflows. The document also reviews changes in Project Server 2013 like Active Directory synchronization improvements and database consolidation. It discusses options for training and certification and announces an upcoming Project Server conference.
Architecting for Huper Growth and Great Engineering CultureSARCCOM
Architecting for Huper Growth and Great Engineering Culture
by Ifnu Bima
@SARCCOM MEETUP
http://sarccom.org
https://www.meetup.com/Software-Architect-Indonesia
Architecting for Hyper Growth and Great Engineering Cultureifnu bima
The document discusses architecting for hyper growth and great engineering culture at a software company. It summarizes:
1) The goals are to support hyper growth year over year while fostering innovation and fast iteration through software architecture choices.
2) As a software architect, responsibilities include designing architectures around choices like monoliths vs microservices and databases, picking platforms and libraries, and setting hiring standards.
3) Architectural priorities are speed, performance, scalability, security and code quality to support the goals and customer experiences.
Introduction to cypress in Angular (Chinese)Hong Tat Yew
Cypress framework is a JavaScript-based end-to-end testing framework built on top of Mocha – a feature-rich JavaScript test framework running on and in the browser, making asynchronous testing simple and convenient. Cypress is like Protractor for Angular. In this talk, we will talk about how to write cypress test from scratch and some best practice.
Rohit Kamboj is a senior systems engineer at Infosys with over 8 years of experience. He has extensive skills in Microsoft technologies including SharePoint, C#, ASP.NET, and SQL Server. He has led several projects involving development on the SharePoint platform to automate processes and build custom applications. His role includes gathering requirements, designing solutions, developing code, and testing implementations.
Amsterdam Titanium User Group - Cloud Services for Apps Nov 2013Aaron Saunders
This document summarizes a presentation on cloud services for mobile apps. It discusses various cloud service providers like Parse, Stackmob, and Kinvey that provide features like user management, push notifications, and file storage. It recommends using these services to build MVPs quickly and leverage JavaScript and Appcelerator Cloud Services (ACS) for cross-platform development. Implementing ACS in an Alloy sync adapter is demonstrated to sync models to the cloud. The presentation concludes by advertising a forthcoming book on using ACS and Alloy.
Similar to How we built a job board in one week with JHipster (20)
Predicting Test Results without Execution (FSE 2024)andrehoraa
As software systems grow, test suites may become complex, making it challenging to run the tests frequently and locally. Recently, Large Language Models (LLMs) have been adopted in multiple software engineering tasks. It has demonstrated great results in code generation, however, it is not yet clear whether these models understand code execution. Particularly, it is unclear whether LLMs can be used to predict test results, and, potentially, overcome the issues of running real-world tests. To shed some light on this problem, in this paper, we explore the capability of LLMs to predict test results without execution. We evaluate the performance of the state-of-the-art GPT-4 in predicting the execution of 200 test cases of the Python Standard Library. Among these 200 test cases, 100 are passing and 100 are failing ones. Overall, we find that GPT-4 has a precision of 88.8%, recall of 71%, and accuracy of 81% in the test result prediction. However, the results vary depending on the test complexity: GPT-4 presented better precision and recall when predicting simpler tests (93.2% and 82%) than complex ones (83.3% and 60%). We also find differences among the analyzed test suites, with the precision ranging from 77.8% to 94.7% and recall between 60% and 90%. Our findings suggest that GPT-4 still needs significant progress in predicting test results.
In the bustling tech hub of Coimbatore, businesses are rapidly adopting Enterprise Resource Planning (ERP) software to stay competitive. As the textile capital of South India evolves into a major IT center, the demand for robust ERP solutions has skyrocketed.
InflectraCON 360: Risk-Based Testing for Mission Critical SystemsInflectra
Mission-critical systems demanded unwavering reliability. But in the face of tight deadlines and limited resources, how did Quality Engineering teams ensure comprehensive testing without sacrificing speed?
In this webinar, experts Adam Sandman and Ben Johnson-Ward delved into the world of risk-based testing, sharing strategies honed from their experience with high-stakes software. Attendees discovered how to prioritize testing efforts, targeting areas most likely to harbor critical bugs and prevent catastrophic failures.
Key takeaways:
• Strategic prioritization: The webinar explored how to identify and focus on the most critical components of complex systems.
• Streamlined testing: Experts shared insights on optimizing test generation to maximize coverage while minimizing wasted effort.
• Continuous improvement: The session covered how to integrate risk assessment throughout the development lifecycle for ongoing quality assurance.
• Real-world insights: Attendees gained valuable lessons from industries where software failures had life-or-death consequences.
Whether participants are developing medical devices, financial software, or any other mission-critical application, this webinar equipped them with the knowledge and tools to build quality into every step of their process.
Test Polarity: Detecting Positive and Negative Tests (FSE 2024)andrehoraa
Positive tests (aka, happy path tests) cover the expected behavior of the program, while negative tests (aka, unhappy path tests) check the unexpected behavior. Ideally, test suites should have both positive and negative tests to better protect against regressions. In practice, unfortunately, we cannot easily identify whether a test is positive or negative. A better understanding of whether a test suite is more positive or negative is fundamental to assessing the overall test suite capability in testing expected and unexpected behaviors. In this paper, we propose test polarity, an automated approach to detect positive and negative tests. Our approach runs/monitors the test suite and collects runtime data about the application execution to classify the test methods as positive or negative. In a first evaluation, test polarity correctly classified 117 tests as as positive or negative. Finally, we provide a preliminary empirical study to analyze the test polarity of 2,054 test methods from 12 real-world test suites of the Python Standard Library. We find that most of the analyzed test methods are negative (88%) and a minority is positive (12%). However, there is a large variation per project: while some libraries have an equivalent number of positive and negative tests, others have mostly negative ones.
TEQnation 2024: Sustainable Software: May the Green Code Be with Youmarcofolio
In a galaxy not so far away, software development is taking on an eco-friendly twist! Join me for a journey into the world of Green Software Development, where we explore how the Force of sustainability can be harnessed to create a better, greener future for software and the planet.
We'll fly away to various topics, including:
- The Green Side of Code: Discover the fundamental principles of Green Software Development and how they can lead to reduced energy consumption, lower carbon footprints, and more environmentally responsible software.
- Eco-Jedi Tools: Explore the tools and techniques at the heart of Green Software Development, including energy-efficient coding practices and sustainable development methodologies.
- Carbon Emissions and the Dark Side: Learn about the environmental impact of software and how we can combat the "Dark Side" of excessive energy consumption with eco-conscious programming.
- Ewoks vs. Energy Efficiency: Are you building your software like the energy-efficient Ewoks or the resource-hungry Death Star?
- The Path to a Greener Future: We'll discuss the challenges and opportunities ahead on our journey toward a more sustainable software galaxy and how you can be a part of it.
Join me for an engaging and informative presentation where we combine the power of technology and the wisdom of the Jedi to bring balance to the software development Force. Together, we'll ensure that the code is green, and our planet is preserved for generations to come. May the Green Code Be with You!
PathSpotter: Exploring Tested Paths to Discover Missing Tests (FSE 2024)andrehoraa
When creating test cases, ideally, developers should test both the expected and unexpected behaviors of the program to catch more bugs and avoid regressions. However, the literature has provided evidence that developers are more likely to test expected behaviors than unexpected ones. In this paper, we propose PathSpotter, a tool to automatically identify tested paths and support the detection of missing tests. Based on PathSpotter, we provide an approach to guide us in detecting missing tests. To evaluate it, we submitted pull requests with test improvements to open-source projects. As a result, 6 out of 8 pull requests were accepted and merged in relevant systems, including CPython, Pylint, and Jupyter Client. These pull requests created/updated 32 tests and added 80 novel assertions covering untested cases. This indicates that our test improvement solution is well received by open-source projects.
Fix Production Bugs Quickly - The Power of Structured Logging in Ruby on Rail...John Gallagher
Rails apps can be a black box. Have you ever tried to fix a bug where you just can’t understand what’s going on? This talk will give you practical steps to improve the observability of your Rails app, taking the time to understand and fix defects from hours or days to minutes. Rails 8 will bring an exciting new feature: built-in structured logging. This talk will delve into the transformative impact of structured logging on fixing bugs and saving engineers time. Structured logging, as a cornerstone of observability, offers a powerful way to handle logs compared to traditional text-based logs. This session will guide you through the nuances of structured logging in Rails, demonstrating how it can be used to gain better insights into your application’s behavior. This talk will be a practical, technical deep dive into how to make structured logging work with an existing Rails app.
I talk about the Steps to Observable Software - a practical five step process for improving the observability of your Rails app.
Fix Production Bugs Quickly - The Power of Structured Logging in Ruby on Rail...
How we built a job board in one week with JHipster
1. HOW WE BUILT A JOB BOARD
IN ONE WEEK WITH JHIPSTER
Kile Niklawski
Ippon Technologies
2. Who am I?
• Software Engineer/Architect and technology enthusiast
• A decade of experience - mostly Java
• Worked with various start-ups and large insurance,
finance, and government clients
• Working for Ippon as a Software Architect
kniklawski@ipponusa.com
@KileNiklawski
3. Ippon Technologies
• 200 software engineers in France and the US
➡ Paris, Nantes, Bordeaux
➡ Richmond (Virginia), Washington (DC)
• Expertise
➡ Digital, Big Data and Cloud
➡ Java, Open-source, Agile
• Open-source Projects :
➡ JHipster,
➡ Tatami …
• @ipponusa
3
4. Requirements
• Job Board Site MVP
• Three types of users: Company, Recruiter, Candidate (job seeker)
• Company can register and then post jobs
• Recruiter can login and search for applicants
• User can login and search for jobs
• You have one week!
• 1 Product Owner
• 1 Developer
• 1 Scrum Master
5. What is JHipster?
• Open Source
• Yeoman app generator
• Creates a full stack Java based web app
• Uses Maven/Gradle, Grunt, Bower, Spring and AngularJS
• Spring Boot
• Responsive UI (HTML5/CSS3/Bootstrap)
• Spring Data JPA backend
• Security is wired up
• Caching built-in, log management, monitoring, API docs
7. Writing User Stories
• Candidate
• I want to log in, build a profile and be able to search and apply to
jobs easily
• Recruiter
• I want to log in, build a personal and company profile
• I want to be able to post jobs
• I want to be able to view the applicants for a job
• I want to search the candidate pool to find a good match
• SysAdmin
• I want to be able to monitor the status of the server, the application’s
services and be able to interact with the REST API
• I want to be able to change the log levels from the browser
• Partner
• I want to pull candidates, jobs and companies using a REST API
10. Get it Running
• Created the UML diagram using Modelio
• Exported model in XMI
• Imported XMI using jhipster-uml tool
• Now run it!
• mvn clean install
• mvn spring-boot:run
13. Cloud Time
• Wanted to use heroku but had to install Elasticsearch to a
local server in order to keep it free
• Installed the heroku CLI
• One-time setup for deployment
• heroku login
• yo jhipster:heroku
• Every deployment
• mvn clean install –Pprod
• heroku deploy:jar –jar target/boardatjob.war
14. UI
• Borrowed a few hours from a UI designer for a look-and-
feel
• Chose to use the Compass CSS Authoring Framework
• Replaced the main.scss file with the custom CSS from the
designer
• Modified some image paths and added images
• Copied the designer’s home page into the main.html
• Separated common elements into the navbar template and
created a new header template
16. Candidate Features
• Added a new listing template for the front page, tied in
Elasticsearch, added the job and company detail pages
• Very little backend work required – mostly HTML and AngularJS
• Needed to sort the job listings
• Had to modify a date field on the job object and add a liquibase
changeset
• Modified the REST controller to pass the sort criteria to Spring Data
• Needed pagination (infinite scroll)
• JHipster provides infinite scrolling but we did not select it
• So we generated a new JHipster project with infinite scroll and
borrowed from that
21. Coverage and Static Analysis
• Updated the Sonar version in the pom.xml
• Ignored library files during analysis
• Consolidated test reports in the same directory
• Added code coverage for Java using Jacoco
• Added code coverage for AngularJS using Karma
• Would like to see these generated by JHipster
• Run the analysis:
• mvn clean install
• grunt test
• mvn sonar:sonar
22. Faceted Search
• How do we implement this?
• Elasticsearch supports faceted search but not sure how to
get the information with the Spring Data Elasticsearch
library (display job counts by location)
• Let’s move on!
23. User Profile
• Added a user profile entity to support additional fields
• Design choice versus modifying the existing user entity generated
by JHipster
• User profile is related by unique login id to the user entity
• Modified registration to create a user profile
• Modified the settings page to support additional fields for
user profiles
• Found a minor bug in JHipster where refreshing the page
caused the user to lose his roles
• Already fixed!
• Added storing of résumés as a blob in the user profile
• Added a REST resource for upload/download requests
• Used an AngularJS library for drag-and-drop uploads
25. Recruiter Features
• Created a company page for the recruiter
• Created pages to submit and review job listings
• Added a list of job applications for listings submitted by the
recruiter to the home page
• Added ability to review the cover letter and candidate
contact information
• Added ability to download a candidate’s résumé
31. Candidate Features
• Modified the user profile screen to add fields and support
résumé uploads
• Added screen for applying for a job and adding a cover
letter
36. MVP
• Signed up for a free SendGrid account and configured the
sendmail settings in the application.yml file
• Focused most of the day on fixing bugs
• Believe it or not, some bugs still exist
38. What Did We Get?
• How long does it take to get a new project up and running?
• Started adding features on Day 1
• Scaffolding was generated
• Deployed initial app to the cloud on Day 1
• Can we modify the generated code?
• Modern and clean organization
• Easily added 3rd party libraries with bower and maven
• A prototype that can be turned into a real, scalable
production application
39. References
• JHipster Site
• https://jhipster.github.io/
• White Paper
• http://www.ipponusa.com/whitepaper/jhipster-for-techies-hipster-
developer-diary/
• JHipster Demo
• http://www.ipponusa.com/blog/jhipster-demo/