Skip to content

Development tasks #2

@PhilAndrew

Description

@PhilAndrew

Website

Hot-reload

  • Hot-reload of ScalaJS code when the browser is refreshed
  • Hot-reload of some classes into the OSGi when they are re-compiled

jm Commands

  • jmRename Rename the MicroService name eg, from JMScalaJs to JMEmployment

Making it simple to get started with

  • Simple instructions on how to run a MicroService
  • A generator from a webpage which asks you questions and generates the MicroService for you
  • Compare with Spring boot and SPRING INITIALIZR https://start.spring.io/

Giter8

Docker

  • Docker image for each MicroService
  • Docker demo with Karaf with ability to run each of the MicroServices inside

Kubernetes

Metrics

  • Can show a metrics web page when even only just one service is started

MicroService Generator

  • Allows for adding Camel routes on webpage
  • Can copy an existing MicroService
  • Can merge multiple MicroServices to create a new one

Logging

  • Improve logging by adding log to file, not just the console
  • Centralized logging with logging to a remote server
  • Show logging in a web console

Deployment

  • Demonstrate scale out with many Vagranent environments https://www.vagrantup.com/
  • Demonstrate scale out with many Docker containers
  • Demonstrate single Karaf container running multiple Microservices at the same time
  • Use sbt-native-packager packages the Scala application to deploy it as a non-osgi unit with its dependencies
  • Easy deployment on Fabric8 https://fabric8.io/
  • Funktion for Fabric8 https://funktion.fabric8.io/

Streaming

Serverless integration

  • AWS Lambda deployments of small scripts from the MicroService

Build Automation

  • Can build and self-test on Travis and show the Travis icon on the github page for the build success

MicroService synchronization

  • Synchronize N to N MicroServices when jmSync run
  • Can Java code be more easily synchronized via https://github.com/xai/jdime
  • jmSync to be able to sync build.sbt file by looking at blocks of code

File watching

  • Adjust jmSync to use file watching to trigger the synchronization process

???

  • Continuous Integration/Continuous Delivery
  • Deployment control
  • DevOps workflows
  • Performance monitoring (ZipKin)
  • Security
  • Service Discovery
  • Scalability
  • Fault tolerance - how will it handle failures of its dependencies
  • Fault tolerance - How will the rest of the system handle the failure of the new microservice
  • Upgrade of MicroServices at runtime
  • Monitoring and measuring
  • Rapid provisioning

Demonstrations

  • JavaCV computer vision
  • Google Cloud Vision API
  • Amazon Web Services
  • JavaCV find lines of symmetry in images where the image could be folded and pixels match
  • ?

Integrations

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions