Things You Should Know
May 16th, 2011
At a lunch discussion we talked about things that every architect and developer should now. Not knowing these will yield the "wtf? Where have you been the last ten years"-response
Just some examples that we talked about
http - foundation of the Internet. You should know pretty well how it works.
Java or C# - If you need to code, you really should be able to do it using one of these two.
SQL - For storing data there’s no excuse not to know SQL.
It’s pretty aparent that anything related to CEP has a long way before it finds its way onto that list.
If CEP is ever on the must-know list, in what form do you think we will talk about required CEP skills?
Categories: Complex Event Processing
Hi Marco, I am not really sure why we have to really differ from what is on the list. It seems that SQL is an ideal programming metaphor for CEP. In our product we have seen a huge acceptance of our SQL approach to streaming queries.
My gut feeling is that these SQL based systems are just the first step and eventually we will discover many more concepts which are much more ideal…