• NEJUG Annual Business Meeting

    Attending: 5
    Start Time:

    Jul 12, 2018 6:00 PM

    End Time:

    Jul 12, 2018 8:00 PM

    Location:
    Constant Contact Reservoir Place
    1601 Trapelo Road Waltham MA 021451
    25 Spots available

    Every July, the NEJUG Production Team (formerly known as the NEJUG Advisory Group) gathers to discuss various business items. The meeting is open to all members, as usual, there will be food and drinks. Meeting format, however, will be different. There will be no external/guest speakers, rather, there will be roundtable discussions by NEJUG production team members.



NEJUG Calendar

Recent Events
  • As Java developers, we have long understood the value of early feedback, unit testing, and Continuous Delivery (CD). As practitioners in a DevOps environment, we tell others how important these practices are. How well do we implement these practices for software intended for DevOps applications? Do we “eat our own dogfood”? In this presentation, I will review an approach taken to apply Continuous Delivery practices with a Java application that creates Jenkins Pipelines.   After hearing the presentation, I hope you will walk away with some ideas on how to implement your Java CD practices in a broader context. 

    Kotlin and Category Theory: Pragmatic Functional Programming 
    by Craig Lubin

    What is Functional Programming (FP) and why should you care? This presentation will provide a simple (but not simplistic) introduction of the science behind both Functional Programming and Category Theory by using simple mathematical concepts and the Kotlin programming language. I will show how to apply these techniques for error handling, IO, and more AND how these techniques can also work in Java (it's not just a "Kotlin thing").
    No prior knowledge of Kotlin or advanced mathematics is required. 

     

     

    • Refactoring Existing Java Code


      Thursday April, 12, 2018 06:00 PM
      Constant Contact Reservoir Place
      1601 Trapelo Road Waltham MA 021451
      2

    When should you refactor code and when should you not do it?  How do you make sure you have adequate test case coverage?  What are the strategies, techniques, and patterns for refactoring existing code?  And how do you get your boss to agree to let you spend the time to refactor code?  This presentation will cover these questions and more.  Topics covered include Acceptance/Approval Testing, Design Patterns, Code Smells, Refactorings, and Tools.

     

    For a deeper dive into related topics of Mob Programming, TDD, and software craftsmanship, join Ethan at the Mob Programming Conference April 12-13 in Burlington, MA.  Several of the presentations are on refactoring.

     

  • Ten steps methodology for designing superior Cloud Native RESTFul Microservices APIs

    In most of the Monolithic applications business objects and data, model designs are already present. As part of moving to cloud, companies miss out of the use-cases the REST APIs need to support. Implementing cloud solutions on top of existing models may lead to performance issues with APIs and cause scalability issues. Clients need to rewrite code due to a new version of APIs.

     

    In this talk, we will explore ten steps methodology for designing superior Cloud Native RESTFul Microservices APIs. Firstly, define the business domain objects and how they relate to use cases. If the use-case is to support <500 ms response time and availability of 99.99%, design the application for Consistency, Availability, and Partition tolerant. Next, Create an ideal design which solves the use-cases, refer to the industry standard JSONs and designs from schema.orgiana.org, and ​microformats.org. Later, find the fail points in the process and go back to the first step to resolving the pain points: Go back to Define the problem. Question to ask is what can go wrong? When can it go wrong? Next, create Facade pattern to connect to either existing Monolithic App or create a new App to support the new cloud use-cases. Create API Gateway, so other companies can build software and create more offerings. Next, design common Layers for error handling, logs, and security. For API security, perform Threat Modeling to find security vulnerabilities and plan for mitigation of risks. Use generic authentication using SAML, OAuth, and JWT to support Authentication and Authorization. Next, create API Versioning strategy so that the REST API can evolve with minimal client changes. Apply Cloud Native design patterns for Resiliency. In the end, test APIs using contract driven testing and PACT files.

  • We all have seen our share of bad code and some really good code as well. What are some of the common anti patterns that seem to be recurring over and over in code that sucks? By learning about these code smells and avoiding them, we can greatly help make our code better. Come to this talk to learn about some common code smell and how to improve the quality of code.  

    This presentation is sponsored by the No Fluff, Just Stuff / Software Symposium. The next NFJS event in the Boston area is scheduled for March 16 - 18, 2018 in Wakefield. Venkat is on the roster for that event - which is a great way to get more of him and choose from many other top-tier speakers. Plan ahead and allocate that weekend for a great training, growth, and networking event!