So, as many of you know, I've been working out different ways to host my Oracle labs and demos instances without chewing up phenomenal amounts of disk space and processing power. Lately, I've been diving into Docker.
Docker has turned out to be pretty cool and very easy to learn. And it's lightweight. The idea is that you run containers - your app, your operating system, and your virtual machine - bundled together in a single container. The big win is that containers abstract the operating kernel, so the total overhead of all the container is much, much less than the sum of the parts.
I'm still digging in, so I'll keep you posted as I progress. But it looks pretty promising in terms of fulfilling my non-production needs. One example...
I downloaded and installed the Oracle XE database...with APEX...from scratch in about 22 minutes earlier today. All done with Docker (and because I run OS X, I also use boot2docker).
Game. Set. Match. Pretty easy. Run fast. Low overhead. You may want to check it out.
Showing posts with label #APEX. Show all posts
Showing posts with label #APEX. Show all posts
Tuesday, April 21, 2015
Monday, December 29, 2014
2015 - Less, But Better
Life is really simple, but we insist on making it complicated.
- attributed to Confucius
It's the end of 2014. 2015 is staring us in the face. And as we celebrate the ending of a trip around the sun and kick off yet another one, many of us are predicting what the new year will bring. Sorry, you won't get that here. My crystal ball never has worked all that well, so I don't see much value in sharing my woefully inaccurate predictions.
What I will share is my lone resolution for 2105 and some of the actions I'll be taking as a result, in the hopes that you'll find some value you can apply in your own endeavors.
The motto: Less, But Better. (Yes, I'm a fan of Dieter Rams). The idea is to simplify, eliminating the obtrusive, while improving the end result. Some thoughts on applying this idea.
- attributed to Confucius
It's the end of 2014. 2015 is staring us in the face. And as we celebrate the ending of a trip around the sun and kick off yet another one, many of us are predicting what the new year will bring. Sorry, you won't get that here. My crystal ball never has worked all that well, so I don't see much value in sharing my woefully inaccurate predictions.
What I will share is my lone resolution for 2105 and some of the actions I'll be taking as a result, in the hopes that you'll find some value you can apply in your own endeavors.
The motto: Less, But Better. (Yes, I'm a fan of Dieter Rams). The idea is to simplify, eliminating the obtrusive, while improving the end result. Some thoughts on applying this idea.
- Experience Design: Seems as though everyone is into the Experience Design game these days. User Experience, Customer Experience, Student Experience ... it's a longer list than I'm able to quote here. But I also see that many of these efforts miss the point. Experience Design is not just about things look ... icons, colors, interface layouts. Experience design is about providing simple, elegant solutions to complex problems. I'll be spending calories voicing this point in 2015, especially in terms of how it applies in the world of Oracle software.
- Advocating Oracle Cloud Applications: The big idea behind Oracle Cloud Applications and the SaaS service model is simplification: trade off your in-house maintenance and licensing burdens for a pay-as-you-go service model. Pretty cool in theory. But, from my perspective, we'll still dealing with heavily-engineered products. It's a tough issue for advocates and partners. Among other things, that means I just can't run Oracle's Cloud Applications on my personal test bench anymore. Too many moving parts. Done trying. At the same time, it seems that Oracle is tightening up the accessibility of Oracle Cloud Applications for players in the Oracle eco-system: their own pre-sales consultants and Oracle eco-system partners. Tough even getting access through the Oracle Partner Network without jumping through serious hoops (and you know how I love hoop jumping!). Have to come up with a simple answer for that in 2015. It may come down to running a demo environment of Oracle Cloud Applications on AWS. Or possibly running that demo environment on internal Sierra-Cedar servers. Neither is the simplest approach I can think of, but one or the other may be the simplest approach available.
- More Use Of Simple Oracle Development Tools: In the world of enterprise applications, we sometimes limit ourselves with the tools that we use. We bring out sledgehammers to kill fruit flies. Forcing those sledgehammers to fit our purpose results in solutions that are less than optimal. In the spirit of "Less, But Better", I plan to spend some time researching on ways to use simple tools to extend and enhance enterprise applications - especially Oracle Cloud Applications. Oracle APEX seems to be one of those tools. So my plan is to start there. I also plan to spend more time testing the boundaries of The Oracle Simplified User Interface ("SUI") Rapid Development Kit.
- Extensions and Integration: As more customers jump into Oracle Cloud, functional application implementation is becoming more and more of a fungible commodity service. The lowest price wins the business above all other factors. With this shift in the market and the impact on per project profit margins, implementation partners are beginning to develop strategies of adding value around the edges of an implementation project: extensions and integrations. Those partners who can add simple, elegant extensions and integrations to Oracle Cloud Application implementation projects are the partners who will thrive as the market shifts. This is easier said than done, as many of us in the Oracle eco-system tend to unintentionally sacrifice simplicity by over-engineering our solutions for very specific and unique use cases. I'll be working to reverse that trend in my own work: simple integrations and extensions, applicable to a wide set of use cases, that can be applied repeatedly. I've already mentioned some of the tools I'll use in this effort. This is really about the design of extensions and integrations: simple, elegant solutions to complex problems.
What about you? Any inspiring thoughts from reading this? Or maybe a bit of chortling or laughter? Whatever. Share your thoughts in the comments. And best wishes for a great 2015!
Sunday, September 14, 2014
Simple Solutions Do Not Equal Easy Builds
Am I the only one that often tries to make solutions far more difficult than needed? My first approach to any challenge is likely the most complicated thing I could create. For example, I was working on something with Oracle Apex last week. Came up with what I thought was a nifty new feature and started building. After the equivalent of several hundred lines of code, I had something that worked...just not as well as I hoped.
After sitting back and letting things percolate...with a bit of cussing and fussing...I wound up deleting everything I'd built for that nifty new feature. Replaced it with about two minutes of work. The replacement was probably the equivalent of 25 or 30 lines of code. And now the feature worked exactly as I hoped.
Yeah, I'm pretty sure I could complicate a ball bearing if given the opportunity to go off and running with the first ideas that pop into my head.
My point in all this...simple solutions do not equal easy builds, at least when it comes to building solutions. It takes brain power to refine ideas and initial concepts into simple, elegant solutions.
After sitting back and letting things percolate...with a bit of cussing and fussing...I wound up deleting everything I'd built for that nifty new feature. Replaced it with about two minutes of work. The replacement was probably the equivalent of 25 or 30 lines of code. And now the feature worked exactly as I hoped.
Yeah, I'm pretty sure I could complicate a ball bearing if given the opportunity to go off and running with the first ideas that pop into my head.
My point in all this...simple solutions do not equal easy builds, at least when it comes to building solutions. It takes brain power to refine ideas and initial concepts into simple, elegant solutions.
Thursday, August 21, 2014
Adapt - Learn New Things
Nothing lasts forever. Sand-piles crumble. Companies rise and fall. Relationships change. Markets come and go. It’s just the nature of things. Adapt or die. Personally, I like this feature of life…can’t imagine anything worse than stagnation. There’s nothing better to me than exploring and learning new things.
As Oracle continues their push into cloud-based enterprise applications, we’re seeing some of that fundamental change play out in the partner community; with both partner companies and with the individuals who make up the partners. This is especially true with the technology-based services partners. Companies have merged or faded away. Individuals, many of whom have stellar reputations within the partner and customer communities, have accepted direct employment with Oracle or moved into other technology eco-systems.
Why the big change? Frankly, it’s because the cloud doesn’t leave much room for the traditional offerings of those technology-based services partners. As we shift from on-premise to cloud, the need for those traditional offerings are drying up. Traditional installations, patching, heavy custom development…all those things seem headed the way of the buggy-whip in the enterprise applications space. It’s time to adapt.
As a guy involved in providing services and complimentary products myself, I’ve watched this change unfold over the past few years with more than a little self-interest and excitement - hey, ya gotta pay the bills, right? As a result, I’ve identified three adaptation paths for individuals involved with services in the Oracle technology-based eco-system:
1. Leave. Find another market where your skills transfer well and take the leap. This isn’t a bad option at all, especially if you’ve developed leadership and/or “soft skills”. Believe it or not, there’s a big world outside the Oracle eco-system.
2. Play the long tail. The base of traditional, on-premise work will not disappear over night. It’s shrinking, granted, but it’s a huge base even while shrinking. I also think there will be a big uptick in small, lightweight projects with traditional footprints that will compliment large cloud-based enterprise application systems (for further information, see “Oracle Apex”).
3. Learn new things. Apply your background to build skills in new technologies. If you’re an Oracle DBA or systems administrator (two skillets that are rapidly merging into one), dig into Oracle Enterprise Manager…and remember that private clouds will continue to flourish with Oracle’s larger customers. If you’re a developer, begin building skills in middle-tier integration - connecting cloud offerings in new and creative ways is very much an in-demand skill. Or get smart with building light-weight complimentary applications (ADF, BPM, SOA) - especially mobile (MAF). If you’re a business analyst or functional type, get familiar with Functional Setup Manager and the Oracle Composers. Maybe get a solid understanding of User Experience and how you can apply UX in your job. As a solution architect, I’ve spent a great deal of time learning how the various Oracle Cloud solutions work together from data, integration, business process, and information perspectives…and if I can do it, so can you!
Obviously, my approach has been to explore and learn new things relevant to the market changes. The opportunities I saw for myself consisted of connecting things together and adding value around the edges. It’s been a hoot so far and I’m nowhere near done yet. YMMV.
With Oracle OpenWorld coming up as a huge opportunity to learn new things, it seemed timely to share these thoughts now. So there you have it. My worm’s eye view of how the Oracle partner market (or at least the Oracle technology-based services partner market) is changing. Maybe I nailed it. Maybe I’m all wet. Either way, let me know what you think.
With Oracle OpenWorld coming up as a huge opportunity to learn new things, it seemed timely to share these thoughts now. So there you have it. My worm’s eye view of how the Oracle partner market (or at least the Oracle technology-based services partner market) is changing. Maybe I nailed it. Maybe I’m all wet. Either way, let me know what you think.
Subscribe to:
Posts (Atom)
