All posts by Emmett Walsh

JHipster

A Stack for The Ages – Part 2

JHipster

In the first part of this series we introduced the basics of JHipster – we scaffolded a basic monolithic Java/Angular application and used JHipster’s command line options to generate some entities, services, and web modules for creating, retrieving, updating and deleting those entities. 

Continue reading

AWS Aurora Serverless MySQL Generally Available

As most of us know by now, Serverless computing allows us to build and run applications and services without thinking about servers. Serverless applications don’t require us to provision, scale, and manage any servers.

We can build them for nearly any type of application or backend service, and everything required to run and scale our application with high availability is handled for us. Continue reading

Online Shopping

Online shopping could become more expensive after Supreme Court ruling

Aside from the obvious convenience and choice that e-commerce has always offered, an often overlooked factor in its success in the US over the years has been the fact that sales tax did not have to be collected by a business if they didn’t have a physical presence in the state that they are selling within.

In effect this has led to the majority of online sales being tax-free – great for consumers and great for companies as they did not have to navigate state and local tax codes. Continue reading

‘Node style’ Reactive Java apps with Spring WebFlux

Node.js logoMy last few assignments had taken me away from my relative safety of the JVM and into the topsy turvy world of Node.js for the first time.

It certainly took me a while to get used to things – wrapping my head around the whole non-blocking nature of the Node runtime and how it uses a single thread to process requests – and how important it was that I definitely do not block that thread! Continue reading

REST-less yet ? Try GraphQL

Lets face it, REST can can have its downsides e.g :

  • dealing with a whole bunch of endpoints in a typical application
  • performing multiple roundtrips to the server for multiple resources in order to get data for a single page of the UI
  • getting the request parameters right
  • dealing with api versions – coupling between the client and the responses from the server
  • over-fetching of information that is not needed

Continue reading