Win a copy of Svelte and Sapper in Action this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Re-engineer into Legacy systems from APP-servers ?

 
Ranch Hand
Posts: 123
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Chris !

During the last 15 years a lot Projects has been concentraed on getting programs out of legacy systems to application serves like OAS, WAS etc.

So I ask if time now has come to re-engineer in the opposit direction ?

One good reason could for example be to improve the security.
 
Rancher
Posts: 43016
76
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
How would not running in an app server improve security?
 
Tom Stevns
Ranch Hand
Posts: 123
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Ulf !

What do You mean by

"How would not running in an app server improve security? "
 
Ulf Dittmer
Rancher
Posts: 43016
76
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I mean that I do not understand how moving away from an app server would improve security - something that you mentioned.
 
Author
Posts: 18
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Tom,

Like Ulf, I'm not quite sure how moving away from application server frameworks relates to security. Do you mean because OAS has been discontinued, so it will no longer receive security patches?

In general, I find app server frameworks to be too heavyweight for most use cases. Depending on your app, it's unlikely that you'll need all the features the framework offers. On the other hand, the advantage of such a framework is that a lot of the technologies (the DB access layer, etc.) have been chosen and integrated for you, so you can get started on your project quickly and skip a lot of boilerplate.

Where possible I choose "toolkits" over "frameworks", i.e. you want a more loosely coupled collection of components that you can pick and choose. If a certain component doesn't fit your use case, just swap in a different tool. The loose coupling means that you can upgrade or replace components independently, so you don't suffer the massive lock-in you get with a vendor framework.

Of course, there's always a trade-off between the convenience of "the framework does everything for me" vs the flexibility to customize a toolkit. For web apps, I've had success with Dropwizard (http://dropwizard.io/). I think it gets that balance just right.

As for moving away from an app built with an app framework, I'm afraid it's just like any other monolithic legacy app. You need to find a way to carve it up into independent components, and migrate them away one at a time.
 
I need a new interior decorator. This tiny ad just painted every room in my house purple.
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
    Bookmark Topic Watch Topic
  • New Topic