Showing posts with label architecture. Show all posts
Showing posts with label architecture. Show all posts

Thursday, October 31, 2013

5 Tips for Big Software Projects

Software development isn't easy.  And the bigger the software gets, the harder it is to build right from the ground up.  A string of high-profile failures has given us a timely reminder of this.  But it's not hopeless -- here are five things to consider to bump the odds in your favor:

1. Great software is never built on a poor architecture

The only way to build a large project is to divide and conquer.  But ten teams working in ten different ways will just produce ten times the mess.  The bigger a project gets, the more important it is to build on the best architecture and tools, modularizing where it makes sense without simply introducing more discrepancies and more complexity.  And the more people working on top of an architecture, the more important that it doesn't introduce obstacles that every developer may find different ways to avoid.

2. Generated code is terrible

Many situations land programmers with large amounts of tedious boilerplate code.  The gut reaction is to code-generate your way past it.  But if you think a junior programmer writes bad code, you should see a programmer try to program a computer to program.  It's just as convoluted as it sounds.  Worse, it has to be done over and over again, and it's one way to guarantee that some large chunk of code is rarely up to date.  Whether it's persistence or XML or other boilerplate code, there's a different set of tools that will eliminate the tedium with better code instead of worse code.

3. Best practices aren't always best

If you want to be really cruel, you can write terrible code that adheres to multiple best practices, and just watch an architect splutter.  The problem is that many individual best practices don't make sense when used outside of their associated tools and frameworks, or when used in combination, or when otherwise taken out of context.  Part of what makes experienced programmers better is that they can review all the tools and practices at their disposal, and use their judgement to select the right combination.

4. Software without automated tests is just a pile of code

A large project is built, never adequately tested, and rushed into production.  It doesn't work well.  Why is this a surprise?  But testing is also tedious, and requires a whole additional staff.  That is, if you don't automate it from the beginning.  Your computer is perfectly capable of driving an application with simulated load, an actual Web browser, or real-world integration requests.  There's no reason not to build a comprehensive automated test suite to ensure the software operates as intended.  And the more people who have their hands in the code, the more important it gets.

5. Integration begins with testing

Projects with many integration points tend to have a large number of interested parties, many of whom may be developing their parts of the system in parallel.  Then everybody finishes, and guess what?  It doesn't all work together.  But there's an easy way to avoid that.  If everybody starts by providing simulated requests and replies then testing can begin immediately, and each group can phase in real implementations over time.  Each system gets immediate feedback as to whether anything's breaking, and there's much less debugging required to fix a small change from a working state.

Tuesday, January 18, 2011

Enterprise Integration with Spring Training

Are you a Spring Developer?

Do you have Enterprise solutions to develop or architect?



Chariot Solutions, a Spring Training Partner and Philadelphia leader in Spring Training, Mentoring and Consulting can help you take your Spring skills to the next level - Enterprise Integration!

There are many Spring developers who have learned by experimenting, reading documentation and maybe code dives into an existing application or two. But with the knowledge you gain from Official SpringSource training at Chariot from our certified SpringSource instructors, you can be more equipped to chose the right tools for your complex integration solutions.

The Enterprise Integration with Spring (EIwS) course is not only extremely valuable to any Spring developer it should be REQUIRED for anyone architecting Spring applications.

What is cool in the EIwS course?

  • Synchronous & Asynchronous Processing
  • Messaging with Enterprise Integration Patterns
  • Messaging with JMS
  • Exposing Services with RMI, HTTP
  • Web Services with SOAP, REST and WS Security - and why REST is cool!
  • Spring Local and Distributed Transaction Management - JTA/XA - Open Source distributed transactions without a JEE Server
  • Service Integration with SMTP (email), File, JMS, FTP, JDBC, TCP/UDP, XMPP, etc.
  • Polling and Triggering
  • Tasks and Scheduling of Processes
  • Message Filtering, Routing, Transformation, Splitting, Aggregating, Bridging and Chaining
  • Creating Batch processes for inline or offline execution
  • Monitoring Batch process exceptions
  • Unit and Mock testing of application layers
  • Modifying Integration processes without recompiling... AWESOME Right?


One of the key take-aways from this course is knowing which tools are available to choose from and why.

What does Gordon teach?

When I teach the Core or EIwS classes, I go through the common Spring project application layers, and their respective roles and responsibilities. We discuss the tools you have within Spring and which to use to solve integration concerns. In EIwS, the course builds from common concurrency, tasks & scheduling, Messaging with JMS to the flexible power of Spring Integration and Spring Batch tool sets. I teach layering your applications focussing on the power and flexibility of Service POJOs exposing your processes in a Service Oriented Architecture (SOA) manner and keeping your POJOs - Pure business objects, un-compromised by framework or infrastructure java objects.

I am teaching EIwS February 22-25, 2010 in Philadelphia! If you come you will receive:
  • A shiny new course book
  • An Official Spring USB thumb drive with SpringSource Tool Suite, Course Documentation PDF, all the labs & solutions
  • The secret meaning of the acronym "SOA"
  • Bad humor from your instructor (if I teach you can count on it)
  • Demo's that Gordon creates (if taking my class)
  • Lunch, Coffee, Tea & soft drinks


Q&A


Q: What if I have not taken the Core Spring course?
A: It is highly recommended that you attend the Core Spring Course first. Click here to see the Course Schedule

Q: What if I am not using Spring 3 yet?
A: No problem, although the course focuses on 3.0 features, you will still get usable information for your applications.

Q: What will I learn?
A: Scroll up.

Q: What if I already have used some of the topics covered?
A: Relax during those chapters or, even better, provide your "in the trenches" experience with the class.

Q: How can I get management to pay for the class?
A: This course is Essential to my skills, to provide you with better tools to choose the right approach to solving our complex integration needs. Check Here for possible Early Bird Discounts.

Q: Where do I find out about the Enterprise Integration course?
A: Click here for SpringSource Training Site

Q: When is Gordon teaching the class?
A: Click here for the next scheduled course on February 22, 2011

Q: Is there certification for Enterprise Integration Specialist?
A: Check here for the status on Enterprise Integration Specialist Certification

Memorable Quotes:


  • "Wow, I just learned in 5 minutes what it took me 2 weeks to do in the past"
  • "A Spring Developer without
  • "Understanding the layered design of Spring applications really helps me best architect my solutions."
  • "I really needed to provide file processing into my database, glad I took this class for those implementation discussions"


So, what are you waiting for? Register NOW for Enterprise Integration with Spring!